Biblio number is only relevant for bibs. What should be used for authorities? That is what I was referring to below but the problem may be common to both objects.
-Doug- On Sep 3, 2012 9:49 AM, "Jared Camins-Esakov" <jcam...@cpbibliography.com> wrote: > Doug, > > I would concur that 001 and 003 need to be taken together to have any >> chance of a unique identifier. Our library has our own unique 003 >> (UkLoVW). For indexing, I suspect a better key to hand to zebra would be >> the system control number (035 $a). Are these kept unique by koha? >> > > We already have a unique identifier, the biblionumber. It's stored in > 999$c. The bug in this case is that the DOM indexing uses the contents in > 001 if you have it populated. > > >> While I do believe this is a problem, I am not sure how this would the >> cause of our ModAuthority failures however, unless I am missing something. >> See the other mail thread for details (3.8.4 Error message when editing >> authorities). Its possible these issues are related but I am not sure. >> > > The ZOOM error you reported might have something to do with this, but I > just don't know. I don't think I've ever seen problems with ZOOM element > (as opposed to attribute) before. > > Regards, > Jared > > -- > Jared Camins-Esakov > Bibliographer, C & P Bibliography Services, LLC > (phone) +1 (917) 727-3445 > (e-mail) jcam...@cpbibliography.com > (web) http://www.cpbibliography.com/ > > _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha