You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Signposting Output Now Contains Links to All Dataset Metadata Export Formats
2
+
3
+
When Signposting was added in Dataverse 5.14 (#8981), it only provided links for the `schema.org` metadata export format.
4
+
5
+
The output of HEAD, GET, and the Signposting "linkset" API have all been updated to include links to all available dataset metadata export formats (including any external exporters, such as Croissant, that have been enabled).
6
+
7
+
This provides a lightweight machine-readable way to first retrieve a list of links (via a HTTP HEAD request, for example) to each available metadata export format and then follow up with a request for the export format of interest.
8
+
9
+
In addition, the content type for the `schema.org` dataset metadata export format has been corrected. It was `application/json` and now it is `application/ld+json`.
10
+
11
+
See also [the docs](https://preview.guides.gdcc.io/en/develop/api/native-api.html#retrieve-signposting-information) and #10542.
Copy file name to clipboardExpand all lines: doc/sphinx-guides/source/admin/discoverability.rst
+1-1
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ The Dataverse team has been working with Google on both formats. Google has `ind
51
51
Signposting
52
52
+++++++++++
53
53
54
-
The Dataverse software supports `Signposting <https://signposting.org>`_. This allows machines to request more information about a dataset through the `Link <https://tools.ietf.org/html/rfc5988>`_ HTTP header.
54
+
The Dataverse software supports `Signposting <https://signposting.org>`_. This allows machines to request more information about a dataset through the `Link <https://tools.ietf.org/html/rfc5988>`_ HTTP header. Links to all enabled metadata export formats are given. See :ref:`metadata-export-formats` for a list.
55
55
56
56
There are 2 Signposting profile levels, level 1 and level 2. In this implementation,
57
57
* Level 1 links are shown `as recommended <https://signposting.org/FAIR/>`_ in the "Link"
Copy file name to clipboardExpand all lines: doc/sphinx-guides/source/api/changelog.rst
+1
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,7 @@ v6.6
12
12
13
13
- **/api/metadatablocks** is no longer returning duplicated metadata properties and does not omit metadata properties when called.
14
14
- **/api/roles**: :ref:`show-role` now properly returns 403 Forbidden instead of 401 Unauthorized when you pass a working API token that doesn't have the right permission.
15
+
- The content type for the ``schema.org`` dataset metadata export format has been corrected. It was ``application/json`` and now it is ``application/ld+json``. See also :ref:`export-dataset-metadata-api`.
.. note:: Supported exporters (export formats) are ``ddi``, ``oai_ddi``, ``dcterms``, ``oai_dc``, ``schema.org`` , ``OAI_ORE`` , ``Datacite``, ``oai_datacite`` and ``dataverse_json``. Descriptive names can be found under :ref:`metadata-export-formats` in the User Guide.
1596
+
.. _available-exporters:
1597
+
1598
+
Available Dataset Metadata Exporters
1599
+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1600
+
1601
+
The following dataset metadata exporters ship with Dataverse:
1602
+
1603
+
- ``Datacite``
1604
+
- ``dataverse_json``
1605
+
- ``dcterms``
1606
+
- ``ddi``
1607
+
- ``oai_datacite``
1608
+
- ``oai_dc``
1609
+
- ``oai_ddi``
1610
+
- ``OAI_ORE``
1611
+
- ``schema.org``
1612
+
1613
+
These are the strings to pass as ``$METADATA_FORMAT`` in the examples above. Descriptive names for each format can be found under :ref:`metadata-export-formats` in the User Guide.
1614
+
1615
+
Additional exporters can be enabled, as described under :ref:`external-exporters` in the Installation Guide. The machine-readable name/identifier for each external exporter can be found under :ref:`inventory-of-external-exporters`. If you are interested in creating your own exporter, see :doc:`/developers/metadataexport`.
1616
+
1617
+
To discover the machine-readable name of exporters (e.g. ``ddi``) that have been enabled on the installation of Dataverse you are using see :ref:`get-export-formats`. Alternatively, you can use the Signposting "linkset" API documented under :ref:`signposting-api`.
1595
1618
1596
-
.. note:: Additional exporters can be enabled, as described under :ref:`external-exporters` in the Installation Guide. To discover the machine-readable name of each exporter (e.g. ``ddi``), check :ref:`inventory-of-external-exporters` or ``getFormatName`` in the exporter's source code.
1619
+
To discover the machine-readable name of exporters generally, check :ref:`inventory-of-external-exporters` or ``getFormatName`` in the exporter's source code.
1597
1620
1598
1621
Schema.org JSON-LD
1599
1622
^^^^^^^^^^^^^^^^^^
@@ -1607,6 +1630,8 @@ Both forms are valid according to Google's Structured Data Testing Tool at https
1607
1630
1608
1631
The standard has further evolved into a format called Croissant. For details, see :ref:`schema.org-head` in the Admin Guide.
1609
1632
1633
+
The ``schema.org`` format changed after Dataverse 6.4 as well. Previously its content type was "application/json" but now it is "application/ld+json".
1634
+
1610
1635
List Files in a Dataset
1611
1636
~~~~~~~~~~~~~~~~~~~~~~~
1612
1637
@@ -3174,15 +3199,23 @@ Retrieve Signposting Information
3174
3199
Dataverse supports :ref:`discovery-sign-posting` as a discovery mechanism.
3175
3200
Signposting involves the addition of a `Link <https://tools.ietf.org/html/rfc5988>`__ HTTP header providing summary information on GET and HEAD requests to retrieve the dataset page and a separate /linkset API call to retrieve additional information.
3176
3201
3177
-
Here is an example of a "Link" header:
3202
+
Signposting Link HTTP Header
3203
+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3204
+
3205
+
Here is an example of a HTTP "Link" header from a GET or HEAD request for a dataset landing page:
The URL for linkset information is discoverable under the ``rel="linkset";type="application/linkset+json`` entry in the "Link" header, such as in the example above.
3209
+
The URL for linkset information (described below) is discoverable under the ``rel="linkset";type="application/linkset+json`` entry in the "Link" header, such as in the example above.
3210
+
3211
+
Signposting Linkset API Endpoint
3212
+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3182
3213
3183
3214
The reponse includes a JSON object conforming to the `Signposting <https://signposting.org>`__ specification. As part of this conformance, unlike most Dataverse API responses, the output is not wrapped in a ``{"status":"OK","data":{`` object.
3184
3215
Signposting is not supported for draft dataset versions.
3185
3216
3217
+
Like :ref:`get-export-formats`, this API can be used to get URLs to dataset metadata export formats, but with URLs for the dataset in question.
3218
+
3186
3219
.. code-block:: bash
3187
3220
3188
3221
export SERVER_URL=https://demo.dataverse.org
@@ -5182,12 +5215,14 @@ The fully expanded example above (without environment variables) looks like this
Get the available export formats, including custom formats.
5223
+
Get the available dataset metadata export formats, including formats from external exporters (see :ref:`available-exporters`).
5189
5224
5190
-
The response contains an object with available format names as keys, and as values an object with the following properties:
5225
+
The response contains a JSON object with the available format names as keys (these can be passed to :ref:`export-dataset-metadata-api`), and values as objects with the following properties:
Copy file name to clipboardExpand all lines: doc/sphinx-guides/source/user/dataset-management.rst
+2
Original file line number
Diff line number
Diff line change
@@ -43,6 +43,8 @@ Additional formats can be enabled. See :ref:`inventory-of-external-exporters` in
43
43
44
44
Each of these metadata exports contains the metadata of the most recently published version of the dataset.
45
45
46
+
For each dataset, links to each enabled metadata format are available programmatically via Signposting. For details, see :ref:`discovery-sign-posting` in the Admin Guide and :ref:`signposting-api` in the API Guide.
0 commit comments