markup for repository landing pages is a set of schemas for structured data on the Internet, on web pages, in email messages, and for search engines to coordinate on metadata for indexing the web.

DataCite metadata can be expressed in format and can be used on repository landing pages. DataCite recommends adding to repository landing pages to expose them to Google Dataset Search. For more information on exposing your datasets to Google Dataset Search, see Google's help page on the Dataset content type.

How do I create the markup for my repository landing pages?

There are two ways to do this: 1. manually implementing this in the repository pages, or 2. automating the process using the DataCite Content negotiation service.

  1. DataCite has published a crosswalk which maps DataCite metadata schema 4.4 to to help with manually implementing on repository landing pages.


DataCite Metadata Schema 4.4 to Mapping

Here is a full crosswalk from the DataCite Metadata Schema to

  1. The DataCite Content Negotiation service is also available to enable automated embedding metadata on repository landing pages.


DataCite Content Negotiation for metadata

DataCite Content Negotiation can be used to retrieve metadata to embed in landing pages.

For example, you can include this Javascript file that will return metadata in markup dynamically through DataCite Content Negotiation. Add a <script> tag with the file to the script to your landing page template. Whenever a landing page is requested, the script will append the appropriately marked up metadata in markup.

An example of a repository page using markup can be found here:

If you’re not sure whether your repository landing pages contain the appropriate structured data, you can test them using Google’s Structured Data Testing Tool.