Thanks! One follow-up question: Does this rule apply to supplying a non-Latin script parallel field for a 76X-78X linking field? Should one only be supplied if there are corresponding non-Latin script field(s) in the target record, or is it OK to provide this even if the target record lacks the non-Latin script field(s)?
J. Byrd From: Resource Description and Access / Resource Description and Access [mailto:RDA-L@listserv.lac-bac.gc.ca] On Behalf Of Christopher Thomas Sent: Wednesday, June 05, 2013 11:10 AM To: RDA-L@listserv.lac-bac.gc.ca Subject: Re: [RDA-L] 76X-78X linking fields Data in a linking entry is supposed to match data in the target record. You should not edit 76X-78X to RDA unless you are also editing the target record to match. Christopher Thomas, M.L.S. | Electronic Resources and Metadata Librarian (949) 824-7681 | fax (949) 824-6700 | ctho...@law.uci.edu<mailto:ctho...@law.uci.edu> Law Library * University of California * Irvine www.law.uci.edu/library<http://www.law.uci.edu/library> [Logo_size03] From: Resource Description and Access / Resource Description and Access [mailto:RDA-L@LISTSERV.LAC-BAC.GC.CA] On Behalf Of Byrd, Jacqueline Jo Sent: Wednesday, June 05, 2013 4:51 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA<mailto:RDA-L@LISTSERV.LAC-BAC.GC.CA> Subject: [RDA-L] 76X-78X linking fields Many 76X-78X linking entry fields can be created by inserting the cited record in Connexion, supplying the information on author, title, imprint, etc. from an existing bibliographic record in OCLC. If this cited record has information that is not RDA compliant, e.g. abbreviations when I know that original spelled something out, should I edit the 76X-78X field to reflect RDA? If so, should I do anything to the bib record being cited, or do I leave that in its pre-RDA form? Thanks! Jacqueline Byrd Head, Area Studies Cataloging Section Technical Services Department Herman B Wells Library Indiana University 1320 E. 10th St. Bloomington, IN 47405 TEL: 812-855-4310 FAX: 812-855-7933 b...@indiana.edu<mailto:b...@indiana.edu>
<<inline: image001.jpg>>
