You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
There is an
active
table forkeywords
. 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.
The text was updated successfully, but these errors were encountered: