Use Cases
User A does not use the office calendar but wants to be able to
view and/or edit (depending on the URL) the information in this share.
User B receives the URL to the office calendar and decides to sign
up for a new account on Cosmo.
User C receives the URL to the office calendar and wants to view
the office calendar in iCal (or some other Cal DAV client). Note
currently you cannot edit in iCal even with a read-write URL.
User D already has a Cosmo account. After clicking on the URL/
ticket, user D would like to add the shared collection.
Workflow A
We should specify how we want the email notification pre-populated?
Can we distinguish between newly created events and edits to existing
events?
e.g.
Subject: 'xxx' was added to the shared calendar 'xxx'.
xxx in 'The Gym'
Every Tuesday from 2-4PM PST until Dec 31, 2008
Body text blah blah
Workflow B
Once the user is logged in, can we assume that they wanted to
subscribe to the collection they were looking at before they signed
up for an account? I think we need for them to go back to the 'ticket
view' and explicitly click '+ to my Cosmo account' and log-in. OR we
can make the Sign-up link a part of the Login dialog that pops up
when users click '+ to my Cosmo account'. Then, we can be sure that
they do want to subscribe to the share.
Workflow C
Should we include something about the user accessing Help to get
instructions on how to subscribe?
Should we talk about more than just iCal? e.g. Downloading the file,
etc.
Should we also describe how the user can subscribe via Subscribe
pulldown in the Collection details dialogue (when logged in)
Launch iCal app --> Go to Calendar>>Subscribe... menu --> Paste URL
into URL field. OR we can just say something general like: Subscribe
with iCal.
Workflow D
I believe the user can be either logged in or not logged in when they
click on a ticket and access the ticket view of a share. In either
case, we want to force the user to log in again I think. Otherwise we
will need to have account management UI in the ticket view.
===
I can try and work out a way to make the Workflow diagrams and
Requirements more integrated with the Screenshots. :o)
It seems like there is:
1. Subscribe workflow stuff (including logging in and/or signing up
for a new account)
2. Collaboration stuff (viewing, editing, notifying and managing
collections)
Also, should we outline a workflow for Chandler users signing up for
an account, JUST to publish collections?
Add Ticket View as one of the Requirements?
Add In-place login and in-place account sign-up to the list of
Requirements?
Ticket View: How to subscribe with another application from Cosmo
A subscription drop down box will appear on the top right hand
corner of the application in 'Ticket' view. The drop down list box
visually appears only when the mouse hovers over the 'Subscribe
with…' link. Nice to have: a custom drop down list box would be
ideal to allow different mouse over states and to add the Chandler
icon into the drop down list.
The current proposal for drop down menus (both in the 'Collection
Details' dialog & from the application drop down) are:
| Subscribe with… | v |
| Chandler
| Apple iCal 2.0.x
| Feed Reader
| Download calendar and tasks
| Other…
Selecting any of the items from the subscription drop down will
prompt the 'Collection Details' dialog. If the user selects
'Chandler' from the subscription drop down list, the information in
the 'Collection Details' dialog will default to Chandler and all
the information associated with subscription using Chandler. See
the list below of what will appear in the 'Collection Details'
dialog in association with the selection made in the subscription
drop down list.
When the user selects 'Download calendar and tasks' will the .ics
file be downloaded on to the computer desktop. The web browser will
automatically prompt a dialog as to where to '.ics' file download.
(See Firefox dialog prompt example below.)
For the Chandler option, I think we want something that directs
people to the Chandler landing page to learn more about Chandler. I
can work on mocking that up.
Sharing
Goals and Objectives
Currently in Cosmo 0.6 the Casual Collaborator needs to be able to
inform other users sharing the same calendar that an event change
has been made. There are current proposal is to have a 'mail to
link' where the user could click on the link and it would pre-
populate the subject line and body of the e-mail from the default e-
mail desktop client. (Nice to have would be to add the form element
and send the notification directly from the Cosmo UI (see issue
below). See the discussion on the proposal on the design list.)
Use Cases
Bart the Busybody/Coordinator uses Cosmo to share a calendar
collection with Helen the Hub, a Chandler user. Bart makes a few
changes on Helen’s meeting agenda and clicks on the 'mail to' link
to notify Helen that he’s made a few changes in her calendar
collection. Clicking on the link will launch his default e-mail
desktop client and pre-populate a form message in the subject line
and the body of the e-mail.
How does this relate to the edit and notification pieces of the first
set of use cases in the spec? Perhaps this should be integrated with
those use cases? We can also re-use the PTO example as well.
Should we have settings above the OSAF Administrator features? That
way, all of the CC end-user stuff is together?
Do we also need to outline how SNARF admins and filesharing users
will access admin/home directory browser UIs?
Still need to review Timezones and Admin stuff in more detail. Thx.
Mimi
On Dec 28, 2006, at 1:02 PM, Priscilla Chung wrote:
http://svn.osafoundation.org/docs/trunk/docs/specs/cosmo/rel0_6/
zeroDot6.html
I've tried to capture most of the discussions on the list. I'm
sure there are more questions/concerns which I'd like to capture
by following up with a spec review next Thursday in the Cosmo
meeting.
Cheers, -Priscilla
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
