[Evergreen-catalogers] Authorities question

[Hardy, Elaine]

Yes, thanks for the clarification, Mike.

Elaine


J. Elaine Hardy
PINES & Collaborative Projects Manager
Georgia Public Library Service
1800 Century Place, Ste 150
Atlanta, Ga. 30345-4304


404.235.7128
404.235.7201, fax
ehardy at georgialibraries.org
www.georgialibraries.org
www.georgialibraries.org/pines


-----Original Message-----
From: Evergreen-catalogers 
[mailto:evergreen-catalogers-bounces at list.evergreen-ils.org] On Behalf Of 
Mary Llewellyn
Sent: Friday, October 16, 2015 2:45 PM
To: 'Evergreen Community Catalogers' 
<evergreen-catalogers at list.evergreen-ils.org>
Subject: Re: [Evergreen-catalogers] Authorities question

Thanks for your responses, Mike and Elaine.  Since we're still sitting on 
the edge of the authority pool with our toes barely wet, as it were, I 
wasn't certain what was an issue and what wasn't.  The experience and 
clarification helps.

Mary


-----Original Message-----
From: Evergreen-catalogers 
[mailto:evergreen-catalogers-bounces at list.evergreen-ils.org] On Behalf Of 
Mike Rylander
Sent: Friday, October 16, 2015 2:41 PM
To: Evergreen Community Catalogers
Subject: Re: [Evergreen-catalogers] Authorities question

Mary and Elaine,

To clarify what happens internally in Evergreen when you delete an 
authority, the bibs do indeed retain the $0 but the internal linking is 
removed.  Causing a reingest of all previously-linked bibs by altering the 
MARC would cause the deletion to fail for any non-trivial number of linked 
bibs.  Just as incoming (migrated, imported) bib data may have spurious $0 
fields, those dangling fields are of no consequence once the authority id 
deleted.

Hope that helps,

--
Mike Rylander
 | President
 | Equinox Software, Inc. / The Open Source Experts  | phone: 
1-877-OPEN-ILS (673-6457)  | email:  miker at esilibrary.com  | web: 
http://www.esilibrary.com



On Fri, Oct 16, 2015 at 2:14 PM, Hardy, Elaine <ehardy at georgialibraries.org> 
wrote:
> Mary,
>
>
>
> We have partially implemented authorities – we have a vendor that
> updates our records and headings and we run scripts to link headings
> to authority records. However, I have not fully researched all the
> functionality and have not had a chance to add requests to Launchpad
> bugs. Also, we rarely manually edit or delete authority records from
> the AF. Our vendor does this via batch, somehow. I am not directly
> involved in authorities processing so I don’t know all the magic behind 
> it.
>
>
>
> I would expect, if an authority record is manually deleted that has
> linked bib records, the system warn you, allowing you to halt the
> deletion. If it does delete, whether it generates an error message or
> not, it should de-link the bib records so that they are not linked to a 
> deleted AF record.
>
>
>
> I would not expect the system to retain links to a deleted authority
> record and would consider that a problem. Especially if it prevents a
> link to a replacement record.
>
>
>
> Elaine
>
>
>
> J. Elaine Hardy
> PINES & Collaborative Projects Manager Georgia Public Library Service
> 1800 Century Place, Ste 150
> Atlanta, Ga. 30345-4304
>
>
>
> 404.235.7128
> 404.235.7201, fax
> ehardy at georgialibraries.org
> www.georgialibraries.org
> www.georgialibraries.org/pines
>
>
>
> From: Evergreen-catalogers
> [mailto:evergreen-catalogers-bounces at list.evergreen-ils.org] On Behalf
> Of Mary Llewellyn
> Sent: Friday, October 16, 2015 12:43 PM
> To: Evergreen Community Catalogers
> <evergreen-catalogers at list.evergreen-ils.org>
> Subject: [Evergreen-catalogers] Authorities question
>
>
>
> Hi all,
>
>
>
> So, I was testing authorities in Sprint 2 of the web client, mostly
> out of curiosity since we don’t currently use authorities. I came
> across something I thought was odd and reported it, and it turns out
> to be outside the scope of the testing since the behavior I observed
> is the same as it is in the current client. Before I go to Launchpad
> with a development request/bug fix, I wanted to check with anyone who
> is currently using authorities in Evergreen.
>
>
>
> What I discovered was that, in Manage Authorities, I was able to
> delete an auth record that was linked to bib records. I didn’t expect
> that; I assumed it would behave like other records that are linked
> together, like not deleting bib records with copies attached. Instead,
> the bib records in the web client were left pointing to an auth record
> that no longer existed. So since it apparently behaves that way in the
> current client (according the responses my ticket in Lighthouse got),
> my question is: should it? I don’t see any bugs entered in Launchpad for 
> it yet.
>
>
>
> Since we aren’t using authorities yet, I don’t have a living example
> to put in a Launchpad ticket. Has anyone else seen this happen in
> their system, and do they consider it to be a problem?
>
>
>
> Thank you,
>
>
>
> Mary
>
>
>
> Mary Llewellyn
>
> Database Manager
>
> Bibliomation, Inc.
>
> 24 Wooster Ave.
>
> Waterbury, CT 06708
>
> mllewell at biblio.org
>
>
>
>
>
>
> _______________________________________________
> Evergreen-catalogers mailing list
> Evergreen-catalogers at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catal
> ogers
>
_______________________________________________
Evergreen-catalogers mailing list
Evergreen-catalogers at list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers

_______________________________________________
Evergreen-catalogers mailing list
Evergreen-catalogers at list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers