Design Session Tues Jun 6th

• Desktop-WebWorkflows.ppt: Desktop-WebWorkflows.ppt
• Desktop-WebWorkflows.pdf: Desktop-WebWorkflows.pdf

• Working off of workflows described here: DesktopWebWorkflows

Agenda

Walk-through the desktop workflows with real users/use cases

Ted and Julie Profile

• Ted = busy body
• Julie = coordinator
• Ted and Julie coordinate kids activities
• Julie might not be a desktop client user
• She would want to be able to use Scooby to inform Ted, add things to his calendar
• Ted is a desktop user
• Julie is not an early adopter
• Use Scooby to view Ted's calendar
• hey currently have a household calendar

• Workflows fall out into 2 groups
  • Read-write
  • Ted and julie

• • Readonly
  • Julie and extended family
  • Dance recital
    • Julie might call or email grandparents about recitals - about the one coming up
    • Scheduled - have a date because they need to rent a hall - planned far in advance
  • Piano recital - picks the date and coordinates with the teacher

• Workflow
  • Ted sets up the household calendar in Chandler
  • He would publish it and send a rw ticket to Julie
  • He might send her a ticket to his work calendar - ro
  • Possibly another personal calendar
  • Julie will now have 3 calendars
    • one she manages * 2 she views * she probably has a scooby account - or might happen over time
  • Julie will edit the household calendar * obtains verbal information * paper calendar? * email?

• Dance recitals - knows several months in advance
• Piano recital she has to schedule - collaborates with the teacher
  • Teacher provides options
  • Julie coordinates with family
  • Inform teacher of date and time

• Dance Recital
  • Here is the schedule for the year
  • Notifying of imminent recital - per event basis
  • Julie's mom and brother
    • See which ones they can go to * Might want to mark in Scooby which ones they go to * Might pull this info into their own calendars * putting individual events onto their calendar * subscribe via rss * remind me of this one * other information - directions of where it's held *Ted - dress rehersal - no pictures during performance

• For the casual collaborators there are 3 main workflows
  • scan
  • targeted search
  • upcoming
  • list view might be useful

• How do we make this info easy to view in scooby for the casual collaborator
  • receive a notification in scooby
  • scooby pushing info to a user rather than users having to look for it
  • use email as a proxy - from calendar system rather than person

• Piano Recital
  • receive an event
  • event has a list of options - ie: 3 options for dates
  • Julie wants to get input about who can meet what dates
  • this is an event with no date or time
  • Julie would probably start off with an email - whatever email client she is using
  • If she were using Chandler she could create an event with no date/time and stamp to send out
  • All the text for the options would be in the body field
  • Once there is a resolved date - Julie would enter onto the Scooby calendar and send this to the people who said they can come.
    • to: mom, brother, ted cc: teacher
  • The recipients receive a url to an event item - just like an evite
  • These people would have signed up for notifications/reminders
  • The ticket has some embedded info where we understand the email address
  • It's like a per user ticket
  • A new type of user - needs to be able to receive notifications but doesn't have an account

• We could have capital 'N' notifications or have recipients sign up for updates
• There are some issues we should explore about tickets and acls - is we have acls, tickets will still be useful

• Read only workflows
  • Scanning the calendar
    • Month view - or year view * Mini cal and preview * Table view or list view * Split pane view - like iCal
  • Targeted Search * search box with standard parameters * most likely want the results to show up in a list view * jump to date - go there and look at the month/week - localized scan
• Upcoming * list view * look at next week or next month on the calendar
• Getting notifications - list view * subscribing to a feed for both the calendar or an individual item (PULL) * done via rss, email address * implementing stamping - for julie to send updates (PUSH) * scooby can send email or have a mail to: link

• Mom and brother
  • receiving invitations etc
  • these casual collabs are ending up with more and more tickets
  • how can they be transitioned to more active users
  • how do we encourage people to sign up
  • evite model - sign up options
  • bin of tickets - option to remember who I am and I accessed these tickets
  • we collect information about people then put them into an account
  • people wouldn't have to go and find all the tickets that they have subscribed to
  • could create an anonymous users account for these people
  • could have an osaf cookie on browser that maintains the list

• Next Actions:
  • review more after scooby meeting on thurs - 0.3 plan
  • other interviews - docent, hub, rw scenarios - these imply task scenarios
  • consolodate workflows - write-up

Desktop web workflows - 1-4 are involve no editing - mostly about viewing information - the remainder center around some read write workflows

-- SheilaMooney - 12 Jun 2006