-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resourceTypeGeneral must be mandatory #24
Comments
The issue statement is confused. In DataCite metadata, the resourceTypeGeneral sub-property is already mandatory. It's the ResourceType property that is optional. Also, the resourceTypeGeneral sub-property already accepts values from a controlled vocabulary. It isn't particularly clear what is the intention of this issue: what problem does it solve? Is the goal to document existing behaviour, that OpenAIRE will ignore records without the ResourceType property? or perhaps advocating that some functionality/service (that uses OpenAIRE) is unable to work without ResourceType, so advocating that the profile is updated to support this use-case? |
Thank you for your feedback @paulmillar. The OpenAIRE Guidelines for Data Archives are going to be incorporated to the OpenAIRE Guidelines for Literature Repository Managers v4: https://openaire-guidelines-for-literature-repository-managers.readthedocs.io/en/v4.0.0/ in short time. In any case the ResourceType is mandatory as OpenAIRE needs this information to successfully represent the type of the research products. In the latest versions we have also incorporated the need to use the COAR Controlled Vocabulary for the Resource Type. https://openaire-guidelines-for-literature-repository-managers.readthedocs.io/en/v4.0.0/field_publicationtype.html |
Thanks for the quick response, @pispis. It's certainly useful to know that ResourceType is mandatory. |
We have an issue in
https://guidelines.openaire.eu/en/latest/data/field_resourcetype.html
resourceTypeGeneral must be mandatory and must be provided with a controlled value.
Otherwise such records are ignored during aggregation.
The text was updated successfully, but these errors were encountered: