Difference between revisions of "PFAN - Name Authority Manual - MARC 21 Supplement"

From wiki
Jump to navigation Jump to search
Line 1,648: Line 1,648:
 
751 may be supplied in name authority records in the Canadiana Authority File.
 
751 may be supplied in name authority records in the Canadiana Authority File.
  
Consult the Standard Committee before using subfield $1, $4, $g or $i.
+
Consult the Standard Committee before using subfield $g.
  
Do not use subfields: $v, $x, $y, $z, $6, <span style="color:red>$7</span>, $8.
+
Do not use subfields: $v, $x, $y, $z, $6, $7, $8.
  
[2022-12-13]<!--(2022-12-12)-->
+
[2024-02-20]<!--(2024-02-20)-->
 
<br>[[#toc|''Return to Table of Contents'' <big>&#11165;</big>]]
 
<br>[[#toc|''Return to Table of Contents'' <big>&#11165;</big>]]
  

Revision as of 16:36, 20 February 2024

About PFAN News and Updates Rules for Contributions Name Authority Manual Participant's Manual PFAN Policy Statements PFAN Training Frequently Asked Questions (FAQ) Other Documentation LAC
Name Authority Manual    |    Manual - MARC 21 Supplement   |    667 Field Examples   |    008 field : names


Introduction

The PFAN Guidelines for MARC 21 authority records are intended to be used in conjunction with the MARC 21 Format for Authority Data. They were prepared by the Standard Committee and are based on the LC Guidelines Supplement.

Scope of PFAN Guidelines

The PFAN Guidelines present information relating to usage pertaining to records contributed to the authority files by program participants. In some cases, the information present the usage pertaining to authority records created by Library and Archives Canada (LAC). Records include name and series authority records.

Direction for use of PFAN Guidelines

The PFAN Guidelines for authority records should be used by catalogers and institutions participating in PFAN and creating authority records to be added to Canadiana authority files. The guidelines may also be used by institutions that need or want to know special PFAN practice in authority records. As already mentioned, these guidelines are intended to be used in conjunction with the MARC 21 Format for Authority Data. Data requirements that are not specific to PFAN are presented only in the main text of the authorities format.

PFAN participants creating authority records must also apply the appropriate procedures presented elsewhere on the wiki (e.g., the Name Authority Manual).

[2021-01-11]
Return to Table of Contents

Leader

Leader/05 Record status

PFAN

Do not use codes: a, d, o, s, x.

If PFAN participants identifie an authority record that should be deleted from Canadiana, they must consult LAC at [1] to have the record deleted. PFAN participants are not permitted to delete a record from the Canadiana file.

[2021-01-07]

Return to Table of Contents

Leader/09 Character coding scheme

PFAN

Do not use codes: a.

[2021-01-07]

Return to Table of Contents

Leader/17 Encoding level

PFAN

Consult the Standards Committee before using code “o”.

[2021-01-07]

Return to Table of Contents

Leader/18 Punctuation Policy

PFAN

Do not use codes:  c, i, u. Implementation decision not yet made.

[2021-01-07]

Return to Table of Contents

Directory

PFAN

The Directory is always system generated.

[2021-01-07]
Return to Table of Contents

001 Control Number

PFAN

The control number is system generated. It begins with prefix “ncf”.

[2021-01-07]
Return to Table of Contents

005 Date and Time of Latest Transaction

PFAN

005 field is system generated.

[2021-01-07]
Return to Table of Contents

008 Fixed-Length Data Elements

008/00-05 Date Entered on File

PFAN

The date entered on file is generated by WMS. Do not use the fill character.

[2021-01-07]
Return to Table of Contents

008/06 Direct or Indirect Subdivision

PFAN

Generally use code “n”. Certain corporate names (110), such as religions or religious orders, used as subject access points may be subdivided by place; such corporate names may use code “i” in byte 008/06. Consult the LC Subject Cataloging Manual instruction sheet H 475 for a list of these corporate bodies.

[2021-01-07]
Return to Table of Contents

008/07 Romanization Scheme

PFAN

Always use the fill character.

[2021-01-07]
Return to Table of Contents

008/08 Language of Catalog

PFAN

Always use code “f”. (Note: Code “e” is used in CSH records.)

[2021-01-07]
Return to Table of Contents

008/09 Kind of Record

PFAN

Consult the Standards Committee before using code “b” in a reference record containing a 666 general explanatory reference field.

Do not use codes: d, e, f, g, fill character.

[2021-01-07]
Return to Table of Contents

008/10 Descriptive Cataloging Rules

PFAN

For newly created name/series authority records code “z” is the only value used. When existing NARs using codes “a”, “b”, “c”, or “d” are modified in any way, they are re-coded to RDA and the 008/10 code is changed accordingly. Exceptions to this guideline are found in the Descriptive Cataloging Manual Z1 008/10 section.

Do not use codes: a, b, d, n, fill character.

[2021-01-07]
Return to Table of Contents  |  Manual

008/11 Subject Heading System/Thesaurus

PFAN

Use code “n” in reference records (008/09, Kind of record, code “b” or “c”.) and in records when the 1XX is not appropriate for use as a subject heading. Do not use codes: b, c, d, k, r, s, v, z, fill character. (Note: Code “k” is used in CSH records).

[2021-01-07]
Return to Table of Contents  |  Manual

008/12 Type of Series

PFAN

Do not use codes: fill character.

[2021-01-07]
Return to Table of Contents

008/13 Numbered or Unnumbered Series

PFAN

Do not use codes: fill character.

[2021-01-07]
Return to Table of Contents

008/14 Heading Use-Main or Added Entry

PFAN

Consult the Standards Committee before using code “b” in a reference record that contains either field 664 (Complex See Reference-Name) or field 666 (General Explanatory Reference–Name).

Do not use codes: fill character.

[2021-01-07]
Return to Table of Contents

008/15 Heading Use-Subject Added Entry

PFAN

Do not use codes: fill character.

[2021-01-07]
Return to Table of Contents  |  Manual

008/16 Heading use-series added entry

PFAN

Do not use codes: fill character.

[2021-01-07]
Return to Table of Contents

008/17 Type of subject subdivision

PFAN

Always use code “n”.

Do not use codes: a, b, c, d, e, fill character.

[2021-01-07]
Return to Table of Contents

008/18-27 Undefined character positions

PFAN

Do not use the fill character in these undefined character positions. These positions should contain blanks.

[2021-01-07]
Return to Table of Contents

008/28 Type of government agency

PFAN

There are no special requirements for this character position. Use the appropriate code or the fill character.

[2022-11-10]
Return to Table of Contents

008/29 Reference evaluation

PFAN

Do not use codes: fill character.

It is possible that code “b” may occur in records and will continue to exist until any records containing reference tracings have been evaluated and the authority record updated. Code “b” will also occur in all name/series records with non-Latin script references until guidelines for evaluating non-Latin script references are developed.

When code ”b” is used in this latter case assure that a 667 note with one of these statements is also present in the NAR: • Le renvoi en écriture non latine n'a pas été évalué. • Les renvois en écriture non latine n'ont pas été évalués.

[2021-01-07]
Return to Table of Contents

008/30 Undefined character position

PFAN

Do not use the fill character in this undefined character position. This position should contain blank.

[2021-01-08]
Return to Table of Contents

008/31 Record update in process

PFAN

There are no special requirements for this character position. Note: Follow PFAN procedures for updating existing name authority records.

Do not use codes: fill character.

[2021-01-08]
Return to Table of Contents

008/32 Undifferentiated personal name

PFAN

Do not use codes: fill character.

[2021-01-08]
Return to Table of Contents  |  Manual

008/33 Level of establishment

PFAN

Consult the Standards Committee before using code “d”.

Do not use codes: fill character.

[2021-01-08]
Return to Table of Contents  |  Manual

008/34-37 Undefined character positions

PFAN

Do not use the fill character in these undefined character positions. These positions should contain blanks.

[2021-01-08]
Return to Table of Contents

008/38 Modified record

PFAN

Always use blank.

[2021-01-08]
Return to Table of Contents

008/39 Cataloging source

PFAN

National bibliographic agencies use blank; other PFAN participants use code “c”.

Do not use codes: d, u, fill character.

[2021-01-08]
Return to Table of Contents  |  Manual

010 Library of Congress Control Number

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents  |  Manual

014 Link to Bibliographic Record for Serial or Multipart

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents

016 National Bibliographic Agency Control Number

PFAN

This field 016 is mandatory when cataloguer create, update or use an authority.

Do not use subfields: $8.

[2021-01-08]
Return to Table of Contents  |  Manual

020 International Standard Book Number

PFAN

Cataloguers may supply the 020 field in series authority records for multipart items at their own discretion. There are no further guidelines for the field.

Do not use subfields: $6, $8.

[2021-01-08]
Return to Table of Contents

022 International Standard Serial Number

PFAN

Use this field in series authority records only.

Do not use subfields: $y, $z, $6, $8.

Do not use subfields (implementation decision not yet made): $0, $1

[2022-04-19]
Return to Table of Contents  |  Manual

024 Other Standard Identifier

PFAN

Do not use subfields: $c, $d, $q, $z, $6, $7, $8.

[2022-12-12]
Return to Table of Contents  |  Manual

031 Musical Incipits Information

PFAN

Do not use subfields: $6, $8

[2021-01-08]
Return to Table of Contents

034 Coded Carographic Mathematical Data

PFAN

PFAN participants may supply the 034 field in authority records for geographic name headings (151) only at their own discretion.

Do not use subfields: $6, $7, $8.

[2024-02-20]
Return to Table of Contents  |  Manual

035 System Control Number

PFAN

Do not use subfields: $6, $8.

[2021-01-08]
Return to Table of Contents  |  Manual

040 Cataloging Source

PFAN

Do not use subfields: $f, $6, $8.

[2021-01-08]
Return to Table of Contents  |  Manual

042 Authentication Code

PFAN

Do not use this field.

LAC

LAC cataloguers have to supply this field.

[2021-01-08]
Return to Table of Contents  |  Manual

043 Geographic Area Code

PFAN

PFAN participants may supply the 043 field in authority records for geographic name headings (151) only at their own discretion.

Do not use subfields: $6, $7, $8.

[2024-02-20]
Return to Table of Contents

045 Time Period of Heading

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents

046 Special Coded Dates

PFAN

046 may be supplied in name/series authority records in Canadiana Authority File.

Do not use subfields: $6, $8.

Do not use subfields (implementation decision not yet made): $x, $z, $3

[2022-04-19]
Return to Table of Contents  |  Manual

050 Library of Congress Call Number

PFAN

Do not use this field. Use 055 field.

[2021-01-08]
Return to Table of Contents  |  Manual

052 Geographic Classification

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents

053 LC Classification Number

PFAN

PFAN participants may use this field to record an LC classification number for a literary author. Always use second indicator value 4.

Do not use subfields: $6, $8.

[2024-02-20]
Return to Table of Contents  |  Manual

055 Library and Archives Canada Call Number

PFAN

Use only this field in series authority records. Always use second indicator value 4.

Do not use subfields: $6, $8.

LAC

Use only this field in series authority records. Always use second indicator value 0.

Do not use subfields: $6, $8.

[2021-01-08]
Return to Table of Contents  |  Manual

060 National Library of Medicine Call Number

PFAN

Do not use subfields: $6, $8.

[2024-02-20]
Return to Table of Contents

065 Other Classification Number

PFAN

PFAN cataloguers may supply this field in a personal name heading. Its use is limited to classification numbers in the PS8000 schedule for Canadian literature.

Do not use subfields: $6, $7, $8.

[2022-12-13]
Return to Table of Contents  |  Manual

066 Character Sets Present

PFAN

Do not use this field. Alternate graphic representation fields are not within the scope of the present PFAN program.

[2021-01-08]
Return to Table of Contents

070 National Agricultural Library Call Number

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents

072 Subject Category Code

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents

073 Subdivision Usage

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents

075 Type of Entity

PFAN

Consult the Standards Committee before using field 075.

[2021-01-08]
Return to Table of Contents

080 Universal Decimal Classification Number

PFAN

PFAN participants may supply the 080 field in series authority records for multipart items at their own discretion.

Do not use subfields: $6, $8.

[2024-02-20]
Return to Table of Contents  |  Manual

082 Dewey Decimal Call Number

PFAN

Use only this field in series authority records.

Do not use subfields: $6, $8.

[2021-01-08]
Return to Table of Contents  |  Manual

083 Dewey Decimal Classification Number

PFAN

PFAN participants may supply this field to record a Dewey classification number for a literary author.

Do not use subfields: $6, $8.

[2021-01-08]
Return to Table of Contents  |  Manual

086 Government Document Call Number

PFAN

Use only this field in series authority records.

[2021-01-08]
Return to Table of Contents  |  Manual

087 Government Document Classification Number

PFAN

PFAN participants may supply field 087 in name/series authority records at their own discretion.

Do not use subfields: $6, $8.

[2024-02-20]
Return to Table of Contents  |  Manual

100 Heading-Personal Name

PFAN

Use first indicator value 3 in name authority/series records when creating RDA authorized access points for family names.

Do not use subfields: $e, $j, $v, $x, $y, $z, $6, $7, $8.

[2022-12-13]
Return to Table of Contents  |  Manual

110 Heading-Corporate Name

PFAN

Do not use subfields: $e, $v, $x, $y, $z, $6, $7, $8.

[2022-12-13]
Return to Table of Contents

111 Heading-Meeting Name

PFAN

Do not use subfields: $g, $j, $v, $x, $y, $z, $6, $7, $8.

[2022-12-13]
Return to Table of Contents

130 Heading-Uniform Title

PFAN

Always use second indicator value 0. Omit an initial article that is not an integral part of the uniform title when formulating the entry element of the heading.

Do not use subfields: $g, $v, $x, $y, $z, $6, $7, $8.

[2022-12-13]
Return to Table of Contents

147 Heading-Named Event

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents

148 Heading-Chronological Term

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents

150 Heading-Topical Term

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents

151 Heading-Geographic Name

PFAN

Do not use subfields: $g, $v, $x, $y, $z, $6, $7, $8.

[2022-12-13]
Return to Table of Contents

155 Heading-Genre/Form Term

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents

162 Heading-Medium of Performance Term

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents

180 Heading-General Subdivision

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents

181 Heading-Geographic Subdivision

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents

182 Heading-Chronological Subdivision

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents

185 Heading-Form Subdivision

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents

260 Complex See Reference-Subject

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents

335 Extension Plan [New]

PFAN

Consult the Standards Committee before uthis field.

[2022-04-19]
Return to Table of Contents  |  Manual

336 Content Type

PFAN

Field 336 may be supplied in name/series authority records in Canadiana Authority File.

Do not use subfields: $3, $6, $7, $8.

[2024-02-20]
Return to Table of Contents  |  Manual

348 Format of Notated Music

PFAN

Consult the Standard Committee before using field 348.

[2021-01-08]
Return to Table of Contents

360 Complex See Also Reference-Subject

PFAN

Do not use this field.

[2021-01-08]
Return to Table of Contents

368 Other Attributes of Person or Corporate Body

PFAN

Field 368 may be supplied in name authority records in Canadiana Authority File.

Do not use subfields: $6, $7, $8.

[2024-02-20]
Return to Table of Contents  |  Manual

370 Associated Place

PFAN

Field 370 may be supplied in name/series authority records in Canadiana Authority File.

Do not use subfields: $6, $7, $8.

[2024-02-20]
Return to Table of Contents  |  Manual

371 Address

PFAN

Field 371 may be supplied in name authority records in Canadiana Authority File.

Do not use subfields: $4, $6, $7, $8.

[2022-12-13]
Return to Table of Contents  |  Manual

372 Field of Activity

PFAN

Field 372 may be supplied in name authority records in the Canadiana Authority File.

Do not use subfields: $6, $7, $8.

[2024-02-20]
Return to Table of Contents  |  Manual

373 Associated Group

PFAN

Field 373 may be supplied in name authority records in the Canadiana Authority File.

Do not use subfields: $6, $7, $8

[2024-02-20]
Return to Table of Contents  |  Manual

374 Occupation

PFAN

Field 374 may be supplied in name authority records in the Canadiana Authority File.

Do not use subfields: $6, $7, $8.

[2024-02-20]
Return to Table of Contents  |  Manual

375 Gender

PFAN

Do not use this field.

This field may be found in older records. Whenever an existing record must be changed for any reason, delete any occurrence of field 375.

[2023-10-20)
Return to Table of Contents  |  Manual  |  Participant's Manual

376 Family Information

PFAN

Field 376 may be supplied in name authority records in the Canadiana Authority File.

Do not use subfields: $6, $7, $8.

[2024-02-20]
Return to Table of Contents  |  Manual

377 Associated Language

PFAN

Field 377 may be supplied in name/series authority records in the Canadiana Authority File.

Do not use subfields: $6, $7, $8.

[2024-02-20]
Return to Table of Contents  |  Manual

378 Fuller Form of Personal Name

PFAN

Field 378 may be supplied in name authority records in the Canadiana Authority File.

Do not use subfields: $6, $7, $8.

[2022-12-13]


Return to Table of Contents  |  Manual

380 Form of Work

PFAN

Field 380 may be supplied in name/series authority records in the Canadiana Authority File.

Do not use subfields: $6, $7, $8.

[2024-02-20]
Return to Table of Contents  |  Manual

381 Other Distinguishing Characteristics of Work or Expression

PFAN

Field 381 may be supplied in name/series authority records in the Canadiana Authority File.

Do not use subfields: $6, $7, $8.

[2024-02-20]
Return to Table of Contents  |  Manual

382 Medium of Performance

PFAN

Field 382 may be supplied in name/series authority records in the Canadiana Authority File.

Do not use first indicator values 2 or 3 (implementation decision not yet made).

Do not use subfields: $6, $7, $8.

[2024-02-20]
Return to Table of Contents  |  Manual

383 Numeric Designation of Musical Work

PFAN

Field 383 may be supplied in name authority records in the Canadiana Authority File.

Do not use subfields: $6, $7, $8.

[2022-12-13]
Return to Table of Contents  |  Manual

384 Key

PFAN

Field 384 may be supplied in name authority records in the Canadiana Authority File.

Do not use first indicator value 2 (implementation decision not yet made).

Do not use subfields: $6, $7, $8.

[2024-02-20]
Return to Table of Contents  |  Manual

385 Audience Characteristics

PFAN

Field 385 may be supplied in name/series authority records in the Canadiana Authority File.

Do not use subfields: $m, $n, $6, $7, $8.

Subfields $n and $m may occur in records created prior to August 2021.

[2024-02-20]
Return to Table of Contents  |  Manual

386 Creator/Contributor Characteristics

PFAN

Field 386 may be supplied in name/series authority records in the Canadiana Authority File.

Do not use subfields: $m, $n, $6, $7, $8.

Subfields $n and $m may occur in records created prior to August 2021.

[2024-02-20]
Return to Table of Contents  |  Manual

388 Time Period of Creation

PFAN

Field 388 may be supplied in name/series authority records in the Canadiana Authority File.

Do not use subfields: $6, $7, $8.

[2024-02-20]
Return to Table of Contents

4XX Fields Tracings and References - General Information

PFAN

Subfield Codes

Do not use subfield $i, $4 or subfield $w code "r" in 4XX fields.


$w - Control subfield in 4XX See From Tracing

____/0 Special relationship

Use code "n" (Not applicable) when a subsequent character position in subfield $w is coded.

Do not use the following codes:

a - Earlier heading

b - Later heading

d - Acronym

f - Musical composition

g - Broader term

h - Narrower term

i - Reference instruction phrase in subfield $i

r - Relationship information in subfield $i ou $4

t - Immediate parent body


____/1 Tracing use restriction

Use code "n" (Not applicable) when a subsequent character position in subfield $w is coded.

Do not use the following codes:

a - Name reference structure only

b - Subject reference structure only

c - Series reference structure only

d - Name and subject reference structures

e - Name and series reference structures

f - Subject and series reference structures

g - Name, subject, and series reference structures


____/2 Earlier form of heading

Use code "n" (Not applicable) when neither code "a" nor code "e" applies and a subsequent character position in subfield $w is coded.

Use code a (Pre-AACR 2 form of heading (national name authority file)) when the tracing is for a linking reference from a pre-AACR 2 heading.

Use code e (Earlier established form of heading (national authority file)) in Canadiana primarily when a reference from the former heading is appropriate. This includes former headings where code "c" or code "d" were used. Do not automatically make a reference from the former heading in order to supply code "e".

The following obsolete codes may appear in Canadiana records created before the adoption of AACR 2 in January 1981 until these records have been evaluated (008/29, Reference evaluation is changed to code "a") and the authority record updated.

b - AACR 1 [OBSOLETE]

c - AACR 2 [OBSOLETE]

d - Non-AACR 2 form used with AACR 2 [OBSOLETE]


____/3 Reference display

Code "n" (Not applicable) allows the generation of a cross reference display and need not be coded in subfield $w/3.

Do not use the following codes:

b - Reference not displayed, field 664 used

c - Reference not displayed, field 663 used

d - Reference not displayed, field 665 used

if these fields or code "d" or "b" are found in 4XXs upgrade the NAR to the current practice. Use code "a" (Reference not displayed)when appropriate for suppressing a cross reference display.

[2022-04-19]
Return to Table of Contents  |  Manual

400 See From Tracing - Personal Name

PFAN

Use first indicator value 3 in RDA name and series authority records when providing variant forms of family names.

Do not use subfields: $e, $i, $j, $v, $x, $y, $z, $4, $5, $6, $7, $8.

PFAN usage for subfield $w is given in the section for Tracings and References-General Information-4XX fields.

[2022-12-13]
Return to Table of Contents

410 See From Tracing - Corporate Name

PFAN

Do not use subfields: $e, $i, $v, $x, $y, $z, $4, $5, $6, $7, $8.

PFAN usage for subfield $w is given in the section for Tracings and References-General Information-4XX fields.

[2022-12-13]
Return to Table of Contents

411 See From Tracing - Meeting Name

PFAN

Do not use subfields: $g, $i, $j, $v, $x, $y, $z, $4, $5, $6, $7 $8.

PFAN usage for subfield $w is given in the section for Tracings and References-General Information-4XX fields.

[2022-12-13]
Return to Table of Contents

430 See From Tracing - Uniform Title

PFAN

Always use second indicator value 0. Omit an initial article that is not an integral part of the uniform title when formulating the entry element of the reference.

Do not use subfields: $i, $v, $x, $y, $z, $4, $5, $6, $7, $8.

PFAN usage for subfield $w is given in the section for Tracings and References-General Information-4XX fields.

[2022-12-13]
Return to Table of Contents

447 See From Tracing - Named Event

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents  |  Manual

448 See From Tracing-Chronological Term

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

450 See From Tracing-Topical Term

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

451 See From Tracing-Geographic Name

PFAN

Do not use subfields: $g, $i, $v, $x, $y, $z, $4, $5, $6, $7, $8.

PFAN usage for subfield $w is given in the section for Tracings and References-General Information-4XX fields.

[2022-12-13]
Return to Table of Contents

455 See From Tracing-Genre/Form Term

PFAN

Do not use this field.

[2021-01-11] br>Return to Table of Contents

462 See From Tracing-Medium of Performance Term

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

480 See From Tracing-General Subdivision

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

481 See From Tracing-Geographic Subdivision

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

482 See From Tracing-Chronological Subdivision

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

485 See From Tracing-Form Subdivision

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

5XX Fields Tracing and References - General Information

PFAN

Subfield Codes:

$i – Relationship information

This subfield may be used in either AACR2 or RDA NARs to indicate relationships between authorized access points.

$4 – Relationship

Consult the Standard Committee Division before using this subfield.


$w - Control subfield in 5XX See Also Tracing fields

____/0 Special relationship

Use code "n" (Not applicable) when neither code "a" nor "b" nor "r" applies and a subsequent character position in subfield $w is coded.

r – must be used when subfield $i or $4 are used in NARs

Do not use the following codes:

d - Acronym

f - Musical composition

h - Narrower term

i - Reference instruction phrase in subfield $i

t - Immediate parent body


____/1 Tracing use restriction

Use code "n" (Not applicable) when a subsequent character position in subfield $w is coded.

Do not use the following codes:

a - Name reference structure only

b - Subject reference structure only

c - Series reference structure only

d - Name and subject reference structures

e - Name and series reference structures

f - Subject and series reference structures

g - Name, subject, and series reference structures


____/2 Earlier form of heading

Use code "n" (Not applicable) when a subsequent character position in subfield $w is coded.

Do not use the following codes:

a - Pre-AACR 2 form of heading (national name authority file)

e - Earlier established form of heading (national authority file)

o - Earlier established form of heading (other authority file)


____/3 Reference display

Code "n" (Not applicable) allows the generation of a cross reference and need not be coded in subfield $w/3.

Do not use the following codes:

b - Reference not displayed, field 664 used

d - Reference not displayed, field 665 used

Use code "a" (Reference not displayed) or "c" (Reference not displayed, field 663 used) when appropriate for suppressing a cross reference display.

[2022-04-19]
Return to Table of Contents  |  Manual

500 See Also From Tracing-Personal Name

PFAN

Use first indicator value 3 in RDA name and series authority records when providing relationship links to and from family names.

Consult the Standard committee before using subfield $4.

Do not use subfields: $e, $j, $v, $x, $y, $z, $5, $6, $7, $8.

PFAN usage for subfield $w is given in the Supplement section for Tracings and References-General Information-5XX fields.

[2024-02-20]
Return to Table of Contents  |  Manual

510 See Also From Tracing-Corporate Name

PFAN

Consult the Standard Committee before using subfield $4.

Do not use subfields: $e, $v, $x, $y, $z, $5, $6, $7, $8.

PFAN usage for subfield $w is given in the Supplement section for Tracings and References-General Information-5XX fields.

[2024-02-20]
Return to Table of Contents  |  Manual

511 See Also From Tracing-Meeting Name

PFAN

Consult the Standard Committee before using subfield $4.

Do not use subfields: $g, $j, $v, $x, $y, $z, $5, $6, $7, $8.

PFAN usage for subfield $w is given in the Supplement section for Tracings and References-General Information-5XX fields.

[2024-02-20]
Return to Table of Contents  |  Manual

530 See Also From Tracing-Uniform Title

PFAN

Always use second indicator value 0. Omit an initial article that is not an integral part of the uniform title when formulating the entry element of the reference.

Consult the Standard Committee before using subfield $4.

Do not use subfields: $g, $v, $x, $y, $z, $5, $6, $7, $8.

PFAN usage for subfield $w is given in the Supplement section for Tracings and References-General Information-5XX fields.

[2024-02-20]
Return to Table of Contents  |  Manual

547 See Also From Tracing-Named Event

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

548 See Also From Tracing-Chronological Term

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

550 See Also From Tracing-Topical Term

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

551 See Also From Tracing-Geographic Name

PFAN

Consult the Standard Committee before using subfield $4.

Do not use subfields: $g, $v, $x, $y, $z, $5, $6, $7, $8.

PFAN usage for subfield $w is given in the Supplement section for Tracings and References-General Information-5XX fields.

[2024-02-20]
Return to Table of Contents  |  Manual

555 See Also From Tracing-Genre/Form Term

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

562 See Also From Tracing-Medium of Performance Term

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

580 See Also From Tracing-General Subdivision

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

581 See Also From Tracing-Geographic Subdivision

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

582 See Also From Tracing-Chronological Subdivision

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

585 See From Tracing-Form Subdivision

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

640 Series Dates of Publication and/or Sequential Designation

PFAN

Use this field in Series authority records only.

Always use first indicator value 1.

Do not use subfields: $6, $8.

[2021-01-11]
Return to Table of Contents  |  Manual

641 Series Numbering Peculiarities

PFAN

Use this field in Series authority records only.

Do not use subfields: $6, $8.

[2021-01-11]
Return to Table of Contents  |  Manual

642 Series Numbering Example

PFAN

Use this field in Series authority records only.

Do not use subfields: $6, $8.

[2021-01-11]
Return to Table of Contents  |  Manual

643 Series Place and Publisher/Issuing Body

PFAN

Use this field in Series authority records only.

Do not use subfields: $6, $8.

[2021-01-11]
Return to Table of Contents  |  Manual

644 Series Analysis Practice

PFAN

Use this field in Series authority records only.

Do not use subfields: $6, $8.

[2021-01-11]
Return to Table of Contents  |  Manual

645 Series Tracing Practice

PFAN

Use this field in Series authority records only.

Do not use subfields: $6, $8.

[2021-01-11]
Return to Table of Contents  |  Manual

646 Series Classification Practice

PFAN

Use this field in Series authority records only.

Do not use subfields: $6, $8.

[2021-01-11]
Return to Table of Contents  |  Manual

663 Complex See Also Reference-Name

PFAN

Prefer simple cross references to complex cross references. Use field 663 only when the relationship of other names to the name contained in the 1XX Heading cannot be adequately expressed by simple see also cross references constructed from field 1XX and multiple 5XX See Also From Tracing fields.

Do not use subfields: $6, $8.

[2021-01-11]
Return to Table of Contents  |  Manual

664 Complex See Reference-Name

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

665 History Reference

PFAN

Do not use this field.

Connect related headings with 5XX (See Also From Tracing) fields containing subfield $w position 0 (Special relationship) appropriately coded.

This field may be found in older records. Whenever a record must be changed for any reason, delete any occurrence of field 665 and add or adjust the 5XX fields to accommodate the information originally recorded in field 665.

[2021-01-11]
Return to Table of Contents  |  Manual

666 General Explanatory Reference-Name

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

667 Nonpublic General Note

PFAN

Do not use subfields: $5, $6, $8.

[2021-01-11]
Return to Table of Contents  |  Manual

670 Source Data Found

PFAN

Consult the Standard Committee before using subfield $w.

Do not use subfields: $6, $7, $8.

[2022-12-13]
Return to Table of Contents  |  Manual

672 Title Related to the Entity

PFAN

Field 672 may be supplied in name authority records in the Canadiana Authority File.

Do not use subfields: $6, $7, $8.

[2024-02-20]
Return to Table of Contents  |  Manual

673 Title Not Related to the Entity

PFAN

Field 673 may be supplied in name authority records in the Canadiana Authority File.

Do not use subfields: $6, $8.

[2024-02-20]
Return to Table of Contents  |  Manual

675 Source Data Not Found

PFAN

Do not use subfields: $6, $7, $8.

[2022-12-13]
Return to Table of Contents  |  Manual

677 Definition

PFAN

Do not use this field. [2021-01-11]
Return to Table of Contents

678 Biographical or Historical Data

PFAN

678 may be supplied in name authority records in the Canadiana Authority File.

Do not use subfields: $6, $7, $8.

[2022-12-13]
Return to Table of Contents  |  Manual

680 Public General Note

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

681 Subject Example Tracing Note

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

682 Deleted Heading Information

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

688 Application History Note

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

700 Established Heading Linking Entry-Personal Name

PFAN

700 may be supplied in name authority records in the Canadiana Authority File.

Do not use subfields: $v, $x, $y, $z, $6, $7, $8.

[2024-02-20]
Return to Table of Contents

710 Established Heading Linking Entry-Corporate Name

PFAN

710 may be supplied in name authority records in the Canadiana Authority File.

Do not use subfields: $v, $x, $y, $z, $6, $7, $8.

[2024-02-20]
Return to Table of Contents

711 Established Heading Linking Entry-Meeting Name

PFAN

711 may be supplied in name authority records in the Canadiana Authority File.

Do not use subfields: $v, $x, $y, $z, $6, $7, $8.

[2024-02-20]
Return to Table of Contents

730 Established Heading Linking Entry-Uniform Title

PFAN

730 may be supplied in name authority records in the Canadiana Authority File.

Do not use subfields: $v, $x, $y, $z, $6, $7, $8.

[2024-02-20]
Return to Table of Contents

747 Established Heading Linking Entry-Named Event

PFAN

Consult the Standard Committee before using this field.

Do not use subfields: $6, $7, $8.

[2022-12-13]
Return to Table of Contents

748 Established Heading Linking Entry-Chronological Term

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

750 Established Heading Linking Entry-Topical Term

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

751 Established Heading Linking Entry-Geographic Name

PFAN

751 may be supplied in name authority records in the Canadiana Authority File.

Consult the Standard Committee before using subfield $g.

Do not use subfields: $v, $x, $y, $z, $6, $7, $8.

[2024-02-20]
Return to Table of Contents

755 Established Heading Linking Entry-Genre/Form Term

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

762 Established Heading Linking Entry-Medium of Performance Term

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

780 Subdivision Heading Linking Entry-General Subdivision

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

781 Subdivision Heading Linking Entry-Geographic Subdivision

PFAN

PFAN participants may provide a 781 field in a name authority record for a geographic heading (151) that may also be used as a geographic subdivision. Always use second indicator value 6.

Consult the Standard Committee before using subfield $1, $4 or $i.

Do not use subfields: $v, $w, $x, $y, $0, $2, $5, $6, $7, $8.

[2022-12-13]
Return to Table of Contents  |  Manual

782 Subdivision Heading Linking Entry-Chronological Subdivision

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

785 Subdivision Heading Linking Entry-Form Subdivision

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

788 Complex Linking Entry Data

PFAN

Do not use this field. [2021-01-11]
Return to Table of Contents

856 Electronic Location and Access

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

880 Alternate Graphic Representation

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

883 Metadata Provenance

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

884 Description Conversion Information

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents

885 Matching Information

PFAN

Do not use this field.

[2021-01-11]
Return to Table of Contents