# Presentation: 696129

## Session 3 Updating IR Records for Changes in Bibliographic Elements

**Notes:**
Optional Warm Up Exercises
 What kinds of changes can you think of that take place in Web sites, online databases, and updating loose-leafs?  Which areas in a bibliographic record could be affected by changes in an online resource?  

Instructor References
The Instructor is advised to consult the following:
 AACR Chapter 12 and the corresponding LCRIs: those rules that specifically address changes in integrating resources.

## Goals for Session 3

- Learn how to update existing records when data elements have changed
- Understand how to apply AACR2 chapter 12 rules and MARC coding for integrating entry cataloging

**Notes:**
Object:
 The object of this session is to give an overview of how to update existing bibliographic records when a cataloger discovers that a bibliographic data element of the resource has changed in an later iteration of a resource after the original record was created or since the last time the bibliographic record was updated.  
 This will come up for catalogers in practice when copy cataloging or if one’s institution has policies and procedures for doing regular record maintenance for integrating resources.
 This lesson covers the rules in chapter 12 that deal with changes in integrating resources. 

Important note for instructors: The examples in this session use records as if originally created according to the new rules.  This is in order to better illustrate the new rules for updating records without getting sidetracked into other issues of modifying records created under previous cataloging rules.  This will be taken up in Session 4.

Participants' Goals:
 You might ask the participants if they have any additional or more specific goals or areas they especially want to learn about in this session.

## Changes can occur in any area of description or access points

- Title proper
- Parallel or other title information
- Statement of responsibility
- Edition
- Type and extent of resource [area no longer given]
- Places of publication or publisher names
- Series
- Standard number
- Notes (frequency, responsibility, summary)
- Choice of main and added entries
- Choice of subject headings
- Electronic location and address (URI / URL)

## [blank slide]

## Integrating entry cataloging

- The existing bibliographic record is changed to describe **the current iteration** of the resource
- Data elements of **previous iterations** are recorded in notes if required or if considered important
**A 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
- --Will be covered further ahead in this session

**Notes:**
This is the key to what makes the cataloging of integrating resources especially different from the cataloging of either monographs or current serials cataloging (using successive entry convention).

Terminology:
 In pre-AARC2 serials cataloging this convention was called “Latest entry”.  
 The term “Integrating entry” is new and distinguishes this practice as applying to non-serial resources cataloged according to AACR2.  
 As with “Latest entry”, the term “Integrating entry” does not appear in AACR2, but it does appear in the MARC 21 Format for Bibliographic Data. 

 Bibliographic records for integrating resources will require ongoing maintenance. How exactly this will happen remains to be developed, and will likely be different for different institutions. Individual institutions will need to develop policies for when maintenance will occur. [Possible discussion question: how do you think your institution will deal with updating bib records for changes in integrating resources?]

Note: The term “integrated entry” was sometimes incorrectly used in MARC 21 and other documentation.  The MARC 21 Concise Format online has amended this to “integrating entry.”  OCLC Bibliographic Formats and Standards and the full printed version of MARC 21 Format for Bibliographic Data still have “Integrated entry.”

## Review: Basis of the description for IRs

| Area |  | Basis of Description |
| --- | --- | --- |
| 1 | Title and statement of responsibility | Current iteration |
| 2 | Edition | Current iteration |
| 3 | Type and extent of resource | Current iteration |
| 4 | Place and publisher | Current iteration |
|  |    Dates | First and/or last iteration |
| 5 | Physical description | Current iteration |
| 6 | Series | Current iteration |
| 7 | Notes | All iterations (& any source) |
| 8 | Standard numbers | All iterations (& any source) |

**Notes:**
This slide reviews the basis of the description for integrating resources. Based on rule 12.0B1b.
 Remember that each area of description for integrating resources in chapter 12 has 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.  This session deals just with the latter: the rules that apply to how to deal with changes in later iterations of an integrating resource.

 All areas of description are based on the current iteration of the resource, except for dates of publication, notes, and standard numbers.  This means that the bibliographic record must be changed or updated to reflect the current iteration of a resource.

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

**Notes:**
This slide just shows that the revised chapter 12 provides rules for each area and sub-area of description that specifically address how to deal with changes in the content of that area or sub-area.

If the changes have been numerous, catalogers are instructed to make a general statement.

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

## Change in title proper: 12.1B8 and 21.2C1

- If changes appear in title proper in later iteration:
- Do not create a new record
- 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 proper in a note
- LCRI: Identify which prior iteration had this form of the title proper
- If considered necessary for access, make an added entry for the title proper of an earlier iteration
- Use MARC 247 and/or 547 fields for this
- See section on notes ahead (12.7B42) for examples

**Notes:**
 The rule actually states that the earlier form of the title proper should be given “in general”.  This contrasts with the rule for changes in all other areas of description, which 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.

 The main new piece of information here is that rule 21.30J does specifically address making added title entries for former titles proper in addition to notes.
 In the MARC record field 247 is used to make both notes and added title entries.
 Like the 245 and 246 fields, the 247 field does double-duty as both description and searchable access point.

## 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.
- Give in chronological order from oldest to most recent.
**547: Former title proper complexity note**
- Use for more complex situations and/or when a title added entry is not needed.
_**LCRI**__ 12.7B4.2_: 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:**
This slide deals with the rules specifically for making notes and the two MARC tags used for these notes.

The 247 field was formerly used in Latest Entry serial cataloging and will be new to many catalogers.
	Field is repeatable.
	Common practice is to give multiple 247 fields in chronological order from oldest to most recent.

The 547 field has to be used for more complex situations because the 247 field lacks subfield $i.

## Change in title proper example, slide 1

- _Existing record created in March 2000_:
- 245 00 **Database of biocatalysis and biodegradation information** $h [electronic resource].
- 500    Title from home page **(viewed on Mar. 4, 2000).**

- _What you discover when copy cataloging_:
- Title appearing on current iteration of home page [viewed on Dec. 15, 2002]
- --differs from title recorded in existing record for the Web site

**Notes:**
ANIMATED SLIDE
Trainers please note that this slide contains animations --the arrows on the slide appear with additional mouse clicks, use of the down arrow keyboard key, etc.

Scenario for participants:
 Your institution has selected this Web site for cataloging.
 You search for copy and find an existing record that matches in almost every way, including the URL, but has a different title in the 245 field of the bib record.
 The date in the Item described note tells you that this was the title that appeared on the home page when the resource was originally cataloged on March 4, 2000.
 You must update the record to reflect the title of the current iteration of the Web site, which you are viewing on December 15, 2002.

Note: When an electronic resource’s 245 title changes, a cataloger looks anew at the resource and decides “afresh” what the source of title will be for that iteration.

## Change in title proper example, slide 2

- _Record updated in December 2002_:
- 245 04 **The University of Minnesota biocatalysis/biodegradation database** $h [electronic resource].
**247** 10 Database of biocatalysis and biodegradation information **$f** <**Mar. 4, 2000**>
- 500    Title from home page **(viewed on Dec. 15, 2002).**

**Steps to modify the existing record:**
- Change the title in the 245 to match the current iteration.
- Move the former title to a 247 note/added entry field.
- Move the former date viewed to subfield $f of the 247 field.
- Change the date viewed in the 500 note to current date (current iteration).

- 245 00 **Database of biocatalysis and biodegradation information** $h [electronic resource].
- 500    Title from home page **(viewed on Mar. 4, 2000).**

**Notes:**
ANIMATED SLIDE

Steps to follow to update the record for the current iteration:
 Move the former title proper to a 247 former title proper field, which serves as both a note and a searchable added entry.
 Move the date the record was originally viewed for cataloging to the subfield $f of the 247 field.
 This shows that the former title appeared as such when viewed for description on that date.
 Record the current title proper in the 245 field.
 Change the date viewed for description in the Item described note to the current date you are viewing the resource and updating the description.
 The resource is now searchable by both current and former title, and the description reflects the current iteration of the resource.
 Another cataloger coming to this record should key into the three fields depicted in this slide to read the title history of the resource as recorded by catalogers during two different iterations in its life cycle.

Note: this slide shows only the title proper change for this iteration; there may be other changes as well in the complete resource and the resulting complete updated bibliographic record.

## Change in title proper and Links

***If***  you change a title proper in a bibliographic record,
***And***  that record has a reciprocal linking note for bibliographic history or relationships (76X-78X)
***Then  ***you must also change the linking field on the other record!

**Notes:**
An important reminder

## Changes to parallel title, other title information: 12.1D-E

- Change the title and statement of responsibility area (245 $b) to reflect the current iteration.
- Applies to other title information only if previously recorded in Area 1
- Make a note of the earlier form only if considered important.
- Record former other title information in field 246 and explain the situation in subfield $i.
- Use field 247 and 547 only for former title proper info.

**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 notes.  These can be tagged in fields 500 or 246.
 They are not, however, entered into field 247.  Only former titles proper go into the 247; and only former titles proper complex notes go into the 547.
 In cases where former parallel title or former other title information is considered important for access, field 246 will need to be used with $i note to explain the entry.  See LCRIs 12.7B5.2 and 12.7B6.2.
 Remember that field 246 can serve as either a note, as an added entry, or as both at the same time, depending on the first indicator value (Note/added entry controller):
 0 - Note, no added entry 
 1 - Note, added entry 
 2 - No note, no title added entry 
 3 - No note, added entry 

 See also LCRI 12.7B4 and 21.30J.

## Change in other title information example

- _Existing record created in October 1999_:
- 245 14 The nine planets $h [electronic resource] **: $b a tour of the solar system **/ $c by Bill Arnett.
- 500   Title from home page **(viewed on Oct. 9, 1999).**

- Subtitle on home page [when viewed on Dec. 15,  2002] differs from subtitle in existing record

**Notes:**
 Resource viewed on December 15, 2002.
 Existing record created on October 9, 1999: the subtitle was slightly different, it did not include the word “multimedia”, which was added sometime after 10/9/99.

## Change in other title information: Option 1

- _Option 1 for updating the record_: no note or added entry:
- 245 14 The nine planets $h [electronic resource] **: **$b a **multimedia** tour of the solar system / $c by Bill Arnett.
- 500   Title from home page **(viewed on Dec. 15, 2002).**

**Notes:**
The cataloger has at least three options in how to handle this change, illustrated on this and the following two slides

 Is the change in subtitle important enough to note?  If so it would be recorded in a 500 note or in a 246 with first indicator 0 , but not in a 247 or 547.

 This slide depicts the option of choosing to not mention the former subtitle in the bib record.

The issue of whether or not to record subtitle information was discussed in Session 2A on original cataloging, but it may resurface again here.  
 There is a definite difference in how culture differs between serial and monograph catalogers: serial catalogers are used to asking how valuable it is to record subtitle information because it could change and the record may have to be maintained over time.  Monograph catalogers are used to transcribing subtitles as they appear because the information is fixed and will not change.  Integrating resources may lie somewhere in between, with more necessity for individual cataloger judgment if the situation isn’t one of the three given in rule 12.1E1 requiring other title information to be transcribed.  

## Change in other title information: Option 2

- _Option 2 for updating the record_: note but no added entry:
- 245 14 The nine planets $h [electronic resource] : $b a **multimedia** tour of the solar system** **/ $c by Bill Arnett.
**246 ****0****_**** $i Former subtitle: $a Tour of the solar system $f <Oct. 9, 1999>**
**500    Former subtitle: A tour of the solar system <Oct. 9, 1999>.**

- Either 246 0 or 500 may be used to tag the note

**Notes:**
 This slide depicts the option of choosing to make a note about the former subtitle, but not an added entry.

 Note well: two options for making the note are depicted in the example: you would use one or the other but not both!  

 Remember that field 246 can serve as either a note, as an added entry, or as both at the same time, depending on the first indicator value (Note/added entry controller):
 0 - Note, no added entry 
 1 - Note, added entry 
 2 - No note, no title added entry 
 3 - No note, added entry 

 Another option might be to word the 500 note like this:
500    Subtitle varies.

## Change in other title information: Option 3

- _Option 3 for updating the record_: note and added title entry:
- 245 14 The nine planets $h [electronic resource] : $b a **multimedia** tour of the solar system** **/ $c by Bill Arnett.
**246 ****1****_ $i Former subtitle: $a Tour of the solar system $f <Oct. 9, 1999>**
- 500    Title from home page (viewed on Dec. 15, 2002).

## Changes to statement of responsibility: 12.1F5, 12.7B7.2

- Change the title and statement of responsibility area (245 $c)
- Make a note of the earlier form only if considered important.
- Record former statements of responsibility in field 500 if person or field 550 if corporate body

## 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.** **
- When does a change require a new description?
- See also LCRI 12.2F1 for guidelines (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.
 On the whole this should be quite rare for most Web sites and online databases.

## Change in edition information: LCRI 21.3B

**For updating loose-leafs:**
**Do not make a new description for a gradual replacement** **edition**
- (i.e., the author or publisher considers the publication to be a new edition and issues a replacement title page with a new edition statement but does not issue a new base volume); give a note about the new edition statement (see LCRI 12.7B9).
**In determining if there is a new resource, consider presence/absence and change of header/footer dates**
- See LCRI 21.3B for different situations
**For updating remote access electronic resources:**
**Make a new description only if the resource described in the existing record continues to exist as a resource separate from the new resource to be cataloged.**

**Notes:**
See LCRI 21.3B for guidelines on when to make a new record because edition information has changed or because a new base volume has been received. 

For an updating loose-leaf other than a gradual replacement edition, the decision to create a new record is based upon evidence related to the header/footer dates:  if they are present now but weren’t before and vice versa, various dates vs. same date, etc.  Catalogers should consult the LCRI for specifics.  The default is to create a new record.

## Change in edition example 1

- 245 10 Tax-advantaged securities : $b ILPs, pass-throughs, and other vehicles / $c by Robert J. Haft and Peter M. Fass.
**250    4th ed.**
- 260    [St. Paul, Minn.] : $b West Group, $c **1981- **
**500    Original edition statement: 3rd ed.; updated to 4th ed., 1987.**
- 500    Description based on: t.p., v. 4F-4G, release #58, Sept., 1998.

_**Gradual replacement  edition of loose-leaf**_**:**
- --Publisher issued a replacement title page with a new edition statement but did not issue a new base volume.

- Change 250 edition statement in existing record and add note on the change

**Notes:**
In this example no new record is needed because this was a gradual replacement edition.
 Although the concepts of major vs. minor changes have not yet been introduced into AACR2 or the LCRIs for integrating resources, we might consider this an example of a “minor change” for an integrating resource.

## Change in edition example 2

- 245 00 CONSER cataloging manual / ‡c Jean L. Hirons, editor.
- 260    Washington, DC : ‡b Library of Congress, Cataloging Distribution Service, ‡c **2002-**
**250    2002 ed.**
- 300    v. (loose-leaf) ; $c 29 cm.
**780 00 **$t CONSER cataloging manual. **$b 1st ed.** $z 0844407844 $w (DLC)___93009913_$w (OCoLC)27813639

_**Complete replacement edition of loose-leaf**_**:**
- Publisher issued *in toto*  replacement of base volume with new edition.

- Create new record for new ed.
- (May also link to record for 1st ed. using 780 linking entry)

**Notes:**
In this example a new record is needed because the entire base volume was replaced with the new edition.
 Although the concepts of major vs. minor changes have not yet been introduced into AACR2 or the LCRIs for integrating resources, we might consider this an example of a “major change” for an integrating resource.

## Change in Type and extent of resource

- This area was eliminated with the deletion of rule 9.3 in the 2004 update to AACR2
- If this area was used in the description and the type and/or extent changes, delete the 256 field

**Notes:**
IMPORTANT: This area was eliminated from the rules with the deletion of rule 9.3 in the 2004 Update to AACR2.  Generally retain the terms formerly used for this area (electronic data; electronic program(s); and, electronic data and program(s)) and any details about files, statements, bytes, etc., when using existing records for copy cataloging if the information still characterizes the resource.

Such information now can be given in a Type of computer file or data note (516 field), combined with other notes (e.g., a Summary note), or given in the 300 field if the new option in AACR2 9.5B3 is applied.

If field 256 was included in the record and the type and/or extent changes, delete the 256 field.

Note that LC never supplied this field in original cataloging but accepted it when doing copy cataloging.

## Change in place or name of 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 500 note if considered important.
- Also change MARC 008 Place of publication code to match place of current publisher!

## Change in publisher place & name example (1)

- _Existing record created in May 1997_:
- 008    Ctry: **vau**
- 245 04 The opera database $h [electronic resource].
- 260    **Richmond, VA** : $b **Kramer and Reynolds**, $c 1996-
- 500    Title from home page **(viewed on May 22, 1997).**

- Publisher name on home page (and place of publication on linked page) differ from data recorded in existing record

**Notes:**
Scenario for participants:
 Your institution has selected this Web site for cataloging.
 You search for copy and find an existing record that matches in almost every way, including the URL, but has a different publisher name and place of publication in the 260 field of the bib record.
 The date in the Item described note tells you that this was the publisher that appeared in the resource when it was originally cataloged on May 22, 1997.
 You must update the record to reflect the place and publisher of the current iteration of the Web site, which you are viewing on December 15, 2002.

## Change in publisher place & name example (2)

- 008    Ctry: **mdu**
- 245 04 The opera database $h [electronic resource].
- 260    **Baltimore, Md.** : $b **Marschner and Reynolds**, $c 1996-
- 500    Title from home page **(viewed on Dec. 15, 2002).**
**500    Formerly published by Kramer and Reynolds, Richmond, VA, 1996-<May 22, 1997>.**

- Change in publisher place & name example (2)

**Steps to modify the existing record:**
- Change publication data in 260 $a-b.
- Change Place of publication code in 008.
- Make note on previous publication info. (if considered important), with as much date information as available.
- Change date viewed in note to current date.

**Notes:**
You change the publisher area in the 260 field and make a note of the former publisher in a 500 note, with the range of dates for which it applied.  In this case you are working with existing bibliographic information that recorded Kramer and Reynolds as the publisher starting in 1996, but viewing it in December, 2002, you do not know exactly when the publisher name changed, so you use the viewed on date in angle brackets.

Always change the viewed-on date in the record when making changes that describe the current iteration.

## Change in physical description: 12.5 (1)

- _Change in other physical details_
- 12.5C2: Change area (300 $b) to reflect current iteration and make a note about difference if important; also update 008 if needed
- _Change in dimensions of updating loose-leaf_
- Note: error in rule 12.5D2 corrected in LCRI:
- If dimensions change, change area to match current iteration and make note about difference if important

## Change in physical description: 12.5 (2)

*When updating loose-leaf is completed:*
- Record the number of volumes

**300**    **2 v.** (loose-leaf) : $b ill. ; $c 28 cm.

## 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, justified by 500 note explaining the change in series.
- LCRI 21.30L: Integrating Resource in One or More Series
- LC practice:  Also provide an 8XX series added entry for any traced series included in a note.  (Series not present on the latest iteration will be given in the note area instead of in the series area — cf. AACR2 12.6B2 and 12.7B14.2b.)

**Notes:**
Instructor background:
LCRI 21.30L.  SERIES.
Integrating Resource in One or More Series
     LC practice:  Also provide an 8XX series added entry for any traced series included in a note.  (Series not present on the latest iteration will be given in the note area instead of in the series area — cf. AACR2 12.6B2 and 12.7B14.2b.)
existing record:
260 ## $a Chicago : $b CJ Press, $c 1983-
440 #0 $a Real estate professional series
same record updated later:
260 ## $a Chicago : $b CJ Press, $c 1983-
no 4XX field
500 ## $a Series title, 1983-1995: Real estate professional series
500 ## $a Description based on: release 23, published in Jan. 1996.
830 #0 $a Real estate professional series.
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 later:
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 series statement example

- _Same record updated_:
- 260    Denver : $b Smith Pub. Co.
**490 1**  Library acquisitions
**500    Series title <Oct. 3, 1991>:** Research in library acquisitions.
- 500    Title from home page (viewed on Dec. 15, 2002).
**830  **0 Research in library acquisitions.
**830 ** 0 Library acquisitions (Denver, Colo.)

- _Existing record_:
- 260    Denver : $b Smith Pub. Co.
**440  0** Research in library acquisitions
- 500    Title from title screen (viewed on Oct. 3, 1991).

## Change in frequency of updates (1)

- _Existing record created in February 1998_:
**Freq: f**   Regl: r
- 245 04 The EMBL reptile database $h [electronic resource].
**310    Updated semiannually**
- 500    Title from home page** (viewed on Feb. 8, 1998).**

- _What you discover when copy cataloging_:
- Frequency of updates stated on ‘Introduction’ page [viewed on Dec. 15, 2002]
- --differs from frequency recorded in existing record for the database

## Change in frequency of updates (2)

- _Record updated in December 2002_:
**Freq: q**   Regl: r
- 245 04 The EMBL reptile database $h [electronic resource].
**310    Updated quarterly, $b <Dec. 15, 2002>**
**321    Updated semiannually, $b <Feb. 8, 1998>**
- 500    Title from home page** (viewed on Dec. 15, 2002).**

**Steps to modify the existing record:**
- Change the frequency in the 310 note to match the current iteration, add the current date viewed in angle brackets in subfield $b.
- Change the 006 Frequency code to the current frequency.
- Move the former frequency to a 321 note field.
- Move the former date viewed to subfield $b of 321 field.
- Change the date viewed in the 500 note to current date (current iteration).

**Notes:**
This slide depicts the use of both current and former frequency notes (MARC 310 and 321 fields)

Since no exact date information about the change in frequency is available, use the viewed on date in the 310 and 321 notes.

## Changes to access points

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

**Notes:**
[Examples coming up in next several slides]

## 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 in full level records
- Include dates to identify iteration.
- Add name for earlier person or body in **7XX** if considered important for access.

## Three iterations of a Web site

- Viewed Jan. 15, 2003

- Viewed Aug. 30, 2000

- Viewed June 16, 1998

**Notes:**
These three iterations illustrate changes that need to be made in title, issuing body, and corporate body main entry.

## Bibliographic record updated (1): first title change

**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 on June 16, 1998).**

