Date And Time Service Implementation Plan

Owned by Aron Roberts (Unlicensed)
Last updated: Feb 04, 2009
2 min read
Date And Time Service Home

Boilerplate structure and text below

Much of the page structure and text below this point is boilerplate, copied in from the relevant New Service template. Further work is needed to complete this page.

Plans

This may begin with prose, and expand into something like a project plan at some point. This need not be a complete schedule, but it will make sense to include the steps and approaches, milestones, etc.

Dependencies

  • The Joda-Time framework would likely represent an excellent foundation for a Date and Time Service.

    Joda-Time is a high quality replacement for - and a vastly more functional superset of - the built-in date and time-related packages in core Java. JSR 310, a Java Community Process to improve Java's date and time routines in Java 7 or beyond, is being co-led by a key developer of Joda-Time. In addition, this framework is licensed under an Apache 2.0 license, which may potentially be compatible with CollectionSpace licensing requirements.
  • iCal4j is the most full-featured Java framework for generating calendar event data in iCalendar (RFC 2445, currently undergoing minor revision as RFC 2445 bis), an Internet standard transport format.

    This framework may be of interest if there should be a future CollectionSpace service-level requirement to emit calendar events; so that, for example, events related to loans, exhibits, and conservation activities might be automatically kept updated within institutional or Internet-hosted calendars, or offered as calendar event feeds. iCal4j is licensed under a BSD license (link is to a representative template page).

Implementation's Test Plan

This should describe how the Date And Time Service implementation will be tested. The testing here could include white box style test, unit test, and/or integration tests.

Data Models