r1 - 12 Jun 2006 - 18:03:24 - PriscillaChungYou are here: OSAF >  Journal Web  >  ContributorNotes > PriscillaChungNotes > TargetUserNotesZeroDotThree

Targer User Notes: Scooby 0.3

Usage Scenario

OSAF employee puts their PTO on the office calendar with Scooby

Reality

  1. Esther publish office calendar URL w/ Scooby--> sends and email***
  2. Andi searches through his email, clicks on the read/write URL (that points to Scooby) for the office calendar
  3. Andi see office calendar in the browser
  4. Uses the 'goto date' to find the days which his is taking PTO
  5. Creates an event
  6. Clicks on the 'mail to' link --> launches mail client to notify everyone@osafoundation.org that he has put in his pto in the office calendar.

*Need to make it easy for people to leave in their inbox/email*

Ideal

Andi can pretty much do what he does today.

  1. Andi sends and email to everyone@osafoundation.org, cc: office calendar. Subject line is the title of the event. ie. Traveling to France from June 15th to July 1st, 2006
  2. Sending out a notification with Scooby (address stamping as in Chandler-assume no address book, but there is auto complete)

Issues to address

  1. URL add special header? -->Morgen
  2. cosmo has knowledge of Scooby - today it doesn't
  3. figure out ticket support publish/subscribe UI in Scooby

Use Case Issues

  1. Philippe sent out an email for his PTO with multiple dates. How would one support that when he sends out this information? --main.PriscillaChung this may not be a regular use case
  2. Jake (receptionist) sends out weekly emails with mulitiple events for the office events.

Send to dev list: Task for John Chandler (currently are CalDAV tickets) & Scooby to have the same tickets -->may need to change tickets from Chandler and need to start discussion on the list. -->user's should only see read & read/write

-- PriscillaChung - 13 Jun 2006

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | 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.