User Story
User will be able to fill out, Cancel, and/or Save an acquisition form like this wireframe , in which the following sections are functional: Object entry Information (no vocabularies, just Museum-ID/Number, dates, and strings), and Acquisition Information (no vocabularies, just Museum-ID/Number, dates, and strings). All other sections (Dates, and all right side panels, as well as all banner navigation) will be non-functional, or may not appear.
See also: Object entry, Numbers: Accession numbers, Intake, Acquisition, Vocabulary + Authority Control
Services Stories (not already supported)
- Acquisition service:
- Service consumer can create a new Acquisition record
- Service consumer can retrieve an existing Acquisition record by CSID
- Service consumer can update existing Acquisition record by CSID
- CollectionObjectAcquisition service:
- Service consumer can check if a CollectionObjectAcquisition instance exists associated to a CollectionObject (by CSID).
- Service consumer can create a CollectionObjectAcquisition instance, associating a CollectionObject to an Acquisition Object.
- Service consumer can retrieve a CollectionObjectAcquisition instance, by CSID.
- Service consumer can retrieve a CollectionObjectAcquisition instance associated to a CollectionObject CSID.
- Service consumer can persist changes to existing CollectionObjectAcquisition instance by CSID
- ID service
- Service consumer can request patterns appropriate to Acquisition activity
Application Layer Stories (example guesses - needs attention)
- Application consumer can fetch UISpec for Acquisition page for a new Acquisition
- Application consumer can fetch UISpec for Acquisition page for an existing Acquisition
- Application consumer can create new Acquisition record
- Application consumer can save changes to existing Acquisition record
UI Layer Stories
- Essentially the same as the top level story???]