Active keywords

[stuartmcalpine]

There is an active table for keywords. However its not actually utilized in the code.

Do we want to use this? i.e., a user cannot tag a dataset with a "inactive" keyword.

• What happens to datasets with this keyword tagged that has then become inactivate?
• Should inactive keywords not come up in searches by default ?

[JoanneBogart]

There is an active table for keywords

I think you must mean column, not table.

I think ultimately we do want to use it as you describe. We should supply routines to activate and deactivate keywords. Certainly the state of production keywords can only be changed with sufficient privilege. Even system keywords in the working schema should probably be protected. And inactive keywords should not come up in searches by default, but ideally there should be a way to explicitly ask for them.

[JoanneBogart]

partially addressed by PR #202
Still need to modify searching to ignore inactive keywords by default.
And disallow association of inactive keyword with a dataset.
And disallow disabling of system keyword (or maybe just disallow if there are associations of this keyword with datasets?)

[JoanneBogart]

The new KeywordTable class allows users to create keywords. There is another lower-level utility, _insert_keyword, used by the script create_registry_schema, which inserts entries for standard system keywords. This is perhaps best left as is since the script doesn't use (and for most of its work can't use) the standard API.