# Presentation: 040391

## 2002 Revision of AACR2

- Impact on *Integrating* Remote Access Electronic Resources

- November 2002

## Coverage of This Orientation

- What’s new in AACR2 (2002 Revision), mostly with respect to electronic integrating resources
- What’s new in the LCRIs
- Changes to MARC 21 content designation

## Not Covering

- All aspects of cataloging integrating resources
- Most of the “basics” covered by Barbara Tillett’s overview
- Handouts and exercises
- Direct access electronic resources, non-integrating remote access electronic resources

**Notes:**
Note that this is not a class on how to catalog integrating electronic resources-- only what is newly codified; it is assumed that you are all already familiar with the rules and practices for cataloging remote access electronic resources– this is intended to build on your current knowledge
Barbara covered a lot of content in her briefings– has everybody had a chance to attend yet?  We generally won’t be covering in this specialized briefing most of the general material she already covered, but we will be revisiting some of the important points that I need to make sure you understood.
Judy Kuhagen put together a set of handouts and exercises that were distributed to the teams– these provided great background information needed by all catalogers regarding multiparts and series statements (as well as series authority records)– we won’t be repeating this information here.
Since it is the integrating aspects we’ll be talking about, there won’t be any new material here today that affects direct access electronic resources (beyond what was covered in Barbara’s presentation).  

## Scope of New Chapter 12

- Chapter 12 now covers the integrating aspects of remote access electronic resources
- Be **ALERT** to the new “scope statements” in Chapter 12 (e.g., ***Integrating resources, nonprint resources, electronic resources, remote access resources)***
- Chapter 9 is still applicable and important to supplement Chapter 12, e.g.,
- Sources of information
- Additional notes

## What is New and Different?

- Chapter 12 covers rules for original description of integrating resources as well as “Changes” rules for re-description
- More room for “judgment” in recording data elements, especially related to changes
- “New to the rules” vs. “New to me”
- Current practices that are now documented for the first time in AACR2

- New in 2002

## What Happened to Chapter 9?

- Rules and/or examples related solely to integrating resources were removed; covered elsewhere (mostly Chapter 12)

**Notes:**
No significant change other than this; we'll look at where some things got moved to in Chapter 12.

## Organization

- Quick review of integrating resources
- Creating new records for integrating resources (by area of description)
- Changes to existing integrating resource records (by area of description)
- MARC 21 coding changes
- Uniform titles for electronic resources

## Review of “Integrating Resources”

- Barbara Tillett's presentation
- LCRI 1.0

## Types of Issuance

- Monograph
- A bibliographic resource that is complete in one part or intended to be complete in a finite number of parts.
- The separate parts may or may not be numbered.

**Notes:**
Type of issuance refers to how the bibliographic resource is published, distributed or produced, an dif it is updated, how it is updated.  There are three types of issuance:
Monograph:  nothing really new here, although things we previously called monographs are now excluded

## Types of Issuance

- Serial
- A continuing resource issued in a succession of parts, usually bearing numbering, that has no predetermined conclusion

**Notes:**
Changes to definition to cover unnumbered

## Types of Issuance

- Integrating resources
- 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 finite or continuing.

**Notes:**
The examples we use most frequently to identify integrating resources include updating loose-leafs (not, all things in loose leaf format); updating databases, updating web sites.  Note especially the second criteria– we aren't going to be making any distinctions between finite or continuing integrating resources since we'll use the same rules to catalog either, but just to be sure that you are aware that not all integrating resources are intended to go on forever.

## Slide 12

**Notes:**
This diagram should look familiar to you; in BT's presentation and also in LCRI 1.0.

Another important point to consider here is that as far as Ers are concerned, integrating can only apply to "remote access"; no such thing as a direct access electronic resource.

One of the keys to cataloging integrating resources is that each time updates are made to the resource (such as incorporating new content, deleting other content, changing existing content), you have a new iteration of the resource.  

## LCRI 1.0Decisions Before Cataloging

- Need to determine the type of issuance by looking at the resource and determining:
- If it is updated, and if so
- How it is updated
- --Do the updates remain discrete or are they integrated into the whole?

**Notes:**
Much of what is in LCRI 1.0 is actually not new, e.g., most of the mono vs. serial decision information is from the existing LCRI 12.0A and is being move the LCRI 1.0 now.

## LCRI 1.0

- For electronic resources, make the decision on the type of issuance based solely on the electronic resource itself
- Not another manifestation of the resource, e.g., a print publication

**Notes:**
For example, if a print serial becomes an online electronic resource, don't assume that it is a serial in ER form– need to look at how it is issued.  Good examples are directories, data sets, etc.

## LCRI 1.0:Remote Access ERs

- Catalog as **serial**: resource having material added as discrete, usually numbered "issues"
- Catalog as **integrating**:  resource having material added, changed, or deleted via updates that do not remain discrete
- Catalog as a **monograph**: resource complete in one part or intended to be complete in a finite number of parts, including those resources that are corrected via "errata" information

**Notes:**
Serial: only current issue may be available as a separate issue; an issue can consist of a single article in some instances.
Can still refer to SRD those resources that you think might be a serial. 

Integrating:  might contain the articles from more than one journal (e.g., a database of selected articles from various journals)
Monographs:  Info about errata is included to indicate that this is really no different in principal from printed books that have errata sheets inserted.  The challenge will be on how to determine where the line is drawn between monographs with minor corrections and integrating resources.  

## LCRI 1.0:"In Case of Doubt"

- In case of doubt about the type of issuance:
- Serial vs. integrating: if there is no information about the type of issuance, but the resource has wording that refers to "edition," determine if that wording represents a numeric designation (serial) or an edition statement (integrating)

**Notes:**
The LCRI currently has two "in case of doubt clauses" to help determine between integrating vs. serial or integrating vs. monograph.  These categories may be expanded if additional instances and principals develop– please feel free to identify questionable resources that might help to enhance these statements.

## LCRI 1.0: "In Case of Doubt"

- In case of doubt about the type of issuance:
- Monograph vs. integrating: if there is no information about the type of issuance, catalog the resource as a monograph

**Notes:**
"no information about the type of issuance" usually means that there will be no indication that the resource has been updated.

## LCRI 1.0:Change in Type of Issuance

- In the coming months CPSO will be issuing guidelines on "changes in type of issuance" and how this impacts the type and number of bibliographic records

**Notes:**
Don't worry about this for right now, but as we get into the next phases of implementation of integrating, incorporating the new bibliographic level, then we'll have to pay close attention to the CDS distribution issues that are involved in changes in the type of issuance.  As you'll see near the end of the presentation when we talk about MARC coding, for now we'll be coding all integrating resources as monographs (just as you have been doing).

## Iterations

- An instance of an integrating resource, either as first published, or after it has been updated.
- Creating new records
- Identify the iteration used for description
- Updating existing records
- Identifying the changes in the description between iterations (as well as identifying the iteration used for re-description)

**Notes:**

One last concept I want to be sure you all understand before we move on to the basics of creating new records.

Because the bibliographic details related to each iteration can be different, we'll be paying particular attention to the word iteration today, usually in the context of "current iteration". 

## Part 1 : Creating New Records

- Basis of description
- Area 1 : Title and statement of responsibility
- Area 2 : Edition
- Area 4 : Publication, distribution, etc.
- Area 6 : Series
- Area 7 : Notes
- Area 8 : Standard numbers
- *Note that there is no need to cover Areas 3 or 5

## Basis of the Description 12.0B1 b) Integrating Resources

| AREA | BASIS OF DESCRIPTION |
| --- | --- |
| Title and statement of responsibility | Current iteration |
| Edition | Current iteration |
| Place and publisher | Current iteration |
| Dates | First and/or last iteration |
| Series | Current iteration |
| Notes | All iterations (and any other source) |
| Standard numbers | All iterations (and any other source) |

- New in 2002

## Sources of Information

- Chief source
- for nonprint resources, see subrule .0B in the relevant chapter (i.e., 9.0B1)
- Prescribed sources
- for nonprint resources, see subrule .0B in the relevant chapter (i.e., 9.0B2)
- Nothing new!

## AREA 1 

- Title and statement of responsibility
- Words that serve as introductions
- Typographic errors
- Full forms vs. acronym/initialism

- New in 2002

## Title Proper: Introductory Words

**1.1B1**   “Do not transcribe words that serve as an introduction and are not intended to be part of the title.  Give the title including these words in a note (see 1.7B4).”
**LCRI **  “Use cataloger’s judgment ... Look at other sources in the resource and consider the presentation, differences in typography, etc.  _**If in doubt**_, give the longer form as the title proper and give a title added entry for the shorter form.

**Notes:**
Not really new to practice, but new to the rules (LC has long had an RI for motion pictures where this is also very common).

AACR2 says to give a note, in this case we’ll use the indicator in the 246 field to signify the note, but also need to give access to the title; LCRI 21.30J is in the process of being revised.

## 1.1B1 Example

**Notes:**
Claudia

246 Indicator 1 is for note and title added entry.

Could also have a $I with text like: "Title appears on Web page as:"

## Title Proper: Typographic Errors

**12.1B1**  Correct obvious typographic errors when transcribing the title proper and give the title as it appears on the resource in a note. _**In case of doubt**_ about whether the spelling of a word is incorrect, transcribe the spelling as found.
**LCRI 21.30J  **When the title proper has been transcribed in a corrected form, also make a 246-derived _**title added entry**_ for the title as it appears on the resource

- New in 2002

**Notes:**
You can imagine the philosophy behind this approach– this treatment assumes that the title on later issues or iterations will be in the correct form.  Serials don't have to treat as title change, we don't have to keep worrying about when the typo will be caught by the author.

Note that the rule itself has an "in case of doubt" clause– see next example

## Typographical Error?

**Notes:**
Remember that folks are still going to do "cutsey" things; don't be overzealous in declaring titles to have typographical errors.

## Title Proper: Full Form vs. Acronym/Initialism

**12.1B2**  "When the title appears in full and in the form of an acronym or initialism in the chief source of information ***[i.e., same source],*** _choose the full form_ as the title proper."
**LCRI:  **Do not change any existing records created before Dec. 1, 2002

- New in 2002

**Notes:**
Note added emphasis– don't get carried away here by rejecting the full form that is prominent on the home page of a resource if you find an acronym somewhere else– this is only for those cases where both forms are presented in the same source.

## Treatment of Acronym/Initialism

- When the full form has been chosen as the title proper per 12.1B2:
- Give the initialism/acronym as other title information
- Give the initialism/acronym as a 246-derived title added entry

## Full Form vs. Initialism/Acronym

**Notes:**
Compromise position with ISSN; reminding you here because in some presentations it may defy logic!

So, what do you do with the Initialism?

Serials will do as OTA 
Provide 246-derived title added entry.

Herb : remember, don't change existing records for this reason only, if you have to redescribe, go ahead

## Title Proper: Common Title/Section Title

- Nothing new under revised Chapter 12, but new info in LCRI:
**LCRI 12.1B4**   *Updating remote electronic resources*. For most such 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.

**Notes:**
I know that you will continue to encounter situations when you are cataloging a resource that may itself be part of a larger resource.  In some of these cases, there may be a common title from the larger resource that appears on the resource you are cataloging.  When this occurs, you have to decide how to treat this common title.

When the LCRI review group considered this rule, some wanted an LCRI to tell the cataloger how to treat this situation.  We basically didn't feel it was appropriate to dictate this, that each situation needed separate analysis to determine what role the supposed "common title" was playing.  So the LCRI doesn't tell you what to do, but gives you some things to consider.  We also thought it important to include an "in case of doubt" clause.

For an example, see

## Example: Common Title/Section Title

## Other Title Information

**12.1E1  b)** *Integrating resources*:
- Transcribe other title information as instructed in 1.1E _**if considered to be important**_
- Do not transcribe other title information that consists solely of words relating to the _**currency**_

- New in 2002

**Notes:**
Here is really the first instance of what I warned you about earlier– you are going to be given more leeway to exercise judgement

Currency:  "The best Web sites as of Oct. 2002"

## Good descriptive terms that might prove useful in keyword searches
Helps to clarify or amplify the scope of an otherwise "weak" title
Likely to be "stable," e.g., not "currency" information, or information likely to shift as a resource grows or changes
Others?

- Good descriptive terms that might prove useful in keyword searches
- Helps to clarify or amplify the scope of an otherwise "weak" title
- Likely to be "stable," e.g., not "currency" information, or information likely to shift as a resource grows or changes
- Others?

**Notes:**
The same type of logic you have already been using when constructing summary notes to not lock a volatile resource in time.  

Don't worry too much about this, it really is a judgment call, and the worst case scenario is that you might need to remove or adjust the other title information as the resource changes.

## Examples: Other Title Information

**Notes:**
Pardon my indulgence; may not be an integrating resource.

## Statements of Responsibility

- Follow your normal practice (1.1F, 9.1F– those credited with a "major role"), except:
- Editors
**12.1F3 b)**  *Integrating resources*:
- Record statements relating to persons who are editors as statements of responsibility _**if considered to be important.**_

- New in 2002

**Notes:**
Not so much a case of judgment per se, but had to say something about editors for integrating resources since you shouldn't record them for serials. 

## AREA 2

- Editions
- Transcribing edition statements
- Edition statement vs. frequency

## Edition Statements

**12.2B1  b)**  *Integrating resources*:
- Transcribe an edition statement as instructed in 1.2B _**if considered to be important**_
- Replaces 9.2B8

**Notes:**
Another opportunity to exercise your judgment.  This really isn't a change from what you have been doing, where you were already omitting edition statements for frequently updated resources (the now deleted 9.2B8)

This doesn't mean delete all edition statements!

## Edition Statement : Considered Important?

- Likelihood to be retained as the resource is updated
- Helpful to place this resource in the context of others
- "Currency" information (e.g., "Last updated 10/12/2002") should _**not**_ be considered an edition statement; if used at all, can be included in "item described" note
- Other?

**Notes:**
Can't legislate judgment, but ...

## Edition Statement vs. Frequency

**12.2B2.  **Give statements indicating regular revision or frequent updating (e.g., *Rev. ed. issued every 6 months*, *Frequently updated*) as frequency in the _**note area **_
- (we'll cover later in the notes section)

## Example : Edition Statement

- 250 $a 17th ed., Centennial ed.

**Notes:**
C1999, introduction talks about its other editions, home edition, etc.
This is a case where I would definitely include the edition statement.

## Example : Edition Statement

- 250 $a Web version.
- 500 $a Title from home page last updated Oct. 22, 2002 (as viewed on Nov. 1, 2002).

## Example : Edition Statement

## Example (continued)

- Existing bibliographic record:

**Notes:**
Worst case scenario:  include it and it needs to be updated or removed later, so if in doubt go ahead and include it because you really won't know in some cases.

## AREA 3

- Chapter 9 Area 3: Type and extent of resource
*Do not use per LCRI 9.3B2*
- Chapter 12 Area 3 : Numbering
*Not applicable to integrating resources, even if updates are numbered*

## AREA 4

- Publication, distribution, etc.
- No more "shortcut" recording of publisher name (e.g., "The Society")
- Beginning and/or ending dates when first or last iteration is not available

## Publisher's Name

- DELETE rule **1.4D4**
**DO NOT **shorten the name of the publisher in the Publication, distribution, etc., area, even if the name of the publisher is already given in the title proper or statement of responsibility

- New in 2002

**Notes:**
Reminder, from Barbara's presentation; not associated with integrating resources changes, but in the same revision package, so I didn't want you to forget it.

## Beginning Dates : Rule

**1.4F8. Dates for serials, integrating resources, and multipart items.**
- If the _**first**_ published issue, _**iteration**_, or part is available, give the beginning date followed by a hyphen.
- If the _**first**_ published issue, _**iteration**_, or part is not available, _**do not give**_ the beginning date; give information about the beginning date in a _**note**_ if it can be readily ascertained
- Publication, distribution, etc. note (**12.7B11**)

- New in 2002

**Notes:**
How often will you be cataloging from the first iteration of an integrating electronic resource?

## Beginning Dates : Option

*Optionally*, _**supply**_ the beginning publication date in the publication, distribution, etc., area if it can be _**readily ascertained**_.
**LCRI 1.4F8**, for ***integrating resources***:
_**Apply**_ the option on a case-by-case basis _**only if**_ the resource includes an _**explicit statement,**_ e.g.,
- 	 "*Created on March 12, 2001"*
*	** **"Began publication in 1998*"
-  Do not investigate beyond the resource to find a date.

**Notes:**
Existing records for what we now call integrating resources have a somewhat checkered past; there has always been a lot of guesswork that went into supplying a "starting" date for the 260$c, not always resulting in a very accurate result.
Extending the serial practice to not record a date in 260$c, which has been their practice forever, seemed like a labor saving, and perhaps angst saving exercise.
When the LCRI review group discussed this topic, we were persuaded by some members of the group to apply the option in those cases where conclusive evidence on the beginning date was available, that is, no guesswork was needed.  It seemed a shame in such cases to ignore the beginning date when you didn't have the first iteration.

## "Explicit Statements" vs. Copyright Dates

- If cataloging a remote access integrating resource and you do not have the first iteration, _**do not**_ consider a copyright date (or span) as an "explicit statement" about the beginning publication date
- Cataloger's judgment: if cataloger feels the information is helpful, can include in a note (e.g., Begun in 1999?)

**Notes:**
I am very reluctant to base publication dates on copyright date ranges, which is why we wanted some additional validation of the date from an explicit statement.  
Web sites often include many pieces of intellectual content that have different copyright dates.   When a range of copyright dates is given, you don't really know whether the existence of the site corresponds to the range or whether the content on the site corresponds to the range.  Sometimes there is a single copyright date for the current year, although you know the site has been in existence for quite some time.  LC catalogers should not be considering these types of copyright dates as the "explicit" evidence about the beginning publication date.

You are allowed to use

## Copy Cataloging

- If you use a record from another library to catalog an integrating resource (i.e., you do not have the first iteration), and they have recorded a beginning date in 206 $c, accept that date

## Beginning Dates : Summary

- If not cataloging the first iteration, and
- There is no explicit statement about the beginning date, then:
- _Do not_ record a 260 $c
- _Do give_ any available information about the beginning date in a note (**12.7B11**) using 362 1

**Notes:**
Although we're going to talk about notes in a minute, I wanted to cover this one note, the Publication, distribution, etc. note from 12.7B11 now while we can consider all aspects of dates together.

## MARC 21 : New TAG : 362

- If the date information has been obtained from a source other than the first iteration of the published item, give as _**unformatted**_
- First indicator value 1 = Unformatted note
- $a is for the date(s); prefer real words to cataloger constructs
- $z is for the source of the information (probably won't be used)

**Notes:**
Before we look at some examples

## Examples : 362 1

-  1 $a Probably begun after 2001.
- 362 1 $a Began publication in 2000?
- 362 1 $a Updates ceased in 2002?
**Not**:
- 362 1 $a Began in [199-?]

**Notes:**
Whether you provide these kinds of "approximate date" notes will be cataloger judgment in most cases; may help you decide on coding of the 008 Date 1.

For serials this is an important element because it helps to place a serial in a temporal context with other publication, especially earlier and later titles; this may not prove to be as important for integrating resources, but time will tell.

## Beginning Dates : 008 Coding

- Use "m" (multiple dates) for integrating resource "type of date" (008/06)
- Base DATE1 (008/7-10) on the following:
- 260 $c if present
- Date from 362 1 if 260$c not present
- "Last updated" information if found and above not available
- "Viewed on" date if above not available

**Notes:**
Make a wall chart of this?

## Example 1 : Beginning Dates

- 260 $c  [1999]-
- 500 $a Title from HTML title (viewed on Nov. 10, 2002)

**Notes:**
Integrating resource, not cataloging from first iteration
Title of resource is Topozone
Title screen has copyright statement c2002

008 date 1 = 1999
Other info on site  November 1999

## Example 2 : Beginning Dates

- No 260 $c
- 362 1  Begun in 1997?
- 500 $a  Title from home page last updated Sept. 26, 2002 (viewed on Nov. 12, 2002)

**Notes:**
Not cataloging from first iteration
Title screen:  Last modification Sept. 26, 2002
Other information "began in 1997"

008 Date 1 = 1997

## Example 3 : Beginning Dates

- No 260 $c
- No 362 1
- 500  $a  Title from title screen last updated Nov. 10, 2002 (viewed on Nov. 12, 2002)

**Notes:**
Not cataloging from the first iteration
Last updated ...
Copyright 1980-2002

008 Date 1=  2002

## AREA 5

- Because we are only concerned with remote access integrating electronic resources, no Area 5 is included per footnote 2 at 9.5

## AREA 6

- Nothing new for the series area specifically for integrating electronic resources
- Pay particular attention to changes in recording series statements in bibliographic records and series authority records outlined in the overview and the exercises distributed to teams

## AREA 7

- Notes
- Specifying the applicability of a note
- Frequency of updates
- Source of title proper
- Item described
- Source of edition statement
- Bibliographic history and relationship with other resources

## Notes: Scope of Applicability

**12.7A2**
_**If it is known**_ that the note does not apply to all iterations of an integrating resource, add appropriate numbering or publication dates.

- 500 $a Edited by Ellen Thomas prior to Jan. 2002.

- New in 2002

**Notes:**
Although this general stipulation about recording notes is really going to be more applicable when we look at redescribing a resource in the "changes" section, you may also encounter a situation when first cataloging a resource where you have information about earlier iterations (probably unlikely, but ...).  We'll revisit this topic when we do look at "changes" and discuss some variations in how you might record the information.

## Notes: Frequency

**12.7B1. Frequency**
- Make notes on the frequency of the updates  to the integrating resource unless it is apparent from the rest of the description or is _**unknown**_.

- New in 2002

**Notes:**
The fact is, for most electronic integrating, you won't know the frequency.  Something like "frequently updated" is not a known frequency.

## LCRI 12.7B1  Frequency

- Always make a note on _**known frequencies**_, even if evident from elsewhere in the description
- Don't consider "frequently updated" to be a known frequency
- For integrating resources, include the word "updated" or "updates" with the frequency word, e.g.:
- Updated daily
- Weekly updates
- Continuously updated

## MARC 21 : New Tag : 310

_**Current **_publication frequency notes are found in MARC tag 310
- Indicators undefined
- $a is for current publication frequency

-  $a  Updated on a weekly basis.
- 310 $a  Continuously updated.

**Notes:**
Note that "Continuously updated" in MARC means more than once a day, we'll look at this concept again in the MARC coding section later.

Note that the 310 is for current frequency; we'll talk later about recording former frequencies when we discuss "changes"

## Source of Title Proper

**12.7B3**  for ***nonprint resources***, see .7B3 in appropriate chapter
**9.7B3**  _**always give**_ the source of the title proper
- As before, this note will usually be combined with the "Item described" note

- 500 $a Title from home page (viewed on Dec. 18, 1999)
- 500 $a Title from Web page (viewed on May 29, 1999)
- 500 $a Title from title screen (viewed on Jan. 20, 2000)

**Notes:**
No change here

Examples are illustrative, not prescriptive.

## Item Described

**12.7B23  (9.7B22)**
- If the description is _**not**_ based on the first iteration, make a note on the iteration you used
- For *remote access resources*, _**always**_ give the date on which the resource was viewed for description
- May be combined with other notes (often with Source of title proper note)

**Notes:**
If you're following along in Chapter 12 you'll see that I'm taking the notes a little out of order, just because its easier to talk about related notes together.

Not new to practice, what you have been doing for 9.7B22.

## Examples : Item Described

- 500 $a Title from title bar (viewed on Jan. 12, 2000)
- 500 $a Description based on contents viewed on Oct. 21, 1999.
- 500 $a Title from home page last updated July 2000 (viewed on Aug. 19, 2002)

**Notes:**
This type of note is no different than what you have been doing in the past to tell the users of the record what you were looking at, but it has now taken on added importance that we'll see in a few minutes when we talk about re-describing a resource when data elements change.

## Source of Edition

**12.7B9.1  **for ***electronic resources***, make notes on the source of the edition statement if it is different from the source of the title proper (same as **9.7B7**)

**Notes:**
No change in current practice

## Bibliographic History and Relationships

**12.7B8**
- Make notes on the bibliographic history and on important relationships between the resource being described and the _**immediately preceding, immediately succeeding, or simultaneously issued**_ resources.

- New in 2002

**Notes:**
This will be one of the BIG new changes you will be encountering– monograph and serial catalogers have long taken different approaches on how to show bibliographic relationships.  For monos, certain relationships, e.g., revised editions involving title changes, were covered by a note and a related work added entry.  Serials folks have always used the  specific linking entry fields in MARC to show relationships such as:
Continuations
Mergers
Splits
Absorbtion
Translation
Translations
Simultaneous editions, and 
Supplements

For integrating resources, since the relationships are often times going to be with serial bibliographic records, LC will now apply these linking fields for monographs.

In many instances this will not be a big changes in what you record, but will be a big change in how you record.

(why went this way as opposed to mono way:  most of the relationships that are going to be recorded are for serials so it made sense to do it the same way; bibliographic relationships are very important in the FRBR model, good to start thinking this way)

## Reciprocal Linking Notes

- LC will now implement between AACR2 records:
- Serials and integrating resources
- Integrating resources and integrating resources
- Integrating resources and monographs
- _Reciprocal_ links (i.e., in new record _and_ existing record)
- Link only within LC's catalog
- Generally, do not make related work added entries for titles you are linking to (cf. LCRI 21.28B1)

- New in 2002

**Notes:**
Some of the early records done in the Beonline project included these linking fields
Helps the user to a) know of other related resources, b) depending on the system capabilities, navigate to the related records.

Although we're making new links only within LC's catalog, do not delete any linking fields on copy cataloging records

If you find you have to make a link to a pre-AACR2 records, notify me.

## Reciprocal Linking Notes

**LCRI 12.7B8**
- Gives additional information on the "form" of linking notes for legal works and translations
- Main entry name heading/uniform title/title proper (i.e., 1XX/240/245)
- Main entry uniform title/title proper (i.e., 130/245)

## Reciprocal Linking Notes

- MARC 21 Tags 76X-78X; most common for integrating resources:
- 776  Additional physical form entry
- 780  Preceding entry
- 785  Succeeding Entry
- 787  Nonspecific relationship
- Don't imagine relationships; in case of doubt, don't include
-  When a relationship is known, but the "flavor" is not; don't guess, use 787

**Notes:**
There are a lot of these linking notes, and serials folks end up using lots of them, but I'm pretty sure that for integrating resources you'll really only use a handful of them.  Review the linking tags in MARC 21 to see what the other possible relationships are, but pretty sure you'll use only these.

Also, don't imagine relationships– if it isn't clear, don't 

## Reciprocal Linking Notes : Indicators

- First indicator
- 0  Display note  (usually)
- 1  Do not display note (only when 580 used)
- Second indicator
- Varies depending on field, used to determine display constant in OPAC
- 776	0#	Available in another form:
- 787	0#	Related item:

**Notes:**
"blank" 2nd indicator shown for other physical form or nonspecific

## Reciprocal Linking Notes : Indicators

- Second indicator : 780 (Preceding Entry)
- 0	Continues
- 1	Continues in part
- 2	Supersedes
- 3	Supersedes in part
- *4 	Formed by the union of ... and ...
- 5	Absorbed
- 6	Absorbed in part
- 7	Separated from

**Notes:**
* Means you will have to do a 580

## Reciprocal Linking Notes : Indicators

- Second indicator : 785 (Succeeding Entry)
- 0	Continued by
- 1	Continued in part by
- 2	Superseded by
- 3	Superseded in part by
- 4	Absorbed by
- 5	Absorbed in part by
- *6	Split into ... and ...
- *7	Merged with ... to form ...
- 8 	Changed back to

**Notes:**
* Means probably will have to do 580

## Reciprocal Linking Notes : Subfields

**$a Main entry heading**
- from related record's 100, 110, 111
- individual components of the name heading are included in a single subfield $a
**$s Uniform title**
- from related record's 240
- only used in conjunction with $a
- individual components of a uniform title are included in a single subfield $s

**Notes:**
If you look in the MARC format at the linking fields, you'll see that there are dozens of subfields defined.  In reality, use only a handful of subfields.  $a, $s, $t, $w

## Reciprocal Linking Notes : Subfields

**$t Title**
- from related record's 130 or 245 $a$n$p
- individual components of a title are included in a single subfield $t
**$b Edition**
- from related record's 250
- include only if 1XX/245 are the same in both records (i.e., needed to distinguish)

**Notes:**
$w could include OCLC control numbers; leave in for copy cataloging– add additional $w for the LCCN in these cases

## Reciprocal Linking Notes : Subfields

**$w Control number (LCCN)**
- From related record's 010 field
- Precede LCCN by "(DLC)" and formulate LCCN using proper spacing conventions
- Post-2000 LCCN format
- 			$w (DLC)##2002123456
- Pre-2001 LCCN format
- 			$w (DLC)###98345678

## Reciprocal Linking Notes : Subfields

**$x ISSN**
- from related record's 022 field (serials, possibly some integrating resources)
**$z ISBN**
- from related record's 020 field

## Reciprocal Linking Notes : Subfield Conventions

- Punctuation:  ending punctuation only in $a and in $s (and $t if followed by $b)
- Initial articles:  omit unless intent is to file on (e.g., Los Angeles)

## Form of Linking Entry

| Title proper, and if needed, edition | 245
245/250 | $t
$t $b |
| --- | --- | --- |
| Main entry name heading/title proper, and if needed, edition | 1XX/245
1XX/245/250 | $a $t
$a $t $b |
| Main entry name heading/uniform title | 1XX/240 | $a $s |
| Main entry name heading/uniform title/title proper (legal, translations) | 1XX/240/245 | $a $s $t |
| Main entry uniform title | 130 | $t |
| Main entry uniform title/title proper (translations and other language editions) | 130/245 | $t |

## Reciprocal Linking Notes

- Linking entry complexity note – 580
- Use only if the relationship between two or more bibliographic resources is too complex to be expressed by the second indicator of the linking field  (see 780, 785 indicators marked with asterisks)

## Reciprocal Linking Notes : Example

- "The franchise handbook" published as a serial in print form (a quarterly)
- Now simultaneously published as an integrating remote access resource (updates do not remain discrete) with title "The franchise handbook online"

**Notes:**
Note that online doesn't replace (continue) the paper serial, it continues to be published.

## Existing serial record:

**Existing serial record:**

**New integrating resource record: **

- Add:  776  0#  $t Franchise handbook online $w (DLC)###98801778

- Add:  776  0#  $t Franchise handbook $x  0882-5505 $w (DLC)###85644136

**Notes:**
Serial has 010, 022 (ISBN) and 245 only

Integrating has 010 and 245

776 on Serial record includes $t and $w
776 on Integrating record includes $t $x $w
Note the omission of initial articles.

## Reciprocal Linking Notes : Maintenance

- Will cover in Part 2 : Changes

## MARC 21 : New Field : 550

- Notes on the issuing body (i.e., not a commercial publisher, distributor, etc.), usually used to justify a 7XX added entry, are now to be coded as **550** instead of **500**.

## AREA 8

- Standard Numbers
- LCRI 12.8B1
- If an integrating resource has both an ISSN and an ISBN, give both

## Part 2 : Changes

- Basis of description
- Area 1 : Title and statement of responsibility
- Area 2 : Edition
- Area 4 : Publication, distribution, etc.
- Area 6 : Series
- Area 7 : Notes
- Area 8 : Standard numbers

- New in 2002

## Basis of the Description 12.0B1 b) Integrating Resources

| AREA | BASIS OF DESCRIPTION |
| --- | --- |
| Title and statement of responsibility | Current iteration |
| Edition | Current iteration |
| Place and publisher | Current iteration |
| Dates | First and/or last iteration |
| Series | Current iteration |
| Notes | All iterations (and any other source) |
| Standard numbers | All iterations (and any other source) |

- New in 2002

## Change in Title Proper

**12.1B8 b)**  *Integrating resources:*
- If _**any change**_ in the title proper occurs on a subsequent iteration:
- Change the title and statement of responsibility area to reflect the current iteration
- Give the earlier title in a note

## MARC 21 : New Tag : 247

- Former Title Proper
- See LCRI 12.7B41 for text of how the field scope information will be changed in the next iteration of MARC 21
- Emphasis on _**title proper**_; do not use 247 for earlier change in title other than title proper (e.g., not parallel title, other title information)

**Notes:**
We have been using 246 with an explanatory statement in $I in the few cases where we have had to do this so far.

