...
- Date and time addition and subtraction, in part in support of such concepts as "last week," "this month", and "90 days from now."
- Generating timestamps at the current instant.
Date and
...
Time Ranges
- Calculating the duration of date and time ranges, in support of time-bounded entities, such as loans, exhibits, and temporary access permissions.
- Identifying whether a specific date and time falls before, within, or after a date and time range.
Formatting and
...
Validation
- Formatting dates and times, and converting between formats.
- Validating entered dates and times.
Time
...
Zones
- Conversion between local time zones and Coordinated Universal Time (UTC).
Named time periods
- Association of named time periods with calendar systems.
- Identifying whether a specific named time period falls before, within, or after a date instant, or another named time period.
...
- Generating date-related parts of ID numbers.
- Facilitating searches and reporting based, in part, on date and time ranges (e.g. "collection objects accessioned within the last week" or "collection objects scheduled for conservation activity during March 1-20 of the current year").
- Providing notifications at significant time points related to time-bound events, such as loans, exhibitions, and temporarily-granted access permissions.
- Supporting customization (including Internationalization) of displayed and entered dates and times.
- Support for import of dates and times.
- This service will not attempt to represent dates and times, or
AssumptionsAssumptions
Calendaring System
- Basic date and time operations, and formatting and validation operations, will default to using the Gregorian Calendar system.
- It may be possible, during implementation, to create an abstraction layer to more readily permit these operations on other calendar systems (e.g. Islamic, Hebrew), in the event that might be a future requirement for the CollectionSpace system.
Basic Date and Time Operations
- Basic date and time operations will apply to system dates and times. These include, but are not limited to: the dates and times of meaningful collections management events modeled by the CollectionSpace system, such as the date and time that an object was accessioned, loaned, exhibited, moved, or covered by conservation activities; dates and times related to an insurance contract or shipping manifest; or a date and time range during which temporary access permissions might be granted to a Principal.
Calendar Systems
- This service will default to using the Gregorian Calendar system.
It may be possible, during implementation, to create an abstraction layer to more readily permit the use of other calendar systems (e.g. Islamic, Hebrew) for representing system dates and times, in the event that might be a future requirement for the CollectionSpace system.
Formatting and Validation
- This service will inherently accept any of several widely-used input formats for dates and times.
...
- This behavior generally confirms with Jon Postel's maxum, "Be liberal in what you accept, and conservative in what you send."
Time Zones
- Deployments of the CollectionSpace service may be hosted in a different time zone than users of the service.
...
- Date and time instants SHOULD be converted to, and stored in, then-current Universal Coordinated Time ( UTC).
- One or more date- and time-sensitive frameworks or libraries in the CollectionSpace system, such as the core date and time framework, will require occasional updates to time zone data.
...