Support data usage license information, according to FAIR principle R1.1
sveinugu opened this issue · comments
"R1.1. (Meta)data are released with a clear and accessible data usage license"
Suggestion, for specific data usage schema:
- field: data use limitation/requirement, use GA4GH-approved Data Use Ontology (https://www.ga4gh.org/news/data-use-ontology-approved-as-a-ga4gh-technical-standard/), ancestor: either "data use limitation" (
http://purl.obolibrary.org/obo/DUO_0000001) or "
data use requirements" (http://purl.obolibrary.org/obo/DUO_0000017) - either another free-text field for details, but best is hardcoded set of fields for certain values, e.g. "disease specific research" require a disease.
- perhaps an array of the above, but that is probably a bit too much. Main limitation/requirement is probably enough
- augmentation server fills out a data usage summary field
- URL to data usage license/policy document
Should be placed in each track object, as well as together with "raw_file_ids". Also perhaps a variant for the complete metadata document as such, but that should be required to be "no restriction". This, as there are arguments for providing a CC0 license with a metadata collection.
Add field for URL to access control procedure info, as referred to in A1 in the manuscript
We need to find the proper values to use for the BLUEPRINT data.
Is this what you want? http://dcc.blueprint-epigenome.eu/#/md/data_reuse
@dzerbino Thanks, I think we can extract the proper values on the data usage from there.
However, there is no information about the usage of the metadata, AFAIK, including re-publishing in a transformed form (which we are doing).
I would assume BLUEPRINT did not think to say anything about the metadata as such, as such metadata is typically assumed to be public domain in the research community. There is, however, a complicated discussion on the legalese of reuse of metadata, and as far as I remember from reading about this, the laws regarding this depends on nationality. Being able to slap a CC0 license (https://creativecommons.org/share-your-work/public-domain/cc0/) on the metadata as an example to follow for others would be nice, but we are not in a position to grant such a license, AFAIK.
@dzerbino Even though you are dropping out, do you have any contacts that might be able to grant such a license on our transformed version, or on the source material you used to create it, or help make this happen?
Some relevant links:
- https://www.europeandataportal.eu/sites/default/files/d2.1.2_training_module_2.5_data_and_metadata_licensing_en_edp.pdf
- https://zenodo.org/record/840652
- https://www.researchgate.net/publication/308321199_Assigning_Creative_Commons_Licenses_to_Research_Metadata_Issues_and_Cases
Edit: "Complicated discussion", not "huge discussion" :)
Hello @sveinugu , I'll write now to the Blueprint helpdesk cc'ing you to clarify.