-
Notifications
You must be signed in to change notification settings - Fork 151
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
FAIR score maximization #2942
Comments
Including information about the access restrictions in DataCite (already done in Dublin Core) would be great for harvesters that want to know if the resource in open / restricted. Invenio already does this for dublin core: <oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
...
<dc:rights>info:eu-repo/semantics/openAccess</dc:rights>
<dc:rights>Creative Commons Attribution 4.0 International</dc:rights>
<dc:rights>https://creativecommons.org/licenses/by/4.0/legalcode</dc:rights>
...
</oai_dc:dc> This should be done in DataCite XML as well: <resource xmlns="http://datacite.org/schema/kernel-4" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://datacite.org/schema/kernel-4 http://schema.datacite.org/meta/kernel-4.3/metadata.xsd">
...
<rightsList>
<rights rightsURI="info:eu-repo/semantics/openAccess" />
<rights rightsURI="https://creativecommons.org/licenses/by/4.0/legalcode" rightsIdentifierScheme="spdx" rightsIdentifier="cc-by-4.0">Creative Commons Attribution 4.0 International</rights>
</rightsList>
...
</resource> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tasks identified from issues
No license property was found in the metadata
This was an error with the FAIR checker and no fix was needed
Unable to resolve DOI using HTTP Accept header application/json #2949
Open PR bug: use Accept header to return other formats #2948
Unable to resolve DOI using HTTP Accept header text/xhtml,text/xml
Datacite is the preferred XML flavour of the four we have, but the implementation would depend on what happens to the above PR:
I don't think this is applicable. I could imagine "Open metadata, restricted files" and variations thereof but I'm not sure if that would be expected
No info about file size available in given metadata for files
Tested with ngrok from local system, adding file size to the headers did not work. The test here seems to suggest that it is picked up from the header.
size
andformat
fields (and see if that's something that their code detects)Could not verify content type from downloaded files
Could not find how to modify the current content type. (Will look into this further) This is only valid for datasets.
size
andformat
fields (and see if that's something that their code detects)Formal provenance metadata is unavailable
Predicates metadata should resolve to Linked Data data
Persistence policy not identified
GUID does not conform with any known permanent-URL system
dcat: Missing discoverability oriented metadata
Using:
The text was updated successfully, but these errors were encountered: