# Presentation: 366563

## Session 2bOriginal Cataloging, continued

- _Session 2b covers_:
- Bibliographic description areas 7-8
- Access points
- Linking entry fields
- Final records for three resources

**Notes:**
This session continues Session 2 and picks up where we left off.

## Area 7: Notes

**This workshop covers only notes new or mandatory for IRs:**
- Frequency (310/321)
- Nature and scope, system requirements, and mode of access (516, 538)
- Source of title proper (500)
- Bibliographic history and relationships (530, 580, 76X-78X)
- Item described (500)
- MARC tagging for many notes is the same for both serials and integrating resources
**247/547** for former title proper information
**310/321** for current and former frequency of updates
**362 1** for publication date information when not from first/last iteration
**550** for issuing bodies information
**530, 580, 76X-78X** for bibliographic relationships and links

**Notes:**
 The remaining part of the bibliographic description is to make additional notes, those required by the rules and those judged important by the cataloger.
 MARC tagging of notes:
 With the implementation of the 2002 Amendments in December 2002, some fields formerly used primarily or exclusively for serials now are used for integrating resources as well.  The goal is to tag all continuing resources, whether serial or integrating, in the same way.
 Important Note: this workshop covers only a very few of the many notes that may apply for an integrating resource.  We are looking at those specifically new for updating Web resources and loose-leafs now required by Chapter 12 (Frequency, Item Described, Bib. History & Relationships [as links]) and those mandatory and of special importance for electronic resources (Mode of access, source of title proper).  Many other notes not covered are also very important, for example, the 520 summary note in electronic resource records.
 Additional note: instructors may also want to mention that, unless following guidelines such as those of the CONSER program, notes should be given in AACR2 order rather than MARC tag number order, and, for electronic IRs, following the order given first in chapter 9, then in chapter 12.  
 Info from the PCC module on integrating resources for order of notes:  LCRI 1.7B gives institutions the flexibility of providing notes in either AACR2 prescribed order or MARC 21 field order.  CONSER and BIBCO participants should  follow the practice that is institutionally most expedient.  That is to say, if the majority of integrating resources are cataloged by serials staff, an institution may give preference to the prescribed CONSER MARC 21 field order for notes.  Alternatively, if the cataloging of integrating resources is primarily the work of monograph catalogers, then AACR2 prescribed order may prevail as the preferred order.
	When doing copy cataloging or updating existing records for integrating resources, add or modify notes in the most expeditious manner.  Do not expend time and effort in rearranging notes to fit a certain style or convention.

## 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
- _LCRI 12.7B1_ (LC/PCC practice):
- _Always_ give a note for known frequency of updates, even if already apparent from the rest  of the description

**Notes:**
The frequency note is the first note in chapter 12 for continuing resources.

 This note is new for integrating resources with the publication of revised chapter 12 in 2002.  (Another element not just for serials any more!)
 Reminder: the codes in the 008 Frequency and Regularity elements are based on the content of this note (tagged in the 310 field). 

 Some online databases have known, explicitly-stated frequency of updates, but many do not, and the vast majority of Web sites do not.  
 Many Web sites, however, may be known to be updated very frequently (more often or usually more often than once a day), such as most news and weather sites, or completely irregularly, as many organizational Web sites such as the BIBCO and CONSER sites.  

 If time: Can participants think of examples of regularly and irregularly updated Web sites and databases?  When is the frequency of updates known and when unknown?

## Frequency and regularity example 1

- 245 00 Anglo-American cataloguing rules
- 250    2nd ed., 2002 revision.
**310    Updated annually**
**008    Freq: a   Regl: r**

- 1) You know that this loose-leaf will be updated annually on a regular basis

**Notes:**
You may want to refer to the MARC Coding Guide in Appendix A, which everyone should have loose from their manual for ready reference, while going through these examples.

This is the first of several slides that illustrate the updating frequencies that IR catalogers  are likely to encounter.  

The meaning of the Regularity code and its coordination with the Frequency code may need some explaining for participants.

Always include the term “updated” in the frequency note for IRs, to clarify that this is not frequency of serial issues.

## Frequency and regularity example 2

- 245 04 The EMBL reptile database $h [electronic resource].
**310    Updated quarterly**
**008    Freq: q   Regl: r **

- 2) You know that this database is regularly updated every three months

**Notes:**
This is one of the relatively unusual examples in which a database has a statement of regular updating.  

__________________

Possible discussion questions, if time:
 If there are any serials catalogers present, what is the practice of serials cataloging and statements of frequency in catalog records?
 Is a statement in the resource transcribed and taken at face value?
 Is a comparison made with actual frequency of recent of updates at the time of check-in and the establishment and adjustment of publication patterns and claiming of issues?
 Should the cataloger of an integrating resource take a statement like this at face value?
 How might they check to see if updates really are made quarterly?
 How close would they need to be to quarterly, if not right on the nose, for the statement to remain basically accurate and helpful to users?  [Could say “Updated four times a year.”]

## Frequency and regularity example 3

- 245 00 Nestor $h [electronic resource] : $b bibliography of Aegean prehistory and related areas.
**310    Updated monthly (except June-Aug.)**
**008    Freq: m   Regl: n **

- 3) You know that this database is updated on a monthly basis but regularly skips certain months

**Notes:**
An example of “normalized irregular” updating.

## Frequency and regularity examples 4-6

- _Weather.com Web site  _[http://www.weather.com/]
**310    Continuously updated**
**008    Freq: k   Regl: r**

- _CONSER Web site  _[http://www.loc.gov/acq/conser/]
**310    Updated irregularly**
**008    Freq: _   Regl: x**

- _Global invasive species database_
***[No 310 present]***
**008    Freq: u   Regl: u**

- 4) You know that this Web site is updated on a very frequent basis   [Regl code “k” = continuously updated; defined as “more frequently than daily”]

- 5) You know that this Web site is updated irregularly (no regular pattern)

- 6) You know that this database is updated but have no information about how often or according to a regular or irregular pattern

**Notes:**
Instructor note: MARC 21 has "Continuously updated“ while AACR2 uses "Continually" in 12.7B1 example.  But AACR2 examples are not prescriptive.  In this example the former term has been chosen for the sake of consistency with MARC 21 and CONSER documentation.

Code “k” is defined in MARC 21 as “more frequently than daily.”

If you know a resource is updated completely irregularly, code it as such; for example, the CONSER or PCC Web sites.

There has been some discussion about whether to code the regularity of continuously updated as x or r.  But regularity code “x” can only be used when Freq. equals code blank, or when used to express numbers per year.  Therefore “r” is the best choice.  [This guidance comes from Judy Kuhagen of CPSO and Jean Hirons of CONSER, Jan. 2003]

## Former frequency note

- 245 00 Drug interaction handbook / $c editors, Kenneth A. Scott ; Julie B. Olin.
- 260    Denver : $b MedFacts, $c c1996-
- 300    v. (loose-leaf) ; $c 27 cm.
**310    Updated quarterly, $b July 2001-**
**321    Updated semiannually, $b Jan. 1996-June 2001**
**008    Freq: q   Regl: r **

**Notes:**
Former frequency is tagged in field 321.  This is actually more likely to arise for IRs in the future when the updating frequency is different from that already stated in an existing record.

## For electronic integrating resources:Nature and scope, system requirements, and mode of access note: 9.7B1

- a) Nature and scope
- Make notes on nature and scope of the resource if not apparent from rest of description
- 516    Computer game.
- b) System requirements
- Note system requirements only if special software or hardware are required to access and use the resource
- 538    System requirements: Adobe Acrobat reader.
- c) Mode of access
- Always specify the mode of access for remote access resources
- 538    Mode of access: World Wide Web.

**Notes:**
This is the first note in Chapter 9 for electronic resources: AACR 9.7B1. 

It has three distinct aspects:
 A: Nature and scope: tagged in field 516; is optional for integrating resources.
 B: System requirements: tagged in field 538; is required if applicable for remote-access resources.
 Used in records for remote-access resources only when special software, hardware, or peripherals are required to access and use a resource --beyond a computer with Internet access and a Web browser.
 C: Mode of access: also tagged in 538; is mandatory for remote-access resources, and is normally the first note in the record.

Also noteworthy: Notes are given in MARC tag number order in CONSER records. For non-CONSER records, give notes in the order required by the utility or local system (which, for example might be: give notes in AACR2 prescribed order, regardless of MARC tagging).  

Additional reminder: do not combine system requirements and mode of access notes.

## Nature and scope note, and System requirements note

**516    Text (HTML and PDF).**
**538    System requirements: Adobe Acrobat reader to view and print PDF files. **
**538    Mode of access: World Wide Web.**

- Nature and scope note, and System requirements note

**Notes:**
 This updating database includes documents in both HTML text and PDF formats.  
 The user must have Adobe Acrobat Reader installed on their computer in order to view the PDF versions of the documents.
 Instructors should point out that:
 A “nature and scope” note is optional, but a cataloger could choose to include one such as the one given on the slide, in which case it is tagged in field 516.
 The system requirements note is required in this case because more than just a computer with Internet access and a Web browser is required to access and use the PDF files that are included within this resource.

## Source of title proper note: 12.7B3

- Printed integrating resources:
- Make a note on the source of the title proper if it is taken      from a title page substitute
- Nonprint integrating resources:
- Follow the instructions in subrule .7B3 in the chapter dealing  with the type of material to which the resource belongs
- For remote electronic resources: 9.1B2 & 9.7B3:
- _Always_ give source of title proper in a note
- Examples given in 9.7B3 and 12.7B3 include:
- Title from title screen
- Title from home page (viewed on Dec. 18, 1999)
- (*Source of title proper note combined with item described note*)

**Notes:**
Both chapters 12 and 9 require the source of title proper note always be given in records for remote access electronic resources.

This note is often often combined in e-resource cataloging practice with the Item Described note (alternatively referred to as the “Description based on” note).  Both notes do relate to identifying the title and iteration of the resource being described.  

## Bibliographic history and relationships note: 12.7B8

- Make notes on the **bibliographic history** and on the **important relationships** between the resource being described and the immediately **preceding**, immediately **succeeding**, or **simultaneously issued** resources.
*These include:*
- Continuations
- Mergers
- Splits
- LC/PCC practice: give **reciprocal linking notes**
- Use MARC 76X-78X linking entry fields and 580 linking entry complexity note when appropriate

-  Absorptions
-  Translations
-  Simultaneous editions
-  Supplements

- Detailed coverage of linking notes later in Session 2

**Notes:**
 These kinds of bibliographic history and relationships and their MARC tagging have been worked out in detail for serials over time. 
 LC/PCC practice is to apply Rule 12.7B8 to both serials and integrating resources, using the same MARC tags. 
 This will be very new to those who in the past cataloged exclusively monographic resources.
 See LCRI 12.7B8 for some further guidance.

 Because the use of linking entries is fairly complex and will require many slides, it will be deferred to the end of Session 2b, rather than interrupt this section on AACR2 chapter 12 notes, followed by AACR2 access points.
___________________
“The relationship between one integrating resource and another integrating resource, or between an integrating resource and a serial, or between an integrating resource and a monograph, is generally expressed by reciprocal linking notes on both records rather than by a related-work added entry for the earlier resource on the record for the later resource (12.7B8, LCRI 12.7B8, LCRI 21.28B1)”  --quoted from CPSO Web site “Library of Congress Implementation of the 2002 Edition of AACR2 – Significant Changes” 

## Item described note: 12.7B23

- If the description is not based on the first iteration:
- Make a note of the latest iteration consulted in making the description
- Description based on: 1994 ed. through update 10
- For remote access resources:
- _Always_ give the date on which the resource was viewed for description (see also 9.7B22)
- Description based on contents viewed on Oct. 21, 1999
- Title from title bar (viewed on Jan. 13, 2000)
- (*Source of title proper note combined with item described note*)

**Notes:**
 Although the last note in number order in both chapters 12 and 9, this is one of the most crucially important notes for integrating resources.  
 It is mandatory in all records for remote access electronic resources, but is also required in records for print integrating resources when not cataloging from the first iteration.

 This note is commonly combined in e-resource cataloging practice with the Source of Title Proper, in which case it is usually worded as “viewed on ...” and placed in parentheses after the source of title proper.
 In print IR resource records, it is more commonly given as “Description based on...” (the same as for serials)
 Both notes relate to identifying the title and iteration of the resource being described.  

## Item described note

- The NAB Guide to Endangered Species
- Update no. 16July 2002

- 245 00 Anglo-American cataloguing rules
***No note given because resource is not electronic and description is based on first iteration***

- 245 04 The NAB guide to endangered species.
- 250    4th ed.
**500    Description based on: update no. 16, published July, 2002.**

**Notes:**
If you can give an update or release number that coincides with the iteration upon which the description is based, it should be given especially when cataloging loose-leafs. When cataloging web sites or online resources use judgment.

## Combined source of title proper and item described notes example

- 245 00 USDA national nutrient database for standard reference $h [electronic resource].
**500    Title from home page (viewed on Dec. 15, 2002).**

**Notes:**
 This slide illustrates the two notes combined into one, and the most common form of wording for the note.
 This combination note appears to be used by far the most often in WorldCat records for Internet resources.
 This combined note will be used in this course in examples and exercises, but participants should be aware that they are logically two separate notes, covered by two separate rules in AACR, and that nothing requires their being combined into one.
Note that a note “Description based on” for the release number may also be added, although it is not required.

## Area 8: Standard number and terms of availability: 12.8

- Record standard numbers
- Standard Number (12.8B1)
- ISBN: 020
- ISSN: 022
- LCRI 12.8B1: If an integrating resource has both, give both in the catalog record.

**Notes:**
Integrating resources may bear standard numbers such as ISBN and ISSN.
 If present either or both are to be recorded in the catalog record.

 Remember that a canceled or invalid ISBN that appears in a resource should be recorded in an 020 subfield $z and an incorrect ISSN that appears in a resource should be recorded in an 022 subfield $y; a cancelled ISSN, after verification by an ISSN Center that it represents a cancelled ISSN, is recorded in 022 subfield $z.

## Access Points: Main and added entries

-  Determine name and uniform title entries
- Based on AACR2 chapter 21
- Persons and bodies that bear responsibility for the intellectual or artistic content of the resource
- Uniform titles for resources dealing with works of literature, music, etc.
- Enter in MARC 1XX and 7XX fields
- In full-level records, 7XX entries must be explained (“justified”) by being given in the descriptive part of the record (MARC 2XX-5XX)

**Notes:**
 This workshop does not go into the rules for determining main and added entries since the rules are the same for updating loose-leafs and updating online resources as for other resources.
 See LCRI 25.5B for guidance on constructing uniform titles to resolve title conflicts for integrating resources.  

## Corporate body main entry example

**110 2_ Program for Cooperative Cataloging.**
- 245 10 Program for Cooperative Cataloging $h [electronic resource] : $b [website].

**Notes:**
This slide is intended to contrast with the following slide.
 Both are examples of institutional or organizational Web sites.  
 In this case the name of the organization is given as main entry since the Web site as a whole “emanates” from the PCC and falls within the scope of rule 21.1B2a: “...of an administrative nature dealing with the corporate body itself ... or its offices, staff, and/or membership (e.g., directories) ...”

## Title main entry example

**245 00 Smithsonian Institution** $h [electronic resource] :  	$b [website].
- 710 2_ Smithsonian Institution.

**Notes:**
 In this case, although the Web site as a whole “emanates” from the Institution, the predominant content of the site goes well beyond the scope of the categories given in rule 21.1B2a (“...of an administrative nature dealing with the corporate body itself ... or its offices, staff, and/or membership (e.g., directories) ...”)

## Electronic location and access

- MARC 856 field
- Indicators:
- First indicator = access method
- Second indicator = relationship
- Most commonly used subfields:
- Subfield $u = uniform resource identifier (URI)
- suffices for most Web resources
- Subfield $z = public note
- Subfield $3 = materials specified note
- Serves as active hyperlink from the catalog record to the online resource in Web-based catalogs

**Notes:**
 Perhaps the most crucial access point for an online resource is its electronic address.
 The slides ahead look at the indicator and subfield codes
 In Web-based catalogs it is the URL in subfield $u of the 856 field that serves as a ‘hotlink’ directly to the resource itself on the Internet.
 A resource may have more than one electronic address and/or access method and so have more than one 856 field in the record

 Reminder: do not enter institution-specific URLs into records shared on the utilities (the same as any local, copy-specific, or institution-specific notes or other information).

## 856 indicators

- _Indicator 1: Access method_
- 0 = E-mail
- 1 = FTP
- 2 = Remote login (Telnet)
- 3 = Dial-up
**4 = HTTP**
*Used for most Web resources*
- 7 = Method specified in $2
*Used in records for Web resources before 1997*

- _Indicator 2: Relationship_
*Can generate display constant*
- Blank = No info. provided
**0 = Resource**
*Used in records for Web resources themselves*
- 1 = Version of resource
- 2 = Related resource
- 8 = No display constant generated

**Notes:**
First Indicator: The vast majority of Web sites and databases cataloged will have first indicator 4 since their primary address will be on the World Wide Web.
 It is possible that some resources may include FTP addresses for downloading files or database records, etc., but the majority will have basic HTTP addresses.
 1st indicator value “4” for HTTP was established in 1997, and records cataloged before that time and not subsequently updated will have 1st indicator “7” with http specified in $2 [as was any other access method not specified by another indicator].
Second indicator:
 Second indicator value “0” is used when the body of the record describes an online resource itself.  
 Value “1” is used more often in records for print resources that have an electronic version available online.
 Value “2” is used for example in records for printed books that have a related resource available online.  A common example is when a book has a table of contents available online.  
 This value may be used in online resource records if there is a related online resource which the cataloger thinks is important to note and provide access to, but this is relatively rare in records for updating Web sites and databases. 
 Value “2” is used for an online table of contents because the TOC is not an online version of the entire resource, but only of a portion of it.  [See OCLC records 49383996 and 47844676 as two of many hundreds of examples cataloged by the Library of Congress.]

## 856 Examples

- 245 10 Program for Cooperative Cataloging $h [electronic resource] 	: $b [website].
**856 40 $u http://lcweb.loc.gov/catdir/pcc/**

- 245 00 Charta $h [electronic resource] : $b scegli charta e il 	biglietto tuo.
- 546    In Italian; includes English version.
- 856 4**0** $u http://www.charta.it/
- 856 4**0 $3 English version** $u http://www.charta.it/english/index.php

- 245 00 OCLC firstsearch $h [electronic resource].
- 856 40 $u http://www.ref.oclc.org:2000 **$z Requires authorization and password**

**Notes:**
 Out of the numerous possible subfield codes available in the 856, the vast majority of Web resources will need to use only subfield $u for the URL (Uniform Resource Locator).
 Two other commonly used subfields:
 $3 : Specifies the part of the item to which the 856 applies, e.g., an online table of contents
 $z : Public Note: a note pertaining to the electronic location of the source identified in the field that is in a form adequate for public display.

## URL in 856 must match granular level of description

- URL in 856 40 must match granular level of resource you are selecting for description in the body of the bibliographic record.

**http://www.un.org/english/**= URL for English language portion of Web site

**http://www.un.org/**= URL for whole Web site

**Notes:**
 One of the most important things for catalogers is to be sure URL in 856 40 matches the granular level of resource described in the body of bib record.

 It is all too easy to be maneuvering around within a Web site and copy and paste or insert a URL for a sub-page into the 856 field, when you are really intending to catalog a higher level of granularity.
 This appears too often, for example, in WorldCat records, where the URL in the 856 is for a sub-page of the resource and does not match the description in the body of the bibliographic record.

## Internal bookmarks in 856 URLs must also match

**856 40** $u http://dublincore.org/resources/**faq/**
- URL in 856 40 must match the level of a Web resource selected for cataloging; must not contain an internal “bookmark” to a sub-section within a page ***unless*** that is the specific section being cataloged.  HTML bookmarks are indicated by the “#” sign.

**http://dublincore.org/resources/faq/#whatisanattributevaluepair** = URL for bookmarked sub-section of FAQ

**http://dublincore.org/resources/faq/** = URL for whole FAQ document

**Notes:**
This is another common variation on the same theme:
 Many Web pages contain internal “bookmarks”, indicated by the pound sign, that serve as internal page hyperlinks that take the user to various points within a long page.
 This FAQ is an example, where each question is bookmarked so that the user can click on the question and be taken directly there instead of scrolling down.
 But again we find in too many catalog records that the cataloger has copied and pasted or inserted the bookmarked URL into the 856 instead of the base URL for the whole page.
 Something to pay attention to and be aware of and double-check in original cataloging records.
 There may, however, be cases in which the resource to be cataloged is at the level of a bookmark within a larger page.  In those cases, the bookmark is to be included in the electronic address / URL for the resource.  
 The key is that the electronic address must take the user to the resource described in the body of the bibliographic record, whatever has been selected for cataloging.

## Beyond AACR2: Subject headings and classification

- Do the same thing as for non-integrating resources, but keep in mind the changing content
**Analyze the subject content** of the resource at the selected granular level
**Assign subject headings** from a standard scheme
- LCSH, MeSH, etc.
- May also assign a **classification number** from a standard scheme
- LCC, DDC, etc.
- Class portion alone may suffice in master records

**Notes:**
 Do subject analysis and select appropriate subject headings according to an established scheme, LCSH being the most common.  
 Anticipate changing content as much as is reasonably possible and assign subject headings accordingly.  Do not assign headings for very specific content that is likely to change.
 Beware of topical vs. form subdivisions and topical vs. genre headings for online resources.  There are only a few subdivisions that specifically identifies a resource as being on the Internet (e.g., $v Blogs, $v Electronic discussion groups, $v Online chat groups).
The subdivision --Computer network resources is a topical ($x) subdivision, not a form ($v) subdivision, and is therefore to be used for resources that are about Internet resources on a particular topic, not for resources that are Internet resources about a particular topic.
 The subdivision $v Databases is a form subdivision that may apply to some databases with highly interactive content [see LC Subject Cataloging Manual: Subject Headings for details on the use of the form subdivisions --Databases, --Software, --Interactive multimedia, --Electronic discussion groups, and --Computer games].
 Also see the section on subject analysis and classification in the Jan. 2005 revision of the PCC module on integrating resources.
 Adding a classification number is also valuable as a subject access point, but is not required and different institutions may have different polices about supplying one in a master record.  Local use of classification for online resources will vary from institution to institution as well.
 It has often been recommended that the class portion alone in subfield $a of a call number field is sufficient in a master/shared record, since a cutter number is not needed for shelf arrangement.  But some institutions may want complete call numbers for their local systems.
 If time, instructors may wish to ask participants what they are doing with classification for online resources in their institutions.

## Relationships with other resources and Links between records

- _12.7B8: Bibliographic history and relationships note_
- Make notes on the **bibliographic history** and on the **important relationships** between the resource being described and **immediately preceding, immediately succeeding, or simultaneously issued resources**
*These include:*
- Continuations
- Mergers
- Splits
- _LC/PCC practice: give __reciprocal linking notes_
- Use MARC 76X-78X linking entry fields and 580 linking entry complexity note when appropriate

-  Absorptions
-  Translations
-  Simultaneous editions
-  Supplements

**Notes:**
This was one of the BIG new changes in the 2002 revision of AACR2 --monograph and serial catalogers have long taken different approaches on how to show bibliographic relationships.  
 For monographs, certain relationships, such as revised editions involving title changes, were covered by a note and a related work added entry.  Serials catalogers have long used the specific linking entry fields in MARC to show relationships 
 Chronological relationships have been especially key to serials cataloging: for serial title changes requiring a new record, with links between records for preceding and succeeding titles.
 LC/PCC practice is to apply Rule 12.7B8 as written to both serials and integrating resources, and to use MARC linking entry fields for both. 
 The use of linking fields will likely be quite new to those who in the past cataloged exclusively monographic resources.
 The following slides will provide an overview and introduction to links, followed by examples that apply to integrating resources.
 See LCRI 12.7B8 for some further guidance.

Note: Another type of relationship not listed on the slide because not listed in rule 12.7B8 is: Other physical formats

## Reciprocal links between records

- Relationships are generally expressed by reciprocal linking notes on both records
- Rather than by a related-work added entry for the earlier resource on the record for the later resource:

- Integrating resource

- Serial

- Monograph

- Integrating resource

- Integrating resource

- Integrating resource

- But not: Monograph  Monograph

**Notes:**
The basic rule is that links should be added to each record for a title in a linking relationship, with a limited number of specified exceptions.
 This “principal of reciprocity” may provide impetus for new cooperative effort between catalogers of serials, integrating resources, and monographs; CONSER and BIBCO, etc.

“The relationship between one integrating resource and another integrating resource, or between an integrating resource and a serial, or between an integrating resource and a monograph, is generally expressed by reciprocal linking notes on both records rather than by a related-work added entry for the earlier resource on the record for the later resource (12.7B8, LCRI 12.7B8, LCRI 21.28B1)”  
--quoted from CPSO Web site “Library of Congress Implementation of the 2002 Edition of AACR2 – Significant Changes,” viewed January 6, 2003.

 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

See also for reference: CONSER Cataloging Manual 14.1.5

## What linking fields do and don’t do

- 1. Links generate notes
- In an online record: 780 00 $t Performance practice review $w ... generates the note:
- Continues: Performance practice review.
- 2. Links connect related records in a database
- 3. Links are not intended to provide added entries

**Notes:**
Heads up for trainers: technically linking fields do not provide added entries, but many libraries are choosing to index these in their local systems, in which case they do serve as searchable added entries.  If time allows, instructors might ask participants what their local systems do with linking fields.

See also for reference: CONSER Cataloging Manual 14.1.3

## Chronological relationships

- Relationships in time between resources (sequential relationships)
- May be **simple** (e.g., one-to-one relations such as: continues/ continued by) or **complex** (more than one-to-one relations, such as: mergers, splits, absorptions)
- _Most commonly in IR records_: **when a publication issued over time changes from one format to another**; or for successive editions of an updating loose-leaf with in toto replacement
- A new catalog record is required for the publication in the new format, etc.
- _Examples_:
- A print serial continued by an online database
- Two print serials and a loose-leaf service cease and merge into a single online Web site
- A loose-leaf issued in a new edition, with in toto replacement of the base volume
- An online database separated from a print serial

**Notes:**
Note again that for serials cataloging, chronological relationships have been of crucial importance and using the MARC 780/785 fields has been the key to linking records for preceding and succeeding titles of the same serial.

## Horizontal relationships

- Relationships between different versions of the same resource
- May be issued **simultaneously** (language editions) or at **different times** (reprints or translations); also include **supplements** and **reproductions**
- _Most commonly in IR records_: when a publication appears in** a different format, a different language, or as a reproduction**
- _Examples_:
- A print serial also issued as an online database
- Four map serials also issued as a combined online GIS database
- A CD-ROM serial also issued as an online database

## Common MARC 21 linking fields 

**Linking fields**
- 765 Original language entry
- 767 Translation entry
- 775 Other edition entry
- 776 Additional physical form entry
- 780 Preceding entry
- 785 Succeeding entry
- 787 Nonspecific relationship entry
**Note fields **
- 530 Additional physical form available note
- 580 Linking entry complexity note
- used when appropriate note cannot be generated using a linking field alone

**Notes:**
In case this is raised by participants: you might note that most serial-monograph-IR links created at this time will likely appear as MARC fields 775, 776, 780, and 785. Though it is conceivable that some other linking fields, such as 765, 767, or 787, could also be appropriate under some circumstances.
530 and 580 fields are used in combination with a non-displaying linking field whenever an appropriate note cannot be generated using a linking field alone
----------------------
Extract from MARC 21 Concise Format for Bibliographic Data: RECORD LINKS AND NOTES (see full document for more complete information)
 Linking Entry Fields (fields 760-787) 
These fields carry descriptive data concerning the related item, the control number for the record of the related item, or both. Minimal content designation is provided for the data concerning the related item that is used in the linking entry fields. For data operations requiring fuller content designation, such as indexing and sorting, subfield $w (the record control number for the related item) allows the system to follow that link to the related record to obtain fully content-designated data. Moreover, the coded data in control subfield $7 allows some types of indexing without reference to the actual related record. The value used in the first indicator position of a linking entry field determines whether a note is to be generated from the field. 
 Linking Entry Complexity Note (field 580) 
The Linking Entry Fields are designed to support generation of a note concerning the related item in a display of the record for the target item. When the relationship is too complex to be expressed using a display constant and the data from the linking entry field or the linked record, the note is recorded in the Linking Entry Complexity Note field. When used, this field appears in addition to any relevant 760-787 linking entry field, and no note is generated from the linking entry field. 
 Linked-Record Requirement (Leader/19) 
This data element indicates whether sufficient information is present in the linking entry field to support generation of an eye-readable note that identifies the related item or whether only a related record number is recorded. If only a record number appears, the system will need to obtain the appropriate information from the related record to construct a standard display. 
        The following subfields or subfield combinations are considered sufficient for display purposes: 
Subfield $a + $t (Main entry heading + Title) 
Subfield $a + $s (Main entry heading + Uniform title) 
Subfield $a (Main entry heading) 
Subfield $t (Title) 
Subfield $s (Uniform title) 
Subfield $u (Standard Technical Report Number) 
Subfield $r (Report number) 
 Added Entries (fields 700-730) 
When a cataloging code calls for an added entry for a title used in a linking field, the added entry is recorded in the appropriate 700-730 field. Linking fields are not intended take the place of added entries. Likewise, an added entry in field 700-730 does not take the place of a linking field, as it cannot cause a note to be generated or carry a record link. 

## Components of linking entry fields

**1. Catalog entry**: $a, $b, $t, $s
- Enter the catalog entry from the MARC 130 and/or 1XX, 240, and 245 fields of the related record into the $a, $t, and occasionally $b and $s of the linking field in the record being edited
**2. Standard numbers**: $x, $z
- Whenever it is available on a related record, include the **ISSN** in $x and/or the **ISBN** in $z in the link
**3. Control numbers**: $w
- Include a $w for the **LC** and/or **NLC** record number, if one exists
- Include also a $w for a utility (e.g., OCLC) record number if cataloging in one of the utilities and/or if there is no LC or NLC record number
**See LCRI 12.7B8** for more information and exceptions

**Notes:**
Catalogers should also use the catalog entry in 580 or 530 note fields when needed.

“NLC record number” = National Library of Canada control number, see CONSER Editing Guide, 010 for further information.

See also for reference: CONSER Cataloging Manual 14.1.4

## Linking fields: Indicators (1)

- 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

___________________

[Note of acknowledgement: this and most of the following slides up to the linking entry examples were originally created by Judith Kuhagen and David Reser of LC CPSO, who at this workshop creator’s request agreed to share them for modification and use in this workshop.]

## Linking fields: Indicators (2)

- Second indicator for 780 (Preceding entry)
- 0	 Continues
- 1	 Continues in part
- 2	 Supersedes [Pre-AACR2]
- 3	 Supersedes in part [Pre-AACR2]
- 4  Formed by the union of ... and ...
- 5	 Absorbed
- 6	 Absorbed in part
- 7	 Separated from

-  requires 580 note

**Notes:**
2nd indicator “4” necessitates the use of a 580

Note indicators 2 and 3 are not used for current cataloging because 12.7B8 makes no distinction between the words “continues” and “supercedes”

## Linking fields: Indicators (3)

- Second indicator for 785 (Succeeding entry)
- 0	Continued by
- 1	Continued in part by
- 2	Superseded by [Pre-AACR2]
- 3	Superseded in part by [Pre-AACR2]
- 4	Absorbed by
- 5	Absorbed in part by
- 6	Split into ... and ...
- 7	Merged with ... to form ...
- 8 	Changed back to [Pre-AACR2]

- Usually need 580 note

**Notes:**
Use of 2nd indicators 6 or 7 means you will probably have to do 580

Second indicators 2, 3, and 8 are not used in current cataloging. 

## Linking fields: Subfields (1)

**$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, $b, $t, $w, $x, $z

## Linking fields: Subfields (2)

**$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)

## Linking fields: Subfields (3)

**$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_
- [Must have 12 positions: 2 initial blanks in post-2000 numbers; 3 initial + 1 final blank in pre-2001 numbers]
- In OCLC database, also include: **OCLC record number** from related record
- Precede by (OCoLC) without spaces:   $w (OCoLC)1758471
- Example with both LCCN and OCLC numbers in $w:
- $w (DLC)__2002003771 $w (OCoLC)4471176

**Notes:**
For those working in the OCLC WorldCat database, $w should include OCLC control numbers

## Linking fields: Subfields (4)

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

## Linking fields: 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)

**Notes:**
Reminder: do not use internal subfielding (especially problematic when using $b for a subordinate body in the main entry because $b has a different use in links)

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

**Notes:**
The information on this slide is primarily from LCRI 12.7B8

## 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 or when the cataloger wants to give additional information.

**Notes:**
Examples of when a 580 is required: 780 indicator 4 and, 785 indicators 6 and 7,  as shown on slides 34 and 35.

See examples of giving additional information on slides 47 and 48 to clarify the titles of related resources.

## Example 1: New ed. of updating loose-leaf related to previous ed.

- Record for current edition:

- OCLC record # 27813639
- 010 93-9913
- 020 0844407844
- 245 00 CONSER cataloging manual / $c Jean L. Hirons, editor.
**785 00 $t**** CONSER cataloging manual. ****$b**** 2002 ed. ****$z**** 084441073X  ****$w**** (DLC)__2002071009 $w (OCoLC)50440733**

- Record for previous edition:

- OCLC record # 50440733
- 010    2002-71009
- 020    084441073X (loose-leaf)
- 245 00 CONSER cataloging manual / $c Jean L. Hirons, editor.
- 250    2002 ed.
**780 00 $t**** CONSER cataloging manual. ****$b**** 1st ed. ****$z**** 0844407844 ****$w**** (DLC)___93009913_$w (OCoLC)27813639**

**Notes:**
An example of a simple bibliographic relationship that does not require a 5XX linking complexity note.

Recall that a new bibliographic record is created only if the bibliographic resource is a new edition per LCRI 21.3B.  Because the 2002 ed. of this manual entails an in toto replacement of the entire base volume, it is considered a new resource/work and a new record is required.

If the 100 and 245 are the same in both records, you need to include $b (Edition) after $t (Title) in the linking fields.

## Example 2: Merger of two loose-leaf resources into one new resource

- Record for current resource:

- Reciprocal links are given in each of the records for the two preceding  resources.

- 010    2002111111
- 022    1234-5678
- 245 00 Regulations for commercial and residential property.
**580    Merger of:**** Regulations for commercial property****, and:**** Regulations for residential property**
**780 14**** $t Regulations for commercial property $z 1212343456 $w (DLC)___95012012_**
**780 14**** $t Regulations for residential property $z 0101252252 $w (DLC)___96214789_**

**Notes:**
Reminder: linking entry fields include indicators that generate display constants.  In most cases serials records use these indicators in the majority of cases and do not include an additional 5XX note, because the display constant is sufficient to make clear the nature of the relationship of the linked title to the title described in the body of the record.

Here is an example of a complex relationship that can’t be explained just from the 7XX linking fields.  
The 580 is often needed when there is more than one of the same type of link in a bibliographic record.

Here the new resource is a merger of two previous resources.  Because there isn’t a way to combine the information from the two links in a meaningful way with just the information in the two 7XX fields, the explanation of the relationship is given in the 580 note field.  Then the citations are given in two 780 fields for the two preceding resources.
 The first indicator is “1” because the note should not be generated from the 780 fields (a 580 field is in the record); the second indicator of “4” indicates that a merger is involved.

NOTE: The examples of the other two records, with reciprocal linking notes back to this record and to each other, are not shown in these workshop slides, but it should be understood that they need also to be made.

[This example and the notes have been borrowed from Judy Kuhagen and Dave Reser.]

## Option: generate notes from links

- 245 00 Environmental knowledgebase $h [electronic resource].
**530  ****  ****Also available in a CD-ROM version as:**** ****Environmental periodicals bibliography**.
**776 1  $t**** Environmental periodicals bibliography (CD-ROM) $x 1053-1440 $w (DLC)sn_90003252_$w (OCoLC)22461337**

- Option 1: use 530 note:

- Option 2: use $i in 7xx link:

- 245 00 Environmental knowledgebase $h [electronic resource].
**776 08**** ****$i Also available in a CD-ROM version as:**** ****$t Environmental periodicals bibliography (CD-ROM) $x 1053-1440 $w (DLC)sn_90003252_$w (OCoLC)22461337**

**Notes:**
 An option to using the 530 note used in the past to specify the nature of a relationship of a resource available in more than one physical format is to enter this information into subfield $i of the linking note and thus generate a note from the link.
 In effect you are giving your own note instead of an automatically-generated  display constant (and in which case you use second indicator “8” for ‘no display constant’).

 This is now the preferred method for use when an automatic display constant is not needed.  
 But when a display constant is needed, as in the case of 780 and 785 preceding and succeeding linking entry fields, the $i note cannot be used, and a 580 linking complexity note must be used if needed in conjunction with those two kinds of links..

## Example 3: Online database (IR) related to CD-ROM version (serial)

- 008    Type: a  BLvl: **i**   SrTp: **d**   S/L: **2**
- 006    Type: m  Audn:   File: e   GPub:
- 245 00 Environmental knowledgebase $h [electronic resource].
- 538    Mode of access: World Wide Web.
**776 08****  $i Also available in a CD-ROM version as: $t Environmental periodicals bibliography (CD-ROM) $x 1053-1440 $w (DLC)sn_90003252_$w (OCoLC)22461337**

- Record for online database:

- 008    Type: a   BLvl: **s**
- 130 0  Environmental periodicals bibliography (CD-ROM)
- 245 00 Environmental periodicals bibliography $h [electronic resource].
- 300    computer optical discs ; $c 4 3/4 in.
**776 08**** $i Beginning 1998 available also as an online database: $t Environmental knowledgebase $w (OCoLC)41106254**

- Record for CD-ROM serial:

## Example 4: Web site (IR) related to earlier print serial title [1]

- 008    Type: a  BLvl: i  SrTp: **w**   S/L:  **2**
- 006	Type: m  Audn:   File: d   GPub:
- 245 00 Performance practice encyclopedia $h [electronic resource] / $c editor, Roland Jackson.
- 538    Mode of access: World Wide Web.
**580****    ****A continuation of the print journal: Performance practice review.**
**780 10**** ****$t Performance practice review $x 1044-1638 $w (DLC)___89645461_$w (OCoLC)18712767**
- 856 4**0** $u http://www.performancepractice.com/

- Record for Web site:

## Example 4: Web site (IR) related to earlier print serial title [2]

- 008    Type: a   BLvl: **s**
- 245 00 Performance practice review.
- 300    10 v. : $b ill. ; $c 23 cm.
- 362 0  Vol. 1, no. 1, 2 (spring, fall 1988)-v. 10, no. 2 (fall 1997).
**580****    Continued by an online database called: Performance practice encyclopedia.**
**785 10**** $t Performance practice encyclopedia $w(OCoLC)40223351**

- Record for print serial:

## Example 5: Online database related to simultaneously-issued CD-ROM serial and to earlier updating loose-leaf [1]

- 008    Type: a   BLvl: **i  **SrTp:** d**  S/L: 2** **
- 006 	Type: m   Audn:   File: d   GPub: f
- 245 00 USDA national nutrient database for standard reference $h [electronic resource].
- 246 1_ $i Title in HTML header: $a USDA nutrient database for standard reference
- 538    Mode of access: World Wide Web.
**580****    ****Previously issued as a print loose-leaf: Consumer and Food Economics Institute (U.S.). Composition of foods.**
**776 08****  $i Issued also in a CD-ROM version:**** $t USDA nutrient database for standard reference $w (DLC)**_**___**_**00252195_$w (OCoLC)43564113**
**780 10**** ****Consumer and Food Economics Institute (U.S.). $t Composition of foods $w (DLC)**_**___**_**77602784_$w (OCoLC)3913709**
- 856 40 $u http://www.nal.usda.gov/fnic/foodcomp/Data/SR15/sr15.html

- Record for online database:

## 008     Type: a   BLvl: s
245 00  USDA nutrient database for standard reference $h [electronic resource].
300     computer optical discs ; $c 4 3/4 in.
580	 Previously issued as a print loose-leaf: Consumer and Food Economics Institute (U.S.). Composition of foods.
776 08  $i Issued also as an online database: $t USDA national nutrient database for standard reference $w (OCoLC)44340484
780 10  Consumer and Food Economics Institute (U.S.). $t Composition of foods $w (DLC)___77602784_$w (OCoLC)3913709
856 41  $u http://www.nal.usda.gov/fnic/foodcomp/

- 245 00  USDA nutrient database for standard reference $h [electronic resource].
- 300     computer optical discs ; $c 4 3/4 in.
**580****	**** ****Previously issued as a print loose-leaf: Consumer and Food Economics Institute (U.S.). Composition of foods.**
**776 08****  $i Issued also as an online database: ****$t USDA national nutrient database for standard reference $w (OCoLC)44340484**
**780 10****  ****Consumer and Food Economics Institute (U.S.). $t Composition of foods $w (DLC)___77602784_$w (OCoLC)3913709**
- 856 4**1**  $u http://www.nal.usda.gov/fnic/foodcomp/

- Record for CD-ROM serial:

- Example 5: Online database related to simultaneously-issued CD-ROM serial _and_ to earlier updating loose-leaf [2]

## 008     Type: a   BLvl: i   SrTp: l   S/L: 2
110 2   Consumer and Food Economics Institute (U.S.)
245 10  Composition of foods : $b raw, processed, prepared / $c by Consumer and Food Economics Institute.
300     v. (loose-leaf) ; $c 28 cm.
580     Continued by a publication issued on CD-ROM: USDA nutrient database for standard reference, and online via World Wide Web: USDA national nutrient database for standard reference.
785 10  $t USDA nutrient database for standard reference $w (DLC)___00252195_$w (OCoLC)43564113
785 10  $t USDA national nutrient database for standard reference $w (OCoLC)44340484

- 110 2   Consumer and Food Economics Institute (U.S.)
- 245 10  Composition of foods : $b raw, processed, prepared / $c by Consumer and Food Economics Institute.
- 300     v. (loose-leaf) ; $c 28 cm.
**580 ****    ****Continued by a publication issued on CD-ROM: USDA nutrient database for standard reference, and online via World Wide Web: USDA national nutrient database for standard reference.**
**785 10****  ****$t USDA nutrient database for standard reference $w (DLC)___00252195_$w (OCoLC)43564113**
**785 10****  ****$t USDA national nutrient database for standard reference $w (OCoLC)44340484**

- Record for print loose-leaf:

- Example 5: Online database related to simultaneously-issued CD-ROM serial _and_ to earlier updating loose-leaf [3]

## Final records for three examples

- (1) PCC Web Site
- (2) USDA National Nutrient Database
- (3) AACR2 Loose-Leaf

**Notes:**
To conclude the presentation portion of Session 2, before turning to the Exercises, let’s look at the final records for our three examples, given on the following slides.

If time, it is recommended to review all of the elements in bold face type in these records, and any other elements of interest to the instructor and/or participants,

## Final Record for PCC Web Site (1)

**Type: a**   ELvl: I   Srce: d   GPub: f   Ctrl:     Lang: eng
**BLvl: i**   **Form: s**   Conf: 0   Freq:     MRec:     Ctry: dcu
**S/L: 2    Orig: s**   EntW:     Regl: x   Alph:
- Desc: a   **SrTp: w**   Cont:     **DtSt: c   Dates: 199u,9999**
- 006    m d f
**007    c $b r $d m $e n**
- 041 0_ eng $a spa
- 090    Z693.3.C66 $b P76
- 110 2_ Program for Cooperative Cataloging.
- 245 10 Program for Cooperative Cataloging **$h [electronic ****	**** ****	**** resource] **: $b [website].** **
**246 1  $i Commonly known as:** $a PCC
**260**    [Washington, D.C.] : $b Library of Congress
**362 1_ Began in 1990s.**

**Notes:**
Here is the record for the PCC Web site, starting on this slide and continuing onto the following slide.

Besides what has already been explained in previous slides about the elements shown in bold, here a few additional comments:
 This record includes some content and fields that we did not go over in this session but which should be fairly obviously applicable to a complete record for the resource.
 Note the additional language coding in the 041, that agrees with the 546 language note on the next screen.
 Note also the presence of a classification number.
 Note the corporate body main entry.
 Remember that the wording of the 362 1 note could be done differently.

## Final Record for PCC Web Site (2)

**538    Mode of access: World Wide Web. **
- 546    Chiefly English, but some information also
-        available in Spanish.
**500    Title from home page (viewed on Dec. 2, 2002).**
**520**    Contains information about the Program for Cooperative
-        Cataloging, including its governance, organization,
-        strategic plans, online statistics, and archived
-        reports from various PCC groups and meetings. Features
-        links to the home pages of the PCC's component
-        programs: BIBCO, CONSER, NACO, and SACO.
- 610 20 Program for Cooperative Cataloging.
- 650 _0 Cataloging, Cooperative.
- 710 2_ Library of Congress.
**856 40 $u** http://lcweb.loc.gov/catdir/pcc/

**Notes:**
 Here we have a 520 summary note added as well –generally a very important note for most online resources.
 Note also the subject headings,added entry, and 856 field.

## Final Record for Nutrient Database (1)

**Type: a**   ELvl: I   Srce: d   GPub: f   Ctrl:     Lang: eng
**BLvl: i**   **Form: s**   Conf: 0   Freq:     MRec:     Ctry: mdu
**S/L: 2**    **Orig: s**   EntW:     Regl: x   Alph:
- Desc: a   **SrTp: d**   Cont:     **DtSt: c   Dates: 199u,9999**
- 006    m d f
**007    c $b r $d m $e n**
- 245 00 USDA national nutrient database for standard 	 	 reference **$h [electronic resource].**
- 246 1_ $i Title in HTML header: $a USDA nutrient database 	 for standard reference
**260**    Beltsville, MD : $b USDA Nutrient Data Laboratory, 	 Agricultural Research Service
**362 1  Began in 1990s.**
**538    Mode of access: World Wide Web.**
- 516    Searchable database.
**500    Title from home page (viewed Dec. 15, 2002).**

**Notes:**
This first part of the record for the USDA National Nutrient Database is very similar to the previous one for the PCC Web site.

## 520    Offers access to food descriptions, food group data, nutrient information, and a nutrient definition file. Contains a weight file, source code information, and a description of measures used. Posts contact information for the Nutrient Data Laboratory via street address, telephone and fax numbers, and e-mail.
580    Previously issued as a print loose-leaf: Consumer and Food Economics Institute (U.S.). Composition of foods.
650 _0 Food $x Composition $v Databases. 
710 2_ Nutrient Data Laboratory (U.S.) 
776 08 $i Also available on CD-ROM: $t USDA nutrient database for standard reference $w (DLC)___00252195_$w (OCoLC)43564113
780 10 Consumer and Food Economics Institute (U.S.). $t Composition of foods $w (DLC)___77602784_$w (OCoLC)3913709
856 40 $u http://www.nal.usda.gov/fnic/foodcomp/Data/SR15/sr15.html

**580    Previously issued as a print loose-leaf: Consumer and Food Economics Institute (U.S.). Composition of foods.**
- 650 _0 Food $x Composition $v Databases.
- 710 2_ Nutrient Data Laboratory (U.S.)
**776 08 $i ****Also available on CD-ROM:**** $t **USDA nutrient database for standard reference** $w (DLC)___**00252195_**$w (OCoLC)**43564113
**780 10 **Consumer and Food Economics Institute (U.S.).** $t **Composition of foods** $w (DLC)___**77602784_**$w (OCoLC)**3913709
**856 40 $u** http://www.nal.usda.gov/fnic/foodcomp/Data/SR15/sr15.html

- Final Record for Nutrient Database (2)

**Notes:**
 Here again we have a 520 summary note –actually edited from a longer note in the original OCLC record.

 Note the corporate body name as added entry, not main entry.

 The unique and especially noteworthy thing about this resource is its bibliographic relationship to two other resources, expressed as links to the records for those resources.  Can participants explain what these two relationships are?

## Final Record for AACR2 Loose-leaf (1)

**Type: a**   ELvl: I   Srce: d   GPub:     Ctrl:     Lang: eng
**BLvl: i**   **Form:**     Conf: 0   Freq: a   MRec:     Ctry: onc
**S/L: 2**    **Orig:**     EntW:     Regl: r   Alph:
- Desc: a   **SrTp: l**   Cont: b   **DtSt: c   Dates: 2002,9999**
- 020    083893529X (loose-leaf with binder)
- 020    0838935303 (loose-leaf without binder)
- 050 00 Z694.15.A56 $b A53 2002
- 082 00 025.3/2 $2 21
- 245 00 Anglo-American cataloguing rules / $c prepared under the direction of the Joint Steering Committee for Revision of AACR, a committee of the American Library Association ... [et al.].

**Notes:**
The final record for the 2002 revision of AACR2, issued as an updating loose-leaf.

Note, among other things, the presence of ISBNs.

## 245 00 Anglo-American cataloguing rules / $c prepared under the direction of the Joint Steering Committee for Revision of AACR, a committee of the American Library Association ... [et al.].
246 1_ $i Commonly known as: $a AACR2
250    2nd ed., 2002 revision.
260    Ottawa : $b Canadian Library Association ; $a Chicago : $b American Library Association, $c 2002-
300    v. (loose-leaf) ; $c 30 cm.
310    Updated annually
504    Includes bibliographical references and index.
650 _0 Descriptive cataloging $v Rules.
650 _2 Cataloging $v standards.
710 2_ Joint Steering Committee for Revision of AACR.
710 2_ American Library Association. 
780 00 $t Anglo-American cataloguing rules. $b 2nd ed., 1998 revision $w (DLC)___98008479_$w (OCoLC)39281762

**246 1_ $i Commonly known as:** $a AACR2
**250    2nd ed., 2002 revision.**
**260**    Ottawa : $b Canadian Library Association ; $a Chicago : $b American Library Association**, $c 2002-**
**300**    **v. (loose-leaf)** ; $c 30 cm.
**310    Updated annually**
- 504    Includes bibliographical references and index.
- 650 _0 Descriptive cataloging $v Rules.
- 650 _2 Cataloging $v standards.
- 710 2_ Joint Steering Committee for Revision of AACR.
- 710 2_ American Library Association.** **
**780 00 $t Anglo-American cataloguing rules. $b 2nd ed., 1998 revision $w (DLC)___98008479_$w (OCoLC)39281762**

- Final Record for AACR2 Loose-leaf (2)

**Notes:**
 The 245 was repeated on this slide for convenience.

Notice:
 An edition statement.
 Beginning date transcribed from first iteration in 260 $c
 A physical description.
 A 310 frequency of updates note –because frequency is known.
 A 780 link to the earlier edition of the resource