Warning This is going to be very hard to understand. Because I can't understand it.
How do we differentiate between personal items and public items?
- RSS feeds, mailing lists, public folders
- Group shares (ie. OSAF calendar)
- Mitch's calendar in Esther's repository
If the All collection or Dashboard view is supposed to be a pristine environment in which users only see the items that are relevant to them, then where do non-personal items live? How are they distinguished between personal items?
Do we put a private v. public attribute on collections? OR items themselves?
In our n-dimensional world, shouldn't private v. public be orthogonal to collection? or topic?
Maybe the stuff in the sidebar isn't really topics? Those are the things you attach to items as labels.
The stuff in the sidebar are really shortcuts to groupings of items. So then it's okay to attach private v. public to collections, not items.
Create collection v. Create public collection
So if Blue creates the office calendar, she might do it as a public collection.
Can we get away with not having this.
We can solve the status problem: just figure out a general rule for diplaying event status, or don't display status at all
User can configure their sidebar to show the Kinds they want to show, the Kinds they filter by often.
If an item is in both, it becomes your item.
Or maybe Esther wants to keep track of Mitch's items as well?
Maybe for the public collections your administrating you actually want to treat those items as if they were "mine".
So any items that you create are assumed to be "mine".
So on the item we mark public v. private.
And we mark all items public when you receive them in shares.
Okay so Sheila convinced me that we should make this simpler:
- Basically shared calendar events arrive with an event status of. Sharees can change the status of the event, but that means they're changing their own event status, not someone else's event status.
- When you share or receive a share, the detail view of the share presents users with the option to either include or exclude the shared collection from the "All my items" collection. This option would need to be disabled for the sharer if they were sharing their All collection.
- When DnDing items between collections included and / or excluded from the All collection, the assumption is that it's always an Add.
- However, if the user "deletes" an item from their All collection or from an "included" collection and it also happens to live in an "excluded" collection, Chandler will need to ask the user if they also want to delete the item from the excluded collections.
Hmmm. I'm wondering if this is truly simpler.
Eventually though I think we will need to have public, personal, ??? spheres where you can either see the data from your perspective, from someone else's perspective or from an objective 3rd party perspective. And these might be panes in the sidebar? So that theoretically Esther could have Mitch's entire PIM and view it as if she were Mitch.