Add resourceType for dataset files

[philippconzett]

What is the problem that your suggestion solves?

Our research data repository uses DOIs at file level, meaning that each file within a dataset gets its own DOI. For example, the file https://doi.org/10.18710/WUJCYB/VLJNH1 is part of the https://doi.org/10.18710/WUJCYB dataset. However, in DataCite Commons and other discovery services relying on DataCite metadata, dataset files are handled at the same level as datasets. For example, ORCID records of depositors are flooded with dataset file records, so it's almost impossible to spot the major achievements, which in case of data deposits would be the datasets.

What solution might meet your needs?

To solve this problem, I suggest introducing a resourceType for dataset files to the DataCite metadata schema. This would allow metadata harvesters and indexers to filter information in a more targeted manner. For more information, see Dataverse GitHub issue #5086 and PID Forum thread.

Your name

Philipp Conzett

Your organization

UiT The Arctic University of Norway

What alternatives have you tried or considered?

Stop using DOIs at file-level. However, this alternative would not be align with good practice recommendation of granular PID strategies.

Is there anything else you would like to share?

This suggestion might relate to the current discussion of introducing a new Distribution property.

What group(s) would benefit from your suggestion?

• DataCite members registering DOIs and metadata and administering accounts
• Developers building integrations with DataCite services
• Harvesters who index DataCite DOIs and metadata
• Individuals or institutions analyzing DataCite DOIs and metadata
• DataCite staff
• Other

If other group(s), please describe.

Researchers relying on granular metadata