We do not use the bib 490 as a linking field. The problem is as the expert explains, but with the bib 440 field. We have hundreds of thousands of bib records with the now-obsolete 440 field. The same thing happens if an 830 is replaced by an 800 in the bib (when the authority was a 130 and is now a 100). I believe the expert understands the problem, but I don't think he's understanding that it's not just bibs with a linking 490 field -- the same thing happens with a bib with a linking 440 or a linking 830 field. Jeanette Navia Quoting Nate Cothran <ncothran@bslw.com>:
Hello All,
Yesterday, I sent off an email to Horizon?s Product Manager, Ed Riding, who was able to pass it to their Horizon cataloging expert. The following is what their expert had to say:
--
The only times I?ve seen this be an issue is when a client has the bib 490 field set as the linking tag?which is not the default Horizon configuration?and linking to the auth 130 tag. A bib 800 tag links to an auth 100 tag with all subfields linking (by default).
The problem with the bib 490 is that the heading finds a matching auth 130 created from the auth 430, Horizon determines that the heading is invalid and re-links the bib field to the 100 tag of the valid auth record. Since only $a is valid in 490 tags, only the $a can display. Upon import, the client?s records will wind up with this:
Auth# 401
100 1_ $a Watson, George, $d 1946- $t Hooked on learning library
430 _0 $a <pointer to auth# 402>
Auth# 402 (invalid)
130 _0 $a Hooked on learning library
Bib
490 1_ $a <pointer to auth# 401> (because auth# 402 is invalid)
800 1_ $a <pointer to auth# 401>
Resulting in:
490 1_ $a Watson, George
800 1_ $a Watson, George, $d 1946- $t Hooked on learning library
Ed asked his expert for clarification on how Horizon customers could avoid this problem:
If possible, the 490 tag should not be used as the linking tag. While some sites use the 490 tag as the linking tag so they can search that data along with the other series, it will unfortunately cause the problem outlined above. At this time there is no way to prevent this problem from occurring if our Horizon clients use the 490 tag as the linking tag.
--
We at Backstage are grateful to Horizon for providing us with this explanation and wanted to share it with you immediately.
Nate Cothran
Backstage Library Works
From: bslwac-bounces@mailman.xmission.com [mailto:bslwac-bounces@mailman.xmission.com] On Behalf Of Groenwald, Rosemary Sent: Wednesday, January 27, 2010 7:24 AM To: Backstage Library Works Authority Contol Listserv Subject: Re: [BSLWAC] Series authority problems in Horizon
Jeanette
We also have the same problem. I had talked with Nate about it several times over the past few years but we did not come up with a solution. My notes indicate that BSLW would investigate further. We are on Horizon 7.4.1. I would love to be able to resolve this. For the time being, we clean up the bibs as we discover them only because I haven't had time to plan a clean-up project using MarcEdit.
Rosemary Groenwald
Head of Technical Services
Mount Prospect Public Library
10 S. Emerson St.
Mount Prospect, IL 60056
847-590-3650
"Opinions expressed are those of the sender and not the Mount Prospect Public Library."
_____
From: bslwac-bounces@mailman.xmission.com [bslwac-bounces@mailman.xmission.com] On Behalf Of Maria Mucino [Maria.Mucino@mesaaz.gov] Sent: Tuesday, January 26, 2010 1:52 PM To: Backstage Library Works Authority Contol Listserv Subject: Re: [BSLWAC] Series authority problems in Horizon
Hi Jeanette,
We did have the same problem at MPL, when we sent out data to Backstage. Our particular solution was to change the authority record as follows:
SAR (Series authority record)
100 1 Cabot, Meg. ?t Allie Finkle's rules for girls
430 0 Allie Finkle's rules for girls
We asked Backstage to modify the record for us as follows:
130 0 Allie Finkle's rules for girls
And populated that info into the 490 and 830 fields, I know this is incorrect, whoever our patrons and staff are use to titles in the series only. There was no other way I could have done it.
I you just want to change the 440 to 8XX in Horizon, you can archive this by using MARCEdit, you will have to test first some records. MARCedit is very simple to use.
I hope this helps.
Maria R. Mucino
Librarian II - Cataloguer
City of Mesa Library
480-644-5455
maria.mucino@mesaaz.gov
He who asks a question is a fool for five minutes; he who does not ask a question remains a fool forever. ~Proverb, (Chinese)~
From: bslwac-bounces@mailman.xmission.com [mailto:bslwac-bounces@mailman.xmission.com] On Behalf Of Diane Raines Sent: Tuesday, January 26, 2010 10:26 AM To: jmyntti@bslw.com; Nate Cothran; bslwac@mailman.xmission.com Subject: Re: [BSLWAC] Series authority problems in Horizon
Hi Jeanettee and the List
As you can see Nate wrote to me asking if this was an issue for us. I am trying to picture the sequence to figure out if it is. Could you please give me a few before and after examples that I could check in my database to figure out if it is a problem for me. I am sending this to the list figuring that maybe other Horizon libraries might also have or be interested in some examples so that we all can more easily check for this problem. That way BSLW can understand it and we can figure out if it is something that we need to also bring to the attention of Sirsi-Dynix. By the way, what version of Horizon are you on?
-Diane
M. Diane Raines Technical Services/Serials Librarian Westminster College-Giovale Library 1840 South 1300 East Salt Lake City, UT 84105-3697 email: draines@westminstercollege.edu voice: (801) 832-2260 fax: (801) 832-3109
"Nate Cothran" <ncothran@bslw.com> 1/25/2010 1:37 PM >>>
Hi Diane,
One of our libraries, Williamsburg Regional, has an issue with series authorities in the Horizon system. I was wondering if her question makes sense to you as a Horizon user.
Here is the question:
--
Jeanette Navia [jnavia@wrl.org]
This is a question for Horizon libraries who use Backstage authorities processing. We have problems when series headings that were title-only headings (130 in the authority records) are replaced by series headings that include author and title (100 in the authority records).
Most of our bib records with this problem have title-only series headings in 440 fields. When we get the updated authority records from Backstage, the a subfield of the new heading (the author's name) replaces the a subfield in the 440 field (series title) of the bib record. We end up with series headings in bib records with just the author's name and no series title.
Does anyone reading this know if there is a way to have Horizon change the series field in the bib record from 440 to 800 if an authority record with a 100 field replaces an authority record with a 130 field?
--
Thanks in advance for considering this,
Nate Cothran
Vice President, Authority Control
Backstage Library Works
533 E 1860 S Provo, UT 84606
(v) 800.288.1265 x255 | (f) 801.356.8220 | (e) nate@bslw.com <mailto:nate@bslw.com?subject=Automation%20Services%20-%20Query>
www.bslw.com | www.ac.blog.com <http://ac.bslw.com/community/blog/> | www.ac.wiki.com <http://ac.bslw.com/community/wiki/index.php5/Main_Page>
_____
Image removed by sender.
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Jeanette Navia Technical Services Professional Williamsburg Regional Library 7770 Croaker Road Williamsburg, VA 23188 (757)259-7742 www.wrl.org ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~