Best practice | URL validity

The deposits client | Initialising a deposits client | Metadata | Passing metadata to a deposits client | Creating a new deposit | Retrieving deposits | Uploading files to deposits | Pre-generating frictionless metadata files prior to upload | Editing and updating deposits | Example workflow | Publishing a deposit

Explicit version control | Services without explicit version control

Generating "datapackage.json" files | Generation by uploading files | Local generation | Reading and editing "datapackage.json" files | Updating "datapackage.json" on deposits service

R6 methods | Initialising a deposits client | The R6 client structure

Installation | Setup: API Tokens

Initial Metadata | Preparing data sources | Frictionless metadata | Initiating a remote deposit | Uploading files to a remote deposit | File compression | Editing and updating files | Publishing a deposit

Dublin Core Metadata | Metadata Validation | Metadata to specify connections between deposits | Metadata templates | Valid JSON Files | Metadata and the deposits frictionless workflow

Scope | Background | How datastorr works | The package interface | Worked example | Access control | Semantic versioning of data | Beyond GitHub | How it actually works