[Evergreen-catalogers] Authority records

[Mike Rylander]

Laurie,

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.

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:
https://launchpadlibrarian.net/123618121/bad_auth_record.txt

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.

Thanks again!

--miker



On Thu, Jan 10, 2013 at 3:29 PM, Laurie Kulik <lkulik at mvlc.org> wrote:

> Hi Mike,
>
> 1. A 400 field cannot stand alone without the 1XX field. Therefore, your
> understanding there is correct.
>
> 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.
>
> An example of this Authority record would be  the Dave Matthews Band.
>
> 110 2  Dave Matthews Band
>
> 410 2  Matthews Band
>
> 410 2  DMB
>
> 500 1  Matthews, Dave, $d 1967-
>
> I hope this answers your questions~
> Laurie
>
>
>
> On 1/10/2013 2:31 PM, Mike Rylander wrote:
>
>> 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?
>>
>> 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?
>>
>> Thanks in advance,
>>
>> --
>> Mike Rylander
>>  | Director of Research and Development
>>  | Equinox Software, Inc. / Your Library's Guide to Open Source
>>  | phone:  1-877-OPEN-ILS (673-6457)
>>  | email: miker at esilibrary.com <mailto:miker at esilibrary.com>
>>  | web: http://www.esilibrary.com
>>
>>
>> ______________________________**_________________
>> Evergreen-catalogers mailing list
>> Evergreen-catalogers at list.**evergreen-ils.org<Evergreen-catalogers at list.evergreen-ils.org>
>> http://list.evergreen-ils.org/**cgi-bin/mailman/listinfo/**
>> evergreen-catalogers<http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers>
>>
>
> --
>
> Laurie Kulik
> lkulik at mvlc.org
> Database Manager/Cataloger
> Merrimack Valley Library Consortium
> 1600 Osgood St.
> N. Andover, MA 01845
> (978) 557-8204 (work)
> (978) 557-8101 (fax)
>
> ______________________________**_________________
> Evergreen-catalogers mailing list
> Evergreen-catalogers at list.**evergreen-ils.org<Evergreen-catalogers at list.evergreen-ils.org>
> http://list.evergreen-ils.org/**cgi-bin/mailman/listinfo/**
> evergreen-catalogers<http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers>
>



-- 
Mike Rylander
 | Director of Research and Development
 | Equinox Software, Inc. / Your Library's Guide to Open Source
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  miker at esilibrary.com
 | web:  http://www.esilibrary.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-catalogers/attachments/20130110/abef41fd/attachment.html>