User Story
User can create and save a new Acquisition record, as in the Acquisition schema. Only Acquisition information, Object identification information, and Date information will be supported. Only scalar and string values will be supported, with the following exceptions:
Create New Acquisition Record with Choice of Acquisition Number Patterns
Select Item from Responsible Department Term List
Select Item from Acquisition Method Term List
Related User Stories
Derived Stories:
Services Stories (not already supported)
- Acquisition service:
- CollectionObject service:
- Service consumer can check if an Acquisition record exists associated to a CollectionObject (by CollectionObject CSID).
- Service consumer can create a CollectionObjectAcquisition instance, associating a CollectionObject to an Acquisition Object.
- Service consumer can retrieve an Acquisition record associated to a CollectionObject. (Duplicate of 438?)
- Service consumer can retrieve an Acquisition record associated to a CollectionObject.
- Service consumer can persist changes to existing CollectionObjectAcquisition instance by CSID
- ID service
- Service consumer can request ID 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
Related JIRAs: http://issues.collectionspace.org/browse/CSPACE-506
UI Layer Stories
- Essentially the same as the top level story???
Related JIRAs: http://issues.collectionspace.org/browse/CSPACE-456
Related JIRAs: http://issues.collectionspace.org/browse/CSPACE-460