Keyword master list for metadata form

[sjbruce]

The possibility of creating a master list of CIOOS keywords on GitHub was raised to address the problem of duplicate and redundant keywords spread throughout metadata records.

Broadly speaking:

• The master list would live in a github repo;
• The metadata form would draw on this list and only allow selections from this controlled list;
• RAs become the custodians of the list;
• New keywords are are added via Issues, Branches & Pull Requests;

This should allow a faster, more collaborative method of maintaining the keywords list in the metadata form without any one person, team or organization being responsible for maintaining the list.

This will help with metadata records created on a go-forward basis, but won't necessarily solve the issues with existing records.

[n-a-t-e]

I made a PR for a "Keyword proposal" issue request template. https://github.com/cioos-siooc/cioos-siooc-standards/pull/16 It could probably use more background info/text in it about what we are looking for

[sjbruce]

cioos-siooc-standards seems like as good a place as any for such a list to live (though it doesn't have to be).

It looks like there's currently two files to maintain?

The keyword list in English and the French translations:

• https://github.com/cioos-siooc/metadata-entry-form/blob/master/src/keywordList.js
• https://github.com/cioos-siooc/metadata-entry-form/blob/master/src/utils/i18nDictionaryFr.js

Given the reality of requiring multiple vocabularies, should the master list be in one form (CSV, JSON, etc.) and then get transmuted into those files?

Or should the form alter how it currently works to use the master list directly?

[n-a-t-e]

it would change to be a single file in the metadata repo, but I think the master list could be stored as a CSV here

[sjbruce]

Sounds good - so fields in the CSV would need to be at least:

• English,
• French,
• Vocabulary,
• Status (accepted, provisional, emergent?) - something reflecting how the keyword is regarded inside CIOOS