Taxonomy

 

happy-taxonomy.jpgThe

Coherence Group taxonomy service is designed to help companies create taxonomies for their web-based applications to increase the "findability" of content. We are experts at understanding the information retreival requirements of our clients and at building taxonomies that enable precise retreival of information.

Working with taxonomies requires an understanding of the terms used to describe the work output and the different types of approaches:

A controlled vocabulary is a list of terms that have been enumerated explicitly. All terms in a controlled vocabulary should have an unambiguous, non-redundant definition.

A taxonomy is a collection of controlled vocabulary terms organized into a hierarchical structure. Each term in a taxonomy is in one or more parent-child relationships to other terms in the taxonomy. There may be different types of parent-child relationships in a taxonomy (e.g., whole-part, genus-species, type-instance), but good practice limits all parent-child relationships to a single parent to be of the same type.

A thesaurus is a networked collection of controlled vocabulary terms. This means that a thesaurus uses associative relationships in addition to parent-child relationships. The expressiveness of the associative relationships in a thesaurus vary and can be as simple as ?related to term? as in term A is related to term B.

People use the word ontology to mean different things, e.g. glossaries & data dictionaries, thesauri & taxonomies, schemas & data models, and formal ontologies & inference. A formal ontology is a controlled vocabulary expressed in an ontology representation language. This language has a grammar for using vocabulary terms to express something meaningful within a specified domain of interest.

We work with our customers to apply metadata and taxonomies to solve the most complex search problems. Typically our work includes the following steps:

    1. Taxonomy Workshop: A workshop to help customers understand information architecture concepts, and connect business needs to technical challenges related to taxonomy creation
    2. Define the terms of art: Define the tagging process, metadata usage, taxonomy ownership role definition, metadata change management strategy,
    3. Requirements Analysis: Determining and documenting the information needs and the functional and technical requirements the proposed  taxonomy must meet 
    4. Build Taxonomy: Use the requirements analysis to build taxonomy including the metadata specification, usage of existing industry taxonomies, and integration into the chosen taxonomy platform
    5. Iterate Taxonomy with users: Review the taxonomy with users and correct any misunderstandings
    6. Training: Train staff to ensure successful transition and maintenance of all work, and ensure staff tasked with owning taxonomy is prepared to continue developing it on an ongoing basis