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
Overview of the Feature Request
Add to the metadata blocks that ship with Dataverse a metadata block for describing 3D data
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Curator, Depositor, Guest
What inspired the request?
This request is inspired by work with folks at Boston College and Harvard Library to add metadata fields that help them describe the 3D data that they publish. @siacus asked that we add the metadata block to the metadata blocks that ship with Dataverse, as opposed to making it a metadata block that's exclusive to those two collections in Harvard Dataverse.
Any brand new behavior do you want to add to Dataverse?
Folks who manage Dataverse installations, and folks who manage Dataverse collections within those installations, are able to enable a metadata block that includes fields that their curators and depositors can use to describe 3D data.
When the metadata block has been enabled in the installation, depositors and curators can use the metadata block's fields to describe 3D data that they deposit in the installation's collections, including the installation's "Root" collection if the metadata block has been enabled there. And others can use that metadata to find datasets that have certain properties of 3D data.
Overview of the Feature Request
Add to the metadata blocks that ship with Dataverse a metadata block for describing 3D data
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Curator, Depositor, Guest
What inspired the request?
This request is inspired by work with folks at Boston College and Harvard Library to add metadata fields that help them describe the 3D data that they publish. @siacus asked that we add the metadata block to the metadata blocks that ship with Dataverse, as opposed to making it a metadata block that's exclusive to those two collections in Harvard Dataverse.
See the comment at IQSS/dataverse.harvard.edu#253 (comment) for more context.
Any brand new behavior do you want to add to Dataverse?
Any open or closed issues related to this feature request?
IQSS/dataverse.harvard.edu#144
IQSS/dataverse.harvard.edu#253
IQSS/dataverse.harvard.edu#319
The text was updated successfully, but these errors were encountered: