History of Events Package Overhauling Plan
Version 11
Events Package Overhauling Plan
This is some speculation on what would make EventsPackage better
Events are a complicated thing. This page is a resource for brainstorming and planning a professional events package for bitweaver. Please feel free to append ideas, resources, or whatever else may make an events package better.
While this page defines the needs or a possible new implementation for an event calendar system, also have a look at CalendarResearch for an evaluation of existing solutions.
People Thinking and Working On This
If you want to join the fun on a very dedicated level so as to see implemention of this through to reality, add your name or handle here with a method of contact.wjames5: wjames5-at-nyc.rr.com
michael dean: mdean@sourceview.com
Big Issues
- Event Recurrance
See the first comment by James at the bottom of this page - Invitation and Viewing Permissions Management
- Notification Management
Possible Table Changes
EVENTS TABLE
event_idcontent_id
title - Liberty Package
body/data - Liberty Package
description
start_time
end_time
recurance (will take a stringe of days 0-7, weeks, months, years)
location (text)
lat - Geo Package
lng - Geo Package
category - Pigeonholes Package
comments - Liberty Package
invite_guests - T/F
image
url
permissions - Liberty Package
GUESTLIST TABLE
event_idname
email_address
status
NOTE: The above tables include fields which might be covered by other packages and thus not really be in the table. They are noted with their dependent package.
Additional References
- iCalendar
A widely adopted standard
About
Specification - Mozilla Calendar
- Google Calendar Data API
- Drupal Events