Skip to content

Commit 907383e

Browse files
pdurbinofahimIQSS
andauthored
doc tweaks #11001
Co-authored-by: Omer Fahim <mfahim11427@gmail.com>
1 parent b5fffaa commit 907383e

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

doc/sphinx-guides/source/api/native-api.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3486,11 +3486,11 @@ The fully expanded example above (without environment variables) looks like this
34863486
Link Dataset Type with Metadata Blocks
34873487
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
34883488
3489-
Linking a dataset type with one or more metadata blocks results in additional fields from those blocks appearing in the output from the :ref:`list-metadata-blocks-for-a-collection` API endpoint. The new frontend for Dataverse (https://github.com/IQSS/dataverse-frontend) uses the JSON output from this API endpoint to construct the page that users see when creating or editing a dataset. Once the frontend has been updated to pass in the dataset type (https://github.com/IQSS/dataverse-client-javascript/issues/210), specifying a dataset type in this way can be an alternative way to display additional metadata fields than the traditional method, which is to enabled a metadata block at the collection level (see :ref:`define-metadata-blocks-for-a-dataverse-collection`).
3489+
Linking a dataset type with one or more metadata blocks results in additional fields from those blocks appearing in the output from the :ref:`list-metadata-blocks-for-a-collection` API endpoint. The new frontend for Dataverse (https://github.com/IQSS/dataverse-frontend) uses the JSON output from this API endpoint to construct the page that users see when creating or editing a dataset. Once the frontend has been updated to pass in the dataset type (https://github.com/IQSS/dataverse-client-javascript/issues/210), specifying a dataset type in this way can be an alternative way to display additional metadata fields than the traditional method, which is to enable a metadata block at the collection level (see :ref:`define-metadata-blocks-for-a-dataverse-collection`).
34903490
3491-
For example, a superuser could create a type called "software" and link it to the "CodeMeta" metadata block (this example is below). Then, once the new front end allows it, the user can specify that they want to create a dataset of type software and see the additional metadata fields from the CodeMeta block when creating or editing their dataset.
3491+
For example, a superuser could create a type called "software" and link it to the "CodeMeta" metadata block (this example is below). Then, once the new frontend allows it, the user can specify that they want to create a dataset of type software and see the additional metadata fields from the CodeMeta block when creating or editing their dataset.
34923492
3493-
This API endpoint is superuser only.
3493+
This API endpoint is for superusers only.
34943494
34953495
.. code-block:: bash
34963496

0 commit comments

Comments
 (0)