It worked for us after a couple problems were fixed with our data. The link occurs in the subfield 9 (MARC 21) of the appropriate field in the biblio. When the field is linked to the authority record, the number in the authority record's 001 field will appear in $9 (but you will probably only see the number in editing mode). If your linking doesn't work, check the MARC framework to make sure you've got a $9 in that field. We had a problem with linking the first couple tries. The problem was in the 008 field in the authority records. Position 14 and 15 must be set to 'a' for the linking to work. Also, Koha will automatically create the 001 number in the authority records. It will overwrite anything you have in that field, though my IT wizard (whom I've CC'd just in case he's got any other tricks up his sleeve) managed to force it to accept our last import with the original numbers. Hope this helps, I'm the librarian half of the team, so the serious IT stuff is occasionally lost on me. Elaine On Fri, Feb 18, 2011 at 7:09 PM, Peter Huerter <pete.huerter@gmail.com> wrote:

Thanks Elaine.  I am in the process of trying your method.

Have you had any problems using link_bibs_to_authorities.pl?  It seems to have received some mixed reviews and my initial experiment failed to link the new authorities to existing biblios.

E.g. http://koha.1045719.n5.nabble.com/koha-bibs-authorities-problem-tp3050690p30...

"If you want a best result, you need to re-implement link_bibs_to_authorities.pl with a better matching algorithm"

Did you have to re-implement a better matching algorithm?

Thanks, Pete.

(btw I tried to write a script to do what I wanted in my original post and found that it is not as easy as I thought.  I found that I could not rely on SimpleSearch (and zebra) to find a recently added Authority.  I decided to move on after many failed attempts at trying to fix this).

-- View this message in context: http://koha.1045719.n5.nabble.com/bulk-BiblioAddsAuthorities-tp3378000p33916... Sent from the Koha - Discuss mailing list archive at Nabble.com. _______________________________________________ Koha mailing list  http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

-- Elaine Bradtke Data Wrangler VWML English Folk Dance and Song Society | http://www.efdss.org Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY Tel    +44 (0) 20 7485 2206 ext 36 -------------------------------------------------------------------------- Registered Company No. 297142 Charity Registered in England and Wales No. 305999 --------------------------------------------------------------------------- "Writing about music is like dancing about architecture" --Elvis Costello (Musician magazine No. 60 (October 1983), p. 52)

I have similar problems (Koha 323 on Debian 6). In my opinion, Pete, your auth records are good, since they are imported and indexed correctly. The fault seems to be in link_bibs_to_authorities.pl. Debugging it, I think that C4/Heading.pm adds too much query limiters when trying to find an authority entry starting from values stored in biblio fields. For instance, in the case of authors, the limiter "AND Heading-use-main-or-added-entry=a" introduces the error. So I commented out lines 142-152 of C4/Heading.pm and every author was correctly linked to its own authority. Up to now I don't know it this is a known bug or if Koha 325 solves it. HTH. Stefano On Feb 28, 2011, at 16:52 , Peter Huerter wrote:

Thanks Elaine. I'm still having trouble getting my auth records to link with my biblio records.

Our process is this: 1) Import biblios into koha (without any authority information).

2) Take a dedup't list of authors in a CSV file, and run it through MarcEdit to create a compiled .mrc file of authorities. (I also add 040 info here, and define my own LDR, and 008 but nothing else)

.csv file: Zumwalt, Elmo R. Jr Zimmerman, Linda

.mrk file: =LDR 00000nz a2200000o 4500 =008 110225000000|||a||||aa|||||||||||||||||d|||||| =040 \\$aOPIACS$bENG$cOPIACS =100 \\$aZumwalt, Elmo R. Jr

=LDR 00000nz a2200000o 4500 =008 110225000000|||a||||aa|||||||||||||||||d|||||| =040 \\$aOPIACS$bENG$cOPIACS =100 \\$aZimmerman, Linda

3) Import the compiled authority list into Koha using bulkmarcimport, and re-index Zebra. perl bulkmarcimport.pl -a -file /home/paul/first_authorities2.mrc -match=pn,100a -v 2 perl rebuild_zebra.pl -a -r -v

4) Run the linking script. perl /usr/share/koha/bin/link_bibs_to_authorities.pl --verbose

The authority records are successfully imported into Koha (I can do an authority search and find them), but each search result report that 0 biblios are linked with "this" authority.

