Command line tool to deposit an RO-Crate to an InvenioRDM repository.
Originally developed (up to v1.0.2) as ro-crates-deposit by Philipp Beer and Milan Szente.
Python 3.8.1or higher
Install from PyPI using pip or your preferred package manager:
pip install rocrate-inveniordm
- Register for an account on your chosen InvenioRDM instance. Zenodo Sandbox can be used for testing.
- Go to your profile and select Applications.
- You should see a section called "Personal access tokens." Click the "New token" button.
- Give the token a name that reminds you of what you're using it for (e.g. RO-Crate upload token)
- Select the scopes deposit:write and deposit:actions.
- Click "Create."
- Copy the access token and continue with the next stage.
The package requires two environment variables to be set:
INVENIORDM_BASE_URL– the URL of your preferred InvenioRDM instance, e.g."https://sandbox.zenodo.org/"INVENIORDM_API_KEY– the API token you created in the section above.
Run the following lines to set the environment variables:
export INVENIORDM_BASE_URL="your_preferred_instance_url"
export INVENIORDM_API_KEY="your_api_key"You can also add the lines to your ~/.bashrc file so that they are set whenever you start a shell, if you plan to use the package regularly.
If you want to change your target InvenioRDM instance, you can set the environment variables again using the same code.
Run rocrate_inveniordm <ro-crate-dir> with <ro-crate-dir> being the path to the RO-Crate directory. This will upload the record (including files and metadata) as a draft to your chosen InvenioRDM instance, and save the generated DataCite metadata as datacite-out.json in the current directory.
By default, the record is not published after upload. You can publish the record through the web interface of your chosen instance, or you can instead run the same command with the -p option to re-upload the crate into a new record and publish it immediately.
Some repositories use a "flat" structure for records, where all the files are stored in the root of the archive and there is no directory structure. To preserve a directory structure, which can be important for the RO-Crate metadata file to be accurate, you can upload the crate as a single zip file instead – this can be achieved with the -z option (you do not need to pre-zip your crate). For example,
rocrate_inveniordm -z test-ro-crate
will result in an uploaded file called test-ro-crate.zip.
This tool is a best-effort approach. After converting the metadata file, the resulting DataCite file is stored as datacite-out.json in the root directory. You can adjust the generated DataCite file as needed, and can run the program in two stages to facilitate this:
First, run the program with the --no-upload option, to create the DataCite file in the current directory without uploading anything to InvenioRDM:
rocrate_inveniordm --no-upload <ro-crate-dir>.
After verifying and adjusting the DataCite file, use the -d option to tell the program to use this file for upload and skip the process of conversion:
rocrate_inveniordm -d <datacite-file> <ro-crate-dir>.
Additional options can be found by running rocrate_inveniordm --help.
The project aims at decoupling the definition of the mapping between RO-Crates and DataCite from code. This means, that users can quickly change/add/remove mapping rules without code changes.
To find out how each piece of RO-Crate metadata is converted to DataCite, see How RO-Crate metadata is mapped to DataCite.
For technical details on the implementation, see Mapping.
The result of uploading the minimal RO-Crate as shown on https://www.researchobject.org/ro-crate/1.1/root-data-entity.html#minimal-example-of-ro-crate (/test/minimal-ro-crate) leads to the following result:
The result of uploading the /test/test-ro-crate directory looks like this in TUW's InvenioRDM repository:
We tested the tool on a real-world RO-Crate (https://reliance.rohub.org/b927e3d8-5bfd-4332-b14c-ab3a07d36dc6?activetab=overview). The result is shown below:
