The purpose of this project is to develop a ‘rolling calendar’ function. A rolling calendar is a recurring calendar event, and associates pre-formatted document template and template meta data so that specific document topics and related notes can be ‘rolled over’ to appear in the next version. An example is a meeting agenda, where items are added to the agenda, and then resolved in one way or another. The remaining open topics are ’rolled over’ to the next agenda for the same building. Other items not rolled over are archived in the database. Users with specific ACL’s (access control levels) determine which items are rolled over. Agenda items will be printed as Meeting Minutes, and action items in a ToDo List; both in PDF format.
All events are calendar-driven. Each event is to be classified with appropriate meta data including supporting documents that are created or accessed when such an event is added to the calendar:
1. First event and related docs - rolling agenda
2. Second supporting doc for this event - templates
3. Third Supporting Doc, To Do list generation
This means that within a supporting doc (which itself is a data object related to the event type), there are “nested” or parent-child data objects - each to do is its own object
4. Each object can have notes attached - question - form part of the record or as an adjunct to the object?
SEE DOCUMENT ATTACHED