• Meeting notes from June 6th, 2006 Design Session: DesignSession20060606

• Support Chandler-to-Chandler sharing by previewing shares in Scooby

Proposal for Prioritization of Features to Support Desktop-Web Collaboration; from the Web App perspective

Casual Collaborators: Passers-by and Individual Contributors interacting with Hubs, Busy Bodies, Coordinators, Apexes and Assistant via the Web app

1. View collections without an account. Search for particular Items.
   • Need to find out where the company party is this year.
   • Need to schedule a meeting with Hub, go to look at their free-busy calendar.
   • Hub asks you to review group task list, in particular, the tasks that have been assigned to you
   • Hub assigned you some tasks, go to group task list to remember what they are
   • Have a question about another part of the project, go to group task list to see who owns that part of the project
   • Go to look at packing list the Household Coordinator made for you
   • Go to check when you're supposed to pick up family at airport
   • To find a specific meeting/Tour
   • Teachers want to find Tours about Impressionism
2. Browse collections: Calendar view and Simple table view
   • Docents viewing Tour collection published and maintained by Tour Coordinator
   • Teachers view Tour collection calendar to pick Tours they want to bring their classes to
   • Teachers view Tour collection resources to see "School Tour checklist" of what to bring to Tours
   • OSAF staff reads OSAF Office collection published and maintained by Esther - Although this exists today and I'm not sure how much it is used
   • Working group views group task list published and maintained by Hub
   • Individual Contributor wants to have a high-level understanding of what the Group is working on
   • Apex wants a high-level understanding of what the Group is working on (e.g. What people get out of checking the Recent changes RSS feed on the Wiki)
3. Subscribe to Collection/Item via RSS/Atom feed
   • Docents and OSAF staff can pull down shared collections
4. View single Items without an account by clicking on Ticket URL
   • Hub asks Individual Contributor to update status on a Task
   • Mini scheduling a meeting with a potential IMPLICIT client
5. Add an Event to a Collection: Edit Title, Location, Date/time, Notes field and send out a capital "N"otification about it
   • Individual Contributor updates the OSAF office calendar with his PTO information and sends out a "N"otification
   • Docents update Tour calendar with their Tour plans
6. Add a Task to a Collection: Edit Title, Notes field and send out a capital "N"otification about it
   • Individual Contributor adds their personal Tasks to the Group task list
7. Assign Tags to Items
8. Assign Labels to Items

Helping the Individual Contributor manage multiple ticket URLs

1. Receive an email with a ticket URL
2. Click on a ticket URL to access the collection via Scooby
3. Upon loading the collection, a dialog pops up to ask you if you want to
   • 'Remember this URL on this computer OR
   • 'Wipe out this URL, this is a public computer
4. That way, over time, the IC's URLs stack up in the Scooby UI and it makes it easier for us to say:
5. Hey, manage these URLs with a Scooby account, sign up here.
6. Otherwise, there's a big barrier to creating an account, because you have to hunt through your email, collect all of your URLs and subscribe to them.

Remote access for desktop users, things that users managing shared collections need to be able to do

• Checking for new Items
• Finding a piece of information
  • Viewing all of my collections
  • Overlays
  • Clusters
• Adding new Items, making quick Edits to existing Items
  • Quick Add command-line for dummies
  • Assign Triage status to Items
  • Assign Ticklers to Items
  • Schedule a Task on the Calendar
    • Hub/Coordinator/Assistant blocks out time to perform a Task: Move tables around in Whoville before Sprint week starts
  • Add an Event to the Task list
    • Hub/Coordinator/Assistant adds a meeting they need to prepare for, schedule to the Task list
  • Create/edit recurring events
  • Annotations
• Update Collections (including deleting Items)
  • Drag and drop to add/remove from Collections
  • Trash collection
• Sending out an update Notification about changes to an Item/Collection?
• Sending a quick reply to follow-up on an issue

What we don't need for 1.0

• Super-smooth interaction
• In-place editing in the table
• Auto-complete in the table
• Drag and drop to add and remove items to and from collections
• Multi-select

---

Usage Scenarios for Casual Collaborator Target User

Assistant or Coordinator sets up an Office Collection for Office logistics

• Office Collection includes:

• Individual contributor needs to update it with their PTO information and PING the entire group
• Individual contributor can pull down Office collection as an RSS feed/Atom feed

Hub sets up a working group collection

• Working group Collection includes:
  • Group tasks and who they're assigned to
  • Group meetings
  • Resources: Proposals, specs, relevant discussion threads

Family Coordinator sets up a Household Collection

• Household Collection includes:
  • Weekly Chores as tasks that are on the calendar
  • Who's assigned to each Chore
  • Errands, Household Projects (e.g. Renovate the mud room)
  • 2 calendars for each parent (home/work) and 1 for the kids
  • A Family calendar for events the Family is going to do together (e.g. Vacations, School plays)
  • Family Reunion collection for planning the annual Family Reunion
  • Resources: Packing lists, Research on Summer camps, Research on schools, Homework assignments
  • Contact information: Emergency contacts, School contacts, Friends, Next door neighbors

Museum Tour Coordinator needs to plan Tour schedule, sets up a Tour collection to plan Tours and publishes it

• Tour collection includes:
  • Tour calendar
  • Tasks, e.g. Coordinator asks a Docent to please update
  • Resources: e.g. Tour checklist, Tour descriptions, Tour routes, Museum Tour policies
  • Contacts: Schools and Teachers, Group Tour contacts, Museum administrators, Museum custodial services

• Docents update the calendar with when they're available and when they're not available by:
  • Each Docent creates event lozenges for when they're available and when they're not available
  • Each Docent ranks their available times in order of preference
  • OI How do the docents 'color-code' their availability without creating separate calendars? Can Casual Collaborators without Scooby accounts create additional calendars? Can we have clusters of calendars? Can the Coordinator publish a cluster of calendars?

• Coordinator works with Docents to work out a schedule by:
  • Blocking out proposed times for Docents
  • Asking the Docents to look at the calendar and reply with any feedback

• Docents provide feedback by:
  • Out of band - Sending the Coordinator email
  • In band - Sending comments on the entire Calendar directly from Scooby
  • Updating individual event items and "N"otifying the Coordinator directly from the event, e.g. Amy should be on this tour with me.

• Over time, the schedule solidifies. Docents and Coordinators can update individual events and send out Notifications directly from Scooby with:
  • Figuring out the content of the Tour
  • Cancelling Tours
  • Docents swapping Tours, etc

• Museum is so impressed with the Ecosystem that they build a custom connector between our Ecosystem and their calendaring system.

Assistant sets up Apex collection for managing Apex Tasks and Scheduling as a Proxy

• Apex collection includes:
  • Tasks/Projects, e.g. Coordinate conference speaking engagement. Plan vacation. Prepare for next board meeting.
  • Apex calendar
  • Resources: Packing lists and various other checklists, org structure of the Apex's various organizations, health concerns, medications, etc ??
  • Contacts: Travel agent, home maintenance people: gardener, housekeeping, etc, personal finance stuff, personal physician etc.

• What's assigned to the Assistant? Progress updates.

-- MimiYin - 25 May 2006