Three options for connecting content

There are three possible scenarios for opening up your content on the OpenMinTeD platform as shown in the following picture:

Option 1. Offer content* via Open Access infrastructures

OpenMinTeD is cooperating with OpenAIRE, an EU/global open science infrastructure, and a UK/global aggregator CORE who provide access to scholarly works.

As providers of scholarly publications (e.g., institutional or thematic repositories and open access journals or publishers) you have the option to register with either OpenAIRE or CORE, and in doing so your content will be automatically available to OpenMinTeD.

For this to happen, please take the following steps:

  1. Register your repository with an authoritative registry (e.g. OpenDOAR).
  2. Align your metadata with the OpenAIRE Guidelines or CORE guides.
  3. Offer the publication full-texts with a license that allows both the redistribution and text mining of the content for at least research purposes**, and
  4. Expose metadata using OAI-PMH or ResourceSync.

OpenMinTeD will store the publications, index their metadata and make them available to end users for TDM.

For more information about this option, see the OpenMinTeD guidelines.

For support visit the OpenMinTeD support page.

(*) Content in OpenMinTeD is about scholarly works, i.e., publications, conference proceedings, books, grey literature, etc.

(**) For example: CC0, CC-BY 4.0CC BY-SA 4.0

Option 2. Provide content directly to OpenMinTeD

This option allows you to share your scholarly content by creating a corpus and uploading it directly to OpenMinTeD. In order to do so, please take the following steps:

  1. Describe each publication using the OMTD-SHARE metadata schema.
  2. Ensure that you specify a license that allows both the redistribution and text mining for each publication*.
  3. Describe your corpus (i.e., the collection of publications) using the OMTD-SHARE metadata for corpus.
  4. Create a zip file with the publications (metadata and full-text) along with the corpus metadata and deliver** to OpenMinTeD.

OpenMinTeD will store the publications, index their metadata and make them available to end users for TDM.

(*) For example: CC0CC-BY 4.0CC BY-SA 4.0

(**) The actual method of delivery will be decided when later, during the call, but it will consist of either uploading the file in an ftp server or providing the OpenMinTeD team with a link to the zip file.

Option 3. Offer access to content via the OpenMinTeD APIs

OpenMinTeD has published the OMTD Content-Connector-API service specification, which, when running at your site allows OpenMinTeD to fetch content (metadata and full-text) on demand.

The OMTD Content-Connector-API performs the following tasks:

  • queries your metadata
  • bulk download the metadata of a query results,
  • selectively downloads the resulting publication full-texts.

Currently, this API is implemented and used by OpenAIRE and CORE to allow OpenMinTeD access to their content (see option 1).

A few things to note when implementing this solution:

  1. The schema of the metadata of the publications must conform to the OMTD-SHARE schema.
  2. As with the previous two options, the metadata of each publication must be accompanied by a license that allows both the redistribution and text mining of the content*.
  3. OpenMinTeD is imposing the least possible load on the providers’ servers by
    1. not prefetching any publications until they are requested by users,
    2. caching full-texts to avoid requesting a publication more than once.

The API is specified and implemented in Java, which means that any implementations of this API must be executed within the OpenMinTeD platform. For this reason, all possible implementations will be thoroughly tested to ensure that they work adequately well both in terms of performance and accuracy of results. The source code of the implementation must be made available to OpenMinTeD to ensure that it poses no threat to the stability of the platform.

An alternative specification (currently scheduled for the end of October 2017) will provide a REST API, with exactly the same methods and functionality as its Java counterpart. This REST API will allow providers to implement their connectors in the platform and programming language of their choice, while maintaining an independent source code base.

(**) For example: CC0CC-BY 4.0CC BY-SA 4.0

Additional documentation and support

For any additional information and support, please visit the OpenMinTeD support page, where you will be able to post your questions and get answers from the OpenMinTeD team.