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

resource.keywords.controlled.present #48

Closed
gothub opened this issue Jun 20, 2019 · 3 comments
Closed

resource.keywords.controlled.present #48

gothub opened this issue Jun 20, 2019 · 3 comments
Assignees
Labels
DataCite The target for this check exists in the DataCite dialect ESS-DIVE Suite Essential FAIR Suite Findable Related to the 'Findable' category of the FAIR Suite prototyped checks that have been coded and checked into the repo
Milestone

Comments

@gothub
Copy link
Contributor

gothub commented Jun 20, 2019

Description

Check if keywords are controlled by a vocabulary.

Priority

FAIR: Optional

Issues

  • No known issues

Procedure

  • for each group of keywords, check if a thesaurus has been specified.
  • no check is made regarding the authority of the vocabulary, i.e. is a URL specified and does it resolve.
@gothub gothub added this to the 0.2.0 milestone Jun 20, 2019
@gothub gothub self-assigned this Jun 20, 2019
@gothub gothub added the Findable Related to the 'Findable' category of the FAIR Suite label Jul 9, 2019
@gothub gothub changed the title keyword.thesaurus.present check dataset.keywords.controlled check Jul 10, 2019
@gothub gothub added the prototyped checks that have been coded and checked into the repo label Jul 12, 2019
@tedhabermann
Copy link
Contributor

The target for this check exists in the DataCite Dialect: data[].attributes.subjects[].subjectScheme. If a subjectScheme exists, it indicates that the keywords come from that scheme.

@tedhabermann tedhabermann added the DataCite The target for this check exists in the DataCite dialect label Aug 20, 2019
@JEDamerow
Copy link
Contributor

My understanding is that use of controlled terms is more for interoperability than findability.

@gothub
Copy link
Contributor Author

gothub commented Sep 5, 2019

Added to ESS-DIVE suite in commit 583d381

@JEDamerow each check has it's own default level (REQUIRED, OPTIONAL, INFO) and type (Accessible, Findable, ...) which is defined in the check XML file. These can be overridden for a suite by modifying the suite XML file, for example https://github.com/NCEAS/metadig-checks/blob/dev-0.2.0/src/suites/ess-dive.xml, shows the dataset.keywords.controlled entry with values that will override the check defaults.

@gothub gothub modified the milestones: 0.2.0, 0.2.1, 1.0.0 Sep 10, 2019
@tedhabermann tedhabermann changed the title dataset.keywords.controlled check resource.keywords.controlled Dec 17, 2019
@tedhabermann tedhabermann changed the title resource.keywords.controlled resource.keywords.controlled.present Dec 19, 2019
@tedhabermann tedhabermann modified the milestones: 1.0.0, Essential Dec 20, 2019
@tedhabermann tedhabermann removed this from the Essential milestone Jan 2, 2020
@gothub gothub modified the milestones: 1.0.0, 0.2.5 Mar 12, 2020
@gothub gothub closed this as completed Apr 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DataCite The target for this check exists in the DataCite dialect ESS-DIVE Suite Essential FAIR Suite Findable Related to the 'Findable' category of the FAIR Suite prototyped checks that have been coded and checked into the repo
Projects
None yet
Development

No branches or pull requests

3 participants