## MARC 21 : New Tag : 247

- Indicators
- First indicator: generally use 1 (added entry)
- Second indicator: generally use 0 (display note)

## MARC 21 : New Tag : 247

- Subfields
- Record former title proper in $a $n $p (_**do not use**_ $b or $h)
- Always use $f (date or sequential designation) if information is available; allows for temporal comparisons when multiple 247 fields exist
- Use $x (ISSN) if record has ISSN in 022 field and the title proper changes; _**move**_ ISSN from 022 to 247$x

## Example : Title Change

**Notes:**
It is unlikely that you will ever know exactly when the title changes on a Web page, so you will most likely be using temporary dates, I.e., in angle brackets.  The dates will come from the viewed on dates in the item described or source of title proper notes.

## Important Note

***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!!!
- If the "other record" is a serial, send to SRD

## MARC 21 : New Tag : 547

- Former title proper complexity note
- Only use in those situations where you need to provide more explanation than can be given in the 247 field (i.e., do not give a 547 just because there is a 247).

## Change in Parallel Title

**12.1D3  b)**  *Integrating resources*:
- If a parallel title is added, deleted, or changed on a subsequent iteration:
- Change the title and statement of responsibility to reflect the current iteration
- Give any earlier parallel title in a note if _**considered to be important**_ (for note, see **12.7B5.2 b**)
- Use 246 field for "note"  (see **LCRI 12.7B5.2**)

## Example : Change in Parallel Title

**Existing Record:**

- 245 00 $a	Barn och unga $h [electronic          			resource] = $b Children and young persons.
- 500 ## $a	Title from HTML header (viewed Jan. 13, 2002)

**Same record after parallel title disappears**:

- 245 00 $a	Children and young persons $h [electronic 		resource]
- 246 1# $i	Parallel title in HTML header <Jan. 13, 			2002>: $a Children and young persons
- 500 ## $a	Title from [new source, new date]

## Reminder

- 247 field is used for former _**title proper**_ only;
- For other changes in title area (parallel title, other title information) use 246 field, with explanation in $i

## Change in Other Title Info

**12.1E2 b)**  *Integrating resources:*
- If other title information recorded in the record changes on a subsequent 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**_ (**12.7B6.2 b)** ); use 246 field for "note" (LCRI **12.7B6.2**)

**Notes:**
If you are redescribing a resource that is changed, so that it now has other title information but the existing record does not, don't make a statement as to the earlier lack of other title information– you wouldn't know if there hadn't been any, or if the previous cataloger had not seen it as important enough to transcribe.

## Change in Statement of Responsibility

**12.1F5 b)** *Integrating Resources:*
- If the statement of responsibility is added, deleted, or changed on a subsequent iteration:
- Change the record to match the current iteration
- Make a note if the change is _**considered important**_ (see **12.7B7.2**)

## Change in Edition Statement

**12.2F1 b)** *Integrating Resources:*
- If edition information is added, deleted, or changed on a subsequent iteration and this ***change does not require a new record***:
- change the edition area to reflect the current iteration
- Make a note about the earlier edition _**if considered to be important**_ (see **12.7B92**)

**Notes:**
We'll talk in a few minutes about what might require a new record

## Change in Place of Publication

**12.4C2 b)** *Integrating resources*:
- If the place of publication changes on a subsequent iteration:
- Change the record to reflect the current iteration
- Give the earlier place in a note _**if considered important**_ (see **12.7B11.2**)

**Notes:**
Note that LCRI for serials indicates two cases where it might be important:
Place change involves a country or region

Same goes for place of manufacturer:  12.4G2
Involves a change in place when the place has been used as a qualifier for the uniform title

## Change in Name of Publisher

**12.4D2 b)**  *Integrating resources:*
- If the name of the publisher changes on a subsequent iteration:
- Change the publication statement to reflect the current iteration
- Make a note about the earlier publisher if considered to be important (see **12.7B11.2**)

**Notes:**
Same goes for name of manufacturer, see 12.4G2

## Ending Date of Publication

- 260   [Berkeley, Calif.] : $b Information Systems and Technology, University of California, Berkeley, $c –2000.

- Source: Adam Schiff

**Notes:**
Source for dates was first or last iteration;  you can assume in this case that this is the last iteration and supply the ending date per 1.4F8

## Change in Series Statements

**12.6B2 b)**  *Integrating resources*:
- If a series is added, deleted or changed on a subsequent iteration:
- Change the series area to reflect the current iteration
- Make a note of the change if considered important (see **12.7B14.2**); _**consider it important if it was a traced series**_
- If a former traced series is now recorded only in the note, _**also make **_**an 8XX** series added entry (see p 3-4 of **LCRI 21.30L** for example)

**Notes:**
Note added info on "important"

## Changes to Notes

- Most of the "changes" notes in 12.7 have been mentioned above
- For more information, review the **12.7B*****X*****.2** sections in Chapter 12
- Changes to known frequencies (12.7B1)

**Notes:**
Where X equals any specific note

## MARC 21 : New Tag : 321

_**Current **_publication frequency notes are found in MARC tag 310
- Former publication frequency notes are found in MARC tag 321
- Indicators undefined
- $a is for former publication frequency
- $b is for dates of former publication frequency

## Changes to Notes

**LCRI 12.7B23**  *Item described*
- When the bibliographic record has been updated based on changes in the current iteration:
- Replace the "viewed on" date in the record with the current date (regardless of which note this is associated with)

**Notes:**
Don't "Pile On" to the existing note

## Item Described : Re-description

**Existing Item Described note:**