**110 2  Association of American Economics.**
- 245 10 **Association of American Economics online directory of members** $h [electronic resource].
**247** 10 **Membership directory of the Association of American Economics** $f <**June 16, 1998**>
- 500   Title from HTML header **(viewed on Aug. 30, 2000).**

**Notes:**
This and the following slide present portions of the resulting MARC record for the three iterations shown on the previous slide, illustrating changes in title, issuing body, and corporate body main entry.

## Bibliographic record updated (2):second title change + change of main entry

**110 2  American Economic Association.**
- 245 10 **American Economic Association online directory of members** $h [electronic resource].
**247** 10 **Membership directory of the Association of American Economics** $f <**June 16, 1998**>** **
**247** 10 **Association of American Economics online directory of members** $f <**Aug. 30, 2000**>
- 500    Title from HTML header **(viewed on Jan. 15, 2003).**
**550    Issued by Association of American Economics **<**June 16, 1998**>.
**710 2  Association of American Economics.**

**Notes:**
Give the 247 former titles proper in chronological order from earliest to latest (LCRI).

Note especially here the use of field 550 for former issuing body; this field was used formerly only for serials cataloging.

## Changes in 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 no longer applicable to the resource.

## When resource is completed

- I.e., when you know that updating has ceased:
- Close off the record:
- Record ending date, if known
- In 260 $c if cataloging from last iteration
- Include date of last update for loose-leaf if different from last date of publication given on chief source
- In 362 1 if not cataloging from last iteration
- Change 008 Date 2 from “9999” to ending date.
- Change physical description of loose-leaf:
- Add number of volumes

## Closing record for completed resource

- _Same record updated based on known last iteration_:
**008**    DtSt: d   **Dates: 1997,2003 **
**260**    Denver : $b Smith Pub. Co.**, $c 1997-2003.**
- 500    Title from home page (viewed on Jan. 15, 2003).

- _Existing record_:
**008**    DtSt: c   **Dates: 1997,9999**
**260**    Denver : $b Smith Pub. Co.**, $c 1997-**
- 500    Title from title screen (viewed on Oct. 3, 1997).

- _Same record updated without known last iteration_: (one of several possibilities)
**008**    DtSt: d   **Dates: 1997,2003**
**260**    Denver : $b Smith Pub. Co.**, $c 1997-**
**362 1  Updating ceased in 2003?**
- 500    Title from home page (viewed on Jan. 15, 2003).

**Notes:**
The 362 1 note given in the third example is only one of several possible ways to word the note.  
 Instructors note: there might be some discussion as to how best to word this note; e.g., another option:  
362 1_  Ceased being updated in 2003? 

This concludes Session 3