Usage Scenarios

Sharing a Personal calendar (Mine) versus Sharing a Group calendar (Not-Mine).

1. Esther manages Mitch's personal calendar
2. Mitch and Esther share a task list (mostly of tasks assigned to Esther)
3. Apps team sharing a group task list
4. Design list subscribers sharing a group discussion collection
5. Ted and Julie sharing a household task/calendar collection
6. Everyone managing and subscribing to the OSAF Office Calendar
7. Glenda and Brenda share and manage a "Visitor Pass Request" Inbox together

Questions

• How does the user want to view shared items in their Dashboard?
• How does the user want to view shared items in their Mine collections?
• How does the user want to view shared items in the Shared collection?
• What attributes should be shared? not shared? Determined by whom? Sharer, Sharee or both? What attributes need to have values on a per user basis?

Sharing Use cases (for 1.0?)

• Collaborative editing
• PPD team is working together on an email to send out about Scooby planning
• Sheila, Mimi and Alec are working together to clean-up meeting notes from the Sections Design Session
• Julie wants to find the phone number of the Contractor Ted found for a home improvement project. She then wants to update the "Get quote" task with the quote she gets over the phone.

• Assigning and Inviting
• Esther manages Mitch's calendar for him, sending out invitations and responding to invitations on his behalf.
• I assign the "Summarize Design list" task to Sheila for next week.
• Blue invites everyone to the picnic.
• Bear adds the OSAF Picnic to his personal calendar, because he plans to be in town that week.
• Alec signs up to tackle Trash and Deletion tasks on the shared Apps team task list.

• Surveying the lay of the land
• Philippe wants to get an overall sense of how the Apps team is doing in terms of their Tasks for alpha2
• Community members want to see what issues are being actively addressed on the design list

• Focusing the group's attention
• PPD team wants to focus the Design community on 0.7 planning issues on the Design list
• Use case: I'd like to be able to add the thread I had with Sheila and Morgen about Auto-Sync to the shared Design Discussions Collection without having to forward each individual mail to the list.

Must-have ability to Personalize these attributes

Attribute	Use cases for Personal attribute values	Use cases for Shared attribute values
Event status	Everybody will have their own Event status for the company picnic.	But the picnic itself also has an Event status, as in, Is this picnic time confirmed?
Reminders	Ted and Katie want different alarms for their weekly 1-on-1. Katie needs more time in order to find a free room with a phone. Ted just needs to pick up his home office phone.	Esther wants to be able to set alarms for Mitch to leave enough time to travel to his weekly class at UC Berkeley.
In/Out communication status	Blue invites everyone to the summer picnic (including herself). She's the Organizer and everyone else are Invitees, however everyone shares the event on the Office calendar.	Glenda and Brenda share an "Inbox" for Visitor Pass Requests. They respond to requests as a single "person" security@543howard.com
Collection names / Labels	1. I call my Work calendar: Work. However, Sheila wants to see it as Mimi's Work 2. Q What are some use cases for personal Labels?	1. The Design team becomes the PPD team. Sheila wants to update the name of the shared Design collection to PPD 2. The Design list community wants to collaboratively label emails by Bugzilla component.

Nice-to-have ability to Personalize these attributes

Attribute	Use cases for Personal attribute values	Use cases for Shared attribute values
Annotations	1. I have personal meeting notes that are too messy for anybody else to understand. 2. I want to jot down my personal agenda for a meeting. 3. Priscilla wants to see 1-on-1 meeting with Sheila as the Title of the event on her Calendar. Sheila wants to see 1-on-1 with Priscilla as the Title of the event on her Calendar. 4. Off-site folks, want the Location field on meetings to reflect whether they should: a) Call-in to the bridge; b) Be called; c) Coming into OSAF for e.g. Spring week.	I write up a proposal for Sharing in 0.7. Morgen and bcm would like to be able to add in-place comments to the body of the proposal.
Triage status	1. Bryan is going to do a little bit of research up-front into detail view UI affordances for user-defined attributes. However as a whole, the Apps team is not going to address the issue until alpha3. 2. Priscilla and I are tasked with coming up with concept sketches for item browsing. She's going to work on it Today. I can't work on it until next week.	Mitch would like to be able to keep track of Esther's progress on tasks he's assigned to her.
Stamps	Sheila wants to put a few of the longer Design list threads onto her "Read & Review" Task list. But she doesn't want it to show up on the shared Design list Task list.	MimiYin I'm not sure this is so bad. It will just show up as a Task assigned to Sheila. It might be nice to be able to see everyone's status wrt what people haven't had a chance to read yet. This is especially true of small, tight-knit working groups. Not being able to keep stamps private becomes more of a problem when sharing information with large groups of people.

Other use cases for "Personal attribute values" that we should solve by requiring the user to create a separate, but linked item.

• Use case I would like to invite a friend to an OSAF talk, but I don't need/want to add them to the official shared invite.
• Proposed workflow Forward the item. Forward is related to original invitation because both are part of the same thread.

Use cases related to Access controls

If I only have read-only access to a collection, what happens when:

• When I'm explicitly invited to one of the events on the calendar, can I edit and update the invite? (I think Yes)
• Can I Label the item, add my own personal Tags? (Yes, you can do that today by adding it to Collections)
• Can I still Stamp the item? Add the item to a Read & Review task list

Use cases related to Spheres

Personal perspective versus Group perspective

• People need to identify which Collections are
  • Personal collections: My Dashboard, My Work
  • Other People's Personal collections: Esther sets up Mitch's Personal calendar. Pop-up dialog when Mitch subscribes: Esther has set up a Personal calendar for you Mitch, are you okay with that?
  • Group : Our PPD Team, Our Apps Team, Our OSAF Office calendar, Our Home, Our Book club
• Depending on whether the User is in a Personal or Group collection, the User should see different metadata in the Summary Table view.
• ie. Julie assigns a Task to Ted on their Home Task list: In the Home context, Ted wants to see that he is the Assignee. On his personal task list in the Dashboard, Ted needs to see that Julie assigned it to him.
• Mine, Not-mine might be an accurate predictor of whether a collection is Personal or Group.

Priscilla wants to add her weekly 1-on-1 with Sheila to the shared PPD calendar.

• Priscilla wants to see: 1-on-1 with Sheila
• Sheila wants to see: 1-on-1 with Priss
• PPD team should see: 1-on-1 for Sheila + Priss

• Do we offer 3 fields?
  • What Priss sees
  • What Sheila sees
  • What PPD sees

{or}

• Do we let the user type what makes sense to them and have the smarts to parse it correctly automatically?
• Dynamic_List_View.png:
  

Group discussion collections

• • You want to see Who a message is From in the Mailing list collection (since all the messages are To the Mailing list)
  • You want to see Who a message is To in your Dashboard

Proposal for Beta / 1.0

• No perspectives

• Ability to choose whether you want to share Triage status or not
• No Group Triage status versus Personal Triage status

• No ability to choose whether you want to share Stamps or not
• No Group Stamps versus Personal Stamps

• No ability to share Labels
  • In the future, if we want the ability to share labels, then collection names will be shared as well. So if A shares a collection with B and B changes the collection name, B will be changing the collection name for A as well.

• No Annotations, private or public