Description
The Centralized Calendar came about because several user groups exist in Utah. Many of the groups vary in subject, but others are large distances (>30miles) apart. Due to this fact, many users desired to go to meetings that they were interested, but the information wasn't available about these meetings or their topics. The Centralized Calendar is a solution to this problem.
This page is to solicit ideas for what a Centralized Calendar should contain. So feel free to suggest items below, we'll take what we're given and present it at this Wednesday's Calendar Interoperability meeting.
Definitions
- Event is defined as any activity provided by the accepted Submitters
- Submitter is defined as an individual with a login. Submitters can submit events to an event queue.
- Readers aggregate and choose the submissions to which they subscribe
- A Delivery profile is a simple page allowing the reader to subscribe/unsubscribe from a list of submitters
Features
- Simplistic and intuitive user interface
- Add/remove groups from your delivery profile
- Breakdowns of groups by topic and/or geographic location (eg. Language vs OS, Social vs Business or Provo vs SLC)
- Multiple topics allowed, but only one geographic location
- Google Maps integration to show distance from a particular reader
- Readers may choose the tags/labels for a particular submission
- Make it easy for a Group to add their calendar to the aggregator
- Simple add and automated approval process
- Multiple delivery methods
- Web, RSS, iCal, Twitter, Mailing List, Facebook, etc. as plugins.
- Sync!! (I want it on my bb, palm, etc!!!!!)
Moderation queue, who can submit events & meetings
- Moderation is nothing more than approval or disapproval of feeds