r49 - 05 Mar 2005 - 15:17:44 - SheilaMooneyYou are here: OSAF >  Projects Web  >  ChandlerHome > ZeroPointFivePlanning > ZeroPointFiveCalendarWorkflowsSpec

Overview

This page summarizes all the calendar related workflows we would like to support by the end of release 0.5. Since the decision was made to focus our kibble effort on a calendar centric application, our strategy is to get as much calendaring functionality done in the 0.5 release then fill out other features later in 0.6 and 0.7. Calendar goals for 0.5 include basic navigation to calendar week and day views and adding events and tasks to the calendar at the day, multi-day and specific day time level and a simple form of reminders. A simple invitation workflow will allow users to send a text email to others notifying them of an event or scheduled task.

High-level Workflows

Reviewing the Calendar

  • Use Case #1: Reviewing my calendar
  • Use Case #2: Reviewing someone else's calendar (sharing a collection that has calendar items).

Scheduling and Managing a Calendar

  • Use Case #3: Add/edit event on my calendar.
  • Use Case #4: Add/edit task on my calendar.
  • Use Case #5: Add/edit event or task on someone else's calendar.
  • Use Case #6: Invite someone to an event including a scheduled task.
  • Use Case #7: Find an available time slot to schedule an event (this use case removed for 0.5 - 11/11/04)

Sharing Calendar Information

  • Use Case #8: Sharing a calendar collection with one or more people.

Detailed Features and Workflows

Use Case #1: Reviewing my calendar

  • mac_calendar_vertical.gif:
    mac_calendar_vertical.gif

Success Criteria: Navigation to the calendar view

  • There are 2 calendar views, the week view and the day view.
    • A calender has NO list view, only week or day view.
    • The month view has been removed.
    • Remove the view selection buttons (list, day, week, month) in summary table view [TODO] add to 0.5 Summary Table View Spec.
  • A user navigates to the calendar view from the calendar kind filter or the mini calendar.
  • Select the calendar kind filter to display the calendar view.
    • By default we display the calendar week view for today.
    • The following attributes of the calendar view retain their value even when different sidebar collections are selected
      • week view or day view display.
      • visible dates (current dates visible on the calendar view)
    • Click on All or another kind filter in the sidebar reverts back to the table summary view.
  • Double click on day in mini calendar to display the calendar view.
    • Navigates to the week view or day view for the day we clicked on - persistence for the week/day selector.
    • If we have never displayed the calendar view, the default is the week view.
    • The calendar kind filter is selected automatically.
  • Navigate to the day view from the week view by clicking on the day column heading in the calendar week view. The week days still appear across the top.
  • Click on another day (in the top week bar) to navigate to a different day.
  • When in the day view, click on the "week" button in the top left hand corner of summary view to go back to the week view.
  • In day view, navigation arrows go forward and backward by 1 week. We automatically go to the day view for the next or previous week that corresponds to the day of the week we had selected ie: we are in day view for Tue Oct 5 2004, hit forward, we go to Tue Oct 12 2004.
  • In a week view, navigation arrows go forward and backward by 1 week.
  • In a week view, single click on day column for copy and paste.
  • In a day and week view, double-click to add a new item.
  • Selected header item in calendar view is blue, today's header text is in bold.
    • In week view for today, the header text for today is bold ie: Feb 22nd and the "week" header item is in blue to indicate the week view is selected.
    • In the day view for today, the header text for today is bold and the header item for today is in blue to indicate the day view is selected.

Success Criteria: Displaying the calendar week view

  • calendar_week20041117.gif:
    calendar_week20041117.gif
  • Handle anytime this day items which live in the top "week" bar under the days.
    • Anytime items have the following calendar statuses, confirmed (black), fyi (grey), tentative (dotted black line).
    • The area is fixed so if there are too many items to display - add mechanism to expand and collapse anytime area so see all events.
  • Handle event calendar statuses, confirmed (black bar), tentative (dotted black line), FYI (grey bar).
  • Handle task calendar statuses confirmed (black bar), tentative (dotted black line), FYI (grey bar).
    • Tasks on the calendar are tasks which have been stamped as an event.
  • Visual elements for calendar items
    • Color bar in top area indicating multi-day and all day events (background color).
  • Ability to print a week.
    • Prints expanded version of anytime area.
  • Distinction between tasks and events - tasks have an checkmark next to them.

