Story: User can fill out, Cancel, and/or Save a basic Intake form like the Intake wireframe, in which the following sections are functional: Object entry information (no vocabularies, just Museum-ID/Number, dates, and strings). All other sections (Valuation, Insurance, Condition, Location, and all right side panels, as well as all banner navigation) will be non-functional, or may not appear.
See also: Object entryNumbers: Accession numbers
Functionality
- User: Object (or group of objects) data entered into fields and stored in repository. Limited to text and non-complex numerical fields.
- Auto: ID number generated based on auto-incrementing pattern.
- Services Stories
- CollectionObject service:
- Service consumer can retrieve Intake record for a CollectionObject
- Intake service:
- ID service
- Service consumer can reserve next available number in a given pattern
- Service consumer can release a reserved number in a given pattern
- CollectionObject service:
- Application Layer Stories (example guesses)
- Application consumer can fetch UISpec for ObjectEntry page for a new entry
- Application consumer can fetch UISpec for ObjectEntry page for an existing entry
- Application consumer can create new Intake record
- Application consumer can save changes to existing Intake record
- UI Layer Stories
- Essentially the same as the top level story???
Add Comment