- 500 $a	Title from home page last updated July 			2000(viewed on Aug. 19, 2002)

**Revised Item Described note: **

- 500 $a	Title from home page last updated Aug. 2002 		(viewed on Oct. 12, 2002).
**NOT:**
- 500 $a	Title from home page last updated July 2000 		(viewed on Aug. 19, 2002) and revised based on 		Aug. 2002 update (viewed on Oct. 12, 2002).

**Notes:**
In this example the item described note is combined with the source of title proper.

## Changes That Require a New Record

- Follow the rules for changes we've just discussed, regardless of the "major" or "minor" aspect of the change, even with a new edition statement
- Make a new entry only if the resource described in the existing record _**continues to exist**_ as a resource separate from the new resource to be cataloged—cf. **LCRI 21.3B**, section on *Updating remote access resources*

## The Ultimate Change

- New **LCRI 9.7B**  for remote access electronic resources that are no longer available
- Original URI no longer active
- Original URI still active, but original resource no longer available (i.e., not a different iteration of the original resource)

**Notes:**
While were on the topic of changes, let's talk about --

## Original URI No Longer Active

- Use an Internet search engine to determine if the resource described in the record is now available at a different URI
- If found, update 856 $u
- If not found
- Indicate in a note that the resource isn't findable (and the date you searched)
- Include the reason, if known
- Move the 856 $u to 856 $z
- Suppress the bibliographic record

## Different Resource at Old URI

- Treat the existing bibliographic record as we just discussed (as if it was no longer there)
- Create a new record for the new resource (if that resource is one that is appropriate for adding to the catalog)

## Caveats

_**Do not**_ apply these procedures if:
- The record represents a resource from a Library of Congress domain (e.g., lcweb.loc.gov, www.loc.gov)
- Another 856 in the record indicates that LC has archived the resource
- LC has a paid subscription to the resource
- Notify CPSO if any of these apply

## MARC 21 Changes

- Leader:  Bibliographic Level (Ldr/07)
- New code "i" for integrating resources will not be implemented at this time (must be coordinated with bibliographic utilities)
- Interim decision:  continue to use code "m" (monograph)
- Interim: same 008s that you are using today!

**Notes:**
We'll be getting back together probably sometime next year to discuss the implementation of the new bibliographic level when the time comes.  This is when we'll have to take very special steps for any instance of a "change" in the type of issuance of a resource (I mentioned earlier that CPSO would be issuing guidelines)

## MARC 21 Changes

- ADD:  Serial 006 Field
- Begin with implementation of "integrating resources" on Dec. 1, 2002
-  Add the 006 if you have received the new Voyager update package
- If you must complete a record after Dec. 1 but prior to receiving rollout package, add cataloger note:
- "952 $a Add serial 006"

**Notes:**
Because the 008s are the same as you are using now, namely for the monographic aspects, we will now begin using the serials 006 to bring out the seriality aspects.  I know that none of us are familiar today with the serial 006, so we'll look at what you will get as a default and which bytes you will need to adjust. 
Note that the Voyager client rollout that is supposed to happen to support LC's implementation of integrating resources may lag a few days behind your first integrating record.  

## Serial 006 in Voyager

## Serial 006 Positions To Address

- Leave default values **except**:
- Frequency (006/01)
- Default: no determinable frequency
- If 310 field present, value in Frequency should match
- Note: value "k" continuously updated is defined as "more often than daily"
- Type of continuing resource (006/04)
- Default: fill
- Change to one of the following:
- "d"  updating database
- "w" updating Web site

## Serial 006 Positions To Address

- Form of item (006/06)
- Default:  fill
- Change to: "s"  electronic
- Entry convention (006/17)
- Leave as default "2" (integrating entry)

**Notes:**
For copy cataloging, accept values in other positions

## Uniform Titles : LCRI 25.5B

- LCRI revised to remove the separate paragraph related to "computer files"
- Treated computer files as "special" publications but they weren't
- Didn't cover all instances when a uniform title may have been required (e.g., translations)
- Didn't have flexibility for cases of conflict

**Notes:**
Note that this pertains only to those who need to create uniform titles for electronic resources; usually for inclusion as secondary access point on a related bibliographic record, but now there will be an additional reason.

## LCRI 25.5B : Extent of Change

- For electronic resource _monographs_, now incorporated as the "norm" (treat as any other monograph)
- For _integrating_ _resources_, treat as monographs, EXCEPT: also create a uniform title if a serial _becomes _an integrating resource (i.e.,  stops/starts) and _doesn't_ change its title proper

## LCRI 25.5B : Choice of Qualifiers

- Was:   "(Computer file)"
- Now: use judgment to identify the ***most appropriate*** qualifier.  Possibilities include:
- Corporate body
- Date of publication
- Descriptive data elements, e.g., edition statement, **GMD**, physical medium
- Place of publication
**(not in priority order!)**

**Notes:**
Computer file: sometimes used in conjunction with the 

So, for new records, can still use the GMD, just not "(Computer file)", but have the flexibility to use something else, e.g., corporate body.  

## "Old" Authority Records

- Let sleeping dogs lie  (LCRI 25.5B)
- Headings that exist with "(Computer file)" should not be changed unless the heading needs to be changed for another reason

## MARC 21 : Summary of New Tags

- Variable fields, generally used only on serials until now, to be used in integrating resource records:
- 022– ISSN
- 247/547– Change in title proper
- 310/321– Frequency
- 362 1– Beginning/ending date of publication
- 550 – Issuing body note
- 580, 76X-78X– Relationships with other resources

**Notes:**
These really aren't new tags, just new to you