[Koha] Linking subject authority records to 650 via MarcEdit?

Thu Nov 10 04:33:52 NZDT 2016

Hi Paul,

Thanks very much for responding.

Our bib records were imported from an Excel flat file. Before import, the data were structured and formatted as best as possible to conform to ISBD punctuation and AACR2r standards. I also did a huge amount of bibliographic enrichment. This included validating the 6xx, 7xx, and 1xx fields against LC Authorities/LCSH using OpenRefine's reconciliation service (an RDF plugin). The problem we had, however, was that the legacy data in the controlled fields in our old system were not controlled by a MARC-based authorities database, which meant that our fresh Koha instance was going to be without a populated authorities db from the start. As it stands, we now have to populate it from scratch. This is opportune, though, because we can create one that is clean and devoid of any duplicate RLINs. We're already up to 300 authorities since September.

>> But I'm at a loss to understand how you can "save" a biblio without the 650 creating its own (proper or duplicate/erroneous) RLIN.

Well, the Excel flat file data in 6xx, 7xx, 1xx, etc. did not contain a $9 subfield with RLIN number, because there was no extant authorities database to cross-reference. The result was fully-validated and parsed headings in these fields in our Koha instance, but uncoupled from an authority file (no $9). Slowly, we're trying to change that by linking authorities to bibs in Koha the expected way, though the staff cataloguing interface. However, if we can do this in batches via MarcEdit, being extremely careful, it would speed up the process immensely. I just want to make sure my methodology is not missing something.

C

Craig Butosi, MA, MLIS, B Mus (Hons.)
LIBRARY SERVICES MANAGER
THE ROYAL CONSERVATORY
TELUS Centre for Performance and Learning
273 Bloor Street West
Toronto, ON M5S 1W2
416.408.2824 x338
www.rcmusic.ca

-----Original Message-----
From: Koha [mailto:koha-bounces at lists.katipo.co.nz] On Behalf Of Paul A
Sent: November-08-16 4:00 PM
To: koha at lists.katipo.co.nz
Subject: Re: [Koha] Linking subject authority records to 650 via MarcEdit?

At 08:26 PM 11/8/2016 +0000, Craig Butosi wrote:
>Hi Brain Trust,
>Koha 16.05.03 on Ubuntu 14.04 (package install) I am seeking advice for
>the following:
>Problem: 650 field text in bib records are not linked to Koha
>authorities database (via $9), but the text itself has been validated
>against LCSH (using OpenRefine). In other words, the text is in its
>authorized form, just not linked to its auth record.

Question: how were your biblio records created? Manually? Z39.50? or some sort of other "import"?

We have experienced, over the years, a few problems, but intrinsically can see a "9 (RLIN)" for every 650 entry. The biggest problem is that if -- for whatever reason, accident, stupidity, IT -- you have *two* authorities, same text, different RLIN, and the cataloguer doesn't do a "search, choose"
for a 650, then you get yet *another* RLIN adding up to eventually hundreds of non-cross-referenced but identical "authorities." If there's only one, single RLIN, then Koha finds it, uses it, perfection...

I'm fairly certain that most of our "duplicate RLINs" were my fault when I migrated ($deity forbid) Excel flat files through the 2010 version of MarcEdit. I was wet behind the ears, knew nothing, and in a hurry -- it's been biting me ever since ;={  And there's no (apparent) simple manner to sort it out, except go manually through every authority...

But I'm at a loss to understand how you can "save" a biblio without the 650 creating its own (proper or duplicate/erroneous) RLIN.

Disclaimer: Koha 3.8.24 from tarball.

Best -- Paul

>Solution: Link 650 field data with its extant authority using MarcEdit
>
>Process:
>
>
>1.       Run a Koha report to extract biblionumbers from records based on
>some Subject  (i.e., "Symphonies")
>
>2.       Import these records from Koha into MarcEdit using the batch
>search function on "Record Number" (upload a plain-text file with
>biblionumbers only)
>
>3.       Check that 650 data is in its authorized form.
>
>4.       Append a $9 subfield with the appropriate RLIN number to the
>batch (i.e., 650  //$aSymphonies --> 650  //$aSymphonies $917)
>
>5.       Upload batch back into Koha db.
>
>Questions:
>
>
>1.       Have any of you linked authority records to controlled variable
>fields using this method?
>
>2.       Is there anything I am missing?
>
>3.       Is this an utterly dangerous and careless way to be linking
>controlled fields to the Koha authorities db?
>
>Thank you!
>
>C
>
>Craig Butosi, MA, MLIS, B Mus (Hons.)
>LIBRARY SERVICES MANAGER
>the royal conservatory
>TELUS Centre for Performance and Learning
>273 Bloor Street West
>Toronto, ON M5S 1W2
>416.408.2824 x338
>www.rcmusic.ca<http://www.rcmusic.ca/>
>
>
>
>Note: This email message and any attachments are intended only for the
>use of the individual to which it is addressed, and may contain
>information that is privileged, confidential and exempt from disclosure
>under applicable law. If the recipient of this email is not the
>intended recipient (or the employee or agent responsible for delivering
>the email to the intended recipient), you are hereby notified that any
>review, dissemination, distribution or copying or other use of this
>message is strictly prohibited. If you have received this communication
>in error, please notify the sender immediately by return email and
>delete this message and attachments from your system, thank you.
>_______________________________________________
>Koha mailing list  http://koha-community.org Koha at lists.katipo.co.nz
>https://lists.katipo.co.nz/mailman/listinfo/koha

---
Maritime heritage and history, preservation and conservation, research and education through the written word and the arts.
<http://NavalMarineArchive.com> and <http://UltraMarine.ca>

_______________________________________________
Koha mailing list  http://koha-community.org Koha at lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha

Note: This email message and any attachments are intended only for the use of the individual to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the recipient of this email is not the intended recipient (or the employee or agent responsible for delivering the email to the intended recipient), you are hereby notified that any review, dissemination, distribution or copying or other use of this message is strictly prohibited. If you have received this communication in error, please notify the sender immediately by return email and delete this message and attachments from your system, thank you.