I realized there's a wrinkle in the magic URL storyboards. What
happens when a user needs to sign-up in order to subscribe to a
shared collection? The workflow steps would be:
1. Casual Collaborator receives a ticket to share a collection from a
Chandler user via email
2. CC clicks on ticket and is taken to the Cosmo UI where they can
view and/or edit the collection without logging in (depending on the
ticket)
3. CC wants to subscribe to the collection in Cosmo but doesn't have
an account yet.
4. CC clicks on Sign-up for an account and is told to wait for a
confirmation email.
5. CC closes their browser and goes away.
6. CC receives confirmation email and clicks on a link to confirm
their new account.
At this point, can we tell that the user was trying to subscribe to a
collection and redirect them to the collection after they confirm
their new account? Or are they on their own?
1. CC goes back and finds the ticket
2. Clicks on ticket
3. Clicks on 'Add to Cosmo'
4. Logs into Cosmo with their new account info
Mimi
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
