DCM Z1:  667  Nonpublic General Note

LC series practice:  As of June 1, 2006, LC does not create or update SARs.

PCC series practice:  Transcription of the series statement is mandatory if applicable.  Searching for series authority records, tracing the series, and the creation and maintenance of series authority records are optional.

General:

Give information of permanent value and general interest that would be useful also to institutions outside of LC and to LC staff not working in the LC Database.  A representative listing of notes is given below.  Generally, wording is recommended but not prescriptive unless specified in the instructions.  The separate 667 fields may be given in any order.

Examples:

667  ##  $a Not same as:  [name or title, LCCN].

667  ##  $a Cannot identify with:  [name or title, LCCN].

667  ##  $a Reinvestigate before using again.

667  ##  $a Formerly on undifferentiated name record:  [LCCN of undifferentiated name record].

667  ##  $a Coded provisional because [reason for coding].

667  ##  $a Date of birth removed from all fields per author request, [date updated].

667  ##  $a For works issued before/after [date].

[To be used for official language changes.]

NARs for persons with identities not established:

Generally, for contemporary authors with two or more identities, name authority records are created for each name, including in some cases the possible unused real name.  In the interest of efficiency, if research indicates that a person has numerous pseudonyms that are not likely to appear on separately published works, LC/PCC catalogers may choose not to create separate authority records for each pseudonym.  In this case, list in the 670 field all the known pseudonyms; list the unestablished pseudonyms in a 667 field following the phrase:  "Pseudonyms not found on published works."

Example:

667  ##  $a Pseudonyms not found on published works: Miz Scarlett, SCC, and Stevenopolis.

NOTE:  Do not make references from the unestablished pseudonyms.

More information on creating NARs for persons with alternate identities is found in the FAQ - LC/PCC RDA and AACR2 Practice for Creating NARs for Persons Who Use Pseudonyms available at:  http://www.loc.gov/catdir/cpso/pseud.pdf.

NARs for series of conferences, etc.  (LC-PCC PS 11.13.1.8.2):

When creating an authority record for the collective conference, do not add the numbers and/or dates to the authorized access point.  Include a 667 field when there are authority records for both collective and individual instances of an ongoing conference.

Example:

667  ##  $a See also related access points for individual instances of this conference which include specific information about the number, date, or place of the individual conference.

NARs and subject usage:

Follow these guidelines for newly-created authority records.  Revise existing records when making any other change to the records.

1.   Notes indicating subject cataloging usage when an authorized access point is not appropriate for use as a subject entry:

a.   Heads of state, etc.

Add a 667 note indicating subject cataloging usage to name authority records for corporate names representing the office held for Heads of state, Heads of governments, etc. (RDA 11.2.2.18), International intergovernmental bodies (RDA 11.2.2.18.3), Governors of dependent or occupied territories (RDA 11.2.2.18.4), and Religious officials (RDA 11.2.2.26) when the name of the incumbent is included as part of the authorized access point.

667  ##  $a SUBJECT USAGE: This name is not valid for use as a subject. Works about this person are entered under [personal name heading].

Assign value "n" in 008/11 and value "b" in 008/15.

Examples:

008/11  =  n

008/15  =  b

110  1#  $a United States. $b President (1923-1929 : Coolidge)

667  ##  $a SUBJECT USAGE: This name is not valid for use as a subject.  Works about this person are entered under Coolidge, Calvin, 1872-1933.

008/11  =  n

008/15  =  b

110  2#  $a Catholic Church. $b Pope (1503-1513 : Julius II)

667  ##  $a SUBJECT USAGE: This name is not valid for use as a subject. Works about this person are entered under Julius II, Pope, 1443-1513.

See also DCM Z1 008/11 and DCM Z1 008/15.

b.   Earlier/later linear jurisdictional name changes

It is LC subject cataloging policy to assign as a subject access point or as a geographic subdivision only the latest name of a political jurisdiction that has had one or more earlier names, as long as the territorial identity remains essentially unchanged (cf. SHM H 708).  Upon creating an earlier/later authorized access point for a geographic name, catalogers must add a 667 subject usage note to the earlier name and adjust the appropriate 008 fields (008/11 and 008/15).

Example:

008/11  =  n

008/15  =  b

151  ##  $a Ceylon

667  ##  $a SUBJECT USAGE: This name is not valid for use as a subject. Works about this place are entered under Sri Lanka.

2.   Notes indicating that authorized access points for names of a city section, neighborhood, district, etc, are not appropriate for use as a geographic subdivision:

LC/PCC practice:  Add a 667 note to name authority records for geographic names that are not appropriate for use as geographic subdivisions in subject cataloging usage (per SHM H 835) when the name represents an entity within a city and is qualified by the city name.  Do not add a 781 field.

667  ##  $a SUBJECT USAGE: This name is not valid for use as a geographic subdivision.

Example:

151  ##  $a Hollywood (Los Angeles, Calif.)

667  ##  $a SUBJECT USAGE: This name is not valid for use as a geographic subdivision.

LC subject catalogers may optionally send a message to PSD policy@loc.gov and ask to have the NAR updated.

Non-Latin script reference notes:

In an authority record that contains non-Latin script variant access points use the 667 field with a note stating:  "Non-Latin script reference not evaluated."  If there are several non-Latin script variant access points, the sentence may be modified to reflect that condition.  Assure that 008/29 is set to "b" to indicate that the variant access point is not evaluated.

Example:

008/29  =  b

100  1#  $a Xi, Jinping

400  1#  $a

400  1#  $a

667  ##  $a Non-Latin script references not evaluated.

MESSAGE notes  (LC-practice):

Use a note in the 667 field to indicate that an authority record is not yet finished or that it needs further investigation.  Use the notes only when the work cannot be completed promptly.

If a new authority record cannot be completed immediately, adjust the code in LDR/17 from "n" to "o" and add a 667 note:  "MESSAGE:  Early notice."  When the record has been completed, change the code back to "n" and delete the 667 MESSAGE note.

If an existing authority record needs investigation that cannot be completed immediately, adjust the code in 008/31 from "a" to "b" and add a 667 note:  "MESSAGE: Being updated.  [code and date]".  Additional information explaining the problem may be added, if considered useful.  When the record has been revised as necessary, change the value back to "a" and delete the 667 MESSAGE note.

667  ##  $a MESSAGE  Being updated. [code and date]

SARs:

1.   Notes on the title proper:

There may be a clear pattern of fluctuation between two or more forms of title proper of a numbered series (based on information in the database or from items in hand).  There may be a change in the form of the title proper that is not considered a title change (see RDA 2.3.2.13.2).  Use a 667 field in lieu of a 670 field to indicate the different title proper that is not generating its own SAR.  Give that form of the title proper in a 4XX field.

Examples:

667  ##  $a Some issues have title:  [title proper]

667  ##  $a Vol. 8 has title:  [title proper]

[Used for fluctuating titles.]

667  ##  $a Vols. 9-  have title:  [title proper]

[Used for a minor title change.]

If the subtitle could be interpreted as the title proper of the series or as a subseries, note the subtitle in a 667 field and give it as a 4XX variant access point.

667  ##  $a Subtitle:  [title of subtitle]

Do not use the 667 field to indicate variant titles of the series title proper found on the same item (e.g., form of series title on cover is different from form of series on series title page); note the variant titles in 670 field(s) and give them as 4XX variant access points.

2.   Notes on the relationship to other series/records:

If a series authority record represents a publication that is a successive entry that has occurred after a series was last handled under pre-AACR2 rules but for which no SAR yet exists, give the information only in a 667 field rather than in 675/5XX fields.  Label it, in square brackets, as an unevaluated catalog entry form.

667  ##  $a Continues: [pre-AACR 2 catalog entry form]

[Unevaluated catalog entry form.]

667  ##  $a Continued by: [pre-AACR 2 catalog entry form]

[Unevaluated catalog entry form.]

When the pre-AACR2 catalog entry form is being evaluated in terms of construction of the RDA authorized access point, delete this 667 and replace it with appropriate 675/5XX fields on both SARs.

If the earlier publication was not analyzable, give the information only in a 667 field rather than in 675/5XX fields.

Example:

667  ##  $a Continues the not-analyzable serial:  Directory of computer assisted research in musicology.

