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
Enhanced JSON schema validation with checks for required and allowed child objects, type checking for field types including `primitive`, `compound` and `controlledVocabulary`. More user-friendly error messages to help pinpoint the issues in the dataset JSON. See [Retrieve a Dataset JSON Schema for a Collection](https://guides.dataverse.org/en/6.3/api/native-api.html#retrieve-a-dataset-json-schema-for-a-collection) in the API Guide and PR #10543.
New optional query parameter "returnDetails" added to "dataverses/{identifier}/facets/" endpoint to include detailed information of each DataverseFacet.
2
+
3
+
New endpoint "datasetfields/facetables" that lists all facetable dataset fields defined in the installation.
### Pre-Publish File DOI Reservation with DataCite
4
+
5
+
Dataverse installations using DataCite (or other persistent identifier (PID) Providers that support reserving PIDs) will be able to reserve PIDs for files when they are uploaded (rather than at publication time). Note that reserving file DOIs can slow uploads with large numbers of files so administrators may need to adjust timeouts (specifically any Apache "``ProxyPass / ajp://localhost:8009/ timeout=``" setting in the recommended Dataverse configuration).
6
+
7
+
## Major Use Cases
8
+
9
+
- Users will have DOIs/PIDs reserved for their files as part of file upload instead of at publication time. (Issue #7068, PR #7334)
By default, this endpoint will return an array including the facet names. If more detailed information is needed, we can set the query parameter ``returnDetails`` to ``true``, which will return the display name and id in addition to the name for each facet:
@@ -566,9 +582,7 @@ The fully expanded example above (without environment variables) looks like this
566
582
Retrieve a Dataset JSON Schema for a Collection
567
583
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
568
584
569
-
Retrieves a JSON schema customized for a given collection in order to validate a dataset JSON file prior to creating the dataset. This
570
-
first version of the schema only includes required elements and fields. In the future we plan to improve the schema by adding controlled
571
-
vocabulary and more robust dataset field format testing:
585
+
Retrieves a JSON schema customized for a given collection in order to validate a dataset JSON file prior to creating the dataset:
572
586
573
587
.. code-block:: bash
574
588
@@ -593,8 +607,22 @@ While it is recommended to download a copy of the JSON Schema from the collectio
593
607
Validate Dataset JSON File for a Collection
594
608
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
595
609
596
-
Validates a dataset JSON file customized for a given collection prior to creating the dataset. The validation only tests for json formatting
597
-
and the presence of required elements:
610
+
Validates a dataset JSON file customized for a given collection prior to creating the dataset.
611
+
612
+
The validation tests for:
613
+
614
+
- JSON formatting
615
+
- required fields
616
+
- typeClass must follow these rules:
617
+
618
+
- if multiple = true then value must be a list
619
+
- if typeClass = ``primitive`` the value object is a String or a List of Strings depending on the multiple flag
620
+
- if typeClass = ``compound`` the value object is a FieldDTO or a List of FieldDTOs depending on the multiple flag
621
+
- if typeClass = ``controlledVocabulary`` the values are checked against the list of allowed values stored in the database
622
+
- typeName validations (child objects with their required and allowed typeNames are configured automatically by the database schema). Examples include:
623
+
624
+
- dsDescription validation includes checks for typeName = ``dsDescriptionValue`` (required) and ``dsDescriptionDate`` (optional)
625
+
- datasetContact validation includes checks for typeName = ``datasetContactName`` (required) and ``datasetContactEmail``; ``datasetContactAffiliation`` (optional)
598
626
599
627
.. code-block:: bash
600
628
@@ -4826,6 +4854,28 @@ The fully expanded example above (without environment variables) looks like this
@@ -5242,7 +5292,7 @@ The fully expanded example above (without environment variables) looks like this
5242
5292
Reserve a PID
5243
5293
~~~~~~~~~~~~~
5244
5294
5245
-
Reserved a PID for a dataset. A superuser API token is required.
5295
+
Reserve a PID for a datasetif not yet registered, and, if FilePIDs are enabled, reserve any file PIDs that are not yet registered. A superuser API token is required.
5246
5296
5247
5297
.. note:: See :ref:`curl-examples-and-environment-variables`if you are unfamiliar with the use of export below.
0 commit comments