moving this post from cosmo-dev to design, original post is at: <http://lists.osafoundation.org/pipermail/cosmo-dev/2007-February/002813.html> ====== Maybe for some Preview release?
When someone shares a collection in Candler and provides you with a ticket to access the calendar from Cosmo via your web browser, the default name for the calendar is whatever the collection was named in Chandler. You can change what you call this calendar using the Collection Details dialog. Now that it has a new name you have no idea what it was originally called, (but Cosmo does...) Let's assume the Chandler owner of the calendar has 15 or 20 different calendars she shares. The casual collaborator using Cosmo to view the pim collections also has a dozen or more calendars in their drop down menu. If there is an issue with an event in one of these it will be VERY helpful to be able to inspect (via the Account Browser perhaps?) from whom the original share came, and just as important, to be able to tell that person what THEY named that collection (i.e. the name of the collection so that they can find it in their Chandler sidebar). To complicate matters slightly. The original person who shared the calendar can "rename collection' in Chandler and sync with Cosmo. Now Cosmo knows what that calendar was originally called and what it's current name is in the owners account, and Cosmo still maintains the sync link with whatever the calendar name is in the subscriber's account. So when this happens, upon inspection Cosmo should be able to tell the subscriber what the owner's current name is for that collection not the original name. Just a thought. Pieter _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
