Herbaria Extension Set - DRAFT

Introduction

The adopters of CollectionSpace represent a wide range of different museum domains. In order to facilitate adoption that takes advantage of configuration work completed by existing implementers, extension sets supporting specific communities of practice are being designed and developed by the CollectionSpace program team. The extension sets, consisting of schema extensions, procedures, and vocabularies supporting domain-specific practices (e.g. propagation for botanical gardens or digital migration for variable media), are available on this wiki. Development work is underway that will allow new implementers to select a community-vetted extension set as the starting point for their own installation of CollectionSpace.

Draft Herbaria domain extension set

The CollectionSpace DRAFT herbaria domain extension set is based on work done by the University and Jepson Herbaria at the University of California, Berkeley as part of their CollectionSpace implementation. Extensions for Cataloging, Loans In and Out, and the Taxonomy Authority have been created; these extensions can be viewed via maps which compare the default CollectionSpace data model to several community standards as well as the schema implemented at UCJEPS. The next step in the process is taking these draft maps and sharing them with the wider herbaria community in order to:

• ensure that the majority of fields necessary to properly document and manage an herbarium are present
• ensure that fields that are in the CollectionSpace core data model but not relevant to herbaria are removed
• ensure that deployment-specific fields, useful only to the organization originating the extension set are removed (in this case, UCJEPS)

How to Review and Comment

1. Visit the Review and Comment wiki page for each procedure and authority
2. Review the fields present, and ask the following questions in relation to your organization:
   1. Is this procedure or authority 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
   
   

Additional Procedures and Authorities; No Extensions Recommended

Data and Configuration Maps

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