Object Intake - Basic entry information

Story: User will be able to 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.

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 _Should we separate the Intake and CollectionObject service stories here?
- CollectionObject service:
  - Service consumer can retrieve Intake record for a CollectionObject
- ID service
  - Service consumer can reserve next available number in a given pattern
  - Service consumer can release a reserved number in a given pattern
- Intake service:
  - Service consumer can create a new Intake record.
  - Service consumer can update existing Intake record.
  - Service consumer can delete existing Intake record.

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???