Add your own Repository

If you like to add your (institutional) repository, please get in contact with us. On this page we offer you some information about our services and what has to be done on your side.

Currently we work on implementations for EPrints, MyCore and DSpace.

Deposition Protocol

Currently we support the SWORDv2 protocol. However, this protocol offers a lot of options about how to deposit and how to organize the metadata and should be seen as a framework. Technically we can offer different depositing methods, e.g. via some REST API or similar.

Metadata

We use the Metdata Encoding & Transmission Standard (METS) to ship our metadata and describe what is delivered. Most repositories are able to ingest a METS-package.

Bibliographic Metadata

Most of our data comes from CrossRef and has thus a certain quality.

We offer two main formats for our bibliographic data: Dublin Core (DC) and Metadata Objects Description Data (MODS).

Non-Bibliographic Metadata

In addition to our bibliographic metadata we ship non-bibliographic metadata. This metadata is meant to support publication workflows in institutional repositories, for example helping in the moderation process.

We ship the following data:

Data Explanation
authentication method The method of authentication. This is currently shibboleth and orcid.
name The first and last name of the depositor. Note that the depositor does not need to be a contributor of the publication.
email E-Mail address of the depositor in case you need to contact them.
orcid ORCID if the depositor has one.
is contributor true/false and states if the depositor is one of the contributors or if deposits on behalf
identical institution true/false and states if the depositors institution is identical with the institution of the repository.
license The license. Most likely Creative Commons, but different licenses are possible. We happily add new licenses for your repository. We deliver the name and if existing URI and short name like CC BY 4.0.
SHERPA/RomeoID ID of the journal from SHERPA/RoMEO. Using their API or web interface you can quickly obtain publishers conditions.
DisseminID This ID refers to the publication in Dissemin. This ID is not persistent. The reason is the internal data model: Merging and unmerging papers might create or delete primary keys in the database. For a ‘short’ period of time, this id will definetely be valid. You can use the DOI shipped in the bibliographic metadata to get back to the publication in Dissemin.

If you need more information for your workflow, please contact us. We can add additional fields.

You can find our schema for download in Version 1.0.