History of Events Package Overhauling Plan
Version 1 | Current version | |
---|---|---|
Proposed Table ChangesEVENTS TABLEevent_idcontent_id title body description start_time end_time recurance daily weekly monthly yearly location (text) lat - Geo Package lng - Geo Package category - Pigeonholes Package comments - Liberty Package invite_guests - T/F image url permissions GUESTLIST TABLEevent_idname email_address status NOTE: Most of this could be implemented quickly, but guest stuff might come later as the security requirements and making use of email might be beyond my abilities. -wjames5 | 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 ThisIf 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 phoenixandy: andy at andystanford dot me dot uk Big Issues
Possible Table ChangesEVENTS TABLEevent_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 TABLEevent_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
|