contacts-usecases
From DiSo wiki
Contents |
Contacts Usecases
What actions will users want/need to perform with contacts.
Add a person to contact list
- add a person as a contact after a first OpenID login (present DiSo procedure)
- edit details on how they know each other
- tag the contact freely (groups or companies or projects, the user would know by context)
- inherit the contact's tags if available (similar to Networks in Facebook, but could be a project tag)
- eventually explicitly label the contact with trust levels: "authorized to share my contact data", "OK to receive IMs", etc.
- warn this person about addition to contact list, eventually with labels
View and edit contact list
Search and Filter
- Search by name, tags, URL, email domain name, company, address, telephone number, etc.
- filter by name
- filter by tags
Edit contacts
- Edit tags
- Receive original data modification warning (propagation from original person's source)
- Validate such edits that emerge from the contact itself
Delete contacts
- Delete contacts from contact list
- Deletion should eliminate all contact privileges
Authorize contacts to access a resource or perform an action
- Allow applications to discover contact data, including tags, from my contact list and allow contacts to perform a given action or access a resource through OAuth token (a WP-DiSo in-house application, ie for tagging a post, or 3rd party apps like Flickr)
- Send warning message to these contacts
- Contacts can login to said application with OpenID to benefit from their privileges
- Users should be able to see when such permissions are granted when they consult the contact list
De-autorize a contact
- Ungrant one or all privilege(s) from a contact
A first shot at pouring some content --AlexandreSolleiro 18:08, 16 January 2008 (PST)
