# Presentation: 502890

## Cataloging Integrating Resources

- A Prototype PCC Training Resource
- Revision of a training workshop given at LC on May 2, 2002
- by Steven Jack Miller
- University of Wisconsin—Milwaukee

## Acknowledgements

- This slide presentation is a revision of a training workshop given for the PCC at the Library of Congress on May 2, 2002, which was the result of a collaborative effort by the members of the PCC SCT Task Group on Integrating Resources Training:
- Steven Miller, Chair/course developer, UW-Milwaukee
- Jean Hirons, Ex-officio, Library of Congress
- Judith Kuhagen, Ex-officio, Library of Congress
- Louise Rees, University of Pennsylvania
- Ann Sitkin, Harvard Law School Library
- Paul J. Weiss, University of California, San Diego
- With additional input from: Adam Schiff, University of Washington

## Training Outline

- 1. Definition of Terms
- 2. Brief Cataloging Highlights
- 3. AACR2 2002 Overview
- 4. MARC Leader and 006/008
- 5. Additional Examples
- 6. Concluding Review

## Schedule (as of July 2002)

- Text of revised Chapter 12 to be published in August 2002.
- LCRIs to be published in August 2002.
- LC to implement Chapter 12 and RIs on December 1, 2002.
- MARC 21 format changes are published, but not yet implemented by utilities.
- OCLC: All coding for integrating resources except Bibliographic Level “i” to be implemented in December, 2002.
- RLIN: All coding except Bibliographic Level “i” and Entry Convention “2” to be implemented in December, 2002.

## Definition of Terms

- Bibliographic Resource
- Finite Resource
- Continuing Resource
- Monograph
- Serial
- Integrating Resource
- Iteration

**Notes:**
These include both new and revised definitions in AACR2 2002.

## Conceptual Categories

- Bibliographic Resources

- Finite Resources

- Continuing Resources

- Finite Integrating Resources

- Monographs

- Continuing Inte-grating Resources

- Serials

**Notes:**
This is one of several different ways that we can divide and categorize the world of bibliographic resources / information entities.  This slide depicts logical conceptual categories based on type of issuance.  In reality these categories are not all equal: the vast majority of integrating resources are continuing; only a relatively few are finite, and that of those even fewer would be likely candidates for cataloging.   Thus it makes sense that AACR covers all IR in Chapter 12.  In the world of cataloging that is the logical place for IR and the locus of the rules about all of them.

## Finite resources

**Finite resources**

**Notes:**
This from Jean Hirons slide depicts where resources are covered in AACR2.  Chapter 12 covers all integrating resources, both finite and continuing.

## Bibliographic Resource

- An expression or manifestation of a work or an item that forms the basis for bibliographic description.
- A bibliographic resource may be tangible or intangible.

**Notes:**
Note the use of FRBR (Functional Requirements for Bibliographic Records) terminology.

## Finite and Continuing

- Finite Resource:
*No definition in AACR; by implication the opposite of “continuing”:*
- A bibliographic resource issued once or over time **with a predetermined conclusion** (completed** **within **a finite number of parts or iterations**).
- Includes monographs and finite integrating resources.
- Continuing Resource:
- A bibliographic resource **issued over time with no predetermined conclusion**.
- Includes serials and ongoing integrating resources.

## Monograph and Serial

- Monograph:
- A bibliographic resource that is complete in one part or intended to be completed in a finite number of parts.
- Serial:
- A continuing resource issued in a succession of discrete parts, usually bearing numbering, that has no predetermined conclusion.
- Examples include journals, magazines, electronic journals, continuing directories, annual reports, newspapers, and monographic series.

**Notes:**
Note the elements that make a resource a serial.

## Integrating Resource

- A bibliographic resource that is added to or changed by means of updates that do not remain discrete and are integrated into the whole.
- Integrating resources can be either finite or continuing.
- Examples include updating loose-leafs and updating Web sites.
**Iteration**: An instance of an integrating resource, either as first published or after it has been updated.

## Three Major Types of IR

**Updating Loose-leaf**
- A bibliographic resource that consists of a base volume(s) updated by separate pages, which are inserted, removed, and/or substituted.
**Updating Database**
- A database is a collection of logically interrelated data stored together in one or more computerized files, usually created and managed by a database management system.
**Updating Web Site**
- A Web site that is updated, but does not fit into one of the other Type of Continuing Resource categories.
- Definitions from: *MARC 21 Format for Bibliographic Data*, 008 – Serials p. 8 (character position 21: Type of Continuing Resource).

**Notes:**
Definitions of “database” and “Web site” may need to be further developed and clarified in future documentation and training.

## Updating Loose-Leaf

- PCC Integrating Resources Training

**Notes:**
A familiar example of an updating loose-leaf.  The physical loose-leaf format alone does not make a resource integrating.  Only if the loose-leaf pages are added, discarded, and/or replaced over time is it integrating.  Finite monographs may also be published in a physical loose-leaf format (i.e., a static document, with no replacement pages).

## Updating Database

- PCC Integrating Resources Training

**Notes:**
Only remote-access updating databases are integrating resources.  All direct-access updating databases, e.g., those on CD-ROM, will have numbered “issues” and be treated as serials.  
Note that an updating database consisting of journal articles taken from different journals, such as JSTOR, is not a serial but an integrating resource.

## Updating Web Site

- PCC Integrating Resources Training

**Notes:**
A familiar Web site that undergoes continuous change over time.

## Continuing and Finite IR

**Continuing** integrating resource:
- Issued over time in a series of iterations with         no predetermined conclusion.
- Most integrating resources are continuing.
**Finite** integrating resource:
- Issued over time with a predetermined conclusion; intended to be completed in a finite number of iterations.

## Finite Updating Web Site

- PCC Integrating Resources Training

- _http://www.uwlax.edu/murphylibrary/waal2001/postconf.htm_

**Notes:**
An example of a finite updating web site for an annual conference: the site was updated with new content until the conference was over and final post-conference content was added; then it ceased to be updated: note “Last updated” date at bottom of home page.

## Brief Cataloging Highlights

**Four things** that will be especially new and different for catalogers of integrating resources

## 1) AACR2 Chapters

- Use AACR2 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 [& 2.5]**.
- _For updating Web site_: use Chapters **12 & 9**.
- _For updating cartographic Web site_: use Chapters **12, 9, & 3**.

**Notes:**
Chapter 12 covers almost all aspects printed integrating resources; in effect the only part of Chapter 2 that is used for loose-leafs will be Area 2.5 on physical description.
Catalogers of updating electronic resources will now need to learn and use Chapter 12 in addition to Chapter 9 for bibliographic description.

## 2) Integrated Entry

**Existing bibliographic record is** **changed** to describe current iteration of the resource.
- Most areas of description based on** ****latest iteration**.
- Different 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 medium still under consideration.)
- Bibliographic records for integrating resources will therefore 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 the MARC 21 Format for Bibliographic Data. 

## 3) MARC Variable Fields

- Some notes will be tagged in variable fields formerly used for serials.
- For example:
**247** – for former title.
**310** – for frequency of updates.
**362 1** – for dates of publication when not from first/last iteration.
**550** – for issuing body information.
- These fields will be new for most monographs catalogers.

**Notes:**
Most variable fields were open for use in records for all types of materials at time of format integration, but many such as these were not used in practice for most monographic cataloging.  OCLC will enable their use in monographs records as of December 1, 2002.

## 4) MARC Leader and 006/008

- New codes for integrating resources published but not yet implemented by the utilities:
- Leader/07 (Bibliographic level) code “**i**” for Integrating resource.
- New Serials **006/008** codes for integrating resources.
**Prior to implementation of code “i”:**
- Continue to code integrating resources as Monographs: **Bibliographic level** “**m**”.
**Add ****Serials 006** using new values for integrating resources.

**Notes:**
Because of the complexities of searching, indexing, and display tables, the bibliographic utilities will not be able to implement Bibliographic Level code “i” before July 2003 at earliest.  Until that time we will code integrating resources with Bibliographic level code “m”.  But OCLC and RLG will be able to implement the new 006/008 fixed-length data element codes for integrating resources as of December 1, 2002, with the exception of 006/17 (Entry convention) code “2” in RLIN.  
Therefore our practice should be to add the Serials 006 to all records for integrating resources during this interim period prior to the implementation of code “i”.  Also, libraries that input directly into the RLG Union Catalog will not be able to use code “2” in 006/17 until later implementation; they should use the fill character instead in this position.  
After code “i” is implemented, records with the serials 006 containing values unique to integrating resources should be able to be identified and automatically converted to Bibliographic level “i”.  

## AACR2 2002 Overview for Integrating Resources

- An introduction to the brave new world of cataloging integrating resources

## Chapter 12 and New Scope: 12.0A

- _Former title_: “**Serials**”
- _New title_: “**Continuing Resources**”
- Covers the description of _all_ continuing resources:
**Successively issued resources**, i.e., **serials.**
**Integrating resources**, e.g., updating loose-leafs, updating Web sites.
- Also covers selected categories of _finite_ resources that exhibit certain characteristics of serials:
- Reprints of serials.
- Finite integrating resources.
- Resources with characteristics of serials but whose duration is limited

**Notes:**
Most of the rules in each area of description have separate sections specifying how they apply to both (a) serials and (b) integrating resources.
This presentation deals only with the rules for integrating resources, and covers primarily only those areas that will be different from pre-2002 practice.
It is important for loose-leaf catalogers to know that the principles in Hallam’s loose-leaf manual were generalized and moved into Chapter 12 so that in general there is not that much change form pre-2002 practice for cataloging loose-leafs.

## Basis of the Description: 12.0B1b 

- Areas based on _current_ iteration:
- 1. Title and statement of responsibility.
- 2. Edition.
- 3. Material-specific details.
- [e.g., Type and extent of electronic resource]
- 4. Publication, distribution, etc.
- [Except Dates]
- 5. Physical description.
- [Not used for remote access e-resources]
- 6. Series.

**Notes:**
Each area of description will also have rules for both (1) how to record the information in the area and (2) how to deal with changes to  information in that area in later iterations of a resource.  

## Basis of the Description: 12.0B1b

- Area based on _first and/or last_ iterations:
- 4F. Dates of publication, distribution, etc.
- Areas based on _all_ iterations and any other source:
- 7. Note.
- 8. Standard number and terms of availability.

## Chief Source of Information: 12.0B2

- Printed resources (updating loose-leafs):
- Title page or title page substitute.
- Nonprint resources (updating Web sites and databases):
- Follow directions in subrule .0B in the relevant chapter.
- For electronic resources: Rule 9.0B.

## 1. Title and Statement of Responsibility Area

## Transcription of Title Proper: 1.1B1 and 12.1B

- 1.1B1: Do not transcribe introductory words not intended to be part of the title (such as “Welcome to”); instead give the title with these words in a note.
- 12.1B1: Correct obvious typographic errors and give title as it appears in a note.
- 12.1B2: When title appears in full and in the form of an acronym or initialism, choose the full form (e.g., *Program for Cooperative Cataloging* instead of *PCC*).
- 12.1B4: If resource is a part of another resource and bears both the common title and its own section title, give both in that order, separated by a period. E.g.:
- 245 10 $a Program for Cooperative Cataloging. BIBCO home page $h [electronic resource].

**Notes:**
This is a condensation of what are probably the most significant rules that will be new for transcribing title information integrating resources; it does not include all the rules nor the full text of the rules stated here..
1.1B1 is especially noteworthy for IR in addressing online resources that begin with “Welcome to.” 
LCRI 12.1B4 For updating remote electronic resources, “what appears at first to be a common title may instead be a statement of responsibility, the name of the  parent electronic resource, or another component of the resource.  If in doubt, do not consider it to be a common title.”

## Change in Title Proper: 12.1B8

- If changes appear in title proper in later iteration:
- Change the title and statement of responsibility area (245 $a/n/p) to reflect the current iteration.
- And, in most cases, give the earlier title in a note.
- Use MARC 247 and/or 547 fields for this.
- See section on notes ahead (12.7B42) for examples.
- LCRI: Identify which iteration prior to the current had this form of the title proper.
- [See also rules 21.2C1 and 21.30J.]

**Notes:**
The rule will read “in general” give the earlier title proper in a note.  This contrasts with the rule for changes in all other areas of description, which will direct us to give earlier forms in a note only “if considered important.”  
The rule here does not say “always” so as to give us some wiggle room in cases of very minor changes in wording that are not likely to affect access, such as a small change in the 12th word of a 14-word title or such cases.
The slides on notes will give examples of how to record changes in title proper using fields 247 and 547, which will be new to most non-serials catalogers.
See also LCRI 21.30J.

## Parallel Title and Other Title Information: 12.1D-E

- Transcription of other title information:
- Transcribe other title information only if considered to be important; do not transcribe if it consists only of words relating to the currency of the contents (12.1E).
- Changes to parallel title and/or other title info.:
- Change the title and statement of responsibility area (245 $b) to reflect the current iteration.
- Applies to other title info. only if recorded in Area 1.
- Make a note of the earlier form only if considered important.

**Notes:**
The rules allow more flexibility in recording other title information that is certain to change and is not integral to identifying the resource.
Changes in parallel titles and other title information may be accounted for in 500 or 547 title complexity notes.  They are not, however, entered into field 247.  In the relatively rare cases where such former title information is considered important for access, field 246 will need to be used with $i note to explain the entry [see LCRI 12.7B4 and 21.30J].

## Statements of Responsibility: 12.1F

- Transcription:
- Record statements relating to editors in this area only if considered to be important (12.1F3b).
- Changes:
- If a statement of responsibility is added, deleted, or changed in a later iteration:
- Change the title and statement of responsibility area to reflect the current iteration.
- Make a note if the change is considered to be important.
- [Note: such changes may also entail a change in choice of main entry; see slides ahead for examples.]

## 2. Edition Area

## Transcription of Edition Statement: 12.2B 

- Transcribe an edition statement if considered to be important.
- Statements indicating regular revision or frequent updating:
- Give as frequency information in the note area rather than as an edition statement (12.2B2; 12.7B1).
- [Note: Rule 9.2B8 to this effect is deleted in 2002 Amendments and is now covered here.]

## Change in Edition Information: 12.2F1b

- If edition information is added, deleted, or changed in a later iteration, and this change **does not require a new description**:
- Change the edition area to reflect the current iteration.
- Make a note if the change is considered to be important.** **
**Certain changes do require a new record:**
- When there is a change in edition information and the resource is considered to be a new work: see next slide 

**Notes:**
This is the one area in which a change in information might in some cases require a new bibliographic record / description.
See the next slide for LC’s interpretation of what kinds of changes require a new description.

## Change in Edition Information: LCRI 12.2F1

- Make a new description/record:
- For updating loose-leafs: only if there is a new base volume (i.e., an *in toto* replacement edition), but not for a gradual replacement edition with no new base volume.
- For updating remote access e-resources: only if the resource described in the existing record continues to exist as a resource separate from new resource to be cataloged.

**Notes:**
This LC Rule Interpretation helps to clarify when to make a new record and when to change the existing record.

## 3. Material-Specific Details Area

- 12.3 – Numbering Area
- 9.3 – Type and Extent of Resource Area

## Numbering Area: 12.3

- This area is not generally applicable to integrating resources.
- [Note: use of MARC field 362:
- 362 with first indicator 0 (zero) is a formatted designation used for serials numbering, _not_ for integrating resources.
- 362 with first indicator 1 is an unformatted note that may be used for giving date information for some integrating resources when first/last iterations are not available.
- See slides on publication dates (Area 4F).]

## Type and Extent of Electronic Resource Area [9.3]

- If this area is used in the description, and  the type and/or extent of the electronic resource changes:
- Change the type and extent of resource area to reflect the current iteration.
- Make a note if the change is considered to be important.

**Notes:**
This rule does not actually appear in Chapter 12, which covers Area 3 only for printed continuing resources (i.e., serials); nor does it appear in Chapter 9, which does not cover changes in the description for integrating resources.  It seems to have been unintentionally overlooked, but the consistency of the rules implies that the same approach be applied to this area as to the other areas of description based on the current iteration of an integrating resource. 
Also, the LCRI for 12.7A2 instructs that if the information for the Type and extent of resource area is added, deleted, or changed on a subsequent iteration, the steps above should be followed.

## 4. Publication, Distribution, Etc. Area

## Change in Place or Name or Publisher: 12.4C2 ; 12.4D2

- If the place and/or name of the publisher, distributor, etc. changes in a later iteration:
- Change the publication, distribution, etc., area to reflect the current iteration
- Give the earlier place and/or name in a note if considered important.

## Dates of Publication: 1.4F8 ; 12.4F

- If the first and/or last iteration is available, give the beginning and/or ending dates in this area.
- If first/last iteration is not available, do not give the date(s) in this area;
- Instead, give date information in a note if it can be readily ascertained.
- Optionally, supply the date(s) in this area if they can be readily ascertained.
- LC/PCC practice for IR: apply this option on a case-by-case basis when the resource includes an explicit statement [LCRI1.4F8].

**Notes:**
The main rule about dates for integrating resources stresses whether or not the cataloger has the first and/or last iteration of the resource available for viewing at the time of cataloging.  
The optional rule allows the cataloger to supply the dates if readily ascertainable whether or not the first and/or last iteration is available.
For updating loose-leafs, catalogers may fairly easily determine whether or not they have the first and/or last iteration in hand.
For updating Web sites and databases, this will be in most cases impossible to determine, especially for the “first” iteration.  
LC and PCC have decided to apply the option of supplying these dates when the fist/last part or iteration is not available for multipart items and integrating resources, but not for serials; this applies only when the bibliographic resource includes an explicit statement.

## Dates of Publication: 1.4F8 ; 12.4F 

**Use hyphens in dates for integrating resources:**
- _Beginning date_ (resource ongoing, beginning date available):
- 1998-
- _Ending date_ (resource completed, beginning date not available):
- -2001
- _Beginning and ending dates_ (resource completed, both dates available):
- 1998-2001.
- _For updating loose-leafs: also supply the date of last update if considered important_:
- 1996-1999 [updated 2000].

**Notes:**
The last bullet on this slide applies to loose-leafs when the date of the last update differs from the latest date of publication appearing on the chief source.

## Dates for Electronic IR (1)

- Most will be ongoing, not yet completed.
- Will have “open” date, followed by a hyphen.
- Most will not have “first iteration” available.
- Impossible to determine for most Web resources.
- Beginning date may be readily ascertainable even if “first iteration” not available.
- May be explicitly stated (e.g., on home page or “about” page).
- May have range of copyright dates where the first date can  be taken as explicit statement of beginning date.

**Notes:**
Most updating Web sites and databases change frequently or continually over time and have no numbering or other clear indications of “first” vs. subsequent iterations.  Therefore the concept of “first iteration” does not work terribly well for electronic integrating resources.
Often there is no indication of the date (year) that the Web site or database was first “published” on the Web.  But in some cases such a date is explicitly stated on the home page or, more frequently, on a separate “about” page for the resource.
A single copyright date, e.g., (c)2002, especially when it is the current year, is not likely to the the beginning date for the resource.  But when you have a range of copyright dates, e.g., (c)1997-2002, and these apply to the whole resource being cataloged and not just a part of the whole, then the first date in the range can usually reasonably be taken to indicate the beginning date of the publication.  But note that the second date is not the concluding date of the integrating resource, which is continuing, but rather simply indicates that the copyright continues from the time the resource began on the Web into the current year.  That second date in the range will change annually to indicate the current year.

## Dates for Electronic IR (2)

- If following LC/PCC practice to apply the option, give explicitly stated dates in 260 $c:
- 260    New York : $b Corona, $c 1997-
- 260    New York : $b Corona, $c 2001-
- If no beginning date is explicitly stated within the resource, omit 260 $c and give more general date information in a note instead:
- 260     New York : $b Corona
- 362 1  Began in 1997.         [date ascertainable but not stated]
- 362 1  Began in 1990’s.       [date not ascertainable]
- 362 1  Began in late 1990’s or early 2000’s.

**Notes:**
Reminder: this slide depicts what to do only if the first iteration is not available.  As said before, it will be the rare case in which catalogers will know that they are viewing the “first iteration” of an updating Web site or database.  Therefore this will be by far the most common situation for electronic integrating resources.

## 5. Physical Description Area

-  Used for _printed_ IR:
-  Updating loose-leafs.
-  Not used for _electronic_ IR:
-  Updating Web sites & databases.

## Physical Description: 12.5B

- 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.

## Physical Description: 12.5D2

- _Change in dimensions_:
- Change 300 $c to reflect current iteration.
- LCRI 12.5D2: If there is more than one unit in the current iteration and those units differ in size, record the range of dimensions:
- 300    $a v. (loose-leaf) ; **$c 24-26 cm.**

## 6. Series Area

## Change in Series Statement: 12.6B2

- If a series is added, deleted, or changed in a later iteration:
- Change the series area to reflect the current iteration.
- MARC 4XX and/or 8XX.
- Make a note if the change is considered important.
- Retain former series entries in 8XX if traced in local library, justified by 500 note explaining the change in series.

## Example: 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.)

## 7. Note Area

## General Rules for Notes for IR

- Include all notes prescribed by the** **relevant AACR2 chapter for the content being cataloged, and any other notes considered important.
- 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.

## MARC Tagging of Notes

- Most notes tagged in MARC **5XX** range.
- Some AACR2 notes will be tagged in other MARC fields, such as:
**247** for former title proper.
**310** for frequency of updates.
**362 1** for publication date information when not from first/last iteration.
- Some fields formerly used primarily or exclusively for serials will now be used for integrating resources as well.

**Notes:**
This presentation is covering the bibliographic description in AACR2 order, rather than MARC tagging order.  Some of these fields serve both as notes and as searchable entries, such as 247, just as 246 and 440 do.  That is, they do double-duty as description and access points at the same time.

## Identification of Iterations in Notes: LCRI 12.7A2

- When a data element changes (LC/PCC Practice):
- Give exact information about the timing of the change if that information is readily available
- If exact information is not readily available, use information already in the record to locate in time the presence of the earlier data element.
- Give that information in angle brackets.
- _For electronic IR_: use the date from the “viewed on” information.
- _For non-electronic IR_: use information from a “Description based on” note.

**Notes:**
This is LC/PCC practice.  If the cataloger does have the exact date of a change, this exact date is used.  This may happen with loose-leafs but is much less likely with most updating Web sites and databases.

## Frequency Note: 12.7B1

- Note the frequency of updates to an integrating resource.
- _Unless_:
- Frequency is apparent from content of the title and statement of responsibility area
- Frequency of updates is unknown.
- _LC/PCC Practice_:
- _Always_ give a note for known frequency of updates, even if already apparent from the rest of the description [LCRI 12.7B1].

**Notes:**
Question: what constitutes a “know” frequency of updates?  For most loose-leafs this may be stated or be readily apparent.  For most Web sites and database that are continually, frequently, and/or irregularly updated, the “frequency” may be considered to be “unknown” and therefore omitted from the record.

## Frequency Note: MARC Tagging

- State _current frequency_ in 310 frequency note.
- 310    Updated quarterly
- 310    Continuously updated
- 310    Updated irregularly, $b 2001-
- State _former frequencies_ in 321 former frequency note.
- 321    Updated monthly, $b 1998-2000
- 321    Frequency of updates varies, $b –2001

**Notes:**
Note the use of dates in subfield $b when the frequency changes..
Reminder: the code in the Frequency 008 element is based on the content of the 310 field.

## Example: 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 Jan. 1997-June 2001
- 500 ## $a Description based on: update 19, published in July 2001.

## Example: 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 Continually updated, $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).

## Change in Title Proper Note: 12.7B4.2

- Make notes on earlier titles proper.
- MARC tagging:
- 247: Former title proper.
- Use to generate title added entry in addition to note.
- Use for title proper only.
- 547: Former title proper complexity note.
- Use for more complex situations and/or when a title added entry is not needed.
- 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.

## Example: 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 6, published 2000.
*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 6, published 2000.
- 500 ## $a Description based on: update 7, published 2001.

**Notes:**
In this loose-leaf example, the exact timing of each title change in title is known and coincides with a specific published update.
Note the use of the “Description based on” information already in the record to identify the iteration to which the former title proper applied.  Each time the record is updated to change the title proper, the Description based on note in the body of the record is changed, and the previous “Description based on” date is transferred to the 247 field to which it applies.  

## Example: Change in Title Proper (Web site)

*Existing record:*
- 245 00 $a Early music resources on the Web $h [electronic resource].
- 500 ## $a Title from HTML header (viewed Jan. 5, 1999)
*Same record updated:*
- 245 00 $a Resources for early music $h [electronic resource].
- 247 10 $a Early music resources on the Web $f <Jan. 5, 1999>
- 500 ## $a Title from HTML header (viewed Apr. 15, 2001)
*Same record updated again:*
- 245 00 $a Resources for early music scholars $h [electronic resource].
- 247 10 $a Early music resources on the Web $f <Jan. 5, 1999>
- 247 10 $a Resources for early music $f <Apr. 15, 2001>
- 500 ## $a Title from HTML header (viewed July 7, 2002)

**Notes:**
In this Web site example, the exact timing of each title change in title is NOT known; therefore the cataloger uses the “date viewed” information already present in the record to identify the iteration to which the former title proper applied, and this date information is give in angle brackets in the 247 former title proper field.  Each time the record is updated to change the title proper, the date viewed in the 500 note in the body of the record is changed, and the previous date viewed is transferred to the 247 field to which it applies.

## Notes for Changes in Description

- Make notes on information no longer present in current iteration, or that appeared in a different form in previous iterations, if considered to be important.
- If the changes have been numerous, make a general statement.
- Rules given for each area, for example:
- 12.7B5.2b: Change in parallel title.
- 12.7B6.2b: Change in other title information.
- 12.7B7.2b: Change in statements of responsibility.
- 12.7B9.2b: Change in edition information.
- 12.7B11.2b: Change in place of publication or publisher.
- 12.7B12.2b: Change in physical details.

## Bibliographic History and Relationships Note: 12.7B8

- Note the bibliographic history and important relationships between resource being described and other related resources, such as:
- Continuations
- Mergers
- Splits
- Absorptions
- Translations
- Supplements
- Simultaneous editions

**Notes:**
These kinds of bibliographic history and relationships and their MARC tagging have been worked out in detail for serials. LC/PCC practice is to apply Rule 12.7B8 to both serials and integrating resources, using the same MARC tags.  See LCRI 12.7B8 for some further guidance.

## Publication, Etc. Note: 12.7B11

- Make notes on beginning and/or ending dates of publication not recorded in the publication area (260 $c).
- e.g., when not cataloging from first/last iteration.
- Use field 362 1_ (unformatted note).
- Only an unformatted 362 field is used for IR.
- Examples:
- 362 1  Began in 1987.
- 362 1  Ceased in 1999.
- 362 1  Began in 1973; ceased in 2001.

**Notes:**
The use of this note ties in with the rules for Dates of publication, distribution, etc. in Area 4 (1.4F8 ; 12.4F).
Recall the difference between the formatted and unformatted forms of the 362 field mentioned in the slide on the Numbering Area (12.3).

## 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.
- For remote-access resources, _always_ give date on which resource was viewed for description.
- 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: the format for remote-access resources is not prescribed, but has become common practice and is given in examples in AACR2.

## 8. Standard Number [etc.] Area

- Standard Number: 12.8B1
- 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.

## Access Points

## Main and Added Entries

-  Changes in name and uniform title entries.
- 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.

## 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.

## Example: Change in 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 Membership directory / $c DEF Association.
- 500 ## $a Description based on: update 5, published 2000.
- 550 ## $a Issued by ABC Association (update 2, published 1998.
- 710 2# $a ABC Association.

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

*Same record updated again:*
- 110 2# $a GHI Association.
- 245 10 $a Membership directory / $c GHI Association.
- 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.

## 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 Leader and 006/008

## MARC Leader and 006/008

- Most new IR values to be implemented by OCLC and RLIN in December, 2002.
- Except for Leader/07 code “i”.
- Not implemented until ca. July 2003 or later.
- And, in RLIN only: Serials 006/17 (entry convention) code “2”.
- Interim coding practice will therefore be required.

## 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.

## Leader: Bibliographic Level

- Previously existing codes:
- a - Monographic component part
- b - Serial component part
- c - Collection
- d - Subunit
**m - Monograph/item**
**s – Serial**
- New code added:
**i - Integrating resource**

**Notes:**
Remember that code “m” will continue to be used until code “i” is implemented.

## Leader and 008 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 of code “i”, the Serials 008 elements will be used for most integrating resources.  Since these elements are being broadened to include integrating resources in addition to serials, the name is likely to be changed from Serials to Continuing Resources or something similar.

## 008 and 006

- _All records_ for integrating resources may include these continuing resources elements:
- Will be in **008** when resource content is primarily textual.
- May be added in **006** when primary resource content is other than textual.
- E.g.: cartographic, computer file, sound, visual.
- Serials 006 is optional in MARC records, but may be valuable to add for systems that use any of the codes for searching, indexing, etc.

**Notes:**
The serials [continuing resources] fixed-length data elements may be added in a 006 field to any record in which the 008 does not contain them.

## Interim Practice

- Before implementation of Bibliographic Level code “i”:
- _For loose-leafs and textual electronic resources_:
- Use Type “**a**” + Bib. Level “**m**” with resulting “**Books**” 008.
- _For non-textual electronic resources_:
- Use Type code appropriate to the content of the resource  + Bib. Level “**m**”, resulting in the appropriate 008, such as “Computer files” or “Maps”.
_**Add Serials 006**_ to all records to code for the continuing/integrating aspects of the resource.
- RLIN catalogers: code Serials 006/17 with the fill character until code “2” (Integrated entry) is implemented.

**Notes:**
But before we get to the eventual targeted coding practice as depicted in the previous two slides, we will follow this interim coding practice, using the Serials [continuing resources] 006 in all records for integrating resources, and using the new codes for integrating resources --with the exception of 006/17 (Entry convention) code “2” in RLIN.  Libraries that input directly into the RLG Union Catalog will not be able to use code “2” in 006/17 until further notice; the fill character should be used instead in this position.

## New 006/008 Elements

- Additions and changes to Serials 006/008 for continuing resources:
- Frequency [006/01]
- (Includes new code)
- Type of Continuing Resource [006/04]
- Formerly named: Type of Serial
- Entry Convention [006/17]
- Formerly named: Successive/Latest Entry

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

## Frequency

- Frequency of issues for serials;
- Frequency of updates for integrating resources.
- Previously-existing values include, among many others:
- “**a**” – Annual
- “**d**” – Daily
- “**q**” – Quarterly
- “**w**” - Weekly
- New value added:
- “**k**” – Continuously updated
- Always coordinated with “Regularity” element.

**Notes:**
This field contains numerous codes for different frequencies.  Only a few are given here for the benefit of those (e.g., monographs catalogers) who are not familiar with this element.

## Type of Continuing Resource

- Previously-existing values include:
**m** - Monographic series
**n** - Newspaper
**p** - Periodical
- New values added:** **
**d **- Updating database
**l** - Updating loose-leaf
**w** - Updating Web site

**Notes:**
Three new values for integrating resources have been added to the three existing serials values.

## Entry Convention (1)

- Previously-existing values:
**0 - Successive entry**
- New bibliographic record created with major change in title proper, or when corporate body main entry or corporate body uniform title qualifier changes, etc.
**1 - Latest entry**
- Item is cataloged under its most recent title or issuing body (pre-AACR cataloging rules).

**Notes:**
Note: these definitions are taken directly from the MARC 21 format for Bibliographic Data.
Serials cataloged according to AACR2 use the Successive entry convention.  Serials cataloged prior to AACR2 used the Latest entry convention.

## Entry Convention (2)

- 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.

**Notes:**
Integrating resources are cataloged using the Integrated entry convention.  The definition here is taken directly form the MARC 21 Format for Bibliographic Data.  Note that Integrated entry is basically the same convention as Latest entry, but the name distinguishes this AACR2 cataloging convention used for integrating resources from the pre-AACR2 cataloging convention used for serials. 

## Other 006/008 Elements for continuing resources

- Regularity
- ISSN center
- Form of original item
- Form of item
- Nature of entire work
- Nature of contents

- Government publication
- Conference publication
- Original alphabet or script of title

**Notes:**
These are the remaining Serials 006/008 elements that will apply to all continuing resources, both serials and integrating resources.  They will be used in either the 006 or 008: in the 006 in all records before implementation of Bibliographic level code “i”, and in either the 008 or 006 after implementation.

## Additional Examples

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

- Description if created _before_ 2002 Amendments:
- 245 00 $a Educational resources cataloging guidelines.
- 250 ## $a 2nd ed.
- 260 ## $a Monroe, NJ : $b Gosford, $c 1989-
- 300 ## $a 2 v. (loose-leaf) ; $c 30 cm.
- Description if created _after_ 2002 Amendments*:*
- 245 00 $a Educational resources cataloging guidelines.
- 250 ## $a 2nd ed.
- 260 ## $a Monroe, NJ : $b Gosford, $c 1989-
- 300 ## $a v. (loose-leaf) ; $c 30 cm.
- 310 ## $a Updated quarterly

**Notes:**
Note that this and the following slides do not imply that descriptive cataloging that was valid according to rules at the time of original record creation pre-2002 should be edited to conform to post-2002 rules.  These examples are meant only to illustrate differences in how a cataloger would create an new original record before and after the 2002 Amendments.

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

- Description if created _before_ 2002 Amendments:* *
- 245 00 Comparative religions web $h [electronic resource].
- 260 ## $a Berkeley, Calif. : $b RELCOM, $c [199-]-
- 500 ## $a Title from title screen (viewed Oct. 1, 2001).
- Description if created _after_ 2002 Amendments:* *
- 245 00 Comparative religions web $h [electronic resource].
- 260 ## $a Berkeley, Calif. : $b RELCOM
- 362 1# $a Began in late 1990’s.
- 500 ## $a Title from home page (viewed Oct. 1, 2002).

**Notes:**
These records reflect the fairly common case where the cataloger cannot ascertain the beginning date of the Web site other than it began sometime in the late 1990’s.  Prior to the 2002 Amendments, a date always needed to be supplied in the publication area (260 $c).  Even if choosing to supply a ascertainable date when not cataloging from the first iteration, most catalogers would probably judge that this date is not “readily ascertainable” and choose to omit it from the publication area.  The value of including the publication date note (in 362 1) may be debatable.  We may see clarification of “best practice” for this situation in the near future.

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

- If description is created based on available _first iteration_:
- 245 00 $a Kramer’s guide to MARC 21 format for holdings data.
- 250 ## $a 2000 ed.
- 260 ## $a Chicago : $b Kramer Library, $c c2000-
- 300 ## $a v. (loose-leaf) ; $c 30 cm.
- If description is created based on _later iteration_, with first iteration _not_ available:
- 245 00 $a Kramer’s guide to MARC 21 format for holdings data.
- 250 ## $a 2000 ed.
- 260 ## $a Chicago : $b Kramer Library
- 300 ## $a v. (loose-leaf) ; $c 30 cm.
- 362 1# $a Began in Oct. 2000.
- 500 ## $a Description based on: update no. 2, published Oct. 2001.

## Description of Finite Updating Web Site

- Conference Web site: began in 2000; frequently updated until it ceased with last update Feb. 20, 2001.
- 245 10 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 home page (viewed Mar. 20, 2002).
- 856 40 $u http://www.uwlax.edu/murphylibrary/waal2001/

## Leader & 006/008: Interim Practice: Dec. 2002 – after ca. July 2003 

- 245 00 **Global invasive species database** $h [electronic resource].
- Record _before Dec. 2002_ implementation of new 006/008 codes:
- Leader/06 (Type of Record)          a - Language material
- Leader/07 (Bibliographic Level)     m - Monograph
- 008 (Fixed length data elements)  Books
- Record _after Dec. 2002_ implementation of new 006/008 codes:
- Leader/06 (Type of Record)         a - Language material
- Leader/07 (Bibliographic Level)    m - Monograph
- 008 (Fixed length data elements) Books
- 006/00 (Form of material)           Serial
- 006/01 (Frequency)                    k – Continuously updated
- 006/04 (Type of cont. resource)  d - Updating database
- 006/17 (Entry convention)           2 – Integrated entry

**Notes:**
Remember that libraries that input directly into the RLG Union Catalog will not be able to use code “2” in 006/17 until future implementation and that until that time the fill character should be used instead in this position.

## Leader and 008: Eventual Practice: sometime after ca. July 2003 

- 245 00 **Global invasive species database** $h [electronic resource].
- Record before implementation of Leader/07 code “i”:
- 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 Leader/07 code “i”:
- Leader/06 (Type of Record)                         a - Language material
- Leader/07 (Bibliographic Level)                    i - Integrating resource
- 008 (Fixed length data elements                  Serials [Continuing resources]
- 008/06 (Publication status)                          c – Currently published
- 008/18 (Frequency)                                    k – Continuously updated
- 008/21 (Type of cont. resource)                  d - Updating database
- 008/34 (Entry convention)                          2 – Integrated entry

## Concluding Review

## Review: Definitions

- _Integrating resources_:
- Added to or changed by means of updates that do not remain discrete and are integrated into the whole.
- Include updating loose-leafs, updating databases, and updating Web sites.
- Most are continuing; some are finite.

## Review: Bib. Description

- _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.

## Review: MARC Coding

- _Interim__** **__MARC coding: before implementation of Bibliographic Level  “i”_:
- Code IR as monographs: Bibliographic level “m”.
- Add Serials 006 with integrating resources codes.
- _MARC coding after implementation of code “i”_:
*All* will have Bibliographic Level code “i”.
*Most* will be have Type of Record “a” and Serials 008 .
*Some* will have have other Type of Record codes and 008s.
- May also then add Serials 006 to code for integrating aspects.

**Notes:**
[A final reminder that libraries that input directly into the RLG Union Catalog will not be able to use code “2” in 006/17 until future implementation and that until that time they should use the fill character in this position instead.]

## END