Use Case Bibliographic Network

From Library Linked Data
Revision as of 18:22, 27 October 2010 by Jschneid4 (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Back to Use Cases & Case Studies page

Name

Bibliographic Network (Link Bibliographic Networks of entities)

Owner

Tod Matola

Background and Current Practice

Libraries and other Cultural Heritage institutions have been collecting, describing and presenting resources for a long time. Other parties are playing increasingly significant resource collection, description and consumption roles. We need to define resource description and presentation processes and products in a less “culture-bound” fashion. In addition many of the processes and products are based on aging standards and models that are not conducive to web-scale use of the carefully curate resource information. In response to this, the International Federation of Library Associations and Institutions (IFLA) initiated a fundamental re-examination of these issues to produce a framework that would provide a clear, precisely stated, and commonly shared understanding of what it is that the bibliographic record aims to provide information about, and what it is that we expect the record to achieve in terms of answering user needs. The terms of reference also gave a second charge to the study group: to recommend a basic level of functionality and basic data requirements for records created by national bibliographic agencies.

Goal

  1. Collect and curate resource descriptions of entities to aid users in the following actions: browse, explore, find and retrieve of entities of the descriptions.
  2. By giving each of the entities an identifier (URL), that when dereferenced will contain meaningful metadata with links to other related information, humans and machines can take advantage of the curate resource descriptions.

Use Case Scenario

As a part of my discovery session, I would like to see all expressions, manifestations and items related to a work that I find interesting.

Application of linked data for the given use case

Data needed for this case would include:

  • Title
  • Sub-Title
  • Author/Editor/Composer/etc
  • Publisher
  • Publication Date
  • Language
  • Material Type
  • Availability details
  • Relevancy measure of the item

The above attributes are distributed across the various levels of the information entities, with clear links and relationships about the objects they refer to. Linked data techniques would allow these relationships to be described as an information graph and web standards can be utilized to facilitate the user's discovery requirements.

Existing Work (optional)

  1. API with RDF/XML output available - The Open Library Blog

Related Vocabularies (optional)

  1. Bibliographic Ontology
  2. Core FRBR

Problems and Limitations

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. Please explicitly list here the technical challenges made apparent by this use case. This will aid in creating a roadmap to overcome those challenges.


Related Use Cases and Unanticipated Uses (optional)

The scenario above describes a particular case of using linked data.. However, by allowing this scenario to take place, the likely solution allows for other use cases. This section captures unanticipated uses of the same system apparent in the use case scenario.

Added by Antoine following this thread

Library Linked Data Dimensions / Topics

Topics:

  • Conceptual models and KOS > Types of library data other than bibliographic and authority
  • Applying SemWeb Technology to Library Data (Implementation) > Vocabularies > Applying FRBR, FRAD, RDA
  • Applying SemWeb Technology to Library Data (Implementation) > Use of Identifiers for and in LLD > Reuse or urlification of traditional identifiers
  • Management of data and distribution > Issues of Web architecture

Dimensions:

  • Users needs > Browse / explore / select
  • Users needs > Retrieve / find
  • Users needs > Identify
  • Systems > Library systems > Online reference
  • Systems > Non library information systems
  • Information assets -> Books
  • Information assets -> Journal articles
  • Information assets -> Databases
  • Information lifecycle > present / publish

References (optional)

This section is used to refer to cited literature and quoted websites.

  1. IFLA Study Group Functional Requirements for Bibliographic Records, Final Report — 1998
  2. Murray, Ronald J., Tillett, Barbara B. (Collab.) From Moby-Dick To Mashups: Thinking About Bibliographic Networks. Washington DC: American Library Association 2010 Annual Conference.