Metropolitan Museum of Art
notes for NACO records and workflow
(part four)
[not yet completely posted here]

Continued from notes of 4XX and 5XX

Abbreviations: KD = Ken Dinin; SC = Sherman Clarke; JRD = Ross Day; DAS = Daniel Starr

NOTES ON SPECIFIC FIELDS

670 FIELD

GENERAL

SC comment:
Please reformulate 670s as necessary to current practice, e.g. only use main entry when needed. Use subtitle when it will clarify what the book is about or what the author is known for.
In the 670 $a, I would (as much as possible) try to replicate the 245 $a of the bib record. Clearly, sometimes that is not adequate to uniquely identify the work. In those cases, adding the uniform title or author main entry will uniquely identify the work. If the subtitle is a better or more informative way of amplifying the 245 $a, do that.

Try to avoid URLs in citing web addresses.

ABBREVIATIONS

biography
KD question and DAS comment:
KD: Should "bio" have a period?
DAS: I think it's used more often without the period than with. I know I never used it when I was doing records at MoMA, and no one ever mentioned it.

Example

NAFR9018982
040	NjP $cNjP $dNNMM
100 1	Salander, Lawrence B.
670	Lawrence Salander : paintings, 2001: $bbio (b. 1949, New York)
SC reply:
"bio" is usually an abbreviation and should probably have a period. I think I've said "biog." lately. If the section of the book is actually called "bio" without a period, then you certainly can use that.

USAGE FROM STANDARD REFERENCE SOURCES

KD question:
When does a standard reference source justify the addition of a 4XX, and what constitutes justification for a 4XX based on a heading or usage found in RLIN, or LC in RLIN?
SC reply:
References should generally be based on usage. In talking about IDA, I just wanted to be sure that we weren't confusing "real" usage with IDA conventions.

Usage in a directory can be considered usage as long as it's really reasonable as usage and doesn't reflect the prejudice of the directory. For example, IDA generally doesn't give the generic word like gallery, galeria, galerie, when giving the gallery information; museums seem to be full entries usually. If a directory always translated to a particular language, I'd not consider that usage. If the usage is authentic looking (clearly a judgement call), I'd include a reference but would probably default to no reference in case of doubt.

CITING LC RECORDS

Multiple heading forms
JRD question:
I find three forms of entry in the LC database for the same entity:

  1. "Huntington Free Library" (dcf:a, $dDLC)
  2. "Huntington Free Library and Reading Room" (dcf:a)
  3. "Huntington Free Library and Reading Room, New York" (dcf:i) as well as
  4. "Huntington Free Library and Reading Room, New York" [from old catalog]
As far as the 670 goes, how do you negotiate all these forms?

SC reply:

I would construct my 670:

LC database, Oct. 10, 2001 $b (hdg.: Huntington Free Library and Reading Room; Huntington Free Library and Reading Room, New York; Huntington Free Library and Reading Room, New York [from old catalog])

JRD question:

Are (1) and (3) examples of bfm (but not (4))?

SC reply:
Only 3 is candidate for bfm.

Citing MLC records in 670
SC comment:
Re nr2002-1397 (Willburger, Peter, 1942-1998). We are not obligated to record MLC bib precedence but I added it here since we'll be requesting bfm.

100 1 Willburger, Peter, $d1942-1998
670 LC database, Jan. 16, 2002 $b(MLC hdg.: Willburger, Peter, 1942- )

ERRORS IN CIP DATA INCORPORATED IN HEADINGS

 
NAFL88276675  [earlier version]
040	DLC $cDLC                                                              
100 10	Dryden, Ernst, $d1883-1938                                             
670	Lipmann, A. Divinely elegant, 1989: $bCIP t.p. (Ernst Dryden) galley (Austrian artist, b. 1883; d. 1938 in Hollywood)
DAS comment:
NAFL88276675 Dryden, Ernst, 1887-1938 [bfm]
LC's NAF record based on CIP; we updated their 670 in this case; they had a typo in the birth date which was corrected.

SC review:
Generally, keep the 670(s) as they are. I wouldn't change the form of date for a database search. Here, I would have kept the CIP info in the 670 and added the information from the printed book.
Altogether:
670 Lipmann, A. Divinely elegant, 1989: $b CIP t.p. (Ernst Dryden) galley (Austrian artist, b. 1883; d. 1938 in Hollywood) p. 11, etc. (b. Aug. 3, 1887 in Vienna; famous as a poster artist in Berlin; changed name and career after World War I to menswear designer; costumier in Hollywood since 1934; d. 1938 in Hollywood)

Revised record, resubmitted for review:

NAFL88276675
				Other Versions: earlier
040	DLC $cDLC $dNNMM
100 1	Dryden, Ernst, $d1887-1938                                             
400 1	Deutsch, Ernst, $d1887-1938                                            
400 1	Deutsch-Dryden, Ernst, $d1887-1938                                     
670	Lipmann, A. Divinely elegant, 1989: $bCIP t.p. (Ernst Dryden) galley (Austrian artist, b. 1883; d 1938 in Hollywood) p. 11, etc. (Ernst Deutsch; b. Aug. 3, 1887 in Vienna; famous as a poster artist in Berlin; changed his name and career after WWI to menswear designer; costumier in Hollywood since 1934; d. 1938 in Hollywood)                                      
670	LC in RLIN, Feb. 11, 2002 $b(hdg.: Dryden, Ernst, 1883-1938; usage: Ernst Dryden)                                                               
670	RLIN database, Feb. 11, 2002 $b(hdg.: Deutsch-Dryden, Ernst, 1887-1938; 	usage: Ernst Deutsch-Dryden (1887-1938))

DAS followup comment:
I'm still concerned that LC will recognize that the birthyear in the original heading was a typo.

SC followup reply:
Since the 1883 is based on CIP info, that can be so slippery that all of us in NACOland are ready to jump off .... even LC.

KD comment:
In other words, the fact that the source justifying the 1883 birthdate is CIP data renders suspect any info. cited therefrom; hence, when a more reliable source is cited that contradicts the CIP data (e.g. the published text of the very same work) there is no need to be concerned that the library which used the CIP data will bother to revise it (nor should any other library do so) in order to eliminate errors found.

SC followup reply (cont’d.):
If there was a long tradition in NUC and older LC records (or on cards) for using a certain birthdate and newer evidence varied, I might feel a strong need to check several sources. If the only "LC in RLIN" is the record for Divinely elegant, I think I wouldn't do the 670 for LC in RLIN (if so, they set up the authority record for the subject heading on that book).

KD comment:
Inasmuch as the heading for Dryden appears to have been established by LC based solely on the (erroneous) CIP data, citing the heading created on the basis of that data as an additional “source” is reductive, hence unncecessary.

To summarize: (1) Leave uncorrected any erroneous CIP data contained in a 670 note; (2) Do not cite as an additional source any LC (or other) heading that has been established solely on the basis of such erroneous data; (3) Revise a long-used LC or NUC heading that is based upon erroneous data only after consulting more than one reliable source (see AACR2 22.2A1).

CITING NON-LC RECORDS IN RLIN

 
NAFL88276675
040	DLC $cDLC $dNNMM
100 1	Dryden, Ernst, $d1887-1938
400 1	Deutsch-Dryden, Ernst, $d1887-1938
670	RLIN database, Feb. 11, 2002 $b(hdg.: Deutsch-Dryden, Ernst, 1887-1938; 	usage: Ernst Deutsch-Dryden (1887-1938))

KD question:
Is it necessary to cite the non-LC hdg. found in RLIN, or simply the usage, which differs from the form of the heading being established, in order to justify a 4XX reference?

SC reply:
I usually cite the form(s) of the heading(s) in any 670 source. After citing the form(s) of the heading(s), I add whatever info is new. If the forms are numerous, I'd not do them all. The other day, I suggested to an NYU cataloger who had a number of minor variants that she cite the most widely used ones and add "[etc.]"

SC followup reply:
My message yesterday about Dryden/Deutsch-Dryden was responding to your question without searching. I've now done some searching in RLIN and LC.

Another way to handle a particular usage in RLIN is, for example:

 
670  RLIN CTYAFHE0000-B Von Wien bis Hollywood : die Blute der
Mode-Illustration und Werbegrafik : Ernst Deutsch-Dryden (1887-1938) ...
c1990.

KD comment:
The above Yale record uses the heading: Deutsch-Dryden, Ernst, 1887-1938 which is based on usage from the source. Rather than citing the two variant headings found in RLIN (neither of which matches the revised heading) and their usages in a single 670 note, one can simply cite the usage for the significant variant (different entry element) as illustrated above.

SC followup reply (cont’d.):
One could also stick on the end [portion of] the title with Hollywood [to a standard RLIN database citation note] and do $b with hdg/usage; or [using the format above] add an ellipsis rather than doing the first portion of other title info and then give usage as further other title info.

KD comment:
670 RLIN database, Mar. 12, 2002 $b(hdg. Deutsch-Dryden, Ernst, 1887-1938; usage: Ernst Deutsch-Dryden (1887-1938)) [This is the end portion of the “Hollywood” title that contains the usage]
or
670 RLIN CTYAFHE0000-B Von Wien bis Hollywood … Ernst Deutsch-Dryden (1887-1938)), c1990. [Underscoring shows portion of further other title info. that constitutes usage]

SC followup reply (cont’d.):
If I wanted to do the conventional RLIN 670, I'd do:

670 RLIN, Mar. 12, 2002 $b (hdg.: Dryden, Ernst, 1883-1938; Deutsch-Dryden, Ernst, 1887-1938; usage: Ernst Dryden; Ernst Deutsch-Dryden (1887-1938))

CITING REFERENCES TO EARLIER / LATER HEADINGS FOR CORPORATE BODIES

JRD question:
What is the proper procedure for citing a previous/later corporate entity for which there are no known publications? I have a “missing” link between two corporate entries (actually two I think). Do you cite them in a 410, and if so, which gets it, the previous or the later?

SC reply:
If there are no known publications, or at least none within your purview, you should probably record the existence of the related names in 670 or 675 but not make a 410. And since there won’t be a related name authority record, no 510 to refer to. That’s the general thought; the particular case might lead to some fine tuning.

NACO Participants’ Manual, 2nd ed. (1996), p. 33:
* Always give the citation for the item being cataloged in a 670 field. If the work does not contain the name being established, give an explanatory note (e.g., "(name not given)"). Give other source citations as necessary.
* If any other sources give only an earlier or later name, but not the name used in the heading, cite the source in the 675 field. Note that subfield b is not used in the 675 field because all information is given in subfield a. Do not, however, divide a citation for successive issues of a serial; give the complete citation in the 670 field if any volume contains the heading or in the 675 field if no volume contains the heading.

Examples

 
110 20 American Material Handling Society
510 20 $w b $a International Material Management Society
670    Materials handling handbook, 1984: $b t.p. (International Material Management Society (successor to the American Material Handling Society))

110 20 International Material Management Society 510 20 $w a $a American Material Handling Society 670 Materials handling handbook, 1984: $b t.p. (International Material Management Society (successor to the American Material Handling Society))

CHINESE / JAPANESE PERSONAL NAMES

KD question:
NAFR200149415 Liu, Genggu, $d1940-

670 Liu Genggu hua ji, 1990: $bcolophon (Liu Genggu [in rom.]; Liu Geng-gu)p. 221 (b. Dec. 26, 1940 in Chia-Yih Hsien, Taiwan; painter)

Min wants to distinguish between her romanization of the vernacular version of the name (i.e. [in rom.]) from the romanized form supplied by the publisher, both of which appear in the colophon. She was basing her addition of the bracketed note on examples found in other authority records, e.g.

NAFR9427233 Kawashima, Takeshi, 1930-
670 Kawashima Takeshi, 1989: $bp. 75, etc. (Takeshi Kawashima [in rom.]; b. 1/13/30 in Kagawa-ken Takamatsu-shi; painter, sculptor; res. in New York)

Are there specific protocols for the use of this romanization note, and would her application be a valid instance of its use? It seems to me that in the case of her record it is helpful in clarifying how the heading was established. Can you shed any light on this matter?

There also appear to be other protocols for recording types of personal name variants in field 670, e.g. "t." and "h." which Min indicates are romanized abbreviations of Chinese-language terms that indicate particular kinds of versions of personal names. Is there documentation regarding these conventions that we can consult and retain for our files?

SC reply:
Below is the answer I got from Philip Melzer about the "t." (pinyin "z.") and "h." in 670 of authority records for Chinese names. It would appear that there are not strict and fast guidelines about using these abbreviations.

In the example you and Min cite (nr94-27233) in your earlier message, "Takeshi Kawashima" should be expected to be found in latin characters. I would expect the title to be in Japanese characters.

Memo from Philip Melzer, Team Leader
Korean/Chinese Cataloging Team
Regional and Cooperative Cataloging Division
Library of Congress

Chinese NACO guidelines:

Chinese language catalogers have used "t." in the 670 field to indicate the term tzu (in Wade-Giles, zi in pinyin), which is a familiar name that a man calls himself; and 'h.' for hao (in both systems), which is a courtesy name. Some catalogers are now using "z." for zi in the 670 field, but of course one could also simply use the full romanized forms for these terms. I'm not sure how we got into the habit of using these abbreviations.

These kinds of names have always been used by educated people, especially artists, writers. We generally provide x-refs. from those forms because people are occasionally referred to by those names in publications.

CITING MULTIPLE REFERENCES IN 675 NOTES (SOURCE DATA NOT FOUND)

SC comment:

Re nr2001-51861 and nr2001-51859 (Holzer, Ann and Holzer, Philip), I made some non-access changes to the 675s. Each subfield should be separated by semi-colon.

 
NAFR200151861	
100 1	Holzer, Ann
675	WW in Amer. art, 1999/2000; $aWW in Amer. art, 1990/91; $aWwasW in Amer. art

NAFR200151859 100 1 Holzer, Philip 675 WW in Amer. art, 1999/2000; $aWW in Amer. art 1990/91; $aWwasW in Amer. art


... go to top of Art NACO page ...