Walk into any library catalogue today and you will find records not just for printed books, but for websites, online journals, databases, and digital repositories. The shift from physical shelves to networked content has reshaped how cataloguers work. A printed book sits still on a shelf with a fixed title page and stable publication details. A web resource can change its content overnight, move to a new address, or disappear entirely. Describing these materials demands a different mindset and a specialised set of rules. Let us look at how cataloguers create reliable bibliographic records for the constantly shifting world of internet resources.
Table of Contents
- Defining internet resources in cataloging
- The problem of the integrating resource
- Instability and the disappearing resource
- Key rules for describing web content
- Finding the title and source of information
- Recording publication and access details
- The role of metadata and Dublin Core
- The role of MARC and AACR in internet resource cataloging
- From AACR2 to RDA
- The MARC 856 field
- Bringing the rules and the format together
Defining internet resources in cataloging
An internet resource is any material that is accessed through a network protocol such as HTTP, FTP, or telnet. This includes web pages, online databases, e-journals, digital documents, and streaming media. The Library of Congress uses the phrase networked electronic resource to describe content reached over a network rather than held on a physical carrier like a CD-ROM.
The key difference from traditional resources lies in stability and form. A printed monograph has a clear physical boundary, a title page, and details that never change once published. Internet resources rarely offer that comfort. Their content can be updated continuously, their titles can shift, and the page you describe today may look different next week.
The problem of the integrating resource
Traditional cataloguing recognised two broad categories of publication: monographs, which are complete in one part, and serials, which appear in successive issues. Websites fit neither category neatly. To solve this, cataloguing rules introduced a third category called the integrating resource. This is a resource that changes through updates which are folded into the whole, rather than being issued as separate parts.
A frequently updated government portal is a good example. It is never “finished” like a book, and it does not release numbered issues like a magazine. New information simply replaces or merges with the old. Because of this, an integrating resource is described based on its current iteration, with earlier details recorded in notes. This is the opposite of serial cataloguing, where description is based on the first issue.
Instability and the disappearing resource
Perhaps the biggest challenge is impermanence. A book does not vanish from a shelf on its own, but a URL can break, a domain can expire, and content can be silently revised. This is sometimes called link rot or reference rot. Cataloguers must therefore record the date they viewed the resource and be prepared to update records as addresses change. Stable identifiers such as Digital Object Identifiers (DOIs) and Persistent URLs (PURLs) were developed precisely to address this fragility.
Key rules for describing web content
Describing a web resource follows the same broad goal as describing a book: create a record detailed enough to identify and distinguish the item so users can find it. The areas of description remain familiar, including title, statement of responsibility, edition, publication details, and notes. The methods for gathering that information, however, are adapted to the digital environment.
Finding the title and source of information
For a printed book, the title page is the obvious starting point. Online resources have no title page, so cataloguers look elsewhere. The current standard, Resource Description and Access (RDA), replaced the older idea of a single “chief source” with the broader concept of preferred sources. As the Library of Congress training materials explain, the preferred source is where you find the title proper, and information taken from outside the resource is enclosed in square brackets.
For online materials, the title is usually taken from the textual content displayed on screen or from embedded metadata such as the HTML title tag. When details are not stated on the resource itself, the cataloguer supplies them from a reliable external source and marks them as supplied. This honesty about the origin of information is a core principle of good cataloguing.
Recording publication and access details
Publication information for web resources can be vague or absent. There may be no clear publisher, place, or date. Cataloguers record what is available and note uncertainty where needed. Two pieces of information become especially important for internet resources: the access date, which tells users when the description was accurate, and the electronic address, which tells them where to find the resource. Because online content changes, these elements anchor the record in time and space.
The role of metadata and Dublin Core
Full library cataloguing is detailed and time-consuming, which is impractical for the vast scale of the web. This gap led to the development of simpler metadata schemes. The most widely known is the Dublin Core Metadata Element Set, created in 1995 at a workshop in Dublin, Ohio, jointly involving the library organisation OCLC and the National Center for Supercomputing Applications.
Dublin Core offers 15 core elements, including Title, Creator, Subject, Description, Publisher, Date, and Identifier. It was designed to be simple enough for non-specialists to use while still describing networked resources effectively. According to the Dublin Core developers, it is not intended to replace richer models such as AACR2/MARC cataloging, but to provide a lowest common denominator for resource description that catalogers and non-catalogers alike can apply. As the INFLIBNET teaching resources note, Dublin Core acts as a kind of digital library card catalogue for the web, helping with resource discovery across different domains.
An added benefit is that well-structured metadata improves how search engines understand a page, which supports search engine optimisation. This shows how library description principles quietly underpin everyday web discovery.
The role of MARC and AACR in internet resource cataloging
Two pillars support traditional descriptive cataloguing: the rules that tell you what to record, and the format that tells you how to encode it. For decades the rules came from the Anglo-American Cataloguing Rules, and the encoding came from the MARC format. Both had to adapt to the internet.
From AACR2 to RDA
The Anglo-American Cataloging Rules, second edition (AACR2), provided instructions for describing library materials and establishing access points. Its descriptive rules were organised by material type, following the areas defined by the International Standard Bibliographic Description. As electronic resources grew, AACR2 was revised, and its 2002 revision formally introduced the integrating resource concept to handle websites and databases that update continuously.
AACR2 was eventually succeeded by RDA, released in 2010. RDA was built for the digital environment from the ground up. It is based on conceptual models such as the Functional Requirements for Bibliographic Records (FRBR), which separate a work from its expressions, manifestations, and individual items. This structure suits online resources well, where the same content may exist in many digital forms. RDA also gives cataloguers more flexibility in choosing sources of information, which matters when a resource lacks a clear title page.
The MARC 856 field
If RDA is the rulebook, MARC is the container. Within MARC, one field stands out for internet resources: field 856, Electronic Location and Access. The Library of Congress designed this field to hold the information required to locate and access an electronic resource, including online materials.
Field 856 stores the URL in subfield $u and uses indicators to specify the access method, such as HTTP or FTP. It can be repeated when a resource is available through more than one access method, when mirror sites exist, or when different formats have different addresses. The OCLC guidance recommends using field 856 in a record whenever the resource, or a subset of it, is available electronically. Other subfields can hold public notes, logon strings, and information about the relationship between the link and the item described.
Interestingly, cataloguers are advised not to delete a link simply because it appears broken. Because the 856 field is searchable in shared systems, even an inactive address can give clues about title changes, content changes, and former resource providers. This reflects a wider truth about cataloguing internet resources: the record must capture history as well as the present.
Bringing the rules and the format together
In practice, a cataloguer describing a website applies RDA to decide what to record and how to phrase it, then encodes that description in MARC fields, placing the access information in field 856. For lighter-weight description, especially at scale, Dublin Core offers a simpler alternative that can interoperate with fuller MARC records. Together, these standards allow libraries to bring the chaotic, changing web into the ordered world of the catalogue.
What do you think? As more knowledge moves online and resources change or vanish without warning, should libraries prioritise capturing a perfect snapshot of a resource, or building flexible records that can keep pace with constant updates? And in an age of search engines, does detailed bibliographic description of web content still add value that automated indexing cannot?
References
- https://www.loc.gov/marc/bibliographic/bd856.html
- https://en.wikipedia.org/wiki/Resource_Description_and_Access
- https://www.loc.gov/catworkshop/RDA%20training%20materials/LC%20RDA%20Training/Module1IntroManifestItemsSept12.doc
- https://www.dublincore.org/specifications/dublin-core/usageguide/
- https://asistdl.onlinelibrary.wiley.com/doi/10.1002/bult.70
- https://ebooks.inflibnet.ac.in/lisp3/chapter/metadata-and-dublin-core/
- https://www2.archivists.org/groups/standards-committee/anglo-american-cataloging-rules-2nd-edition-revised-aacr2
- https://www.loc.gov/marc/holdings/hd856.html
- https://www.oclc.org/bibformats/en/8xx/856.html

Leave a Reply