I have seen this message when loading bib data if there are no authorities loaded. I think it's a quirk of having no authorities in the database. I have got round it by creating a single authority. I believe the message is cosmetic but it is disturbing. Seems you have solved it anyway. Ian On Thu, 30 Jul 2020, 19:54 Stephen Graham, <s.graham4@herts.ac.uk> wrote:
Thanks for the reply Michael. We did have the BiblioAddsAuthorities sys pref set to allow. I changed to don’t allow, and now my script doesn’t generate the error. Hmmmmm…. We are not using authorities so I guess it’s OK keep this set to “don’t allow”?
Stephen
*From:* Michael Hafen (TECH) <michael.hafen@washk12.org> *Sent:* 30 July 2020 18:56 *To:* Stephen Graham <s.graham4@herts.ac.uk> *Cc:* koha-devel <koha-devel@lists.koha-community.org> *Subject:* Re: [Koha-devel] ModBiblio function error
I did a quick look over the code.
If your searchengine is set to Elasticsearch, then when ModZebra() is called it tries to index the record in the background at that time (at least that's the way it reads to me, I could be wrong).
Also if you have the BiblioAddsAuthorities preference set, then ModBiblio calls BiblioAutoLink() to update authorities links, which will create an authority record if the AutoCreateAuthorities preference is set, which calls AuthorityMarc::AddAuthority(), which calls ModZebra().
The error to me looks like it's trying to contact the search engine to add/update an authority record, and can't find it. But you have to have a lot of system preferences set just so to get that far. So I'm not sure that's what's happening.
On Thu, Jul 30, 2020 at 4:46 AM Stephen Graham <s.graham4@herts.ac.uk> wrote:
Hi All – I have a script which uses the ModBiblio function (i.e. https://perldoc.koha-community.org/19.11.x/C4/Biblio.html#ModBiblio). I haven’t used the script for a while, and we’ve upgraded to 19.11 since I ran it last. Running the script today and I’m getting the following “error”:
oAuth error: Database unavailable (109) authorities Bib-1
I’m seeing this 4-5 times for each bibilo I’ve updated. The update does work. The record looks fine in staff/OPAC, it’s findable etc. I’ve only updated 10 records on our test server, and before I update any more I’m just wondering why I’m getting this message and it will have an adverse effect on our indexing/database if I just ignore and update the reamining 6000+ records?
Any advice would be most welcome!
Cheers, Stephen
--------------------------------------
Stephen Graham
Library Technology Consultant
Content and Collections Team
Library and Computing Services
University of Hertfordshire
Tel: 01707 286111
Ext: 77751
Email: s.graham4@herts.ac.uk
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
--
Michael Hafen
Washington County School District Technology Department
Systems Analyst _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/