# Presentation: 659935

## Part 2. Description of Integrating Resources

## Outline

- Cataloging Overview
- MARC Coding Preview
- Examples
- Conclusion

##  Cataloging Overview

- Highlights of what will be new and different for integrating resources

## AACR2: Which Chapters?

- Use Chapter 12 for _all_ integrating resources.
- Both finite and continuing.
- _Also_ use any other chapter relevant to the predominant type of resource content.
- Examples:
- _For updating loose-leaf_: use Chapter **12**.
- _For updating Web site_: use Chapters **12 & 9**.
- _For updating cartographic Web site_: use Chapters **12, 9, & 3**.

## MARC21 Tagging in the “interim” 

- Fields 247, 547, and 550 are already valid in OCLC with bib level “m”
- All the fields shown on this slide are valid with bib level “m” in RLIN
- These may be validated for bib level m before level i is implemented:
**310** for frequency of updates.
**321 **former frequency
**362 1** for publication date information when not from first/last iteration.

**Notes:**

A quick word about MARC21 tagging of Notes:

In OCLC Fields 247 and 547 can be used in monograph records already along with 550, 580, and 76x-78x.  The fields that are currently tied to bibliographic level"b" and "s" are 022, 222, 310, 321, and 362.  The validation rules for these fields will be changed to allow their use on monograph records during the interim period between implementation of the revised rules and implementation of bibliographic level "i" in OCLC.
Also: 
Implementation of 006 fields with new codes for "d" "l" and "w" in 006/05 and code "k" in 006/01 might be implemented by OCLC for the “interim” when records need to be coded bib level m, although, LC & RLG would delay implementation of these codes later

## “Integrated Entry” Cataloging

**Existing bibliographic record is** **changed** to describe current iteration of the resource.
- Most areas of description based on** ****latest iteration**.
- Data elements of **previous iterations** entered in notes if required or considered important.
**New bibliographic record** is created only for certain changes in edition**, **mergers, splits, or when there is a new work.
- (Changes in physical format still under consideration.)
- Integrating resources will be actively updated and bibliographic records will require ongoing **maintenance**.

**Notes:**
Note that in pre-AARC2 serials cataloging this convention was called “Latest entry” [but not in AACR itself].  The term “Integrated entry” is new and distinguishes this practice as applying to non-serial resources cataloging according to AACR2.  As with “Latest entry”, the term “Integrated entry” does not appear in AACR2, but it does appear in MARC 21 (Format for Bibliographic Data). 

## Changing the Description

- General Principle:
- Change description to reflect current iteration.
- Give earlier information in a note.
- For title proper: “in general”.
- For other elements: “if considered important”.
- Identify iteration to which note applies.
- Exceptions:
- Create new bibliographic record for certain changes to edition area, mergers, splits, etc.
- e.g., *in toto* replacement of base volume of a loose-leaf.
- Give range of dimensions of looseleaf.
- If dimensions change in subsequent iterations.

## Change in Title Proper 12.1B8

- Change 245 $a/n/p to reflect the current iteration.
- Give the earlier title in a note.
- Use MARC 247 and/or 547 fields.
- (To be covered in section on notes ahead.)
- LCRI: Identify which iteration prior to the current had this form of the title proper.

**Notes:**
LCRI 12.7A2:	LC/PCC practice:  When a data element (e.g., title proper, statement of responsibility) changes, give information enclosed in angle brackets to locate in time the presence of the earlier data element.  Use information already in the record:  for electronic integrating resources, use the date from the “viewed on” information; for non-electronic integrating resources, use information from a “Description based on” note.  Do not try to determine exactly when the data element changed.

## Change in Edition Information 12.2F1

**Certain changes require a new record**.
- LCRI 12.2F1: New record if edition statement changes and:
- _For updating loose-leafs_: if there is a new base volume (i.e., an *in toto* replacement edition), but not if a gradual replacement edition with no new base volume.
- _For updating remote access e-resources_: only if resource described in existing record continues to exist as resource separate from new resource to be cataloged.
- When new record is not required:
- Change 250 to reflect current iteration and make note if change is considered important.

## Numbering 12.3

- Not usually applicable to integrating resources.
- 362 0 formatted designation used for serials; _not_ used for integrating resources.
- Note that 362 1 unformatted note may be used for giving beginning/ending publication dates when first/last iterations are not available.

## Date of Publication, etc. 1.4F8

- If cataloging from first _or_ last iteration:
- Record beginning date or ending date in 260 $c.
- Beginning date followed by a hyphen.
- Ending date preceded by a hyphen.
- Supply an approximate date in brackets if necessary.
- If both first _and_ last iterations are available:
- Record both dates in 260 $c, separated by a hyphen.
- For updating loose-leaf, supply date of last update if considered important.

## Date of Publication, etc. 

- If _neither_ first nor last iteration is available:
- Do not give beginning or ending date.
- Omit 260 $c and preceding comma.
- Give information about beginning and/or ending date in a note if it can be readily ascertained.
- Example: 362 1  Began in 2000.
- Optionally, supply beginning/ending date (in 260 $c) if it can be readily ascertained.
- LC will apply this option.

**Notes:**

It should be noted that an unformatted 362 1 could be used in cases where a possible date could be inferred– this would allow the fixed field to be coded with an approximate date. 

## Date Examples (1)

- Resource currently ongoing, first iteration available:
**260 **... **, $c 1994-**
- Resource currently ongoing, first iteration available, date approximate:
**260 **... **, $c [1998?]-**
- Resource currently ongoing, first iteration not available:
**260 **... $b ...

**Notes:**
Slides reflect LC practice; PCC practice will be decided at the meeting.

## Date Examples (2)

- Resource completed, last iteration available,  first iteration was not available:
**260 **... **, $c –2001.**
- Resource completed, all iterations issued in the same year:
**260 **... **, ****$c 2002.**
- Updating loose-leaf completed, date of last update available and considered important:
**260 **... **, ****$c 1974-2001 [last updated 2002]**

**Notes:**
Slides reflect LC practice; PCC practice will be decided at the meeting.

## Physical Description 12.5B1

- Extent of item for loose-leafs:
- Add the qualifier “(loose-leaf)”.
- _For ongoing loose-leaf_:
- No number of volumes given:
**300    $a v. (loose-leaf) **
- _For completed loose-leaf_:
- Number of volumes added:
**300    $a 3 v. (loose-leaf)**
- Note: Do not give physical description for remote access e-resources.

**Notes:**
This is a change for loose-leaf cataloging practice: the number of volumes is no longer given until the resource is complete. Loose-leafs now handled like serials, - remains v. until complete.

## Physical Description 12.5D2

- _Change in dimensions_:
- Change 300 $c to reflect current iteration.
- Record range of dimensions if applicable:
- 300    $a v. (loose-leaf) ; **$c 24-26 cm.**

## Change in Series Statement 12.6B2

- Additions, deletions, and other changes:
- Change 4XX and or 8XX to reflect current iteration.
- Make 500 note if change is considered important.
- Retain former series entries in 8XX if traced in local library, based on 500 note.

## Notes

- General rule:
- Include all notes prescribed by the** relevant AACR2 chapter** for the content being cataloged, and any other notes considered important.
- For integrating resources:
- Also include notes for **changes** to all areas of description as prescribed in **Chapter 12** or as considered important.
- If it is known that a note does not apply to all iterations of an integrating resource, add appropriate numbering or publication dates.

## Identification of Iterations in Notes

- Give exact date of change of data element if known.
- If exact date is not known: LC/PCC practice:
- Give information enclosed in angle brackets to locate in time the presence of the earlier data element.
- Use information already in the record:
- _For electronic IRs_: use the date from the “viewed on” information.
- _For non electronic IRs_: use information from a “Description based on” note.
- Do not try to determine exactly when the data element changed.

**Notes:**
If cataloger does have exact date of a change, the exact date would be used

## Frequency Note 12.7B1

- Note the frequency of updates.
- Unless already apparent or unknown.
- LCRI: _always_ give a note for known frequency of updates, even if already apparent from the rest of the description.
- State _current frequency_ in 310 frequency note.
- 310    Updated quarterly
- 310    Continuously updated
- 310    Updated irregularly, $b 2001-
- Reminder: the code in the Frequency 008 element is based on the content of the 310 field.

**Notes:**
Note the use of subfield $b for the date range that applies to a particular frequency (if it changes).

## Former Frequency Note

- State _former frequencies_ in 321 former frequency note.
- 321    Updated monthly, $b 1998-2000
- Example of change in frequency:
- 310    Updated monthly, $b 2001-
- 321    Updated quarterly, $b 1998-2000
- 321    Updated semiannually, $b 1995-1997

**Notes:**
Notice how the dates in the 310 and 321 record the history of the frequency of updates.
AACR2 says to combine notes, but in MARC former & current info. is in two different fields.

## Change in Title Proper Note 12.7B4.2

- Make notes on earlier titles proper.
- Use MARC 247 and 547 fields:
- 247: Former title or title variations.
- Use to generate title added entry in addition to note.
- 547: Former title complexity note.
- LCRI: Give a separate 547 “Title history” note in addition to the 247 field only if the situation requires more explanation than can be given in the 247 field.

**Notes:**
At least for the meantime, the 547 field is necessary if the cataloger needs to give extensive notes about the earlier title because there is no subfield “i” defined for the 247. However, dates/designations can be given in subfield f and ISSN in subfield x of the 247.

## Change in Title Proper Note 

- Example:
- 245 00 Resources for early music $h [electronic resource].
- 247 10 Early music resources on the Web $f <Jan. 5, 1999>
- 500    Title from homepage (viewed Apr. 15, 2002).

**Notes:**
Note the use of angle brackets for dates to identify information form previous iteration: LC practice. 

## Publication, etc. Note 12.7B11.1

- Make notes on beginning/ending dates of publication not recorded in 260 $c.
- i.e., when not cataloging from first/last iteration.
- Use MARC **362 1** field.
- Examples:
- 362 1  Began in 1987
- 362 1  Ceased in 1999
- 361 1  Began in 1973; ceased in 2001

**Notes:**
Note the purpose of the 362 field and the difference between the formatted and unformatted forms of this field.

## Item Described Note 12.7B23

- Note the latest iteration used for the cataloging description (if not the first):
- 500    Description based on: update no. 3, Sept., 2001.
- Often combined with source of title proper note:
- Example for printed loose-leaf:
- 500    Description based on: update no. 4; title from cover.
- Example for remote access electronic resource:
- 500    Title from HTML header (viewed Feb. 15, 2002).

**Notes:**
Note the difference between the way this note is formatted for tangible resources vs. remote access electronic resources.

Description based on note for the loose-leaf example would be changed if a later iteration or update were consulted to make changes on the record.

The date viewed for an electronic integrating resource would be changed on later viewings when changes are made.

## Linking fields

- Linking notes can be provided as needed:
- 775, 776, 770, 772,780, 785, 787
- Both horizontal and chronological relationships can be identified:
- Editions (775)
- Supplements (770, 772)
- Preceding/Succeeding titles (780, 785)
- Non-specific relationships (787)
- PCC/LC provides links between:
- Serials and integrating resources
- Integrating resources and integrating resources
- Integrating resources and monographs

**Notes:**
PCC/LC policy is to provide links for chronological and horizontal relationships to other resources.

Provide the appropriate linking fields (and related notes, if necessary) for earlier/later titles, supplements, and other related works.  The 776 field Additional physical form entry should be used to link to records for items available in other physical forms.

Note: For records created at the CONSER core record standard, not all linking fields are required.
LCRI 12.7B8.  NOTE AREA.  Bibliographic history and relationships with other resources. [New]
	 LC practice: 	Integrating resources:  To show a relationship between two integrating resources if the main entry and/or titles proper are not the same, give a bibliographic history note and a related work added entry (21.28B) on the bibliographic record for the later integrating resource; do not add the note or added entry to the bibliographic record for the earlier integrating resource.

## Standard Numbers

- ISBN: 020
- ISSN: 022
- LCRI: If an integrating resource has both, give both in the catalog record.
- Change in ISBN:
- Add new ISBN.
- Example: when a loose-leaf becomes multi-volume and each volume has a separate ISBN.

## Main and Added Entries

-  Name and uniform title entries.
-     (Additions, deletions, or other changes).
- Make changes to reflect latest iteration.
- Retain entries for past iterations.
- If considered important for access.
- Choice of main entry could change.
- Apply Chapter 21 to current iteration.

## Uniform titles

- Use of uniform titles to distinguish identical titles for integrating resources is still under discussion by PCC members
- Possible uses could include distinguishing databases that appeared in other formats (e.g. print and/or CD-ROM serial) and now appear online.

## Change in Main Entry

- Change **1XX** entry for person or body currently responsible for the resource.
- Make note for earlier responsible person in **500** or body in **550** note, if considered important.
- Required to justify 7XX entry if present.
- Include dates to identify iteration.
- Add name for earlier person or body in **7XX** if considered important for access.

## Beyond AACR2:Subject Headings

- Original headings should be broad enough to encompass changing subject content.
- If significant additions, deletions, or other changes in subject content considered important:
- Add new subject headings for current iteration and/or delete headings for past iterations no longer applicable to the resource.

## MARC Coding Preview

**Not yet implemented by the bibliographic utilities!**

## MARC Coding for Integrating Resources

- Most integrating resources are textual or have predominantly textual content.
- Including most databases and Web sites.
- Most will therefore use the MARC **Leader and** **008** for **continuing resources**:
**Type of Record** code “**a**” – Language material.
**Bibliographic Level** code “**i**” – Integrating resource.
- Will result in** Serials 008**, but with some new values for integrating resources.

**Notes:**
Note that after implementation the Serials 008 elements will be used for most integrating resources.  Since they are being broadened to include integrating resources as well, the name is likely to be changed from Serials to Continuing Resources or something similar.

It is possible that the serial 006 could be implemented for use with bib level m in the “interim” at least by OCLC- RLG and LC would not be able to implement these until later. 

## MARC Leader and 008 (1)

- New codes for integrating resources published but not yet implemented by the utilities:
- Bibliographic Level code “**i**” for Integrating resource.
- New Serials **008** codes for integrating resources.
**Prior to implementation of new codes:**
- Continue to code integrating resources as **Monographs**: Bibliographic Level “**m**”.

**Notes:**
Leader: Type of Record
Used to differentiate MARC records created for various types of content and material.
Definitions revised to include electronic carriers of primary content in addition to print, etc.
Examples:
a - Language material:
“Code a is also used for ... electronic resources that are basically textual in nature ...”
e - Cartographic material:
Includes digital maps. 
g - Projected medium:
Includes digital video. 

## MARC Leader and 008 (2)

**Prior to implementation of new codes:**
- Integrating resources that are predominantly textual still have “**Books**” 008.
- Including textual databases and Web sites.
- Integrating resources with primarily non-textual content have other 008 coding.  Examples:
- Online system or service: “**Computer Files**” 008.
- Cartographic updating Web site: “**Maps**” 008.

## New 008 codes

- Changes to 008 for continuing resources:
- Frequency
- “**k**” **– Continuously Updated**
- Type of Continuing Resource
**d **- Updating database
**l** - Updating loose-leaf
**w** - Updating Web site
- Entry Convention
**2 – Integrated entry**

**Notes:**
Note the significance of the change of name from “Type of Serial” to “Type of Continuing Resource”: indicates the greater scope of this 008 to encompass both serials and integrating resources.

Entry Convention: Formerly named: Successive/Latest Entry
New value added:
2 – Integrated entry
Record is cataloged under its latest (most recent) title and/or responsible person or body. 
A new record is made only when there is a major change in edition or it is determined that there is a new work, and for title mergers and splits.

## Examples

- Records cataloged according to 2002 Amendments.
- Records updated for changes in iterations.

## Description Before and After 2002 Amendments (Updating Loose-leaf)

*Description  *before* 2002 Amendments:*
- 245 00 $a Library of Congress rule interpretations.
- 250 ## $a 2nd ed.
- 260 0# $a Washington, D.C. $b Cataloging Distribution Service, Library of Congress, $c 1989-
- 300 ## $a 2 v. (loose-leaf) ; $c 30 cm.
*Description  *after* 2002 Amendments:*
- 245 00 $a Library of Congress rule interpretations.
- 250 ## $a 2nd ed.
- 260 0# $a Washington, D.C. $b Cataloging Distribution Service, Library of Congress, $c 1989-
- 300 ## $a v. (loose-leaf) ; $c 30 cm.
- 310 ## $a Updated quarterly.

## Description Before and After 2002 Amendments (Updating Web site)

*Description  *before* 2002 Amendments:*
- 245 00 Program for Cooperative Cataloging ‡h [electronic resource].
- 260 0# $a Washington, D.C. $b Library of Congress, $c [199-]-
- 500 ## $a Title from title screen (viewed Oct 1, 2001).
*Description  *after* 2002 Amendments:*
- 245 00 Program for Cooperative Cataloging ‡h [electronic resource].
- 260 0# $a Washington, D.C. $b Library of Congress
- 362 1# $a Began in late 1990’s.
- 500 ## $a Title from homepage (viewed May 1, 2002).

## Description based on first iteration vs. later iteration when first was not available

*Description based on *first* iteration:*
- 245 00 $a MARC 21 format for holdings data.
- 250 ## $a 2000 ed.
- 260 ## $a Washington, D.C. : $b Library of Congress, $c c2000-
- 300 ## $a v. (loose-leaf) ; $c 30 cm.
*Description based on *later* iteration:*
- 245 00 $a MARC 21 format for holdings data.
- 250 ## $a 2000 ed.
- 260 ## $a Washington, D.C. : $b Library of Congress
- 300 ## $a v. (loose-leaf) ; $c 30 cm.
- 362 1# $a Began in October 2000.
- 500 ## $a Description based on: update no. 2, published October 2001.

## Record Before and After New MARC Codes (Updating Database)

-     245 00 Global invasive species database ‡h [electronic  resource].
*Record  *before* implementation of new Leader & 008 codes:*
- Leader/06 (Type of Record)           a - Language material
- Leader/07 (Bibliographic Level)      m - Monograph
- 008 (Fixed length data elements)     Books
- 008/06 (Type of Date)                m – Multiple dates
*Record  *after* implementation of new Leader & 008 codes:*
- Leader/06 (Type of Record)           a - Language material
- Leader/07 (Bibliographic Level)      i - Integrating resource
- 008 (Fixed length data elements      Serials
- 008/06 (Publication status)          c – Currently published
- 008/18 (Frequency)                   k – Continuously updated
- 008/21 (Type of continuing resource) d - Updating database
- 008/34 (Entry convention)            2 – Integrated entry

**Notes:**
Reminder that these will not be implemented by the utilities and most local systems until sometime in the as yet unspecified future.

## Finite Updating Web Site

- Conference Web site: began in 2000; frequently updated until it ceased with last update Feb. 20, 2001.
- 245 00 2001, a library odyssey $h [electronic resource] : $b annual conference, Wisconsin Association of Academic Librarians : April 18 - 20,  La Crosse, Wisconsin.
- 260    La Crosse, Wis. : $b University of Wisconsin— La Crosse, $c 2000-2001.
- 500    Title from homepage (viewed March 20, 2002).
- 856 40 $u http://www.uwlax.edu/murphylibrary/waal2001/

## Change in Title Proper (Web site)

*Existing record:*
- 245 00 $a Swedish genealogical resources.
- 500 ## $a Title from title bar (viewed Mar. 10, 2000)
*Same record updated:*
- 245 00 $a Resources for Swedish genealogical research
- 247 10 $a Swedish genealogical resources $f <Mar. 10, 2000>
- 500 ## $a Title from title bar (viewed Sept. 14, 2001)
*Same record updated again:*
- 245 00 $a Genealogical resources for Sweden.
- 247 10 $a Swedish genealogical resources $f <Mar. 10, 2000>
- 247 10 $a Resources for Swedish genealogical research $f <Sept. 14, 2001>
- 500 ## $a Title from title bar (viewed May 28, 2002)

**Notes:**
Reminder that use of angle brackets is LC practice

## Change in Title Proper (Loose-leaf)

*Existing record:*
- 245 00 $a Health profession opportunities.
- 500 ## $a Description based on: update 5, published 2000.
*Same record updated:*
- 245 00 $a Healthcare profession opportunities
- 247 10 $a Health profession opportunities $f <update 5, published 2000>
- 500 ## $a Description based on: update 8, published 2001.
*Same record updated again:*
- 245 00 $a Opportunities in the healthcare profession.
- 247 10 $a Health profession opportunities $f <update 5, published 2000>
- 247 10 $a Healthcare profession opportunities $f <update 8, published 2001>
- 500 ## $a Description based on: update 10, published 2002.

## Changes in Title Proper and Responsible Body (Loose-leaf)

*Existing record:*
- 110 2# $a ABC Association.
- 245 10 $a Membership directory / $c ABC Association.
- 500 ## $a Description based on: update 2, published 1998.
*Same record updated:*
- 110 2# $a DEF Association.
- 245 10 $a DEF membership directory / $c DEF Association.
- 247 10 $a Membership directory $f <update 2, published 1998>
- 500 ## $a Description based on: update 5, published 2000.
- 550 ## $a Issued by ABC Association <update 2, published 1998>
- 710 2# $a ABC Association.

## Second Change in Responsible Body (Loose-leaf)

*Same record updated again:*
- 110 2# $a GHI Association.
- 245 10 $a Membership directory / $c GHI Association.
- 247 10 $a Membership directory $f <update 2, published 1998>
- 247 10 $a DEF membership directory $f <update 5, published 2000>
- 500 ## $a Description based on: update 9, published 2002.
- 550 ## $a Issued by ABC Association <update 2, published 1998>; DEF Association <update 5, published 2000>
- 710 2# $a ABC Association.
- 710 2# $a DEF Association.

## Change in Series Statement (Loose-leaf)

*Existing record:*
- 260 ## $a Denver : $b Smith Pub. Co.
- 440 #0 $a Research in library acquisitions.
- 500 ## $a Description based on: update 2, published in 1991.
*Same record updated:*
- 260 ## $a Denver : $b Smith Pub. Co.
- 490 1# $a Library acquisitions.
- 500 ## $a Series title <1991>: Research in library acquisitions.
- 500 ## $a Description based on: update 9, published in 2000.
- 830 #0 $a Research in library acquisitions.
- 830 #0 $a Library acquisitions (Denver, Colo.)

## Change in Frequency of Updates (Loose-leaf)

*Existing record:*
- 260 ## $a New York : $b Corona, $c 1997-
- 310 ## $a Updated quarterly
*Same record updated:*
- 260 ## $a New York : $b Corona, $c 1997-
- 310 ## $a Updated monthly, $b July, 2001-
- 321 ## $a Updated quarterly, $b January, 1997-June, 2001.
- 500 ## $a Description based on: update 19, published in July, 2001.

## Change in Frequency of Updates (Database)

*Existing record:*
- 245 00 $a Database of prescription drugs $h [electronic resource]
- 260 ## $a San Francisco : $b Medical College
- 310 ## $a Updated weekly
- 362 1# $a Began in 1999.
- 500 ## $a Title from title screen (viewed Feb. 5, 1999).
*Same record updated:*
- 245 00 $a Database of prescription drugs $h [electronic resource]
- 310 ## $a Updated continuously, $b <2001->
- 321 ## $a Updated weekly, $b 1999-<2001>
- 362 1# $a Began in 1999.
- 500 ## $a Title from title screen (viewed May 28, 2001).

## Conclusion

## Description of integrating resources

- _Description is based on latest iteration_:
- Called “Integrated entry” in MARC 21.
- Bibliographic record reflects changes in resource:
- Change description to reflect current iteration.
- Give earlier information in a note.
- For title proper: “generally.”
- For other elements: if considered important.
- Exception: certain changes to edition area require new bibliographic record.
- e.g., in toto replacement of base volume for loose-leaf.

## MARC21 coding

- _MARC coding_ ***after**** future implementation*:
*All* will have Bibliographic Level code “i”.
*Most* will be predominantly language material content.
- Will have Type of Record “a” and Serials 008 elements.
*Some* will have predominantly non-language material content.
- Will have other Type of Record codes and 008 elements.
- Will still have Bibliographic Level code “i”.
- May also have Serials fixed elements in 006.

## Credit

- This presentation on integrating resources is based on a work developed by **Steven Miller**, Chair/course developer, University of Wisconsin-Milwaukee in collaboration with members of the PCC **SCT Task Group on Integrating Resources Training**