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

[Mimi Yin]

I have attempted to pull together a summary of the many responses to  
my original Dogfood feedback email. I hope I have capture all the  
various issues, solutions and explanations below. Please review. In  
the mean time, Priss and I are planning to sit down to review these  
issues so we can do a design SWAG. Ultimately, I would like to get  
these suggestions into bugzilla so the bug council can have their way  
with them.

Thx!

Mimi

> 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)

This is an a4 specific bug that will go away for Preview.

>
> + 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?

Suggestion:
+ In the future, we could re-design the grant a ticket functionality  
so that the table for tickets doesn't appear until you 'grant a ticket.'

> https://osaf.us/cosmo/browse/<USERNAME>/freebusy
> + All 3 Collections he had were of Type=Calendar

The Type column is a legacy of DAV.
+ Dav users need to be able to tell if a collection can be used as a  
CaldAV calendar collection or a CardDAV addressbook collection.

Suggestion:
+ In the near-term, could we label the column DAV Type? and rename  
the Name column: Collection Name.
+ In the near-term, we can also make sure we distinguish between  
Collections versus Items.
+ In the future, we can consider adding a column to display the kind  
of each item: Note, Message, Task, Event, etc. bcm, what's the use  
case for this? What is the Admin or Chandler Server user doing when  
inspecting this kind of information?

> + 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.

Going away with new sharing framework.

>
> + 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)
>

Proposal is: [Chandler] [DAV] [Feeds] Logged as: https:// 
bugzilla.osafoundation.org/show_bug.cgi?id=8060

I'm assuming here that [Chandler] would cover both Chandler Desktop  
and Chandler Hub. I don't think we need to have separate links for  
each one?

> The bookmarkable Chandler URL is not available from the Collection  
> Details Dialog, although the DAV and Feeds URLs are.

Questions:

1. What are the reasons for *not*making the ticket-URLs in the  
Collection Details Dialog?  When would you want to hand out non- 
ticket URLs versus the ticket URLs?

Suggestions:
What if users only gave out ticket-URLs? Then, if the user is already:
+ Logged into their Chandler Hub / Chandler Server account; and
+ Subscribed to the collection in question; then
+ We just log them in; otherwise
+ We send them to a 'ticket-view' of the collection.

Also, for Preview, won't users have access to the ticket-[Chandler]  
URLs from the Collection Details Dialog because Chandler Desktop will  
have switched over to the new sharing format?

> Additional suggestion from bcm: Make 'home collection' page look  
> different from sub-pages.

I think this will require some up-front design work and will be hard  
to do in a vacuum (without touching other page templates, etc). I  
would recommend punting this to future, Priss?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20070316/b708a768/attachment.html