Scheduler Service Description and Assumptions

Description

The Scheduler Service supports the simple description of individual and recurring events that can have some action(s) associated with them.

At some later point, this service may also need to import or export events to and from external calendaring services.

Two examples:

• This service may be used to schedule system events, such as sending a Notification, at a specified future date or time.

• This service may also be used to maintain calendars of significant institutional events, such as exhibits, or to import events from those calendars for use within the CSpace system.

Assumptions

• Try to be explicit and exhaustive, but not pedantic.
  • Patrick Schmitz (Unlicensed): If there is an active discussion or comment, you may want to call it out as a sub-bullet. This example also uses a color macro to call it out, and provides a link to a given user to indicate that this is a particular contributor's position.

Subtopic

• More assumptions around peripheral subject
  • Ex. An example of the case
• Yet another assumption
  • Details of the assumption
    • Nitty-gritty detail 1
    • Nitty-gritty detail 2

Key Concepts

• Especially things that become common sense, and so usually missed by new reviewers

Dependencies

• This service may have dependencies on a Date and Time utility service.
• A Notification service may depend on this service.

Background Documentation

• If we have notes from community design meetings, link to them here.
• If we have relevant sections in Spectrum or another such document, link to them here (or cite section numbers, etc.)

Key Team Members

• (Name(s) of members) is/are the primary tech team member(s) for this service
• Need to identify the community members acting as Domain Experts.