[Design] Manage Share/Collection Sharing dialog
mimi at osafoundation.org
Thu Jun 29 08:53:56 PDT 2006
It seems like if the user re-names an account, it would be to change
it to something that is more meaningful to them.
For example, OOTB, we might call the Cosmo Sharing account: Cosmo
However, an user who is told to share via Cosmo Sharing because their
office has decided to adopt the Chandler Ecosystem might associate
that account more with their job, than with the OSAF server Cosmo. As
a result, they may change the name of the account to: Work Sharing.
Either way, the account name is the user's way of identifying the
server/service that is being used to share the collection.
The server/service that is being used to share the collection is
simply part of the profile of the share and in some situations it is
a helpful piece of information to have when managing a shared
Otherwise, it's like looking at your Outbox in your email client and
only being able to see the Title of the email, but not being able to
see which account you sent the email from. Most of the time, it
doesn't matter, but once in a while, it does.
That being said, Priscilla's original observation is spot on. There
are better and worse ways to communicate the concept of the sharing
server/service. Changing the OOTB name of the Sharing account from
'Sharing' to 'Cosmo Sharing Service' would be a first step. Changing
the name of the field from 'Sharing account' to 'Shared via' would be
WHAT WE HAVE TODAY IS CONFUSING:
Collection name: My calendar
Sharing account: Sharing
Collection name: My calendar
Shared via: Cosmo Sharing Service (or whatever we call the service in
Q. Can we figure out the server or service name for subscribers as well?
On Jun 28, 2006, at 3:43 PM, Priscilla Chung wrote:
> Please see my notes inline:
> On Jun 28, 2006, at 2:21 PM, Ted Leung wrote:
>> I may be an edge case here, but I currently have calendars from 3
>> different servers in my Chandler, so account information is useful
>> to me in recalling what came from where.
> True, but I'm still questioning do you usually recognize your
> collection by the 'collection name' or by what server it comes from?
> In regards to your comment, '3 different servers in my Chandler', I
> agree there should some sort of 'supplementary' information, just
> not what's currently there which is the 'Description'. The
> 'Description' name can be changed in the 'Accounts' dialog so you
> can pretty much label it anything you want it to be. (See attached
> screenshot w/ no photoshop tricks, the 'Sharing account' was
> renamed in Chandler. Question: Which collection is this office
> calendar from? iCal or Chandler, can you tell? And how?)
> Again to my last point:
> + Another way to tell where a collection is shared might be to
> describe the server that hosts the collection. ie. The server name
> and path that is not editable by the user in 'Accounts'. iCal
> server at Mac.com or Cosmo server at Cosmo-demo.osafoundation.org.
> This information is useful, however once again, displaying this
> type of information may be more useful for the advanced users; a
> user who would understand the difference of collections being
> hosted on different severs.
> Yes, we should provide the user with information to which 'server'
> the collection is stored on. Though to get to this point, Mimi and
> I are going to sit down and work out an 'ideal' solution–which
> hopefully will be the least amount of work for releasing Chandler's
> Having said that of course, I welcome suggestions for a better
> solution then what is there currently. Or if your opinion is that
> everything 'looks fine by me', that's fair too.
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> Open Source Applications Foundation "Design" mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Design