Summary: The primary focus of this document is on updating Web sites and databases. This document applies if all of the following conditions are met: 1) The resource is a remote access electronic resource, 2) The resource is updating, 3) Updates are integrated into the resource. 3. Updates are integrated into the resource. These guidelines may be used for original cataloging and for evaluating/editing copy.

This procedure needs to be updated from AACR2 to RDA and some info may be out of date.

Remote access vs. direct access

Remote access electronic resources, i.e., online resources, are accessed over a computer network such as the Internet (AACR2). Do not ever consider direct access electronic resources to be integrating resources. Cataloging guidelines for CD-ROMs and other direct access electronic resources are available elsewhere on the TS wiki.

An integrating resource is added to or changed by means of updates that do not remain discrete and are integrated into the whole; they can be finite or continuing (AACR2). Possible but not conclusive evidence that a resource is integrating is the presence of a range of publication or copyright dates, the presence of a "what's new" section, or the appearance of latest update information. If there is no indication that the resource is being updated, catalog it as a monograph. Cataloging guidelines for online monographs are available elsewhere on the TS wiki. A new bibliographic record is required when a resource changes its mode of issuance.

When in doubt, consult with your team manager.

Back to top

Special situations

1. A serial in print format may become an integrating resource when issued online since it is continually or frequently updated and previous iterations no longer exist as discrete issues. As long as the current issue remains discrete, the resource is cataloged as a serial (CONSER Cataloging Manual, Module 35, p. 16).

2. When determining mode of issuance, base the decision on the item being cataloged, not on another manifestation. For example, the online version of The New York Times provides access to today's paper in the print edition but has additional content, so it would be cataloged as an online integrating resource.

3. Integrating resources that have ceased being updated are still cataloged as integrating resources.. Such web sites for events are typically updated only until the completion of the event. See, for example, the Meaningful Play 2008 conference website.

4. A multi-part monograph, series, etc., in print format may become a finite integrating resource when issued online if multiple parts or volumes are issued together, the resource is reissued with additional parts or volumes, the same URL is used for each release, and previous releases are not maintained. See, for example, Britannica Online. Because previous releases are not maintained, it is impossible to isolate the content added in each release, even if that content is discrete, so the resource would fall within the scope of these guidelines.

Back to top

Cataloging references

The primary reference source for cataloging integrating resources is the Integrating Resources Cataloging Manual (Appendix A of the BIBCO Cataloging Manual and Module 35 of the CONSER Cataloging Manual).

For additional guidance on describing the electronic aspect of online integrating resources, consult AACR2 Chapter 9 (Electronic Resources).

For guidance on describing the content of an online integrating resource, consult the appropriate format chapter of AACR2. For additional guidance on describing the continuing aspect of online integrating resources, consult AACR2 Chapter 12 (Continuing Resources). In all cases, consult AACR2 Chapter 1 for general descriptive rules.

Use caution when consulting Cataloging Electronic Resources: OCLC-MARC Coding Guidelines, since some of its provisions are specific to OCLC. But it does have a useful summary of guidelines for fixed field coding.

Back to top

General rules

For online resources, the chief source of information is the entire resource itself (AACR2 9.0B1). Prefer formally presented evidence from the home page, table of contents page, HTML header, etc. If no information is available from the resource itself, it is acceptable to use information from the publisher, creator, etc. (which may be on another web page). For all areas, information issued by the publisher or distributor is one of the prescribed sources of information, so it does not need to be bracketed (AACR2 9.0B2), no matter where is comes from.

For integrating resources, unlike serials, the current iteration serves as the basis of description and information on previous iterations is provided in notes. For each area of the description, the prescribed source(s) of information are listed below. Enclose information taken from outside the prescribed source(s) in square brackets.

Area	Basis of description
Title Stmt. of Responsibility	Current iteration Information issued by the publisher, etc.
Edition	Current iteration Information issued by the publisher, etc.
Place and Publisher	Current iteration Information issued by the publisher, etc.
Dates	First or last iteration Information issued by the publisher, etc.
Series	Current iteration Information issued by the publisher, etc.
Notes	Any source
Standard Numbers	Any source

When evaluating/editing a bibliographic record, make sure the following areas are accurate and up to date: title proper, statement of responsibility, publisher, and edition.

Back to top

Fixed Fields

Leader/Type of Record`

Supply a value for Type of Record that reflects the content of the resource. Online integrating resources of primarily textual content should be coded a (Language material), even when they include search functions. Since online resources are considered published (AACR2 9.4B2), do not use codes for manuscript material. Refer to the Type Coding table for other types of content. Bibliographic Level should always be coded i (Integrating resource).

Copy cataloging policy: Accept the leader/type of record coding as given on cataloging copy. The Type of Record and Bibliographic Level codes should not be changed. In records created before July 2006, Bibliographic Level was coded m (Monograph/item), and the continuing aspect of the resource was captured separately in an 006 coded s (Serial control). When searching, prefer records with codes used in current cataloging, all things being equal.

008 – Continuing Resources fixed fields

The value supplied for Type of Record in the leader triggers the type of 008. For a (Language material), that type is Continuing Resources. For textual resources, provide values for Publication Status, Date 1, Date 2, Place of Publication, Frequency, Regularity, Type of Serial, Original Item, Form of Item, Type of Entry, Language, Modified Record Code, and Cataloging Source.

Obtain publication information as instructed in 260/362 - Publication Area. Publication
Status should be coded c (Currently published) or d (Ceased publication).

If specific, explicit update information is available, code the Frequency and Regularity bytes accordingly. If update information is unavailable, follow the CONSER standard record practice (in which the coding of 006/008 bytes for frequency and regularity is optional), so a fill character may be used for these elements. [Note: You may accept copy that codes Frequency as _ (blank) (No determinable frequency) and Regularity as x (Completely irregular).

Type of Serial should be coded w (Updating Web site) or d (Updating database).

Form of Item should be coded o (Online). In copy, s (Electronic) is also acceptable.
Type of Entry should always be coded 2 (Integrated entry).
Code other bytes appropriately.

Copy cataloging policy: In records created before July 2006, the continuing aspect of textual resources was described in an 006 coded s (Serial control). The type of 008 was Book, with Publication Status coded m (Multiple dates). Accept the 008 coding as given on cataloging copy. When searching, prefer a record with the codes used in current cataloging, all things being equal.

006 - Additional Material Characteristics

Electronic Aspect 006
Create an 006 to describe the computer aspect of the resource.
For textual resources, Type of File should be coded d (Document). You may add a GPub byte if the resource is a government document.

006 Type: m File: d GPub: f

Copy cataloging policy: Always create an 006 for m (Computer file) if not found on copy.

Note: Continuing Aspect 006
In records created before July 2006, an additional 006 for s (Serial control) was created to describe the continuing aspect of all online integrating resources. An 006 field for s (serials) is no longer added to records for textual resources. In records for nontextual resources, since the 008 is used to describe the content of the resource, continue to add an 006 for s (Serial control) to describe the continuing aspect of the resource. Follow the instructions provided in the 008 for Continuing Resources.

Copy cataloging policy: Accept records for textual resources with an 006 for s (Serial control). When searching, prefer records with codes used in current cataloging, all things being equal.

007 - Physical Description

Create an 007 to describe the physical medium of the resource.
Specific Material Designation is always coded r (Remote). Dimension is always coded n (Not applicable). Code other bytes appropriately (usually m for mixed). Image Bit Depth, File Format, Quality Assurance Target(s), Antecedent/Source, Level of Compression, and Reformatting Quality may be coded u (Unknown) with no further investigation unless information is readily available.

007 __ $a c $b r $d m $e n

Copy cataloging policy: Always create an 007 for c (Computer file) if not found on cataloging copy.

Back to top

Variable Fields

In the variable fields of the bibliographic record, follow the current established guidelines and procedures for continuing resources cataloging (AACR2 Chapter 12) in all areas, with particular emphasis on the instructions below. Consult the Integrating Resources Cataloging Manual for additional guidance as needed.

050/090 Classification Number

Evaluate classification numbers as you would for any other resource. Accept 050 - Library of Congress Call Numbers or supply an LC classification number using the 090 field. Full cuttering (use of the $b) is not needed.

24X - Title Area

Take title information from formally presented evidence (e.g., title page, table of contents page, home page, HTML header). If the information in these sources varies in degree of fullness, prefer the source that provides the most complete information. Make notes and added entries for variant titles as instructed below.

Title Proper

An online integrating resource may be part of a larger site or may represent a collection of distinct resources. Select the title that applies to the resource at the level selected for description, typically the page at the URL given in the 856 field. The title proper is bracketed only if supplied by the cataloger.

Omit from the title proper those words that serve as an introduction and are not intended to be part of the title. When applying this rule, consider layout, presentation, and typography. Titles that are presented as graphics or images are not considered to be formally presented. Examine other pages of the resource. Give the introductory words plus the title proper as a variant title in a 246 field. Code the first indicator 1 for a note and added entry. Explanatory text may be provided in subfield i.

245 00 World Bank e-library $h [electronic resource].
246 1 $i Title on home page: $a Welcome to the World Bank e-library

When a title appears in full and abbreviated form on the chief source, choose the full form as the title proper and give the abbreviated form as other title information (AACR2 12.1E1(a)). Give the abbreviated form as a variant title in a 246 field. An added entry without a note (first indicator 3) is sufficient.

245 00 Defense Logistics Agency publishing system $h [electronic resource] : $b DLAPS.
246 3 DLAPS

If the phrase is the name of a body, transcribe it as part of the title proper only if it is consistently presented that way. Otherwise, give the body's name plus the title proper as a variant title in a 246 field. Code the first indicator 1 for a note and added entry.

245 00 Directory of published proceedings $h [electronic resource].
246 1 $i Title in HTML header: $a InterDok - Directory of published proceedings

If the phrase is the name of the parent resource, transcribe it as part of the title proper only if required to make sense of the section title. Give the section title alone as a variant title in a 246 field. An added entry without a note (first indicator 3) is sufficient.

245 00 Medicare. $p Publications $h [electronic resource].
246 30 Publications

When cataloging a resource having links from one language version to another, create 246 field(s) for the title in the language(s) not given in the 245 field. Provide transliterated title(s) if necessary and possible.

245 00 B'tselem $h [electronic resource] : $b the Israeli information center for human rights in the occupied territories.
246 1 $i Title from Hebrew home page: $a Be-tselem
246 1 $i Title from Arabic home page: $a Bi-tisi¯lim

Changes in Title Proper

If a resource has changed title, give information about a former title proper in a 247 field (AACR2 12.1B8(b)). Code the first indicator 1 and the second indicator 0 to generate an added entry and a note, respectively. In subfield f of the 247 field, enter the range of dates of the former title proper. If that information is unavailable (the most common situation), enter instead the date given in the source of title note and enclose the date in angle brackets. Update the date in the source of title note. See 500 - Source of Title Note.

Change the title proper to reflect the current iteration (AACR2 12.1B8(b)). Delete any variant titles that do not appear in the current iteration. Previous subtitles, however, may need to be retained. See Changes in Other Title Information.

Example: Record as first cataloged
245 00 AMA physician select $h [electronic resource].
246 30 Physician select
246 10 $i Title appears on home page as: $a Welcome to AMA physician select
246 10 $i Title in HTML header: $a AMA online doctor finder
246 3 Online doctor finder
500 Title from home page (viewed on Jan. 22, 2003).

Example: Record after being updated
245 00 AMA doctorfinder $h [electronic resource].
246 30 Doctorfinder
246 3 AMA doctor finder
246 3 Doctor finder
247 10 AMA physician select $f <Jan. 22, 2003>
500 Title from home page (viewed on Apr. 11, 2006).

If the title proper changes more than once, update the 245 field again and move the previous title proper to an additional 247 field. Give the 247 fields in order from earliest to most recent. For complex changes to title proper, suppress the generation of a note from the 247 fields by coding the second indicator 1 and describe the changes in a 547 field.

General Material Designation

Give the general material designation (GMD) electronic resource in subfield h, immediately after the title proper, i.e., following any alternative title or part number (subfield n) or name (subfield p) but preceding any parallel title(s) or other title information (subfield b) (AACR2 9.1C). The GMD electronic resource is used for all formats of material accessed online, including images, audio, and video, as well as text (LCRI 1.1C).

Copy cataloging policy: The GMD computer file may appear in records created before 2001. Change the GMD to $h [electronic resource].

Other Title Information

In addition to the situations described above, supply other title information in the following situations.

If the statement of responsibility or the name of the publisher, distributor, etc., is an integral part of the other title information, transcribe it as it appears on the chief source (AACR2 12.1E1(b)).

245 00 Colorado chess informant $h [electronic resource] : $b the official Web site of the Colorado State Chess Association.

If the title proper consists solely of the name of a corporate body, etc., supply other title information by adding in square brackets a brief explanation (AACR2 12.1E1(c)).

245 00 Federal Labor Relations Authority $h [electronic resource] : $b [web page].

Changes in Other Title Information

If other title information is recorded in the 245 field and that information changes on a later iteration, decide if the other title information is important enough to be recorded in the 245 field according to the guidelines above. If not, delete the existing other title information in the 245 field; if so, change the 245 field to reflect the current iteration and enter previous other title information in a 246 field (12.1E2(b)). Code the first indicator 1 to generate a note and added entry; the second indicator may be left blank.

In subfield i, enter the explanatory text Subtitled, followed by a colon. In subfield f, enter the range of dates of the former subtitle. If that information is unavailable (the most common situation), enter instead the date given in the source of title note and enclose the date in angle brackets. Update the date in the source of title note. See 500 - Source of Title Note.

Example: Record as first cataloged
245 00 Africana.com $h [electronic resource] : $b the Black lane on the information highway.
246 30 Black lane on the information highway
500 Title from home page (viewed Feb. 2, 1999).

Example: Record after being updated
245 00 Africana.com $h [electronic resource] : $b the gateway to the Black world.
246 1 $i Subtitled: $a Black lane on the information highway $f <Feb. 2, 1999>
500 Title from home page (viewed Aug. 15, 2002).

Statement of Responsibility

If a statement of responsibility is transcribed as part of the title, do not give a further statement of responsibility unless a separate statement appears prominently on the chief source (AACR2 12.1F2).

If a statement of responsibility does not appear on the chief source, do not attempt to construct one. A statement of responsibility is not required in a bibliographic record. Names of persons or corporate bodies that appear somewhere other than on the chief source may be named in a note if necessary to justify an added entry.

Changes in Statement of Responsibility
If a statement of responsibility is added, deleted, or changed on a subsequent iteration, change the 245 field to reflect the current iteration (AACR2 12.1F5(b)). Also, provide a note and access points. See 500/550 - Changes in Statement of Responsibility and Issuing Bodies Note, 1XX - Main Entry, and Name Added Entries for additional instructions.

250 - Edition Area

Transcribe an edition statement, if the resource contains differences from other editions of the resource or is a named reissue of a resource.

250 2004 TEI-P3 conformant version.

Do not always consider information on updates that commonly appears on Web sites to be equivalent to a formal edition statement. Use judgment in determining where to record version information. This type of information may change frequently and should not necessarily be transcribed in the edition area.

If frequent updates are made, give update information in conjunction with the source of title note. See 500 - Source of Title Note.

256 - Computer File Characteristics

This field is obsolete.DO NOT USE. File characteristics may be described in a 516 Type of Computer File note, if necessary.

Copy cataloging policy: Delete if found on cataloging copy.

260/362 - Publication

Consider all remote access electronic resources published (AACR2 9.4B2). Take publication information from explicit statements of publication on the home page, title screen, table of contents page, etc. If an explicit statement is unavailable, it is acceptable to supply information from material provided by the publisher, distributor, or manufacturer without brackets.

Take the place of publication and publisher name from the current iteration of the resource (AACR2 12.4 and 1.4; LCRIs). Even if the name of the publisher is already given in the title proper or statement of responsibility, repeat the name in the 260 field. If a place or name is added, deleted, or changed on a subsequent iteration, update the 260 field to reflect the current iteration (AACR2 12.4C2 and 12.4D2).

If the date of publication is explicitly stated on the chief source (e.g., created on, mounted on, first posted on), give the date in subfield c of the 260 field. Changes in publication (e.g., no longer maintained after) should be specified in a note. See 500 - Publication Note.

260 Parañaque City, Philippines : $b Center for Asia-Pacific Women in Politics, $c 2001-

If the original date of publication is NOT explicitly stated on the chief source, follow CONSER standard record practice and record the publication date in the 362 field (if any information is available), and do not attempt to record the publication date in the 260 $c.

260 Nairobi : $b United Nations Centre for Human Settlements (Habitat)
362 1 Began in 1996?

If a range of copyright dates or multiple copyright dates are given, infer a possible beginning date and enter it in a 362 field, first indicator 1 (LCRI 1.4F8). Do not take the final copyright date as an ending date for the resource. The date may be updated annually to reflect the latest year.

If a single copyright date is provided, infer a possible beginning date and enter it in a 362 field, first indicator 1 (LCRI 1.4F8).

260 [Marlborough, England] : $b Adam Matthew Publications : $b Datagold
362 1 Began in 2003?

The following table gives some examples that correlate publication dates entered in the variable and fixed fields.

260 $c field	362 field	008/Date 1	008/Date 2
1999-	None	1999	1999
[2002?]-	None	2002	9999
-2004.	None	uuu	2004
-[2003]	Began in 1998?	1998	2003
None	Began in 2001?	2001	9999
None	Began in 1990s	199u	9999
None	Began between 2002 and 2004.	200u	9999
None	None	uuuu	9999

The values in the final row are used when it is impossible even to guess.

300 - Physical description

Provide a general physical description of the resource by using an appropriate SMD.

300 1 website

Copy cataloging policy: Accept the physical description as found on cataloging copy.

310/321 - Frequency of Updates

Give notes about the known frequency of updates to an integrating resource even if the frequency is apparent from the content of the title proper and statement of responsibility area (LCRI 12.7B1). Give notes about both the current frequency and earlier frequencies. Give the current frequency in a 310 field and earlier frequencies, from earliest to latest, in multiple 321 fields. Always use the word "updated" or "updates" with the frequency word (e.g., "Updated quarterly" or "Monthly updates").

310 Updated weekly, $b <July 8, 2004>
321 Updated quarterly, $b <June 1, 1994>

Determining frequency of updates for online integrating resources can be difficult. Use
"Continuously updated" only for online integrating resources updated more frequently than daily.

Use the following table of examples to correlate frequency information in variable and fixed fields.

310 008/Frequency 008/Regularity
Continuously updated k r
Updated monthly m r
None _ x

If information on frequency cannot be easily determined – the typical case – do not create a note.
5XX - Notes
Take information given in notes from any source and from any iteration. Give notes to
· Provide information to justify access points;
· Record information on changes in the resource over time;
· Provide additional information about the content of the resource;
· Provide information about relationships to other resources.

Order of Notes

For original cataloging, follow the AACR2 prescribed order of notes. When updating existing records for integrating resources, add or modify notes in the most expeditious manner. But you do not need to spend time and effort in rearranging notes to fit a certain style or convention.

Copy cataloging policy: Accept the order of notes as found in the record.

Language used in Notes
Write notes supplied by the cataloger in English, but give an update number or release date in the language in which it appears on the resource. For example, a release date in a French language resource would be: 500 Released juin 2002.

538 – Mode of Access/System Requirements Notes

The Mode of Access note is optional, but the System Requirements note is required if applicable.

Do not make notes about the make or the model of the computer, the amount of memory, or the operating system. Do not make notes about software requirements or peripherals unless they are uncommon. You therefore should not make a note of the need for the Adobe Acrobat Reader.

538 Database and its Greek texts are best viewed using Internet Explorer browser on a PC. It is possible to use a Macintosh, but the Greek texts are not viewable unless one downloads the necessary font to view the Greek text (which is available via the site).

Copy cataloging policy: Accept Mode of Access and System Requirements notes as written.

546 - Language and Script Note

Give information on the language(s) of the text, summaries, etc., if the language is not clear from the rest of the description. When cataloging a resource having links from one language version to another, give language information in a 546 field and create 246 field(s) for the title in the language(s) not given in the 245 field.

546 Text in English, Arabic, and Hebrew.

588 - Source of Title Note

Provide a note documenting the source of the title proper and the date the resource was viewed for description. Combine these in a single note. Use the term home page for the first, opening, or entry page of a web site consisting of multiple individual web pages and other files.

588 Title from home page (viewed May 25, 2004).

Use the term table of contents page for a page that lists the contents of a resource.
588 Title from table of contents page (viewed Dec. 14, 2005).

Use the term HTML header for the content of the title tag in the HTML header
(<head><title> ... <title><head>), which displays in the browser title bar.
588 Title from HTML header (viewed Feb. 20, 2002).

See OLAC’s Source of Title Note for Internet Resources for more information.

When an integrating resource includes a specific date of update, include this update date in the note, as well as the date viewed.

588 Title from home page (viewed Jan. 26, 2006); last updated Sept. 14, 2005.

If the title proper of the resource has changed, the title area and the date in the source of title note should be updated. See Changes in Title Proper for additional instructions and examples.

500/550 - Statement of Responsibility and Issuing Bodies Note

Make notes on statements of responsibility not recorded in the title area or on changes in the statement of responsibility, if considered important (AACR2 12.1F5(b)). Use the 550 field for information about issuing bodies; use the 500 field for information about persons. See 1XX - Main Entry and Name Added Entries for instructions on updating headings.

Example: Statement of responsibility not recorded in the title area

245 10 Medical school faculty online directory $h [electronic resource].
550 Issued by: Faculty Roster System.
710 2 Association of American Medical Colleges. $b Faculty Roster System.

Example: Change in statement of responsibility

110 2 American Economic Association.
245 10 Directory of members $h [electronic resource] / $c American Economic Association.
247 10 Membership directory of the Association of American Economics $f <June 16, 1998>
500 Title from home page (viewed Apr. 7, 2006).
550 Issued by Association of American Economics <June 16, 1998>.
710 2 Association of American Economics.

500 - Edition Note

Make a note on the source of the edition statement if different from the source of the title proper. In citing the source of the edition statement, it may be useful to refer to the terms defined in the OLAC Source of Title Note for Internet Resources. If the source or its location cannot be described succinctly, provide the URL. Include the date viewed.

250 2004 TEI-P3 conformant version.
500 Edition statement from: http://ets.umdl.umich.edu/o/oec/moreoec.html (viewed Mar. 10, 2006).

500 - Publication Note

Make notes on changes in publication, distribution, etc., no longer present on the current iteration or in a different form on an earlier iteration, if considered important. (If the changes have been numerous, a general statement can be made. e.g., Publisher varies.)
245 00 arXiv.org e-Print archive $h [electronic resource].
260 [Ithaca, N.Y.] : $ Cornell University
362 1 Began in 1991.
500 Started in Aug. 1991, by Paul Ginsparg at the Los Alamos National Laboratory, Los Alamos, New Mexico.
700 1 Ginsparg, P. $q (Paul)
710 2 Los Alamos National Labratory.

516 - Type of Computer File Note

Do not supply a Type of Computer File note (516 field), unless the nature or scope of the resource is unusual and not apparent from the rest of the description.

516 Electronic text (HTML) and search engine.

Copy cataloging policy: Accept the note as found in copy. Do not seek to add one if it is lacking.

530 - Other Formats Note

Make a note if it is readily apparent that the resource is available in another physical format(s) (AACR2 9.7B16). Notes on multiple formats may be combined in a single note. Search the local library catalog for information on the availability of other formats.
If the title of the other format is different, create a linking entry with explanatory text in a 776 field instead of a note. See Title Added Entries and Linking Entries for instructions.

530 Also issued in print and on CD-Rom.

Copy cataloging policy: Accept the note as found in copy. Do not search SkyRiver or the library catalog seeking other physical formats.

856 field

Create an 856 field to provide access to the resource. Code the first indicator 4 to specify that the access method is HTTP. Code the second indicator 0 (zero) to specify that the URL provides direct access to the resource described in the body of the record. Enter Online database or Web site in subfield 3 for the link text. In subfield u, copy and paste the URL as it appears on the screen. If the URL changes from session to session, copy the link location by moving the cursor above the link text, right-clicking on the mouse, and selecting copy link location. If the publisher provides a URL for bookmarking or linking, use that URL. Do not use the $3. After saving the record, switch to the OPAC and test the link.

Access Points

When creating original records derived from variant edition records, check series headings (4XX, 80X-830), subject headings (6XX), and name and title headings (1XX/7XX) against the authority file for currency and accuracy.

6XX - Subjects

When assigning and constructing headings, consider changes to the resource, but base the analysis on the current iteration. When modifying a bibliographic record to reflect changes to the description, also check subject headings for appropriate coverage of the subject content and scope of the resource. If there are significant changes, add, delete, or modify headings accordingly.

Do not assign a heading for the form of a resource, e.g., Electronic information resources, as a topical subject heading unless the resource is about the form.

Assign headings for the form of the resource using the 655 field. Use second indicator “0” if the term is found in LCSH.

Do not assign form subdivisions, e.g., --Electronic information resources, merely to indicate that a resource is online.

Do not assign the subdivision --Databases under subjects for online integrating resources that are not formatted as databases, even if they are searchable (SCM, H 1520). This restriction applies to online integrating resources that have the structure of and present themselves as reference-type works, including directories, bibliographies, catalogs, dictionaries, encyclopedias, etc., as well as article databases such as JSTOR, PubMed, etc. Assign instead the pertinent form headings or form subdivision under subjects.

1XX - Main Entry

Update main entry headings to reflect changes in responsibility. See Changes in Statement of Responsibility and 500/550 - Statement of Responsibility and Issuing Bodies Note.

Example: Record as first cataloged, URL unavailable
110 2 Association of American Economics.
245 10 Membership directory of the Association of American Economics $h [electronic resource].
500 Title from HTML header (viewed June 16, 1998).

Example: Record after being updated on Apr. 7, 2006
110 2 American Economic Association.
245 10 Directory of members $h [electronic resource] / $c American Economic Association.
247 10 Membership directory of the Association of American Economics $f <June 16, 1998>
500 Title from home page (viewed Apr. 7, 2006).
550 Issued by Association of American Economics <June 16, 1998>.
710 2 Association of American Economics.

7XX - Added Entries

Name Added Entries
Make an added entry for a prominently named person if important for access (AACR2 21.30F). Make an added entry for a prominently corporate body, unless it functions solely as a publisher, distributor, or manufacturer (AACR2 21.30E).

Example: Corporate body functioning solely as publisher
245 00 Biography resource center $h [electronic resource].
260 Farmington Hills, MI : $b Gale Group, $c c2001-

Example: Corporate body functioning as producer and publisher
245 00 Bibliography of Scottish literature in translation $h [electronic resource].
260 Edinburgh : $b National Library of Scotland, $c [2000]-
500 Hosted by the National Library of Scotland; administered jointly by the University of Edinburgh and the National Library of Scotland.
710 2 National Library of Scotland.
710 2 University of Edinburgh.

Create an added entry for a person or body previously responsible for a work. Create an added entry for a previous publisher if considered important. The added entry should be justified in a note. See 500/550 - Statement of Responsibility and Issuing Bodies Note and 500 - Publication Note.

Example: Change in statement of responsibility
110 2 American Economic Association.
245 10 Directory of members $h [electronic resource] / $c American Economic Association.
247 10 Membership directory of the Association of American Economics $f <June 16, 1998>
500 Title from home page (viewed Apr. 7, 2006).
550 Issued by Association of American Economics <June 16, 1998>.
710 2 Association of American Economics.

Example: Change in publisher
245 00 arXiv.org e-Print archive $h [electronic resource].
500 Started in Aug. 1991, by Paul Ginsparg at the Los Alamos National Laboratory, Los Alamos, New Mexico.
700 1 Ginsparg, P. $q (Paul)
710 2 Los Alamos National Laboratory.

Title Added Entries and Linking Entries

Create an additional physical form entry for an item available in another format if important for access, e.g., if the title is a common word or if the print and online formats have different titles. Code the first indicator 0 to display a note. If explanatory text is needed as a display note, code the second indicator 8 to suppress the automatic display constant and provide explanatory text in subfield i as shown. Provide control numbers from the records for the other format(s) in separate occurrences of subfield w. You may include an OCLC control number (code = OCoLC) if you know it, but you are not required to find it, if it is unknown. You may use a SKY control number (code = CaEvSKY) or an LCCN (code = DLC) instead (or in addition) in the $w.

776 08 $i Also issued on CD-ROM as: $t Illustrated ISTC $w (CaEvSKY)sky123456789 $w (OCoLC)43080749

Create preceding entries for titles of resources that have merged. The added entries should be justified in a note.

245 00 Africa-wide $h [electronic resource] : $b NiPAD.
580 "Incorporating African studies and South African studies."
780 14 African studies (Grahamstown, South Africa : Online)
780 14 South African studies (Online)

Create a preceding entry for the title of a resource from which a resource has separated. The added entry should be justified in a note.

245 00 International index to the performing arts full text $h [electronic resource] : $b IIPA full text.
580 Separated from: International index to the performing arts.
780 17 International index to the performing arts

Succeeding entries will generally be unnecessary since the record for the preceding resource is deleted if it is no longer available.

Copy cataloging policy: Accept linking fields found in copy. Do not create ones if they don’t exist

Back to top

When to Create a New Bibliographic Record

Most changes in subsequent iteration(s) of an integrating resource do not require the creation of a new bibliographic record. Instead, the bibliographic record is changed to reflect the current iteration, and information about the earlier iteration(s) is moved to notes with access points, as appropriate, if considered important.

A new bibliographic record is required in the following cases:

If access to previous iterations of the resource is available, create a separate record for the current iteration and supply an edition statement

245 00 English poetry $h [electronic resource].

245 00 English poetry $h [electronic resource].
250 2nd ed.

Create a new record for an online integrating resource that represents the merger of existing resources. Delete the records for the merged resources if they are no longer available separately.

245 00 Africa-wide $h [electronic resource] : $b NiPAD.
580 "Incorporating African studies and South African studies."

Create a new record for an online integrating resource that has separated from another resource. Delete the record for the resource from which it has separated if it is no longer available.

245 00 International index to the performing arts full text $h [electronic resource] : $b IIPA full text.
580 Separated from: International index to the performing arts.

When the original URL remains active but links to a different resource than that described in an existing record (LCRI 21.3B), create a new record, rather than modify the record for the resource previously at that location. If the resource previously at that location is not available at another URL, the record for it should be deleted from our local catalog and MSU holdings removed from the OCLC record.

Back to top

Contact	Janet Baldwin or Joshua Barton
Team	CMS
Updated	March 2018
Created	March 2018

Browser not supported