Add a Calendar Date to a Procedural Record
User Story
User can manually add a date to a date field in an procedural record, such as an Intake, Acquisition, or Loan. Depending on the purpose of the field, this date may represent the date on which the activity occurred, or another date of significance to the activity (e.g. a return date for an intake or loan).
Fields for Release 0.4:
Intake > Entry date
Intake > Return date
Intake > Field collection date
Intake > Insurance renewal date
Intake > Location date
Intake > Condition check/assessment date
Acquisition > Accession date
Acquisition > Acquisition date
Once entered, it should be possible to further edit the date, both before and after changes to the object record are saved.
The user should be guided to enter data in a manner that ensures that only a valid calendar date may be entered. This may involve choosing a date via a date picker widget, but does not require that approach. If a date picker is to be added at a later time, rather than as part of the initial implementation, a new user story should be created accordingly.
The date is assumed to be a calendar date in the default, Gregorian calendar system.
The date represents a full day (e.g. any time instant belonging to a single calendar date). It is not a timestamp, and is not accompanied by a time of day.
The default assumption about the time zone in which the date falls in TBD. Once made, it will need to be further described in this user story.
This story is not about:
- Customizing or personalizing whether a default date should be presented to the user, or whether the contents of a date field should initially be blank.
- Adding a date to any type of record other than procedural records, such as object or organizational records.
- Adding association information to a date (e.g. "created", "manufactured", "sold").
- Adding certainty information to a date (e.g. "circa", "before", "probably", "early").
- Adding qualifying information to a date (e.g. "+ or - 150", "approximate").
- Choosing an era, epoch, dynasty, event, or other named time period.
- Associating two date fields within a record as a date range.
- Handling logic associated with date ranges, such as returning records that fall within a range.
- Adding a timestamp, or any other date-time representation that includes both date and time components.
- Specifying a calendar system that differs from the default.
- Customizing or personalizing a date and time representation format (e.g. "2009-10-29" or "10/29/2009" [as commonly used in the USA]).
- Setting a default time zone for the system.
- Customizing or personalizing the time zone in which dates and times are displayed or entered.
If any component of the functionality listed above is required, now or in the future, a new user story should be created accordingly, and linked from this story in the Related User Stories section, below.
See also:
Fluid Date Time Picker, linked from object data entry wireframes.
Dates in Object and Procedural Records
Related User Stories:
Add Date Information to an Object Record