These use cases are a product of the 2014 CDI Project: Use of Controlled Vocabularies in USGS Information Applications: Requirements Analysis for Automated Processes and Services (Bureau-wide Application) The use case team evaluated three use cases. The first use case, “Assign keywords to a metadata record using one or more controlled vocabularies,” develops the functional requirements for a vocabulary server interacting with a metadata creation tool. The second use case, “A catalog search interface uses vocabulary services to help users find data,” develops functional requirements for the same vocabulary server, but this time interacting with a catalog user interface. The third use case, “Create specialized indexes to enhance the [...]
The use case team evaluated three use cases. The first use case, “Assign keywords to a metadata record using one or more controlled vocabularies,” develops the functional requirements for a vocabulary server interacting with a metadata creation tool. The second use case, “A catalog search interface uses vocabulary services to help users find data,” develops functional requirements for the same vocabulary server, but this time interacting with a catalog user interface. The third use case, “Create specialized indexes to enhance the searchability of metadata,” develops the requirements if the vocabulary server is used by a catalog system to develop an internal table that cleans up and cross-references keywords that are found in metadata records.
Analysis of the three use cases produced the preliminary set of requirements indicated in the table below. Functional requirements discovered through analysis of use cases. “CVS” refers to a specific controlled vocabulary set that is provided by the vocabulary server.
Service Description
Case 1
Case 2
Case 3
Server provides list of all available CVS identifiers.
x
x
Server provides list of all available CVS names, both preferred and alternative.
x
x
Given a CVS identifier, server provides a description of a single CVS (producer, version, identifier, preferred name, recommended use, etc.)
x
x
Given a CVS identifier, server indicates whether broader and narrower relationships in that CVS are transitive.
x
x
Given a CVS identifier, server indicates whether that CVS has a hierarchical structure.
x
x
Given a CVS identifier, server provides a list of top level terms or recommended starting terms for browsing that CVS.
x
Given a CVS identifier and a choice of hierarchical level, server provides a list of all terms included on that level in a single CVS.
x
Given a search string (possibly including wildcards) and a CVS identifier, server provides terms that match the given string within the CVS.
x
x
x
Given a search string (possibly including wildcards), server provides terms that match the given string within all available CVSes.
x
x
x
Given a search term and a CVS identifier, server provides a description of the given term as specified in the CVS (identifier, scope notes, etc.)
x
x
Given a search term and a CVS identifier, server provides the set of non-preferred terms listed in the CVS for the concept identified by the given term.
x
Given a search term and a CVS identifier, server provides the set of other terms within the CVS that are related to the given term.
x
x
Given a search term and a CVS identifier, server provides the set of other terms within the CVS that are broader than the given term.
x
x
x
Given a search term and a CVS identifier, server provides the set of other terms within the CVS that are narrower than the given term.