Difference between revisions of "Controlled vocabulary"

From Earth Science Information Partners (ESIP)
Line 6: Line 6:
  
 
==== Overview ====
 
==== Overview ====
A controlled vocabulary (CV) is being developed to improve discoverability of software registered in the IMCR. Colin is leading this effort and can be reached at colin.smith@wisc.edu if you have comments or questions.
+
[http://vocab.lternet.edu/vocab/registry/index.php The IMCR Controlled Vocabulary (CV)] is designed improve discoverability of registered software. The IMCR controlled vocabulary is organized around [https://www.dataone.org/data-life-cycle the data life cycle] with the notable exclusion of the "analysis" phase of the cycle (we consider analysis tasks outside the scope of information management and thus the IMCR). Extension of the controlled vocabulary to "science domain" is underway. Contact Colin (colin.smith@wisc.edu) if you have comments or questions.
  
 
==== Action items ====
 
==== Action items ====
* Use the [http://vocab.lternet.edu/vocab/registry/index.php IMCR CV]
+
* Extend the CV to cover "science domain". Anyone is welcome to contribute to [http://bit.ly/imcrvocab this working document] in which development of the "science domain" categories and terms is occurring.
* Develop the IMCR CV by suggesting new categories, terms, and relationships between terms to Colin, or contribute directly to this [http://bit.ly/imcrvocab Google sheet]
+
* Refine the CV. Suggest new terms and definitions or refine existing ones by contacting Colin (colin.smith@wisc.edu).
 
* Get software terms form Kepler ontology (Kristin is doing this).
 
* Get software terms form Kepler ontology (Kristin is doing this).
* Expand CV coverage to all relevant software attributes:
 
** Domain specific keywords (e.g. community survey, meteorological).
 
** Software maturity (e.g. development, staging, production)
 
  
==== Resources ====
+
==== Links ====
[https://groups.niso.org/apps/group_public/download.php/12591/z39-19-2005r2010.pdf Guidelines for the construction, format, and management of monolingual controlled vocabularies]. See sections 5.3 and 6.32.
+
* [http://vocab.lternet.edu/vocab/registry/index.php The IMCR Controlled Vocabulary]
 +
* [http://bit.ly/imcrvocab CV working document]
 +
* [https://groups.niso.org/apps/group_public/download.php/12591/z39-19-2005r2010.pdf Guidelines for the construction, format, and management of monolingual controlled vocabularies]

Revision as of 11:16, October 14, 2018

Return to IM Code Registry main page


Controlled vocabulary

Overview

The IMCR Controlled Vocabulary (CV) is designed improve discoverability of registered software. The IMCR controlled vocabulary is organized around the data life cycle with the notable exclusion of the "analysis" phase of the cycle (we consider analysis tasks outside the scope of information management and thus the IMCR). Extension of the controlled vocabulary to "science domain" is underway. Contact Colin (colin.smith@wisc.edu) if you have comments or questions.

Action items

  • Extend the CV to cover "science domain". Anyone is welcome to contribute to this working document in which development of the "science domain" categories and terms is occurring.
  • Refine the CV. Suggest new terms and definitions or refine existing ones by contacting Colin (colin.smith@wisc.edu).
  • Get software terms form Kepler ontology (Kristin is doing this).

Links