How to share content directly to OpenMinTeD
If you are a publisher or a repository, archive, etc. of scholarly works and wish to share your content directly to the OpenMinTeD platform instead of following the procedure through aggregators, you can do so if you implement the following:
- Map the metadata of your contents to the OMTD-SHARE schema
- Provide search capabilities on the metadata, according to the specifications of the ContentConnector described below
- Provide the actual content (i.e. the full text).
Minimum requirements for single documents (publications)
For each publication, you must
- ensure that you adhere to the minimal level of the OpenMinTeD Interoperability specifications,
- provide access to a file with the full text
- deliver a metadata description with a minimal set of metadata elements in compliance with the OMTD-SHARE schema for publications in XML format; the metadata elements are used for creating uniform facets for querying the entire set of publications uploaded in OpenMinTeD (see here for more information on the deployment of publications in OpenMinTeD).
How to connect to OpenMinTeD
You must implement a Java interface, called ContentConnector, according to the instructions found at https://github.com/openminted/content-connector-api. Through this interface, your contents will be integrated in the OpenMinTeD platform.
- querying for specific metadata elements and retrieving their values with statistical information (e.g. number of records satisfying the query criteria),
- retrieval of the metadata themselves in XML format
- retrieval of the full texts of the pulications.
Additional technical information is provided in the Java code of the interface.
For more information and/or to notify us of your connector, you can contact us.
1. The OpenAIRE schema and guidelines are currently under revision; collaboration with the relevant actors has been established to take into account the new features and, where desired, influence the changes so as to support TDM processes in accordance to the interoperability requirements. ↩