Skip to content
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

Open
joschirr opened this issue Jun 23, 2016 · 3 comments
Open

resourceTypeGeneral must be mandatory #24

joschirr opened this issue Jun 23, 2016 · 3 comments
Assignees

Comments

@joschirr
Copy link
Member

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.

@paulmillar
Copy link

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?

@pispis
Copy link
Contributor

pispis commented Jan 6, 2025

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

@paulmillar
Copy link

Thanks for the quick response, @pispis. It's certainly useful to know that ResourceType is mandatory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants