Priority Features

Features we'd like to add before the end of the semester (or think we need to add).

Assignments

• DONE Duplicate Detection [CF]
• DONE Improved tag cloud - Only uses the fifty or so most popular tags [CF]
• DoneClean the code - Format and comment to PEAR standards [AH]
• Send to Google Calendar [DK]
• Sanitize Input - Input is sanitized in some places, but not others. [DK]
• • done Location Management* - Revise the Category management code to do the same for locations. [TK]
• Hide this event - Personal [TK]
• Grab events from primary campus calendar - Note that you have to be careful not to grab the same event repeatedly. [JL]
• DONE Incremental filtering - Users can continually refine their selection of events. E.g., they can click on a location, then on a category, then on a tag, then on another tag and see events that meet just those criteria. They can also selectively remove each criterion. (Amazon and B&N provide similar features.) [JTL]
• Calendar View [ARS]
• DONE Report spam - Users can mark events and comments as spam and the administrator can easily see what has been identified as spam and remove/hide it. [EU]

Other Large Things For Later Work

• Grab events from the memo
• Private Tags - Users can add tags that only they see (mostly used for filtering). Needs to include appropriate search, too.
• Remove Redundancies - A good database should not have redundant information, since such redundancies lead to errors. For example, the category table does not need a count of requests, since we can get that by using a select(count) type query. Remove those and other redundancies. Other redundancies in the database: Event popularity (can be found with a count of attendees), user email (we get it from their display name)
• Super advanced searching with Boolean logic

Other Smaller Things for Later Work

• Skins - Let a user choose which CSS they would like
• View my events - Obvious
• Sort events by Number attending - This way, users can find popular events.
• Expand administrator tools - Manage locations like categories are currently managed; Streamline adding categories and locations to the Db.
• *Some sort of descriptive statement, either on the home page or elsewhere, describing the format and purpose of the calendar. Also possibly a record of updates, like plans?
• Social Media Support - Click on a button and tweet or share on Facebook
• *Delete user not yet implemented
• *Forgot password not yet implemented
• *Recommend events based on user's past attended events
• *General "contact administrators" link for questions, etc.
• *Detail view for users, displaying created events