Dashboard > The DataPortability Project > ... > Technical Documentation > Use Cases
  The DataPortability Project Log In | Sign Up   View a printable version of the current page.  
  Use Cases
Added by Julian Bond , last edited by Christian Scholz on May 03, 2008  (view change)
Labels: 
(None)

This page defines Use Cases that relate to Dataportability. They may be expanded out into more detail elsewhere. They are intended as starting points for the development of best practices, standards and specifications.

Basic Social Networking Use Cases

Profile

  • Auto-Filling a Profile when signing up to a new site. See Best Practices Document 1 - Login and Discovery
  • Pre-populating a job application form or otherwise sharing profile information with a career site or prospective employer.
  • Automatically building a "YASN-Roll" A list with links to my profile pages on all the different systems I've joined
  • Maintaining several persona or profiles that can be used and chosen from when signing up to a new site.
  • Assigning permissions to profile fields (at least what is public or whether it can be exported and to whom). 

Social Network Data

  • Export and aggregate your contacts from an online service into your contact management application
  • Find your contacts on an online service you have joined
  • Building a searchable aggregation of global social network data. A white pages for people.
  • Building a searchable aggregation of your individual social network data from all the sites where you have a contact list.
  • Answering the question "Who says they know this person"
  • When joining a new site, having the site say "You seem to know these people, do you want to connect with them here?"
  • When you make a new contact on one site, having the same relationship automatically created on all other sites where you are both members 
  • Being able to assign certain permissions to contacts (can see my cell number, email address etc. regarding content the same) 
  • Being able to group/tag your contacts to more easily assign permissions to them (e.g. family, business partners, friends).
  • When changing the relationship between you and a contact on one site, propagating that relationship to all the other sites where it exists.
  • Telling a new aggregation site "My YASN-Roll is here" instead of having to give it the ID and Password of each service you belong to
  • Never having to type your password for site B into site A
  • Automatically building a life stream from your YASN-Roll

Content

  • Migrate an existing Blog from one CMS to another
  • Aggregate your, and your friend's, "Status" (eg Twitter) from all the "Status" systems you belong to.
  • Post a Status update from a single application to all the Status like systems you belong to.
  • Moving to a new Photo sharing site and taking all your photos with you. Or wishlist, list of RSS feeds, list of books read, etc.
  • Aggregating rich presence information. I'm online. I'm at this location. I'm doing this with these people. In a couple of hours I'm moving there to meet them.
  • Encouraging people to have a rich "AboutMe" page on blogs. Perhaps by encouraging the building of a Wordpress plugin.

Function

  • Encouraging Social Networks to link to best of breed websites instead of duplicating (badly) their functionality

Other

just as note for myself: Some more explanation should be added on the process, on naming and how use cases should look like.

Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators