Discoverability

Datasets are made discoverable by a variety of methods.

DataCite Integration

If you are using DataCite as your DOI provider, when datasets are published, metadata is pushed to DataCite, where it can be searched. For more information, see Legacy Single PID Provider: :DoiProvider in the Installation Guide.

OAI-PMH (Harvesting)

The Dataverse software supports a protocol called OAI-PMH that facilitates harvesting dataset metadata from one system into another. For details on harvesting, see the Managing Harvesting Server and Sets section.

Machine-Readable Metadata on Dataset Landing Pages

As recommended in A Data Citation Roadmap for Scholarly Data Repositories, the Dataverse software embeds metadata on dataset landing pages in a variety of machine-readable ways.

Dublin Core HTML Meta Tags

The HTML source of a dataset landing page includes “DC” (Dublin Core) <meta> tags such as the following:

<meta name="DC.identifier" content="..."
<meta name="DC.type" content="Dataset"
<meta name="DC.title" content="..."

Schema.org JSON-LD/Croissant Metadata

The <head> of the HTML source of a dataset landing page includes Schema.org JSON-LD metadata like this:

<script type="application/ld+json">{"@context":"http://schema.org","@type":"Dataset","@id":"https://doi.org/...

If you enable the Croissant metadata export format (see External Metadata Exporters) the <head> will show Croissant metadata instead. It looks similar, but you should see "cr": "http://mlcommons.org/croissant/" in the output.

For backward compatibility, if you enable Croissant, the older Schema.org JSON-LD format (schema.org in the API) will still be available from both the web interface (see Supported Metadata Export Formats) and the API (see Export Metadata of a Dataset in Various Formats).

The Dataverse team has been working with Google on both formats. Google has indicated that for Google Dataset Search (the main reason we started adding this extra metadata in the <head> of dataset pages), Croissant is the successor to the older format.

Signposting

The Dataverse software supports Signposting. This allows machines to request more information about a dataset through the Link HTTP header.

There are 2 Signposting profile levels, level 1 and level 2. In this implementation,

  • Level 1 links are shown as recommended in the “Link” HTTP header, which can be fetched by sending an HTTP HEAD request, e.g. curl -I https://demo.dataverse.org/dataset.xhtml?persistentId=doi:10.5072/FK2/KPY4ZC. The number of author and file links in the level 1 header can be configured as described below.

  • The level 2 linkset can be fetched by visiting the dedicated linkset page for that artifact. The link can be seen in level 1 links with key name rel="linkset".

Note: Authors without author link will not be counted nor shown in any profile/linkset. The following configuration options are available:

  • dataverse.signposting.level1-author-limit

    Sets the max number of authors to be shown in level 1 profile. If the number of authors (with identifier URLs) exceeds this value, no author links will be shown in level 1 profile. The default is 5.

  • dataverse.signposting.level1-item-limit

    Sets the max number of items/files which will be shown in level 1 profile. Datasets with too many files will not show any file links in level 1 profile. They will be shown in level 2 linkset only. The default is 5.

See also Retrieve Signposting Information in the API Guide.

Additional Discoverability Through Integrations

See Discoverability in the Integrations section for additional discovery methods you can enable.