Local History and Material Culture 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 Local History and Materials Culture domain extension set
The CollectionSpace DRAFT local history and material culture domain extension set is based on work done by the Pope County Historical Society. Extensions for Cataloging 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 Pope County. The next step in the process is taking these draft maps and sharing them with the wider local history and material culture community in order to:
- ensure that the majority of fields necessary to properly document and manage a local history collection are present
- ensure that fields that are in the CollectionSpace core data model but not relevant to local history collections are removed
- ensure that deployment-specific fields, useful only to the organization originating the extension set are removed
How to Review and Comment
- Visit the Review and Comment wiki page for each procedure and vocabulary
- Review the fields present, and ask the following questions in relation to your organization:
- Is this procedure or vocabulary necessary to manage our collections?
- If so, are all the fields needed to manage our collection present? If not, what would we need to add?
- Are there field that are not useful? If so, what would we delete?
- Contribute your comments directly via the comment box at the bottom of the wiki page
- Stay tuned for further iterations as community critiques are factored in
Extension Name | Review and Comment Page |
|---|---|
Cataloging - Cultural Care Extension | Cultural Care Extension Review Page - LHMC |
| Any Procedure - Transport Extension | Transport Extension Review and Comment Page - LHMC |
| Cataloging - Photograph Template | Configuration and Data Map - Cataloging - Local History Draft - Photograph Template |
Cataloging - Archival Materials Template | Configuration and Data Map - Cataloging - Local History Draft - Archives Template |
| Cataloging - Quick Catalog Template | Configuration and Data Map - Cataloging - Local History Draft - Quick Catalog Template |
| Cataloging - Ethnographic Materials Template | Configuration and Data Map - Cataloging - Local History Draft - Ethnographic Materials Template |
| Cataloging - Library Materials Template | Configuration and Data Map - Cataloging - Local History Draft - Library Template |
Additional Procedures and Authorities; Configuration but No Extensions Recommended
Procedures and Authorities not Recommended for the Local History and Material Culture Profile
Procedure or Authority Name | Configuration and Data Maps |
|---|---|
Work Authority | Configuration and Data Map - Work Authority |
Reports
As important as the ways in which we get data into the system are the ways in which we get data out. On the Reporting Review and Comment Page - LHMC, you can post sample reports, make requests for useful reports, and more.
Data and Configuration Maps
To learn more about how CollectionSpace Data and Configuration Maps are formatted, visit the Configuration and Data Map Templates page.