Datasets are made discoverable by a variety of methods.
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 :DoiProvider in the Installation Guide.
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.
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.
The HTML source of a dataset landing page includes Schema.org JSON-LD metadata like this:
- 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
Note: Authors without author link will not be counted nor shown in any profile/linkset. The following configuration options are available:
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.
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.
See Discoverability in the Integrations section for additional discovery methods you can enable.