Those are good points, as were John Marr’s.


To go back to Diane’s original message, I do find it strange that someone thought it was appropriate to replace a MeSH heading with LCSH. Especially since our NACO training told us to repeat 374 if a term was from a different controlled vocabulary. It was always very clear that there could be more than one vocabulary on authority records.


Actually, just looking at the MARC document, I realized that it doesn’t specifically say repeat 374 if the controlled vocabulary changes. (It only says “The field is repeated if the person has multiple occupations for different time periods.”) But I believe our training said that somewhere else.




From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of John Hostage
Sent: Thursday, February 26, 2015 4:08 PM
To: [log in to unmask]
Subject: Re: [PCCLIST] Best practices in updating authority records


It seems that some people have strong ideas of what they think is the one true way of using RDA elements and MARC fields.  There are good arguments on each side, but I think the expectation that MARC records will be turned into linked data is based more on faith than on evidence.  It’s more realistic that information in the MARC fields could be used to give the user identifying information similar to the way info boxes work in Wikipedia.  See, for example, .  In the box on the right, some of the metadata is linked to other articles, but some is not, e.g. Occupation.  It would be strange if it said “Writers, columnists, authors”, but Wikipedia has ways of distinguishing the displayed form from the link form that we don’t have in the MARC world.  The Wikipedia page with its singular forms is more user-friendly than his authority record as displayed at .  In addition, at the bottom of the Wikipedia page the person is assigned to various categories, such as “American columnists”.


I also doubt that library systems will take attributes from MARC fields and create access points automatically.  Before that happens, the need for unique strings as access points will become obsolete.


We have to allow for a variety of solutions in MARC records.



John Hostage

Senior Continuing Resources Cataloger //

Harvard Library--Information and Technical Services //

Langdell Hall 194 //

Cambridge, MA 02138

[log in to unmask]

+(1)(617) 495-3974 (voice)

+(1)(617) 496-4409 (fax)

ISNI 0000 0000 4028 0917