<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Mike,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></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">https://sites.google.com/site/opencatalogingrules/26-4b--see-references</a> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></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'><o:p></o:p></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>404.235-7128<br>404.235-7201, fax<br>ehardy@georgialibraries.org<br>www.georgialibraries.org<br><a href="http://www.georgialibraries.org/pines">www.georgialibraries.org/pines</a><br><br><br></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></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"'> evergreen-catalogers-bounces@list.evergreen-ils.org [mailto:evergreen-catalogers-bounces@list.evergreen-ils.org] <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<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Laurie,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></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.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></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">https://launchpadlibrarian.net/123618121/bad_auth_record.txt</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></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.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks again!<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>--miker<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></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:<o:p></o:p></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<o:p></o:p></p><div><div><p class=MsoNormal><br><br><br>On 1/10/2013 2:31 PM, Mike Rylander wrote:<o:p></o:p></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)<o:p></o:p></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><o:p></o:p></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><o:p></o:p></p></div><p class=MsoNormal><br><br clear=all><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></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> <o:p></o:p></p></div></div></body></html>