Skip to end of metadata
Go to start of metadata

Introduction

The early adopters of CollectionSpace represent a range of different museum communities of practice. In order to facilitate adoption that takes advantage of this initial work on configuration, schema extensions, and in some cases customization, we have developed a set of recommended domain extensions and profilesdomain extension is a group of fields added to a procedure or authority to support the work of a specific community of practice, such as fine art or anthropology. Extensions to more than one procedure or authority are referred to collectively as extension setsA group of procedures, authorities, and domain extensions combined to support the work of a specific community of practice are referred to as that community's profile. Often, procedures and authorities within the profile may be configured, or slightly changed, to better support the needs of that community of practice.

Botanical Garden Extension Set and Profile

The CollectionSpace DRAFT botanical garden extension set and profile is based on work done by the University of California Botanical Garden at Berkeley as part of their CollectionSpace implementation. Several extensions for Cataloging have been created, including accession use, accession attributes, and determination history; these extensions can be viewed via the maps linked below. In addition, new procedures designed to manage propagation, the creation of vouchers and pot tags, and distribution have been created. The next step in the process is taking these draft maps and sharing them with the wider botanical garden community in order to:

  • ensure that the majority of fields necessary to properly document and manage a botanical garden are present
  • ensure that fields that are in the CollectionSpace common data model but not relevant to botanical gardens are removed
  • ensure that deployment-specific fields, useful only to the organization originating the extension set are removed (in this case, the UC Botanical Garden)

How to Review and Comment

  1. Visit the Review and Comment wiki page for each extension
  2. Review the fields present, and ask the following questions in relation to your organization:
    1. Is this extension necessary to manage our collections?
    2. If so, are all the fields needed to manage our collection present? If not, what would we need to add?
    3. Are there field that are not useful? If so, what would we delete?
  3. Contribute your comments directly via the comment box at the bottom of the wiki page
  4. Stay tuned for further iterations as community critiques are factored in

Extension Name

Review and Comment Page

Cataloging - Determination History Extension OnlyDetermination History Extension Review and Comment Page
Cataloging - Annotation Extension OnlyAnnotation Extension Review and Comment Page
Cataloging - Accession Attributes Extension OnlyAccession Attributes Extension Review and Comment Page
Cataloging - Accession Use Extension OnlyAccession Use Extension Review and Comment Page
Cataloging - Locality Extension OnlyLocality Extension Review and Comment Page
Cataloging - Common Fields + All ExtensionsCataloging Review and Comment Page
VoucherVoucher Review and Comment Page
Current LocationCurrent Location Review and Comment Page
Pot TagPot Tag Review and Comment Page
PropagationPropagation Review and Comment Page
DistributionDistribution Review and Comment Page

Additional Procedures and Authorities; No Extensions Recommended

 

Procedures and Authorities not Recommended for the Botanical Garden Profile

Data and Configuration Maps

To learn more about how CollectionSpace Data and Configuration Maps are formatted, visit the Configuration and Data Map Templates page.

  • No labels