Documents:Usage Scenarios

From ssc.aspirationtech.org

The Social Source Commons Web Tool Usage Scenarios

The following scenarios describe the range of usage the SSC Tool would be designed to support. These scenarios are divided into two groups; publishing and managing information with the SSC Tool, and searching and utilizing aggregated information.

Examples of SSC Tool data gathering/publishing

1. Organization lists own software use: Many NGOs question whether they're using the “right tools” or making the best use of their technology. The SSC tool would allow an organization to describe their use by creating a simple list of software, providing basic demographic data (sector, locale, headcount, etc., though complete anonymity would be supported) and comparing it to what other organizations use. Organizations effectively using software would enjoy recognition & credit for sharing their knowledge.
2. Organization manages lists of software in categories they're tracking or researching: Some entities track software applications as part of a software selection process or to provide support to other organizations via a list of recommended software. NTAPS like One/Northwest or NPower regularly make lists of software in a particular category, such as calendaring tools or content management systems, but often use offline tools to manage that data. The SSC Tool would allow tracking of software lists, including attributes with annotations and links to relevant resources. The information would be aggregated to benefit larger constituencies.
3. Organization or eRider manages a list of software tools and associated documentation for a specific process: Similar to examples 1 and 2 except the software being tracked would relate to a particular function or workflow – for example all the applications and associated documentation necessary to do advocacy or human rights monitoring.
4. eRider or Organization doing research in a software category uses tool to manage research process: In addition to managing simple lists, the tool would allow for the collection and automated comparison of common and custom attributes of the software being tracked. This would additionally channel data back into the SSC network.
5. eRider lists tools they support, maintaining documentation and links to reviews, and blogs about relevant tool developments: The SSC Tool allows each eRider to maintain a list of software tools they support. That information is shared and aggregated with entries made in the SSC tool by others using the same software. Lists could be created along geographic, linguistic or cultural boundaries encourage communities of knowledge to grow.

Examples of SSC Tool searching and data utilization

1. User stays informed By having software lists stored on the SSC network, users automatically receive notification of new resources as they come on line, informing them of new developments and allowing them to follow relevant blogs and other online venues.
2. Organization sees what other organizations "like them" are using: with the collection of organizational software profiles, organizations can browse by geography, sector, headcount and other metadata to explore and discover new tools and solutions.
3. eRider is asked to consult on software category with which they have limited experience: eRiders will enjoy a new reservoir of software information to browse, research and recommend, powered by a peer network with relevant experience and opinions.
4. Developer wants to contribute time and effort to a worthy project: browsing by any of the categories or supported “lenses”, skilled engineers can find projects matching their passions or in need of their particular skillsets.
5. Developer is approached to develop software for an NGO need. The SSC Tool allows assessment of what's already available allowing better software buy, bend or build decision.
6. Funder assessing a grant proposal or other software need could survey what existed in the relevant software category. This would empower funders to focus more on the strategic facets of their grant making rather than on doing “homework”.
7. Organization embeds and publishes SSC data in their own pages: for SSC to offer the broadest value, it must not require visits to a particular site. Web services will be published to allow others sites to query and publish from the SSC database into pages on their own sites.