[Chandler-dev] [Proposal] Sharing and Accessing Individual Items

[Mimi Yin]

Here is a rough sketch to review next Tuesday.

For mock-ups: http://chandlerproject.org/Notes/ 
WebWidgetsMockups#ItemSharing

HOW TO SHARE AN ITEM WITH OTHERS:
+ Desktop + Web UI - Add button to show sharing URLs
- Dialog pops up:

=====DESKTOP DIALOG=====
To share ITEM NAME with others, copy and paste
these URLs into the message:

View and Edit: [                                                     ]
        View-only:  
[                                                     ]

                                                          [Copy URL(s)]
=====DESKTOP DIALOG=====

=====WEB UI / WEB WIDGET DIALOG=====
Give out these URLs to share ITEM NAME with others:

View and Edit: [                                                     ]
        View-only:  
[                                                     ]

                                                         [Close]
=====WEB UI /WEB WIDGET DIALOG=====

ON THE RECEIVING END
+ Recipient clicks on the link and is taken to a 'ticketed' view of  
the item
- User has option to add it to your account;
- which pops-up 'Add to account' dialog + pulldown for selecting a  
collection to add the item to

OPEN ISSUES 1
+ If you receive it in Chandler Desktop, what happens?
- Can user paste URL into Subscribe... dialog?
- Can the Desktop handle users subcribed to individual items?
- All recipient has to do is add the item to a 'shared' collection  
and everything should start working.

+ Do we need to provide instructions on the ticketed view on how to  
subscribe to the item in Chandler Desktop?

+ What if user already has item via collection sharing?
- If they're logged in, can we take them right to the item in the 1st  
collection it's a member of; OR do we always route people through  
ticketed view?
- If the recipient chooses to add the item again, do we tell them  
that the item already exists in xxx collection? Can we take them to it?

+ I realize that I'm conflating ticket-URLs and non-ticket URLs. Is  
there a way we can make the difference transparent to the user?  
Basically ticket URL + login = non-ticket URL? If possible, it'd be  
nice to avoid having to explain the difference to users.

TO ACCESS AN INDIVIDUAL ITEM VIA A WEB WIDGET

Workflow
1. Select a widget
2. Log in
3. Set options"
=====
1. Enter the URL for the item you would like to access:

URL: [                                                   ]
           Note: The URL for an item can be found....

2. How would you like to access the item?

[  ] iGoogle homepage
-------------------------------
[x] Yahoo homepage
      User name: [                           ]
        Password: [                           ] Add | Remove
-------------------------------
Download: Apple iPhone | Mac OSX | Vista

                                            [Cancel] [Save]
======

OPEN ISSUES 2
+ Can we store these settings for users?
+ Can the user adjust these settings from the web/desktop widgets?
- e.g. username/password, item URL
======
Chandler Hub

User name: [                           ]
   Password: [                           ]

Enter the URL for the item you would like to access:

            URL: [                                                   ]
                    Note: The URL for an item can be found....

                                            [Cancel] [Save]
======






-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20080215/8079a03d/attachment.html