The linking script appears to do the opposite of what we want. It actually removes authority links that are already present (I added an authority before running the linking script. I'm able to add the link by editing a given biblio in Koha. Koha adds it automatically - See my original post on this thread). Existing links are gone (reporting "0 biblios"), and no new links are added.

I am using the following LDR, and 008 fields:

LDR: 00000nz a2200000o 4500

008: 000000|||a||||aa|||||||||||||||||d||||||

(I'm sure there are bibs to be linked with these authorities.)

Any ideas? Do you use MarcEdit? Would you be able to provide a sample MARC record for one of your authorities please?

Thanks again, Pete.

-- View this message in context: http://koha.1045719.n5.nabble.com/bulk-BiblioAddsAuthorities-tp3378000p34034... Sent from the Koha - Discuss mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

On Mar 1, 2011, at 19:54 , Peter Huerter wrote:

Thanks Stefano.

Unfortunately it's not working for me - yet :)

In your post you describe commenting out lines 142-152 of C4/Heading.pm. In my Heading.pm file this would also comment out the return statement of _query_limiters. Is your _query_limiters effectively reduced to the following?

sub _query_limiters { my $self = shift; my $limiters = " AND at='$self->{'auth_type'}'"; return $limiters; }

Yes.

When I modify _query_limiters as above and rerun link_bibs_to_authorities.pl the linking still does not occur.

Are you able to show me some raw MARC showing an authority linked with a biblio? I understand basically that _9 subfields are added.., but what I am wondering is if my MARC format is somehow missing some important info (or at least our delta may provide some clues).

E.g. I am trying to link the following biblio with the following authority using link_bibs_to_authorities.pl:

LDR 00572nam a2200193Ia 4500 003 OPIACS 005 20110225150523.0 008 110224t20001998xx 000 0 und d 020 _a0964513331 040 _cOPIACS 100 1 _aZimmerman, Linda

link_bibs should add $9 to this tag, copying the 001 tag of the auth rec

245 10 _aGhosts of Rockland County _cZimmerman, Linda 250 _a2000 260 _bSpirited Books _c1998 _g2000 300 _3pamphlet 650 7 _ashanties _2OPIACS 942 _2ddc _cAU 952 _40 _xpamphlet, fine _esw _00 _912234 _bOPIACS _10 _d2011-02-24 _zindian rock, _8shanties _71 _cshanties _g1.00 _yBK _aOPIACS 999 _c12223 _d12223

000 - LEADER @ 00229nz##a2200097o##4500 003 - CONTROL NUMBER IDENTIFIER @ OPIACS 005 - DATE AND TIME OF LATEST TRANSACTION @ 20110301130115.0 008 - FIXED-LENGTH DATA ELEMENTS @ 110301000000|ge|dz||aaan|||||||||||||||c|||||d 040 ## - CATALOGING SOURCE a Original cataloging OPIACS b Language of catalogi eng c Transcribing agency OPIACS 100 ## - HEADING--PERSONAL NAME a Personal name Zimmerman, Linda

Both of these records are in my database and are found in Koha.

A more general question. You mention "debugging Koha". How do you go about debugging Koha?

Well, I'm able to debug a perl script at a time. In this case I used perl -d link_bibs_to_authority and I followed its work step by step down to C4::Heading::_query_limiters where the query string is built. Sorry: I don't understand why your attempt with the patched _query_limiters doesn't work... Of course I assume you can find the auth rec searching for Perso_name Zimmerman, Linda, and that the result is 1. HTH anyway. Stefano

Hello Pete, I don't know if you solved your problem yet but I had a similar problem this weekend which I solved somehow. This is my solution. I wanted to import both authorities and biblios and then link them. Note that I was importing from a system which already had the link in the form of an id stored in 200@6. First I imported authorities. I wrote a script which parsed the marc for the authorities and stored the old id in a field (900@6) before importing. Then, after the import I wrote another script which parsed the marc for biblios, connected to the db to get the newid (something like: select authid newid, marcxml from auth_ header where extractvalue(marcxml,'//datafield[\@tag=900]/subfield[\@code=6]') = '$aid'", actually I created a temp table to store the association for speed). I stored the newauthid from koha in the 9 subfield of the auth linked field. Upon import of biblios the link was present and working. If you don't have the id you can probably still perform a per name search. Regards, Len www.len.ro On 03/03/2011 05:17 PM, Peter Huerter wrote:

The XML in the last post is being automatically processed away, so here it is in a text file attachment:

http://koha.1045719.n5.nabble.com/file/n3408083/mymarc.txt mymarc.txt

Cheers, Pete.

-- View this message in context: http://koha.1045719.n5.nabble.com/bulk-BiblioAddsAuthorities-tp3378000p34080... Sent from the Koha - Discuss mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

Le 07/03/2011 21:55, Peter Huerter a écrit :

Dear Koha developers,

I would like to bump my original post (previous title "bulk BiblioAddsAuthorities").

addbiblio.pl appears to be called when one chooses "Edit Record" from the koha admin biblio details page. This code appears to call BiblioAddAuthorities and I *really like* the result. Authorities are generated for authors, subjects, and secondary authors. Even better the string "machine generated" is used in the added authorities to mark them as being created automatically. This is great! I would like to do this in batch for all of our biblios since we manage our own authorities in house. I would really like to make use of this feature since it works so well in the singleton case. However I have run into problems writing a perl script to do this.

I have a script working that iterates through a list of biblios calling BiblioAddAuthorities however I have one problem related to bulk processing, a temporal issue, or perhaps a caching issue(?).

BiblioAddAuthorities relies on SimpleSearch to search for existing authorities. However when I am processing in batch SimpleSearch fails for *recently added authorities*. I think SimpleSearch relies on Zebra.

I've tried adding dbh->commits, and re-indexing zebra before processing each biblio, but this does not seem to solve my problem. When my script exits, SimpleSearch finds recently added authorities. It is almost like there is a lazy write, or caching middle-layer getting in the way (but probably working very well for it's intended purpose of course).

It seems that recently added authorities are stuck in some sort of cache somewhere? At the SQL level? At the Zebra layer?

How do I make sure that Zebra, and SQL are written to so that SimpleSearch has the latest up-to-date data to base it's search on? SimpleSearch is relying on zebra. In order to make sure that it is indexed, you should index before your bulk edition goes. Hope that helps. -- Henri-Damien LAURENT

Here is the code. http://koha.1045719.n5.nabble.com/file/n3791805/acsauthlink.pl acsauthlink.pl http://koha.1045719.n5.nabble.com/file/n3791805/callacsauthlink callacsauthlink I hope this helps someone. Comments welcome. Pete. -- View this message in context: http://koha.1045719.n5.nabble.com/bulk-BiblioAddsAuthorities-tp3378000p37918... Sent from the Koha - Discuss mailing list archive at Nabble.com.