Success Criteria: Displaying the calendar day view

  • calendar_day20041117.gif:
    calendar_day20041117.gif
  • Consistent UI affordances with week view.
  • Same inline editing capabilities as above.
  • Ability to print a single day.
    • Prints expanded version of anytime area.
  • Distinction between tasks and events - tasks have an checkmark next to them.

Success Criteria: Looking at the detail view.

  • calendar_detail.gif:
    calendar_detail.gif
  • Changing layout to have the detail view on the right since this looks better for the calendar views.
  • Since 0.5 has a calendar centric approach, the horizontal layout will be the default layout when we run Chandler.
  • PLEASE NOTE: Many of the fields above are not available for 0.5, review specifics for each type of detail view below for a complete description.

  • As per discussion: 01/20/05
    • For 0.5 we should try and have all the fields as text and vertically aligned, don't worry about horizontal alignment for All Day, Alarm and Status (see CalendarSpec)
    • If we click All Day - hide duration field, display start time as date only although we are storing the time behind the scenes. This means that the time may affect the order in which the event is displayed in the summary view. This is ok for 0.5.
    • "Show As" label changes to Status. Order of statuses, confirmed (default), tentative, fyi.
    • Tolerate no entry of time, date only in start time field.
    • Mimi and Sheila will think about what separate alarm choices would better suit All Day and Anytime. For 0.5, changing to use different selections will probably be too ambitious, we can append at the end. Mimi, Sheila will discuss and log a bug if necessary.

Success Criteria: The detail view for an event.

  • Stamping buttons - event (selected), task, mail
  • Title text field
  • Location text field
  • Date-time field - starts
  • Duration field
  • All Day - checkbox
  • Alarm field pulldown - ( None (default), 1, 5, 10, 30, 60, 90 min)
  • Status field - Pulldown for calendar status (confirmed, tentative, fyi)
  • Notes field

Success Criteria: Stamping an event as a mail (invite)

  • Stamping buttons - event (selected), task, mail icon changes to send arrow when we stamp an event as a mail (selected).
  • From - me
  • To - invitee list - click on button and add invitees.
  • Title text field.
  • Location text field.
  • Date-time field - starts
  • All Day - checkbox
  • Alarm field pulldown - ( None (default), 1, 5, 10, 30, 60, 90 min)
  • Notes field.
  • What happens to the statuses when we stamp this as a mail? Nothing, they still appear. They are not sent as part of the event invitation though (0.6).

Success Criteria: The detail view for a task that is stamped as an event.

  • Stamping buttons - event (selected), task (selected), mail.
  • Title text field
  • Location text field
  • Date-time field - starts
  • Duration field
  • All Day - checkbox
  • Alarm field pulldown - ( None (default), 1, 5, 10, 30, 60, 90 min)
  • Status field - Pulldown for calendar status (confirmed, tentative, fyi)
  • Notes field

Success Criteria: Stamping a task as a mail (invite)

  • Stamping buttons - event, task (selected), mail icon changes to send arrow when we stamp an event as a mail (selected).
  • From - my email address
  • To - invitee list - click on button and add invitees.
  • Title text field
  • Date-time field - starts
  • Notes field.
  • What happens to the statuses when we stamp this as a mail? Nothing, they still appear. They are not sent as part of the event invitation though (0.6).

Success Criteria: Using the Mini Calendar

  • mini_calendar_browser.gif:
    mini_calendar_browser.gif

  • PLEASE NOTE: kind filter buttons are now part of the Application Toolbar.
  • PLEASE NOTE: No divider for 0.5.
  • Busy bars display.
  • Mini calendar is always visible in sidebar (cannot be opened or closed) - persists through all filters.
  • Mini calendar always displays month view.
  • Today is highlighted in bold.
  • Single click on mini calendar day, moves to that week if calendar week view open.
  • Single click on mini calendar day, moves to that day view if calendar day view open.
  • Double click on day to automatically display week view for that day in summary view (check with aparna if this is a bug)

Use Case #2,8: Reviewing someone else's calendar

Success Criteria: Sharing a calendar

  • In 0.5, a user will be able to share their calendar either by creating a separate user-defined collection and adding their calendar events or by sharing their All collection that contains calendar items.
  • Release 0.5 WILL NOT handle filtered shares. Sharing any collection, shares all the items. See ZeroPointFiveCollectionSharingWorkflowsSpec.
  • A user will have 2 available workflows to shedule a meeting on a shared calendar.
    • They can create and event on the shared calendar and send an email to other users letting them know the details. This is not a formal invitation just an fyi. If the invitees stamp the invitation mail as an event and put in on the shared calendar, it will appear multiple times. We do not reconcile these for 0.5.
    • A user can also create an event directly on the shared calendar.

