HDV Task: GREI 6 - Initial Dataset Type Support #307
Description
Overview of the Feature Request
Per discussion in https://docs.google.com/document/d/16RvGXmaPQK9DGsEEbrrFEu8mjUrN93YY_yh7ZONyMDI/edit?usp=sharing and as the first development issue to be associated with #110, this issue outlines the creation of a mechanism to allow Datasets to be given a type (e.g. (traditional) Dataset, Software, Workflow, ...), for the type to be used in search/faceting, and for the type to be available when creating exports/metadata sent to PID providers. (Follow on issues will address allowing types to be configured to use different licenses, metadata blocks, etc.)
Issues
- Create the datasetType class and add UI facet dataverse#10517
Implement a global setting and/or API for dataset types dataverse#10518- Implement datasetType metadata block support (at global level) dataverse#10519
- Implement list of allowed datasetType licenses (at global level) dataverse#10520
- extend the getCollectionMetadataBlocks use case to allow passing datasetType dataverse-client-javascript#210
Related
- Proposal: Supporting Multiple Dataset Types in Dataverse #110
- RO-Crate exporter PoC dataverse#10086
- Computational Workflow metadata block bug: links don't link dataverse#10339
- convert workflowCodeRepository field into a clickable link dataverse#10441
- Add MIT Software license to HDV dataverse.harvard.edu#248