[Design] [Cosmo][Dogfood] Using the Account Browser to restore a lost Chandler repo

[Mimi Yin]

Hi,

I did some drive-by usability of my own on the Chandler Server  
Account Browser with User-Alex. We were trying to restore his  
collections into Chandler Desktop on Vista (which looks awesome by  
the way - Go native widgets!) by digging up tickets in the Account  
Browser.

I'm happy to say: Mission Accomplished!

As usual however, here's a laundry list of things that may trip up a  
user 'not-in-the know'.

https://osaf.us/cosmo/browse/<USERNAME>
+ Not immediately clear that the Name=Cosmo, Type=Calendar was where  
my stuff was supposed to be, since he had lots of Notes and Tasks as  
well.
+ I would imagine though that for a Casual Collaborator who only sees  
Calendar data, Calendar would make more sense, than PIM.

+ (Actually, his stuff was in Name=freebusy, Type=Folder) Why is  
freebusy a Folder? and not a Calendar? (That was rhetorical, just in  
case ;o)

+ Not sure what it means to have Tickets on the <USERNAME> page.  
Maybe this page lists all of the tickets for all of the collections?

https://osaf.us/cosmo/browse/<USERNAME>/freebusy
+ All 3 Collections he had were of Type=Calendar
+ When 'browsing' one of the Collections, it appeared that there were  
only 3 items...until I noticed that one was a Type=Folder  
called .chandler.

+ Again, not sure whata it means to have Tickets on the freebusy  
page. But starting to get a clue ;o)

https://osaf.us/cosmo/browse/<USERNAME>/freebusy/<COLLECTION NAME>
+ Okay need to get tickets. How do I construct a ticket? Which one  
works for Chandler Hub? Chandler Desktop? (I understand this is  
temporary? Eventually the [pim] ticket will work for Chandler Desktop  
as well?

+ For now, [pim] doesn't work for Chandler Desktop, is that correct?  
I copied the Id and appended it to the end of the URL in the address  
bar. (Which turns out is wrong, because I was in /browse/ rather  
than /home/. :o)

===

Are there any short-term, trivial fixes we can do to make this  
experience a little better?
+ Do we have any control over Type names? Could we have say a Type  
called Collection?
+ Do we need to segregate non-event items into a separate .chandler  
folder? Or can events and non-events appear together in the same  
list? Will Morse Code on Chandler Server solve this issue?
+ Can we rename the links to the tickets? [Chandler] [DAV] [ Feeds] ?

I understand though, these changes are very specific to Chandler  
users and don't translate well to Chandler Server users using the  
server bundle as a DAV server, etc. Any thoughts?

Mimi


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20070315/efb4f76c/attachment.htm