User Story
When creating a new Acquisition record from an existing Object record, the system will default to the Acquisition ID portion of the item number.
Example: The user creates a new Object, and has the system assign the next available item number using the Acquisition ID pattern. According to the museum's pattern for acquisition numbers, this object receives the number "2009.18.1".
When the user creates an acquisition record based on that object, the ID value "2009.18" will be auto-filled in the acquisition data entry form.
See also:
Rough Work Estimate: 1 ideal work days
Related User Stories:
Create New Object ID based on Existing Acquisition ID
Derived Stories:
Service Layer Stories
Service Story: <Describe a bit of functionality from the perspective of the service consumer.>
Related JIRA Task: <Link to a JIRA task at issues.collectionspace.org>
Service Story: <Describe a bit of functionality from the perspective of the service consumer.>
Related JIRA Task: <Link to a JIRA task at issues.collectionspace.org>
Application Layer Stories
Application Story: <Describe a bit of functionality required by the UI layer components as clients.>
Related JIRA Task: <Link to a JIRA task at issues.collectionspace.org>
Application Story: <Describe a bit of functionality required by the UI layer components as clients.>
Related JIRA Task: <Link to a JIRA task at issues.collectionspace.org>
UI Layer Stories
UI Story: <Describe a bit of end-user functionality and interaction with UI components.>
Related JIRA Task: <Link to a JIRA task at issues.collectionspace.org>
UI Story: <Describe a bit of end-user functionality and interaction with UI components.>
Related JIRA Task: <Link to a JIRA task at issues.collectionspace.org>
Add Comment