[Design] Unified approach to getting data IN and OUT of Chandler

[Mimi Yin]

I'd like to throw a proposal out there to unify all of the various  
"ways to get data in and out of My Chandler Repository".

Off the top of my head, I see the following:

- Incoming and Outgoing emails
- Import and Export files
- Subscribing and Publishing shares
- Subscribing and "Publishing" RSS feeds

Can anyone think of anything else?

- What about subscribing to and Setting up Mailing lists. If we had  
UI in Chandler for users to "Subscribe" to mailing lists, would this  
be a better "model" for helping users understand that they can  
"filter" mailing lists into their own collections automatically, the  
same way they can have separate Inboxes for each email account.

1. It seems to me that these are all different flavors of essentially  
the same user activity: Get stuff in and out of my PIM.

2. Some basic things you will want to be able to do with all of these  
scenarios:

a. Specify which collection(s) you want the data to go in. (What are  
some usage scenarios for wanting the same data to go into multiple  
collections?)

b. Specify more than one "data feed" into a single collection (ie. I  
may want to have a San Francisco collection that subscribes to  
multiple public events calendar feeds from different sources. I may  
have a single collection for all mailing lists I subscribe to.)

c. Specify which "Sphere" you want the data to go into. "All my  
personal items", "All my spouse's items",  "All my work items", "All  
my public items", et cetera...

What are some other common affordances we would want to support?

Mimi