...

Brief Description

...

...

Describes an entity for a concept, with structure among concepts.

For a full description, visit the Service Description and Assumptions page.

Assumptions

{multi-excerpt-include:Concept Service Description and Assumptions|name=brief-assumptions|nopanel=true}

...

• 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.

References

Vocabulary and Authority Overview
Concept Service Description and Assumptions
Concept Service Entity Diagrams
ConceptAuthority Schema, ConceptAuthority Schema and Mockup - UCB Version

REST-based API

The Concept Service offers a REST-based Application Programming Interface (API) to CRUD (create, read, update, and delete) operations on individual ConceptAuthority instances, and on the associated Concept instances. These follow the Common model for CollectionSpace REST services.

Note that the Concept instances are not directly "addressable"; they can only be accessed via the parent ConceptAuthority.

...