User Story
When [creating a new Object record from an existing Acquisition record], the system will default to the next available item number in the Acquisition ID string.
Example: The user creates a new Acquisition, the 18th lot acquired by the museum during the year 2009. According to the museum's pattern for acquisition numbers, this acquisition receives the number "2009.18".
When the user creates an initial object record based on that acquisition, the ID value 2009.18.1 will be auto-filled in the data entry form. Subsequent items added to the intake would be assigned 2009.18.2, 2009.18.3, and so on.
See also:
Rough Work Estimate: 1 ideal work days
Related User Stories:
[Create New Object Record from Acquisition Record]
Create New Acquisition ID based on Existing Object 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