Use Case #3,4,5: Add/edit events and tasks on a calendar.

Success Criteria: Creating events
  • Double click to add event and fill in details - inline editing.
    • Workflow only supports editing the subject field inline. The date and time is updated automatically based on the placement of the event.
  • Add event using double-click (in place editing) in top anytime event area.
  • Click and drag to create event in place in summary view.
  • Drag and drop events around the calendar.
  • Create an event from the menu New -> Event.
  • Stamp another item as an event.

Success Criteria: Creating anytime events
  • An anytime event is specified by entering a date for the event but not a time.
  • This event displays in the anytime area of the calendar (at the top).
  • An All Day event is differentiated from an anytime event by clicking the All Day checkbox.

Success Criteria: Creating reminders
  • Simple reminder workflow for 0.5.
  • The detail view will have a reminder field with a pulldown ( None (default), 1, 5, 10, 30, 60, 90 min).
  • A popup will be generated with a reminder X time prior to the event start time.
  • The fields should have a label - "Alarm" and be left aligned with other fields.
  • "None" should be in the drop-down for the no reminder option.
  • Development page on reminders and issues ReminderPlan.

Use Case #6: Invite someone to an event

Success Criteria: Invitation workflow
  • deferred to 0.6. We can stamp an event as an email and send to someone else although it's up to the user to add the event details to the note section of the event/mail.

Open Issues

  • Date-time widget, close on requirements and solution for 0.5. Donn is researching to understand the proposals and define whether or not there is an incremental step for 0.5 that makes sense 11/16/04. - deferred date-time widget to 0.6.
  • What about internationalization concerns with the date-time widget. KenKrugler See http://groups.yahoo.com/group/i18n-prog/message/1452 for some issues with this. Plus any natural language processing is going to be hard to handle in a generally localizable manner.

Deferred Items from 0.5

  • can multi-select days in calendar (brings you to that week) - deferred on 09/29/04
    • can only multi-select up to 7 days.
  • drag and drop items onto day in mini calendar, auto stamps as event for anytime that day (P3) - deferred on 10/04/04
  • Mini calendar is composite of all the calendars (busyness bars). Does not only show calendar events for the selected collection - scoped out of 0.5 on 10/28/04
  • Mini calendar - Moving up sidebar divider allows you to see more than 1 month - scoped out of 0.5 on 10/28/04.
  • calendar overlays removed from 0.5 scope 10/28/04.
  • DesignDateTimeWidgetNotes
  • DesignFreeBusyUINotes

  • free_busy.gif:
    free_busy.gif

Recurring Events - deferred 10/28/04 (P3)
  • Recurring events will be specified by a pull-down menu: None, Daily, Weekly, Monthly or Yearly.
  • If we create a weekly recurring event, we can change it back to a single event by setting the repeat drop-down to None, which removes all the recurring events but keeps the original one we created as a single event.
  • If the staff meeting for this week changes time, we would open this specific event and change the time. As soon as we press enter or tab out of the date-time field a dialog pops up asking us if giving us 3 choices, Cancel, Apply Changes to All Recurring Events, Apply Changes to This Event.
  • [OI] Recurrence and weekends. What is the same day next year is a weekend/holiday, does it automatically move it to the next business day?
  • Weekly repeats the event on the same day of the week (ie. Tuesdays)
  • Monthly repeats the event on the same date of the month (ie. 12th)
  • Yearly repeats the month and date: (Jan 12th)

Status

  • Initial walk-through with Katie on 09/29/04 - some take aways for detailed out certain areas (see open issues).
  • Second draft of calendar spec due 10/08/04 for second review by Katie.
  • Review of spec with Chao, Mimi and Mitch 10/19/04.
  • Walk-through scheduled with Apps team for 10/21/04.
  • Discussions with Katie on 10/28/04 to remove P3 items from 0.5 scope. Katie has requested ordering scope from design team for calendar functionality.
  • Removed free-busy view from the scope 11/11/04.
  • Design Eng meeting to close on 0.5 goals for reminders and date-time entry widget. Reminders have been defined but the date-time widget research is still ongoing. 11/16/04.

Notes

Demo files

-- SheilaMooney - 28 Sep 2004

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r49 < r48 < r47 < r46 < r45 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.