1 / 9

Vocabulary Management Process

Vocabulary Management Process. Fall 2003. Goals of Vocabulary Management. Provide a method for vocabulary development within DLESE metadata frameworks Track vocabulary terms over time Track most recent vocabulary definitions (definitions are not tracked over time)

maleah
Download Presentation

Vocabulary Management Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Vocabulary Management Process Fall 2003

  2. Goals of Vocabulary Management • Provide a method for vocabulary development within DLESE metadata frameworks • Track vocabulary terms over time • Track most recent vocabulary definitions (definitions are not tracked over time) • Make controlled vocabularies available to other DLESE systems

  3. Functions of Vocabulary Mgmt • Need determination - is a vocab needed • Development and buy-in - get stakeholders involved in crafting the vocab • Metadata framework implementation - put the vocabulary in a metadata framework • Vocabulary Manager/GUI implementation - put the vocabulary, definitions and GUI labels in the Vocabulary Manager

  4. 1. Need Determination • Consistent data is required for browse/search • There are new frameworks or new fields • A significant number (50% or greater) of metadata records across DLESE collections would benefit from a specialized vocabulary • A vocabulary is not meeting the original need intended and needs modification Challenge - differences on what qualifies as a need (individual collection vocabs????)

  5. 2. Development and Buy-in (a) • Craft - • Terms, definitions, parameters of use, GUI labels • How - (remember to give examples) • Use an existing vocabulary and its definitions • DPC staff decides upon terms and definitions • DPC staff and knowledgeable community members work to together (geospatial) • With who - • Determine stakeholders

  6. 2. Development and Buy-in (b) • Complete other important information • Attribution, related terms, broader/narrower terms • Indicate the metadata framework and fields • Iterate - through this process several times with stakeholders Challenge - getting buy-in and agreement on terms, definitions and use parameters

  7. 3. Metadata Framework Implement. • Uses terms only since using XML Schema and not RDF Schema • Make an individual vocabulary schema (vocab.xsd) • Connect it to the framework • Issue a new version of the framework Challenge - most vocab changes cause significant changes in other DLESE systems

  8. 4. Vocabulary Manager Entry • Use the vocab.xsd file (from step 3) • Create a vocab-mgmt.xsd file • Use existing contrl-mgmt.xsd files • Create vocab-terms.xml & vocab-grps.xml • Ingest terms & groups files into Vocab Mgr • CVS everything Challenge - terms and groups files not matched against original vocab.xsd file; so Vocab Mgr could be wrong!!

  9. Example of NSES • Need determined at the Portal to the Future Workshop in August 1999 • Development not required because used the vocabulary was adopted directly from NAS • Vocabulary in framework: August 2001 • Vocabulary in DCS: March 2002 • Vocabulary into the Vocab Mgr: August 2003 • Vocabulary in DDS: August 2003

More Related