Skip to end of metadata
Go to start of metadata

Definition

Documenting and managing the addition of objects and associated information to the collections of the organization and their possible accession to the permanent collections.

Requirements

  • Ensure that written evidence is obtained of the original title to an object and the transfer of the title to the acquiring organization;
  • Enable the reconciling of acquisition records with objects as part of retrospective
    documentation, audit and inventory activity;
  • Ensure that a unique number is assigned to, and physically associated with, all objects;
  • Ensure that accession registers are maintained, describing all acquisitions and listing them by number;
  • Ensure that information about the acquisition process is retained;
  • Ensure that donors are made aware of the terms on which their gift or bequest is accepted by the organization;
  • Ensure that collecting complies with the organization's collecting policy, and does not
    contravene any local, national or international law, treaty or recognized code of practice;
  • Ensure a copy of the information in the accession register is made and kept up to date.

Standards, Guidelines + Use Cases

Use Cases and Community Design Workshop Notes

American Museum of Natural History Paleo Portal: Acquiring

CHIN Humanities Data Dictionary: Registration

CHIN Natural Sciences Data Dictionary: Source

Matters in Media Art: Accessioning

Spectrum Procedure: Acquisition

Visualization from the CIDOC CRM:

Wireframes

Wireframes - Acquisition

Services

Acquisition Service

CollectionObject Service

ID Service

Fields

Acquisition Schema

User Story Summary

Acquisition Stories

Acquisition User Story Summary

Procedures User Story Summary


Definition and requirements from:
Spectrum Version 3.1
Created and Maintained by CollectionsTrust
http://www.mda.org.uk/spectrum.htm

1 Comment

  1. In our work as implementers here at the SMK we found it necessary to make a revision check and comparison of the functional requirements, the schemas, the wireframes, and the current version 1.0 alpha. The purpose of this work was to establish any discrepancies and inconsistencies in the implementation of CollectionSpace programme regarding the eight core procedures of version 1.

    For Acquisition we have the following comments:

    Regarding requirements:

    These requirements are not met in the schema or elsewhere:

    • Ensure that a unique number is assigned to, and physically associated, with all objects
    • Ensure that the collecting complies with the organization's collecting policy, and does not contravene any local, national or international law, treaty or recognized code of practice

    Regarding the schema:

    Should information about the acquiring institution (i.e. the new/current owner (SMK)) be part of any schema? Or is this information inherent? If the acquiring institution should be recorded in the acquisition record, should the definitions of 'Owner' and 'Acquisition source' be edited?

    Regarding CS version 1.0 alpha:

    Generally we find that the strong graphic design of the wireframes is lost in the present version 1.0 alpha.