Overview of the Feature Request
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Sysadmin
What inspired the request?
When a Dataverse repository manager registers a DOI for a file, the information that Dataverse sends to DataCite about that file includes the resourceTypeGeneral "Dataset", which is the same resourceTypeGeneral that Dataverse uses when registering DOIs for datasets. This makes it difficult to rely on resourceTypeGeneral to distinguish between DOIs registered for datasets versus DOIs registered for files, as "datasets" and "files" are defined by folks designing Dataverse and other data repositories.
For example, the dashboard at https://metadata.datacite.org/gdcc.harvard-dv should show information about datasets in Harvard Dataverse, but it includes information about files because files have the resourceTypeGeneral "Dataset".
Working with the folks at DataCite to resolve this has been ongoing, with conversations recorded in places like the Dataverse GitHub issue at #5086 and the DataCite GitHub discussion at datacite/datacite-suggestions#214.
While these conversations progress, we thought about what changes we could make in Dataverse sooner.
What existing behavior do you want changed?
When Dataverse managers register DOIs for files, tell Dataverse to create those files' DataCite exports where resourceTypeGeneral is "Other" instead of "Dataset" and send that information to DataCite.
Also, for files in the repository that already have DOIs, tell Dataverse to resend to DataCite information telling it to use "Other" for the resourceTypeGeneral.
This way, when people want to distinguish between datasets that have DOIs and files that have DOIs, they can include or exclude DOIs whose resourceTypeGeneral is "Other", such as in the resourceType dropdown in DataCite's dashboards at https://metadata.datacite.org. The folks who manage ORCID might also use this so that only information about datasets, and not files that happen to have DOIs, make it onto ORCID profiles.
If DataCite decides to add a new resourceTypeGeneral that people can tell their repositories to use when registering DOIs for files, then we can tell Dataverse to use that new resourceTypeGeneral instead of "Other".
Any open or closed issues related to this feature request?
Overview of the Feature Request
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Sysadmin
What inspired the request?
When a Dataverse repository manager registers a DOI for a file, the information that Dataverse sends to DataCite about that file includes the resourceTypeGeneral "Dataset", which is the same resourceTypeGeneral that Dataverse uses when registering DOIs for datasets. This makes it difficult to rely on resourceTypeGeneral to distinguish between DOIs registered for datasets versus DOIs registered for files, as "datasets" and "files" are defined by folks designing Dataverse and other data repositories.
For example, the dashboard at https://metadata.datacite.org/gdcc.harvard-dv should show information about datasets in Harvard Dataverse, but it includes information about files because files have the resourceTypeGeneral "Dataset".
Working with the folks at DataCite to resolve this has been ongoing, with conversations recorded in places like the Dataverse GitHub issue at #5086 and the DataCite GitHub discussion at datacite/datacite-suggestions#214.
While these conversations progress, we thought about what changes we could make in Dataverse sooner.
What existing behavior do you want changed?
When Dataverse managers register DOIs for files, tell Dataverse to create those files' DataCite exports where resourceTypeGeneral is "Other" instead of "Dataset" and send that information to DataCite.
Also, for files in the repository that already have DOIs, tell Dataverse to resend to DataCite information telling it to use "Other" for the resourceTypeGeneral.
This way, when people want to distinguish between datasets that have DOIs and files that have DOIs, they can include or exclude DOIs whose resourceTypeGeneral is "Other", such as in the resourceType dropdown in DataCite's dashboards at https://metadata.datacite.org. The folks who manage ORCID might also use this so that only information about datasets, and not files that happen to have DOIs, make it onto ORCID profiles.
If DataCite decides to add a new resourceTypeGeneral that people can tell their repositories to use when registering DOIs for files, then we can tell Dataverse to use that new resourceTypeGeneral instead of "Other".
Any open or closed issues related to this feature request?