When the optional linking variant access point cannot be given between the RDA form and the previous form due to NACO normalization, if desired give the previous authorized access point's information in a 667 field.  Use one of the notes given below.  (See "NACO normalization" section in Introduction.)

Use this 667 note if the variant access point would normalize to the same form as the RDA authorized access point or another variant access point on the same record or to the same form as an authorized access point on another record:

667  ##  $a Old catalog heading: ________________.

Use this 667 note if two or more pre-RDA authorized access points will be treated as one authorized access point under RDA:

667  ##  $a Includes old catalog headings:  [pre-RDA a.a.p. 1]; and, [pre-RDA a.a.p. 2].

Use this 667 note if one pre-RDA authorized access point will be split under RDA:

667  ##  $a Previous to RDA covered by: [AACR2 a.a.p.].

3.   Notes on the publisher/issuing body:

When there are more than two changes of publisher or when there have been more than two different consecutive bodies both issuing and publishing the publication, give all of the changes in separate 643 fields or use only one 643 field and give an explanation in a 667 field.  The explanation should be as specific as is appropriate for the situation.

Examples:

667  ##  $a Imprint varies.

667  ##  $a Publisher varies.

667  ##  $a Published by various offices of the Division of Education.

4.   Notes on the type of publication:

If the series is a document series, give a 667 note.

667  ##  $a Document.

If the publication has changed its identity (e.g., from a monographic series to a periodical), give a 667 note that indicates what happened which will explain why a full set of analytic records is not available.

Examples:

667  ##  $a Telephone call to publisher, 11-2-88:  Change in pattern of publication; v. 1-17 monographic works, v. 18- collections of articles.

667  ##  $a Publication was periodical for v. 1-3; monographic series beginning with v. 4.

5.   Notes on the handling of series-like phrase:

667  ##  $a Do not give as a quoted note.

667  ##  $a Give as a quoted note.

667  ##  $a Give as a quoted note if [name of publisher] is not recorded in the publication, distribution, etc. area of the bibliographic record.

[For phrase that combines name of publisher and a generic term.]

667  ##  $a Is an imprint, not a series. Record in publication, distribution, etc. area of the bibliographic record.

[For imprint that could be construed to be a title, e.g., Metropolitan Books.]

667  ##  $a Give as a quoted note, including the number, e.g., AAI no. 85-41.

667  ##  $a Give as other title information in the title and statement of responsibility area of the bibliographic record.

6.   Notes on an undifferentiated phrase record:

When converting a series-like phrase for a single phrase to an undifferentiated phrase record to cover the same phrase used by more than one publisher, give a 667 note using the wording given below.  (See the Introduction for more information about these records.)

667  ##  $a Undifferentiated phrase record:  Covers all instances when this character string used by any publisher is considered to be a series-like phrase; if character string is to be a series, separate SAR has been made.

Optionally, provide a second 667 note:  "Give as a quoted note."  If a different handling is desired for one instance of the phrase, either (a) make a separate phrase SAR and add a qualifier to its 1XX entry, or (b) add another 667 note in the undifferentiated phrase SAR:  "For resources published by [________], give the phrase as [__________]."

7.   Notes on the post-cataloging authority records:

When creating a post-cataloging SAR, that is, one established without the piece in hand, give a 667 note with the wording below:

667  ##  $a Series authority record created without piece in hand.

When a preliminary record with this note is upgraded to full level, delete the note.

8.   Miscellaneous notes:

667  ##  $a Previous to AACR 2 subsumed under made-up set for UN documents.

[See 64X section for more information about UN documents.]

667  ##  $a First printing of vol. 8 of the Princeton theological monograph series erroneously carried the series statement:  Pittsburgh theological monographs.

667  ##  $a Phone call to Borgo Press 1-20-84:  Starmont Press series; Borgo reprints all titles generally 6 months to a year later in cloth.

667  ##  $a Lacked analyzable titles until v. 9.

667  ##  $a Indexed in: Social sciences index.

[For a series not being analyzed.]

667  ##  $a Establish separate records for English and Spanish titles if Spanish edition of v. 3 is received.

For more information on DCM Z1 Instructions, select:

DCM Z1:  Introduction

DCM Z1