add keywords to metadata

[epistasislab]

add keywords to metadata

[trangdata]

I'm in favor of keywords but I'm not sure ACM CSS is an ideal ontology for datasets.

[lacava]

Any idea what keyword ontologies are out there? I'm having trouble finding examples.

[lacava]

added in PR #69 :)

[trangdata]

Hmm... I thought we added a keywords field to all auto-generated metadata.yaml files that haven't been manually modified.

But I don't see keywords, e.g., here.

[lacava]

we haven't added keywords by default except to the template. i'm not sure how we would put them in auto-generated files? just have a blank entry?

[trangdata]

Oh I see. Hmm I was thinking like what you have in the template:

keywords:
  - keyword1
  - keyword2

[lacava]

i don't think we should have dummy keywords appearing in the auto-generated files

[trangdata]

Perhaps keyword1 and keyword2 are not great place holders. Maybe needs_keyword or replace_me would work?

I think we need to make it as easy as possible for a contributor to come in with little knowledge of yaml and can still contribute. The contributor shouldn't have to come back to the template to find out what other fields are there to add. This will make the reviewer's job easier as well. I myself have missed this field most times when reviewing metadata files.

And having two place holders will also avoid a situation where keywords are put in as

keywords:
  - keyword1, keyword2

I'm happy to implement this. I feel like it's a case of practicality beats purity we have here.

[lacava]

How about we add a line like

keywords: # descriptive terms for the dataset, each hyphenated on a new line (see metadata_template.yaml)

EDIT: I think we can use null to be read in as None in python

keywords: # descriptive terms for the dataset, each hyphenated on a new line (see metadata_template.yaml)
  - null # replace with keyword

[trangdata]

Addressed in #107.