ControlledVocabularyManager
ControlledVocabularyManager copied to clipboard
Terms ID namespacing and special characters
Prevent future Term/Vocabulary/Predicates from using forward slashes in the ID, possibly preventing other characters that are sensitive on the URL (ie. ?, &). If terms need a "namespace" so to speak, maybe adopt a format like [NAMESPACE]-[TERM] or something similiar
Definitely need to block . in the ID. The term will be created, show up in Review, but then 'can't be found' when you click the link in Review.