Skip to content

Latest commit

 

History

History
270 lines (207 loc) · 17.8 KB

File metadata and controls

270 lines (207 loc) · 17.8 KB

Repo4Cat (NFDI4Cat Central Data Repository) changelog

2026-06-14: Dataverse Update, v6.2-v6.10.1

The most important changes

1. "Private URL" is now "Preview URL"

2. CVoc (Controlled Vocabulary)

3. Licenses added

4. Citation Metadata block

  • New keywordTermURI Metadata Field in the Citation Metadata Block. A new metadata field - keywordTermURI, has been added in the citation metadata block (as a fourth child field under the keyword parent field). This has been done to improve usability and to facilitate the integration of controlled vocabulary services, adding the possibility of saving the "term" and/or its associated URI.
  • New subfield "Relation Type" (IsSupplementTo for the old datasets)
  • DataCite v4.5

5. File Retention Period

6. Improved Detection of RO-Crate Files

7. Pre-Publish File PID reservation!!!

  • Now PID for files will be reserved, when files are created, and not like earlier only during publication!
  • The big old issue is closed! - IQSS/dataverse#7334

8. ORCIDs Linked to Accounts

9. ROR (Research Organization Registry) has been added as an Author Identifier Type

  • For the case when the author is an organization rather than a person.
  • Like ORCID, ROR will appear in the "Datacite" metadata export format.
  • See #11075 and #11118.

10. Croissant Support Is Now Built In, Slim Version Added

  • Croissant is a metadata export format for machine learning datasets
  • As described in the Discoverability section of the Admin Guide, Croissant is inserted into the "head" of the HTML of dataset landing pages, as requested by the Google Dataset Search team so that their tool can filter by datasets that support Croissant. In previous versions of Dataverse, when Croissant was optional and hadn't been enabled, we used the older "Schema.org JSON-LD" format in the "head". If you'd like to keep this behavior, you can use the feature flag dataverse.legacy.schemaorg-in-html-head.
  • https://guides.dataverse.org/en/6.10.1/admin/discoverability.html#id6
  • https://datasetsearch.research.google.com/

11. Unlink Dataset Button

  • A new "Unlink Dataset" button has been added to the dataset page to allow a user to unlink a dataset from a collection. To unlink a dataset the user must have permission to link the dataset.
  • Additionally, the existing API for unlinking datasets has been updated to no longer require superuser access as the "Publish Dataset" permission is now enough. See also #10583 and #10689.

12. Move a Dataverse Collection

13. Prevent Publishing of Datasets Without Files

14. Dataset Types Can Be Linked to Metadata Blocks

15. Linking Drafts

16. Version Notes

17. Curation Status Label Enhancementsq

18. Signposting Output Now Contains Links to All Dataset Metadata Export Formats

19. View Styled Citation ("Cite dataset" button)

20. Link Permission Split Off from Publish Permission

  • Linking or unlinking a dataset or dataverse now requires the new "LinkDataset" or "LinkDataverse" permissions, respectively.
  • Previously, this action was covered by the "PublishDataset" or "PublishDataverse" permission
  • Splitting linking into its own permission, separate from publishing, allows for more fine-grained access control, if you choose to implement custom roles that differ from the roles that Dataverse ships with.
  • IQSS/dataverse#11691

21. Open OnDemand Integration (now possible)

22. Globus Async Framework (now possible)

23. Role Assignment History Tracking

24. Support for COAR Notify Relationship Announcement

25. Integration with Local Contexts

26. Optionally Require Acknowledgment of a Disclaimer When Publishing

27. Optionally Require Embargo Reason

28. Review Datasets

  • Dataverse now supports review datasets, a type of dataset that can be used to review resources such as other datasets in the Dataverse installation itself or various resources in external data repositories.
  • APIs and a new "review" metadata block (with an "Item Reviewed" field) are in place but the UI for this feature will only be available in a future version of the new React-based Dataverse Frontend (see #876).
  • See https://guides.dataverse.org/en/6.10.1/user/dataset-management.html#review-datasets. This feature is experimental.

29. API changes

Full list of changes

API incompatible changelog