Concept Service Description and Assumptions

Description

We will want to associate concepts with different attributes of objects and procedures.

Also need to describe:

• The hierarchic nature of Concepts

Assumptions

• Concepts can have a default generic use of concepts or terms (providing a flat namespace). 
• However, Concept is designed to allow multiple instances to provide more specific namespaces (e.g., material, technique, culture).
• The initial version will allow for a single term per Concept record for version 2.3 of CollectionSpace.  Refactoring of authorities to support preferred/non-preferred term will allow variants of terms to be supported.

Key Concepts

Dependencies

Background Documentation

• Concept Authority - Functional Requirements

Key team members

• Jan Eklund is the primary functional expert defining the system