Deposit Services
The Deposit Services are independent third party services responsible to provide a place to store and validate data objects (in our case plans). They are used as a source of trust and provide a unique key / signature (called DOIs or Data Object Identifiers) for every data entity deposited to them.
These are the currently services implemented and integrated.
| Service | Supported Version(s) | Docker Image | Notes |
|---|---|---|---|
| Zenodo | InvenioRDM v12.0 | repository-deposit-zenodo | OAuth 2.0 or personal access token. See the semantics reference. |
| DSpace | 8.x | repository-deposit-dspace | Username/password authentication. See the semantics reference. |
| CKAN | 2.11.4 | repository-deposit-ckan | Access token authentication. See the semantics reference. |
| Dataverse | 6.9 | repository-deposit-dataverse | Access token authentication. See the semantics reference. |
| Fedora | 6.x | repository-deposit-fedora | Username/password authentication. See the semantics reference. |
note
You can create your own deposit source. More details here.
Plugin Semantics Reference
Every deposit plugin maps plan and description fields to target-repository metadata fields by matching each field's semantic tag. The following pages document, for each plugin, which repository field is populated by which semantic:
- Zenodo — semantics reference
- DSpace — semantics reference
- CKAN — semantics reference
- Dataverse — semantics reference
- Fedora — semantics reference
See Also
- Deposit Service Configuration - Environment variable reference for deploying deposit services