<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
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"
type="cite">
<style type="text/css">p { margin: 0; }</style>
<div style="font-family: arial,helvetica,sans-serif; font-size:
12pt; color: #000000">
<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"><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"><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"><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"><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 moz-do-not-send="true"
href="mailto:galron.1@osu.edu" target="_blank">galron.1@osu.edu</a>
or <a moz-do-not-send="true"
href="mailto:jgalron@gmail.com" target="_blank">jgalron@gmail.com</a><br>
Tel.: (614) 292-3362, Fax: (614)292-1918<br>
URL: <a moz-do-not-send="true"
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 moz-do-not-send="true"
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">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">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 wrap="">_______________________________________________
Heb-naco mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Heb-naco@lists.service.ohio-state.edu">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">https://lists.service.ohio-state.edu/mailman/listinfo/heb-naco</a>
</pre>
</blockquote>
<br>
</body>
</html>