Back to Use Cases & Case Studies page
The mission of the Library Linked Data Incubator Group is to help increase global interoperability of library data on the Web, by bringing together people involved in Semantic Web activities--focusing on Linked Data--in the library community and beyond, building on existing initiatives, and identifying collaboration tracks for the future. 
Achieving this goal will depend on identifying shared models, modes of collaboration, and a common understanding of the changing ways that data is shared on the web.
One approach to this problem is to identify use-cases that reflect expectations of how end-users will exploit library services and assets, how libraries will make such assets and services available, and the infrastructure and devices necessary to complete this connection. It is important, as well, to recognize that libraries exist within an ecosystem of many information providers and services, and the interrelationships among all information providers is an important component of such use cases.
A use case describes what a user can do with a system, by specifying a sequence of interactions between user and system leading to a desirable outcome. It should not be confused with specifying the technology itself: a use case may allow for many alternatives to achieving user needs. While use-cases are typically devised independent of underlying technology (that is, they are intended to expose functional requirements, rather than the means by which such requirements are satisfied), the focus of this incubator group is specifically how might linked data approaches be brought to bear so as to improve the overall ability to satisfy user needs, and should therefore be integral to the use cases.
To help analysis across use cases and to keep a consistent level of information, each use case should try to follow the template below, providing something for each non-optional field.
The rationale for the design of the template can be found here.
Please follow the curation guidelines.
The Wiki page URL should be of the form "Use_Case_Name", where Name is a short name by which we can refer to the use case in discussions. The Wiki page URL can act as a URI identifier for the use case.
The person responsible for maintaining the correctness/completeness of this use case. Most obviously, this would be the creator.
Library Linked Data Dimensions
The primary dimensions which this use case illustrates, and secondary dimensions which the use case also illustrates.
The current dimensions list suggests various categories of needs, resources, systems, and assets that might be invoked in use-cases, but should be considered a starting place rather than exhaustive.
Background and Current Practice
Where this use case takes place in a specific domain, and so requires some prior information to understand, this section is used to describe that domain. As far as possible, please put explanation of the domain in here, to keep the scenario as short as possible.
If this scenario is best illustrated by showing how applying technology could replace current existing practice, then this section can be used to describe the current practice.
Two short statements stating (1) what is achieved in the scenario without reference to linked data, and (2) how we use linked data technology to achieve this goal.
Use Case Scenario
The use case scenario itself, described as a story in which actors interact with systems, each other etc. It should show who is using linked data technology and for what purpose. Please mark the key steps which show requirements on linked data in italics.
Problems and Limitations
The key to why a use case is important often lies in what problem would occur if it was not achieved, or what problem means it is hard to achieve. This section lists reasons why this scenario is or may be difficult to achieve, including pre-requisites which may not be met, technological obstacles etc.
Important: Please explicitly list here the technical challenges (with regards to linked data) made apparent by this use case. This will aid in creating a roadmap to overcome those challenges.
Unanticipated Uses (optional)
The scenario above describes a particular case of using technology. However, by allowing this scenario to take place, the technology allows for other use cases. This section captures unanticipated uses of the same system apparent in the use case scenario.
Existing Work (optional)
This section is used to refer to existing technologies or approaches which achieve the use case.