Date and Time User Story Summary

User Story Summaries are for capturing notes about broad user stories, or user story themes, related to a particular topic. These may be used as inspiration and source material for creating specific user stories, which may in turn be implemented in various system releases. Some of these broad stories, or themes, may not be implemented in the 1.0 release.

Date stories

User can manually add a date or span of dates to an object, procedural, or organizational record

Use can choose a date or span of dates from a date picker to add to an object, procedural, or organizational record

User can add an qualified date to an object, procedural, or organizational record (e.g. circa, before, probably, early)

User can add an era, epoch, dynasty, event, or other named time period to an object, procedural, or organizational record (may be supported by a controlled list or vocabulary)

User can create (or system can supply) a display date which summarizes or aggregates other date fields

User can specify the calendar system if it differs from the default

User can view a datestamp on system-generated reports, including audit trail

Sysadmin can set the default calendar system (e.g. Gregorian, Julian)

Time stories

User can manually add a time or range of times to an object, procedural, or organizational record

Use can choose a time or span of time from a time picker to add to an object, procedural, or organizational record

User can specify the time zone if it differs from the default

User can view a timestamp on system-generated reports, including audit trail

Sysadmin can set the default time zone

Discussion questions

Do we want to restrict the formatting of entered dates, e.g. YYYYMMDD, or will CSpace validate & convert to ISO-standard format? Nice phrasing from the services description: This behavior generally confirms with Jon Postel's maxim, "Be liberal in what you accept, and conservative in what you send."