Open mhvezina opened 3 years ago
Thank you for pointing out the inconsistency in the documentation of the OpenAIRE Guidelines. We'll fix it in the next release.
Please do not resolve the concepts "journal" or "periodical" to the concept "other".
Thank you @joschirr ; will then resolve to the appropriate COAR values as you instructed.
Working with the Dspace OpenAIRE crosswalk, I stumbled on this:
Actually, in the crosswalk, the dc.type "journal" and "periodical" respectively resolve to resourceType "periodical" with attribute uri "http://purl.org/coar/resource_type/c_0640" and resourceType "periodical" with attribute uri "http://purl.org/coar/resource_type/c_2659" :
https://github.com/DSpace/DSpace/blob/6ac06c8a23b2d2abbaf5ac3dd0bd780395a414da/dspace/config/crosswalks/oai/metadataFormats/oai_openaire.xsl#L1306
https://github.com/DSpace/DSpace/blob/6ac06c8a23b2d2abbaf5ac3dd0bd780395a414da/dspace/config/crosswalks/oai/metadataFormats/oai_openaire.xsl#L1378
However I wonder if they should instead resolve to resourceType "other" with attribute uri "http://purl.org/coar/resource_type/c_1843" as both types (i.e. periodical and journal) are not in the controlled list values found here: https://openaire-guidelines-for-literature-repository-managers.readthedocs.io/en/v4.0.0/field_publicationtype.html#attribute-uri-m ?
More over those types are present in the schema : e.g. : https://github.com/openaire/guidelines-literature-repositories/blob/f2b82d0967590caa8cf19307f73483029aba1e76/schemas/4.0/oaire-resourceType-v4.xsd#L14
Can someone tell me about the primacy of the controlled list of values in the docs vs the schema?