<div dir="ltr">Elaine,<div><br></div><div>It is helpful, thanks, and it makes sense.</div><div><br></div><div>To bring the discussion around full circle, the fix that went in should do what we want in these situations. That is, a simplified version of the issue looks like this: the 410 in the uniform title authority record was being used to look up the appropriate bib fields to overlay using the authority data. But there was (previously) a faulty assumption that a 410 would only exist in an authority record containing a 110 and that it would overlay bib fields 110, 610, 710, etc. The authority record contains a 130 and two 410s, and so the overlay template constructed was just plain wrong. Now we only look at the main heading of the authority record (1xx) when deciding on the shape of the generated overlay template (auth fields to use, bib fields to overlay). Given the example bib and auth, we will now correctly overly the 630 in the bib with the 130 from the authority, ignoring the 410s, when the authority record is updated and causes an automatic bib update. Furthermore, if there are any code paths that slip through the cracks, the function closest to the data will refuse to perform an overlay action where no overlay rules at all are specified, which was the proximate cause of the bib damage.</div>
<div><br></div><div>Thanks for all the info and clarification, folks. It was very helpful!</div><div><br></div><div>--miker</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 16, 2013 at 12:40 PM, Hardy, Elaine <span dir="ltr"><<a href="mailto:ehardy@georgialibraries.org" target="_blank">ehardy@georgialibraries.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Mike,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I think this particular record has an earlier form for the treaty in the 410s hence the difference. Does this help -- <a href="https://sites.google.com/site/opencatalogingrules/26-4b--see-references" target="_blank">https://sites.google.com/site/opencatalogingrules/26-4b--see-references</a> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><div><div><div><div><div><p class="MsoNormal"><i><span style="font-size:18.0pt;font-family:"Garamond","serif";color:#1f497d">Elaine</span></i><span style="color:#1f497d"><u></u><u></u></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="color:#1f497d"><hr size="2" width="100%" align="center"></span></div></div></div></div></div></div><p class="MsoNormal"><span style="color:#1f497d"><br>
J. Elaine Hardy<br>PINES Bibliographic Projects & Metadata Manager<br>Georgia Public Library Service<br>1800 Century Place, Ste 150<br>Atlanta, Ga. 30345-4304<br><br><a href="tel:404.235-7128" value="+14042357128" target="_blank">404.235-7128</a><br>
<a href="tel:404.235-7201" value="+14042357201" target="_blank">404.235-7201</a>, fax<br><a href="mailto:ehardy@georgialibraries.org" target="_blank">ehardy@georgialibraries.org</a><br><a href="http://www.georgialibraries.org" target="_blank">www.georgialibraries.org</a><br>
<a href="http://www.georgialibraries.org/pines" target="_blank">www.georgialibraries.org/pines</a><br><br><br></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:evergreen-catalogers-bounces@list.evergreen-ils.org" target="_blank">evergreen-catalogers-bounces@list.evergreen-ils.org</a> [mailto:<a href="mailto:evergreen-catalogers-bounces@list.evergreen-ils.org" target="_blank">evergreen-catalogers-bounces@list.evergreen-ils.org</a>] <b>On Behalf Of </b>Mike Rylander<br>
<b>Sent:</b> Thursday, January 10, 2013 3:45 PM<br><b>To:</b> Evergreen Community Catalogers<br><b>Subject:</b> Re: [Evergreen-catalogers] Authority records<u></u><u></u></span></p><div><div class="h5"><p class="MsoNormal">
<u></u> <u></u></p><div><p class="MsoNormal">Laurie,<u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">That /is/ very helpful! It identifies a general deficiency in the Evergreen authority code, but one that can be addressed in a rather straight-forward manner.<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">As a followup question, what about records that cross the entire authority type boundary? That is, a title authority record containing a 130 which has a name authority see-from field -- 410 in this case -- and nothing else of substance to this discussion. That's actually the situation I should have started with, as the record in question is here: <a href="https://launchpadlibrarian.net/123618121/bad_auth_record.txt" target="_blank">https://launchpadlibrarian.net/123618121/bad_auth_record.txt</a><u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Regardless of your answer to this question, we now have an understanding of some work that should be done to further extend Evergreen's authority capabilities, but the answer to this will be important to the implementation path we choose.<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Thanks again!<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">--miker<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div></div><div><p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p><div><p class="MsoNormal">On Thu, Jan 10, 2013 at 3:29 PM, Laurie Kulik <<a href="mailto:lkulik@mvlc.org" target="_blank">lkulik@mvlc.org</a>> wrote:<u></u><u></u></p>
<p class="MsoNormal">Hi Mike,<br><br>1. A 400 field cannot stand alone without the 1XX field. Therefore, your understanding there is correct.<br><br>2. You can have a heading that crosses both corporate and personal names, particularly with a musical group and the lead musician. If you have a 410 (See also tracing -- Corporate name) field and a 100 (Heading -- Personal name) then you must also include a 500 or 510 (broader) heading to correspond to the 110 or 400 respectively.<br>
<br>An example of this Authority record would be the Dave Matthews Band.<br><br>110 2 Dave Matthews Band<br><br>410 2 Matthews Band<br><br>410 2 DMB<br><br>500 1 Matthews, Dave, $d 1967-<br><br>I hope this answers your questions~<br>
Laurie<u></u><u></u></p><div><div><p class="MsoNormal"><br><br><br>On 1/10/2013 2:31 PM, Mike Rylander wrote:<u></u><u></u></p></div></div><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div><div><p class="MsoNormal">It's my understanding of authority records that they don't make much sense without a 1XX field. That is, one can not construct a valid authority record containing, say, only a 400 field without a corresponding 100 field. Is that understanding correct?<br>
<br>Further, is there any conceivable reason to construct an authority record such that it contains a 410 (See Also Tracing -- Corporate Name) field and a 100 (Heading -- Personal Name) field, but /without/ a 110 (Heading -- Corporate Name) field? In other words, would one ever want an authority record that crosses the heading type boundary, or should Heading, See From, See Also and Linking entries always be of the same heading type within one record?<br>
<br>Thanks in advance,<br><br>-- <br>Mike Rylander<br> | Director of Research and Development<br> | Equinox Software, Inc. / Your Library's Guide to Open Source<br> | phone: 1-877-OPEN-ILS (673-6457)<u></u><u></u></p>
</div></div><p class="MsoNormal"> | email: <a href="mailto:miker@esilibrary.com" target="_blank">miker@esilibrary.com</a> <mailto:<a href="mailto:miker@esilibrary.com" target="_blank">miker@esilibrary.com</a>><br> | web: <a href="http://www.esilibrary.com" target="_blank">http://www.esilibrary.com</a><br>
<br><br>_______________________________________________<br>Evergreen-catalogers mailing list<br><a href="mailto:Evergreen-catalogers@list.evergreen-ils.org" target="_blank">Evergreen-catalogers@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers</a><u></u><u></u></p></blockquote><p class="MsoNormal">
<br>-- <br><br>Laurie Kulik<br><a href="mailto:lkulik@mvlc.org" target="_blank">lkulik@mvlc.org</a><br>Database Manager/Cataloger<br>Merrimack Valley Library Consortium<br>1600 Osgood St.<br>N. Andover, MA 01845<br><a href="tel:%28978%29%20557-8204" target="_blank">(978) 557-8204</a> (work)<br>
<a href="tel:%28978%29%20557-8101" target="_blank">(978) 557-8101</a> (fax)<br><br>_______________________________________________<br>Evergreen-catalogers mailing list<br><a href="mailto:Evergreen-catalogers@list.evergreen-ils.org" target="_blank">Evergreen-catalogers@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers</a><u></u><u></u></p></div><p class="MsoNormal">
<br><br clear="all"><u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p></div><p class="MsoNormal">-- <br>Mike Rylander<br> | Director of Research and Development<br> | Equinox Software, Inc. / Your Library's Guide to Open Source<br>
| phone: 1-877-OPEN-ILS (673-6457)<br> | email: <a href="mailto:miker@esilibrary.com" target="_blank">miker@esilibrary.com</a><br> | web: <a href="http://www.esilibrary.com" target="_blank">http://www.esilibrary.com</a> <u></u><u></u></p>
</div></div></div></div></div><br>_______________________________________________<br>
Evergreen-catalogers mailing list<br>
<a href="mailto:Evergreen-catalogers@list.evergreen-ils.org">Evergreen-catalogers@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Mike Rylander<br> | Director of Research and Development<br> | Equinox Software, Inc. / Your Library's Guide to Open Source<br> | phone: 1-877-OPEN-ILS (673-6457)<br>
| email: <a href="mailto:miker@esilibrary.com" target="_blank">miker@esilibrary.com</a><br> | web: <a href="http://www.esilibrary.com" target="_blank">http://www.esilibrary.com</a>
</div>