The Virtual International Authority File (VIAF)

VIAF Authority Record for Harper Lee

The authority file goes global.

It was probably inevitable that there would be an attempt to create a global authority file for library bibliographic data.  Any worldwide authority file would need the support of major national libraries and library organizations.  We now have the first viable candidate.

VIAFThe Virtual International Authority File (VIAF) is not a new service, but one that has become more prominent in recent times due to the direction of OCLC (starting in 2012) and the rise of linked data. It began as a joint project of the Library of Congress and the German National Library, then the National Library of France and OCLC, but now has a long list of contributors.

From OCLC, the VIAF service has these characteristics:

  • A collaborative effort between national libraries and organizations contributing name authority files, furthering access to information
  • All authority data for a given entity is linked together into a “super” authority record
  • A convenient way for the library community and other agencies to repurpose bibliographic data produced by libraries serving different language communities

The VIAF combines the national authority files—which contain data such as names of authors and companies, conferences, places, and subject headings in their native languages—into a single international name authority service.

There are several benefits of a global name authority file (or service). Obviously, there is the fundamental benefit of providing uniform names for indexing and searching.  With a global authority file, the connecting application, such as a discovery service, can retrieve and display names based on the language of the application’s user interface—and can switch on-the-fly.  It enables the generation of “see” and “see also” links across languages.  The VIAF allows developers to search and access the authority data using an API.

As mentioned at the beginning, the VIAF is one source which can be accessed via a linked data URI.  Here’s an example:

creator: {
@id: “http://id.loc.gov/authorities/names/n78089036”,
label: “Wodehouse, P. G. (Pelham Grenville), 1881-1975”,
sameAs: “http://viaf.org/viaf/sourceID/LC|n78089036”
}

The above operation translates a Library of Congress control number for an author to the related VIAF record.

You can search the VIAF at viaf.org.

View a typical authority record at viaf.org/viaf/46734193.

VIAF authority Record Map for P. G. Wodehouse

Linked Data: Basics and Resources

Linked Data is a set of practices which involves the publishing, sharing, and connecting of related data across the Web in a structured format, preferably using an open access license.

Why use Linked Data?

Using Linked Data is a way to make online library resources—even those items having metadata and located in online library catalogs—accessible to the Web at large by publishing the data in a standard, openly-accessible way.

Properly described and published, online library resources could be harvested by search engines and linked to from other online resources.  In order to do this, Linked Data must be structured in a standard way for the Web.

On the cataloging and description side, Linked Data from online resources such as the Virtual International Authority File (VIAF) can serve as global authority records.

The Basics

Linked Data mugTim Berners-Lee defined his four principles of Linked Data in 2009:

  1. Use URIs as names for things
  2. Use HTTP URIs so that people can look up those names
  3. When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL)
  4. Include links to other URIs so that they can discover more things.

Linked Data has two components: URI and RDF.

URI (Uniform Resource Identifier) is a location as name of a digital resource on the Web, typically given in the form of a Uniform Resource Locator (URL) that also gives the protocol (ex. HTTP) of accessing it.

RDF (Resource Description Framework) is a standard structured file (often in XML) which describes a digital resource and contains URIs.

For a Linked Data statement, you need three components: subject, predicate, and object.  These together are referred to as a triple.

<subject> <predicate> <object>

Subject – what’s being described and linked, a URI or blank node.
Predicate – describes the connection, always a URI.
Object – the resource being linked to, a URI, literal, or blank node.

<Atlas Shrugged> <was created by> <Ayn Rand>

One framework for moving library metadata records into Linked Data format is BIBFRAME, the replacement for MARC being developed by the Library of Congress and others.  We will continue to see new tools created for the conversion of library metadata formats (such as Dublin Core) into Linked Data formats (such as RDF/XML and Turtle).

Finally, as more library records are converted and made available as Linked Data, we will see library vendors start to utilize Linked Data in their products.  For example, Ex Libris recently announced that the company has launched a program to “harness linked data technology in its resource management and discovery solutions” and published the paper Putting Linked Data at the Service of Libraries.

Resources

Here are some great online resources to learn about Linked Data:

Articles and books about Linked Data and libraries:

Common Ground: Exploring Compatibilities Between the Linked Data Models of the Library of Congress and OCLC by Carol Jean Godby and Ray Denenberg

Common Ground: Exploring Compatibilities Between the Linked Data Models of the Library of Congress and OCLC“Jointly released by OCLC and the Library of Congress, this white paper compares and contrasts the compatible linked data initiatives at both institutions. It is an executive summary of a more detailed technical analysis that will be released later this year.”  Published in 2015.

Access the abstract and full-text article (PDF).

Library Linked Data in the Cloud: OCLC’s Experiments with New Models of Resource Description by Carol Jean Godby, Shenghui Wang, and Jeffrey K. Mixter

Library Linked Data in the Cloud: OCLC's Experiments with New Models of Resource DescriptionPart of the “Synthesis Lectures on the Semantic Web: Theory and Technology” series.  OCLC looks at Linked Data in cataloging and its products.  Topics include authority records including VIAF, cataloging and FRBR, text mining, and the library Linked Data cloud.  Published in 2015.

Watch the companion video (59:50).

View details and find a place to buy or borrow at Google Books.

Library Linked Data: Research and Adoption by Erik T. Mitchell

Library Linked Data: Research and AdoptionThis title is actually an issue of Library Technology Reports from ALA Tech Source.  The report covers basic metadata in libraries and museums, Linked Open Data (LOD), case studies including BIBFRAME, and “issues, opportunities, and trends” in metadata. Published in 2013.

View details and find a place to buy or borrow at Google Books.

Linked Data for Libraries, Archives and Museums: How to Clean, Link and Publish your Metadata by Seth van Hooland and Ruben Verborgh

Linked Data for Libraries, Archives and Museums: How to Clean, Link and Publish your MetadataIn this book published by the American Library Association, the authors cover Linked Data and focus on the metadata standards supporting it. They present key concepts of metadata including metadata modelling, cleaning, reconciling, enriching, and publishing. Published in 2014.

View details and find a place to buy or borrow at Google Books.