Open mbjones opened 4 years ago
I'm going to give this issue a bump - ~especially since we may want to use the intellectualRights
field to describe restricted aspects of sensitive data~ we decided not to do that but it's still important
@robyngit currently, this is not something that has any impact on for the data curation team. It might still be high priority for @mbjones and @jeanetteclark in general, but if you're focusing on immediate ways to "improve the editor in a way that decreases [the datateam's] workload", this issue is not a priority in that sense 🙂
Every dataset needs this structured license info. I thought for a while the datateam was converting that manually in R. Wouldn't it be easier if it came in the right format from MetacatUI in the first place? Ditto with funding info?
Hm. If the datateam was converting that manually in R, it stopped before my time. Just to make sure, we're talking about this section of the dataset, correct?
If so, I haven't seen a more structured format than that, so I'm not sure what that looks like visually. Now with regard to the funding info, it would be a great quality of life upgrade for the interns if MetacatUI got that right in the first place!
A potential candidate for a hosted repository requested machine-parseable licenses today, so bumping this issue (again):
Do you implement machine readable data licenses in data packages?
Describe the feature you'd like EML 2.2.0 introduces machine-parsable licenses, as described here: https://eml.ecoinformatics.org/whats-new-in-eml-2-2-0.html#dataset-license We should support display and editing of this license information, and conversion of earlier licenses like CC-0 and CC-BY to the new format when they are found in existing EML 2.1.1 documents in the
intellectualRights
field.Is your feature request related to a problem? Please describe. Inability to filter datasets by license.
Additional context