<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000'><P>HI Nancy,</P>
<P> </P>
<P>You are absolutely right that a cataloger has the option to call on their own expertise or work-flow to add a date of birth/death to a new RDA personal name heading even if it is not required. This situation is a great example of how RDA allows "catalogers judgment" in many of its rules. This kind of decision may be supported by institutional, departmental or individual decisions and guidelines. <BR><BR></P>
<P>
<HR id=zwchr>
<P></P>
<DIV style="FONT-STYLE: normal; FONT-FAMILY: Helvetica,Arial,sans-serif; COLOR: #000; FONT-SIZE: 12pt; FONT-WEIGHT: normal; TEXT-DECORATION: none"><B>From: </B>"Nancy Sack" <sack@hawaii.edu><BR><B>To: </B>heb-naco@lists.service.ohio-state.edu<BR><B>Sent: </B>Tuesday, October 9, 2012 8:22:44 PM<BR><B>Subject: </B>Re: [Heb-NACO] RDA: Update of RDA NARs<BR><BR>I know it isn't required but in the case of common names, at least, I tend to go the extra mile and do a brief search for a date. A similar topic was recently discussed on the PCC list. It involved adding a fuller form to Smith, P. even if it weren't needed to make the access point unique. <BR><BR>Nancy<BR><BR><BR>
<DIV class=moz-cite-prefix>On 10/9/2012 10:43 AM, Heidi G Lerner wrote:<BR></DIV>
<BLOCKQUOTE cite=mid:1015460224.8683799.1349815409069.JavaMail.root@zm06.stanford.edu>
<STYLE>p { margin: 0; }</STYLE>
<DIV style="FONT-FAMILY: arial,helvetica,sans-serif; COLOR: #000000; FONT-SIZE: 12pt">
<P>p.s. I am basing my comments on not adding dates of birth [and/or death] if the information is not found in the resource or other references sources cited to support the choice of heading and there is no need to break a conflict, on LCPS 9.19.1.1 "Differentiating Authorized Access Points for Persons."</P>
<P> </P>
<DIV id=lcps9-194 class=para>Include the date of birth and date of death if AVAILBLE in the authorized access point for a person when creating a new name authority record. If an addition is needed to differentiate the authorized access point for one person from the authorized access point for another person, apply cataloger judgment when choosing to add one of the following (not listed in priority order) to the authorized access point being established: period of activity of the person, fuller form of name, and/or profession or occupation.</DIV>
<DIV class=para>If there are no additions readily available to differentiate the access point in the new authority record, make an addition to the existing authorized access point.</DIV>
<DIV class=para> </DIV>
<DIV class=para>The important word is "available." To the best of my knowlege RDA nor the LCPS's tell us what avaialble means but most catalogers interpret it as meaning "doing extra research beyond the resource in hand."</DIV>
<DIV class=para> </DIV>
<DIV class=para>Thanks, Heidi</DIV>
<DIV class=para> </DIV>
<DIV class=para><BR> </DIV>
<P></P>
<HR id=zwchr>
<DIV style="FONT-STYLE: normal; FONT-FAMILY: Helvetica,Arial,sans-serif; COLOR: #000; FONT-SIZE: 12pt; FONT-WEIGHT: normal; TEXT-DECORATION: none"><B>From: </B>"Heidi G Lerner" <A class=moz-txt-link-rfc2396E href="mailto:lerner@stanford.edu" target=_blank><lerner@stanford.edu></A><BR><B>To: </B>"Hebrew Name Authority Funnel" <A class=moz-txt-link-rfc2396E href="mailto:heb-naco@lists.service.ohio-state.edu" target=_blank><heb-naco@lists.service.ohio-state.edu></A><BR><B>Sent: </B>Tuesday, October 9, 2012 1:03:06 PM<BR><B>Subject: </B>Re: [Heb-NACO] RDA: Update of RDA NARs<BR><BR>
<STYLE>p { margin: 0; }</STYLE>
<DIV style="FONT-FAMILY: arial,helvetica,sans-serif; COLOR: #000000; FONT-SIZE: 12pt">
<P>Hi Yosi,</P>
<P> </P>
<P>If the date of birth was not cited in the 670s and did not appear in the resources of the existing RDA NAR, then the heading would be established without the date of birth. Catalogers are not expceted to do extra research to find a date of birth unless there is a need to break a conflict.</P>
<P> </P>
<P>If however, if the date of birth comes up later but no other changes to the NAR are being made, then the date of birth would not be added to the heading. We would record the date of birth in a 670 for the new source of information that is being added to the extant RDA NAR and then we can go ahead and record the information in the 046 field. </P>
<P> </P>
<P>If you are going to add the date of birth to the 046 field, you can go ahead and any other relevant information to 3xx fields that are available in the NAR or the new resource. You will find many existing RDA headings that do not have the new 37x fields or 046 field in them. Up until recently, PCC had not issued any statements on whether or not these fields should be included in an RDA authority record and many institutions chose not to include them since they were optional, until PCC made a formal statement.</P>
<P> </P>
<P>Sincerely, Heidi<BR><BR></P>
<P></P>
<HR id=zwchr>
<DIV style="FONT-STYLE: normal; FONT-FAMILY: Helvetica,Arial,sans-serif; COLOR: #000; FONT-SIZE: 12pt; FONT-WEIGHT: normal; TEXT-DECORATION: none"><B>From: </B>"Yossi Galron" <A class=moz-txt-link-rfc2396E href="mailto:jgalron@gmail.com" target=_blank><jgalron@gmail.com></A><BR><B>To: </B>"heb-naco" <A class=moz-txt-link-rfc2396E href="mailto:heb-naco@lists.service.ohio-state.edu" target=_blank><heb-naco@lists.service.ohio-state.edu></A><BR><B>Sent: </B>Tuesday, October 9, 2012 12:28:23 PM<BR><B>Subject: </B>[Heb-NACO] RDA: Update of RDA NARs<BR><BR>There is an RDA NAR record that does not include 046 field and subfield "d" in the 1XX field.
<DIV>Can/should we add the added information (i.e. the 046 field)?</DIV>
<DIV>I guess we are not adding the subfield "d" to 1XX - not to change the heading if there is no conflict</DIV>
<DIV><BR></DIV>
<DIV>Yossi</DIV>
<DIV><BR></DIV>
<DIV><BR clear=all>Joseph (Yossi) Galron-Goldschlaeger<BR>Head, Hebraica & Jewish Studies Library<BR>355A Thompson Memorial Library<BR>The Ohio State University Libraries <BR>1858 Neil Ave. Mall<BR>Columbus, Ohio 43210 USA<BR>E-Mail: <A href="mailto:galron.1@osu.edu" target=_blank>galron.1@osu.edu</A> or <A href="mailto:jgalron@gmail.com" target=_blank>jgalron@gmail.com</A><BR>Tel.: (614) 292-3362, Fax: (614)292-1918<BR>URL: <A href="http://library.osu.edu/about/departments/jewish-studies/" target=_blank>http://library.osu.edu/about/departments/jewish-studies/</A><BR>Lexicon of Modern Hebrew Literature:<BR><A href="http://hebrewlit.notlong.com/" target=_blank>http://hebrewlit.notlong.com</A><BR><BR></DIV><BR>_______________________________________________<BR>Heb-naco mailing list<BR><A class=moz-txt-link-abbreviated href="mailto:Heb-naco@lists.service.ohio-state.edu" target=_blank>Heb-naco@lists.service.ohio-state.edu</A><BR><A class=moz-txt-link-freetext href="https://lists.service.ohio-state.edu/mailman/listinfo/heb-naco" target=_blank>https://lists.service.ohio-state.edu/mailman/listinfo/heb-naco</A><BR></DIV><BR></DIV></DIV><BR></DIV><BR>
<FIELDSET class=mimeAttachmentHeader></FIELDSET> <BR><PRE>_______________________________________________ Heb-naco mailing list
<A class=moz-txt-link-abbreviated href="mailto:Heb-naco@lists.service.ohio-state.edu" target=_blank>Heb-naco@lists.service.ohio-state.edu</A>
<A class=moz-txt-link-freetext href="https://lists.service.ohio-state.edu/mailman/listinfo/heb-naco" target=_blank>https://lists.service.ohio-state.edu/mailman/listinfo/heb-naco</A>
</PRE></BLOCKQUOTE><BR><BR>_______________________________________________<BR>Heb-naco mailing list<BR>Heb-naco@lists.service.ohio-state.edu<BR>https://lists.service.ohio-state.edu/mailman/listinfo/heb-naco<BR></DIV><BR></div></body></html>