Bug #3678
closedIncorporate FIRST features for generalized vocabulary lookup
0%
Description
While you can currently specify a "thesaurus" from which your keywordSet is derived, there is no way of actually selecting values from this [possibly nonexistent] vocabulary list.
The FIRST project is addressing this shortcoming with some enhancements. Those should be added directly to Morpho so that they can be used by both applications.
Related issues
Updated by Matt Jones over 15 years ago
This would allow us to close out one of our oldest Morpho requests -- bug # 345, opened in 2001. I think this bug and that one are duplicates.
Updated by ben leinfelder over 15 years ago
I've incorporated the new VocabularyPlugin that is used for managing controlled vocabularies (lists, trees, more...)
Each configured vocabulary must specify an appropriate UI (an implementation of the new AbstractUIVocabularyPage class) that is used for selecting values.
The GenericVocabularyPage can be used for simple lists, but assumes that there is an accompanying XML file that conforms to the IMS VDEX specification (http://www.imsglobal.org/vdex/) provided in the configuration jar of a Morpho installation.
The VocabularyPlugin has no dependency on the concept of EML's "keywordSet", even though that was the primary motivation for creating it (re: bug #345).
Updated by ben leinfelder over 15 years ago
The "KNBRegistry" vocabulary is a developing list of sites/organizations that contribute to the KNB.
SANParks uses these values to organize their data sets (by park). This is the first constrained vocabulary that was added to Morpho (and may need editing). Suggestions for more?
Updated by ben leinfelder over 15 years ago
added another "generic" UI page: the GenericTreeVocabularyPage allows interaction with an arbitrarily deep tree for selecting keywords. Any level in the tree - whether leaf or branch - can be selected as a keyword.
Updated by ben leinfelder about 15 years ago
this has been incorporated into the Morpho tree for 1.7