Introduction

These are the index cards filled out at codesprints in early 2008. One paragraph per card. Checked-off cards listed in strikeout

Current development issues and projects can be found in the tracker.

Pending

Model

• Events should have an end time or duration.
• Events and venues should remember their source.
• Events, sources, and venues should be taggable.
• Events should be able to have multiple links.

Controller

• Venue fields should suggest existing values.
• Events should be selectable by date range.
• Events should be searchable. (name, description, tags, venue)
• Users should be able to combine keyword and date based searches.

View

• The home page should show a selection of upcoming events.
• The home page should show the 5 most recently added events.
• The home page should include simple forms for adding and inserting events.
• A dynamic thumbnail calendar widget is needed for several views.
• Venue name fields should suggest existing values.
• There should be a detailed form for editing events.
• There should be a detailed form for editing venues.
• Date fields should display a dynamic calendar widget.
• When viewing an event, venue, or source, a user should see an edit link.
• There should be a detailed form for editing sources.
• After importing a calendar, users should see what was imported and be asked to save the source.
• Users should be able to combine keyword and date based searches.
• Events should be selectable by date range.
• Events should be searchable. (name, description, tags, venue)
• Venue pages should display a short list of events they are hosting.
• Users should be able to combine keyword and date based searches.
• Users should be able to search for events by keyword and by date.
• Users should be able to search for events by keyword and by date.

Other

• The home page should have a clear, concise, description of the project.

• Fill in wiki page on event duplication
• trackback using Calagator URLs as unique trackback IDs?
• Research City of Portland business lising and other venue sources
• interface expose hCal on Events page
• The system should import iCalendar
• Justification:
• Data quality
• No accounts
• Model for aggregation on a topic
• PortlandTech what people are doing.
• User
• no accounts
• no preregistration
• connecteness
• Cultures
• Business
• New Media
• Hardcore Tech
• Newbies
• targeting specific users, restricting scope, gives us focus; we can refcosue or generalize later
• Feature Geographic location for events
• Show the content of events not just the time/place
• Check out NY Times calendar output
• Interface
• Events scheduler
• Events gardener
• Admin
• View of Calendar
• What ways can we display a list of events? Are some options more or less suited to our needs?
• Core - modules for import
• How can the system tell if events are duplicates to be merged?
• How can the system tell if imported events are recurring?
• What standarded formats are external calendars providing? iCal, hCal, API, ics, vCal
• The system should be able to export an iCalendar feed.
• The system should import iCalendar
• The system should be able to import an hCal event from website.
• Documentation Take screenshots of existing calendar sources
• The user should see a non-scaffolded events page (index & show)
• The system should have an event model with event name, time, and location
• The system should have a place/venue model.
• A user should be able to add an event
• A user should be able to view a list of all events
• Research Calendar formats in use: messy, HTML, RSS, hCal, trumba
• The system should create a a venue record from locations on an imported event.
• Create wiki page for email template