- Koha - lists.katipo.co.nz

Member of koha Ethiopia Defence University Mr. Tadesse Gebre
by Tadesse Gebre 21 Dec '23

21 Dec '23

How to member of Koha and dspace open software your community ?

1 0

Database discrepancy flagged after Koha upgrade
by City & Guilds of London Art School Admin 20 Dec '23

20 Dec '23

Hello, Platform: Ubuntu 20.04.6 LTS DB: 10.3.38-MariaDB Koha Version: 23.11 Since the most recent upgrade (using the package manager) from 23.05.x to 23.11.00, the following is returned in *About Koha -> System Information* ====== Data problems Some of your tables have problems with their auto_increment values which may lead to data loss. You should not ignore this warning. The problem is that InnoDB does not keep auto_increment across SQL server restarts (it is only set in memory). So on server startup the auto_increment values are set to max(table.id)+1. To know how to avoid this problem see the related wiki page: DBMS auto increment fix Problems found Bibliographic records The following IDs exist in both tables biblio and deletedbiblioitems: 2 , 3 , 4 ====== Note that the fix here: https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix has been implemented since we started with Koha, and that the five tests for data corruption documented there return empty sets. The mysql error.log reports no issues with parsing the bespoke init file etc. Investigating further I see that indeed: > select biblionumber, timestamp from deletedbiblioitems where biblionumber <= '8'; +--------------+---------------------+ | biblionumber | timestamp | +--------------+---------------------+ | 1 | 2023-01-13 11:00:38 | | 2 | 2021-06-09 14:06:34 | | 3 | 2021-06-09 14:06:52 | | 4 | 2021-06-09 14:06:57 | | 5 | 2021-06-09 14:07:00 | | 6 | 2021-06-09 14:07:06 | | 7 | 2021-06-09 14:07:10 | | 8 | 2021-06-09 14:07:13 | +--------------+---------------------+ 8 rows in set (0.000 sec) Whereas: > select biblionumber, timestamp from biblio where biblionumber <= '8'; +--------------+---------------------+ | biblionumber | timestamp | +--------------+---------------------+ | 2 | 2021-11-04 16:32:46 | | 3 | 2022-01-17 16:50:10 | | 4 | 2022-08-02 16:00:02 | +--------------+---------------------+ 3 rows in set (0.001 sec) Also: > select biblionumber, timestamp from deletedbiblio where biblionumber <= '8'; +--------------+---------------------+ | biblionumber | timestamp | +--------------+---------------------+ | 1 | 2023-01-13 11:00:39 | | 5 | 2021-06-09 14:07:02 | | 6 | 2021-06-09 14:07:07 | | 7 | 2021-06-09 14:07:12 | | 8 | 2021-06-09 14:07:14 | +--------------+---------------------+ 5 rows in set (0.000 sec) Correct me if I'm wrong, but my understanding is that Koha row counts should *always* be identical for the pair of tables: *biblio* and *biblioitems*, and also be identical for the pair *deletedbiblio* and *deletedbiblioitems*, since the latter is copied from the former. However, we have: > select count(*) from biblio; +----------+ | count(*) | +----------+ | 11508 | +----------+ 1 row in set (0.006 sec) > select count(*) from biblioitems; +----------+ | count(*) | +----------+ | 11508 | +----------+ 1 row in set (0.033 sec) > select count(*) from deletedbiblioitems; +----------+ | count(*) | +----------+ | 15777 | +----------+ 1 row in set (0.072 sec) > select count(*) from deletedbiblio; +----------+ | count(*) | +----------+ | 15774 | +----------+ 1 row in set (0.011 sec) Also, I was able to ascertain from backups that this discrepancy went back some way - at least till mid October '23 (which as as far back as our backups go), however, Koha did not report on it till after the most recent upgrade from 23.05 to 23.11.00. While this is easy enough to "solve" by removing records 2 - 4 from *deletedbiblioitems*, I have the following questions: *1.* If I run a query modeled on the existing queries for data corruption in the linked wiki page, unsurprisingly I get: > SELECT b.biblionumber FROM biblio b JOIN deletedbiblioitems db ON b.biblionumber=db.biblionumber; +--------------+ | biblionumber | +--------------+ | 2 | | 3 | | 4 | +--------------+ 3 rows in set (0.000 sec) So I'm wondering if the documented fix needs updating since it was last reviewed (11th December 2020). My guess is that an additional corruption test comparing *deletedbiblio* and *deletedbiblioitems*, and something like the below may be needed, but I would prefer someone a *lot* more knowledgeable about SQL (and Koha) to give their input, since my SQL skills are pretty basic: SET @new_AI_deletedbiblio = ( SELECT GREATEST( IFNULL( ( SELECT MAX(biblioitemnumber) FROM deletedbiblio ), 0 ), IFNULL( ( SELECT MAX(biblioitemnumber) FROM deletedbiblioitems ), 0 ) ) + 1 ); SET @sql = CONCAT( 'ALTER TABLE deletedbiblio AUTO_INCREMENT = ', @new_AI_deletedbiblio ); PREPARE st FROM @sql; EXECUTE st; 2. Although I can only check actual backups of the db back to mid October, it seems logical that this error has always existed since we got beyond 4 deleted records (presumably June 2021). So I'm wondering what causes Koha to flag it up now? 3. Is there any chance this could be caused by writes occurring during a mysqldump operation not run as a single transaction? 4. According to the wiki page the issue with persistence only affects < MariaDB 10.2.4. As we are running a later version presumably the statements have nothing to correct and I need to look elsewhere for a cause? Or is this just a case of the Wiki page needing an update? Thanks and all the best, Chris

1 0

Koha integration with other systems
by Russel G. P. Shihepo 20 Dec '23

20 Dec '23

Dear Community Does Koha support integrations such as: - Centralized Single-Sign-On Integration. - ERP Integration (Student and HRMs). - Payment gateway integration. I have been tasked by our school to make an attempt to integrate Koha with other systems at the institution. Thank you in advance. Regards, Russel

3 4

Debian Upgrade Error: 23.02.04-2 to 23.11.00-1
by skaman.tx＠gmail.com 19 Dec '23

19 Dec '23

Attempting to update Koha installation on Debian Bullseye host from 23.02.04-2 to 23.11.00-1. The following is the output and error message. Any ideas on how to resolve? # apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: koha-l10n The following packages will be upgraded: koha-common 1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 49.9 MB of archives. After this operation, 31.0 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://debian.koha-community.org/koha stable/main amd64 koha-l10n all 23.11.00-1 [32.4 MB] Get:2 http://debian.koha-community.org/koha stable/main amd64 koha-common all 23.11.00-1 [17.5 MB] Fetched 49.9 MB in 14s (3,540 kB/s) Reading changelogs... Done Preconfiguring packages ... /tmp/koha-common.config.bbiGxu: 49: koha-list: not found Selecting previously unselected package koha-l10n. (Reading database ... 182866 files and directories currently installed.) Preparing to unpack .../koha-l10n_23.11.00-1_all.deb ... Unpacking koha-l10n (23.11.00-1) ... dpkg: error processing archive /var/cache/apt/archives/koha-l10n_23.11.00-1_all.deb (--unpack): trying to overwrite '/usr/share/koha/misc/translator/po/am-Ethi-installer-MARC21.po', which is also in package koha-common 23.05.04-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../koha-common_23.11.00-1_all.deb ... Unpacking koha-common (23.11.00-1) over (23.05.04-2) ... Errors were encountered while processing: /var/cache/apt/archives/koha-l10n_23.11.00-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1)

4 7

Generating fine in every renewal
by JITHIN N 19 Dec '23

19 Dec '23

Dear community We are using Koha 22.11.07. In our Koha circulation rule patron category have maximum 5 time renewal allowed (Renewal Count) with time period of 10 days (Renewal period). In administration menu *Renewal Period Base* is calculated based on old due date of book and for late return every day 1 rupee is calculated as fine. A patron have overdue of a book which is not returned till date with 30 days late, his account shows accruing fine of 30 rupees. when the staff renew the book, along with 30 rupees an amount of 20 rupees creating with a total of 50 rupees. If again renew the book it again generating an amount 10 rupees along with 50 rupees with total of 60. Since the account have already fine till the date why Koha generating fine again based on new due date of renewal. is it a bug or any configuration need to change?

3 3

Koha Community on Slack
by BRANNON, CHRISTOPHER 18 Dec '23

18 Dec '23

Hi everyone! I wanted to let you all know, several months ago we morphed the koha-US Slack workspace into a Koha Community workspace. We have really enjoyed using Slack, but didn't want to limit the environment to just our user group. So, we opened it up to all. Please note that koha-US and the Koha Community do not endorse Slack in any way. We just recognize that there are folks that prefer communicating in Slack over IRC. This is in no way trying to replace IRC or force any one form of communication on the community. We simply want to provide another venue for people to utilize. If you like Slack, great! Put in a request to join the workspace. If not, just toss ignore this message. Anyway, I've posted a request form to join the Koha Community Slack workspace at https://koha-us.org/request-access-to-koha-community-on-slack/. If you fill it out, I'll send you a Slack invite. Sincerely, Christopher Brannon koha-US Admin

1 0

Setting up an SRU target
by Rubeno 18 Dec '23

18 Dec '23

Hello all, I'm trying to set up an SRU target and can't seem to find the way. The SRU server is the Austrian National Library. Here's the info for their SRU server: https://obv-at-oenb.alma.exlibrisgroup.com/view/sru/43ACC_ONB?version=1.2&o… They provide some more info here: https://labs.onb.ac.at/en/datasets/catalogue/ So I'm trying to look for a book that I know exists, because I can retrieve it in XML like this: https://obv-at-oenb.alma.exlibrisgroup.com/view/sru/43ACC_ONB?version=1.2&q… However I don't know what to set up in the 'Additional SRU options' field. I've tried several combinations of "sru=get,sru_version=1.2,operation=searchRetrieve", but I never get any hit. As for the SRU field mapping, I'm trying this: title=title,isbn=isbn,author=creator,issn=issn,subject=subjects The manual https://software.indexdata.com/yaz/doc/zoom.html that is linked to in the Koha interface is complete gibberish to me. I have no installation of my own yet (still deciding whether Koha is manageable for my association), so I'm using this demo server: https://intra1.orex.es/ Can anybody help, at least describing a working setup for other SRU targets? Thanks! Rubeno

2 1

Re: [Koha] Setting up an SRU target
by Rubeno 18 Dec '23

18 Dec '23

Thanks, Rainer, but unfortunately the connection doesn't seem to work at all with your setup... It doesn't retrieve a thing, no matter what I try to search. What can be the problem? Also, is the Austrian National Library included in K10 at all? I specifically need access to their catalogue, because I'm cataloguing the library of our Esperanto association and I wished to take advantage of the records of the Department of Planned Languages: https://www.onb.ac.at/sammlungen/sammlung-fuer-plansprachen Do you know how to get an account? Or otherwise, what to ask the ANB to get one? How come that living and working in Austria you don't qualify? Thanks El 18/12/23 a les 7:38, Stowasser Rainer ha escrit: > Dear Rubeno > > Im not using the Austrian National Library > although Im Austrian ;-) > cause for the obvsg sru you need an account .... > > You will find everything through K10 > > and this is the configuration (koha 22.05) > > see attached pictures > > first the main setup > and then the databases to search > > Kind regards > Hofrat Mag. Rainer Stowasser > Geosphere Austria IKS-Services > Vice Head Library, Publisher, Archive > branch manager Hohe Warte >

1 0

Koha rest API OAuth authentication fails
by Coehoorn, Joel 18 Dec '23

18 Dec '23

I asked a question yesterday about API access to setup EBSCO catalog sync, and that is moving forward now, as they will be using the public API. While working on that I also spent some time looking at the other API endpoints. I am able to use the authenticated APIs, but only if I login via our normal SAML SSO process first and then make the API calls on the authenticated session. I would like to eventually be able to use OAuth for some things here. However, I was not able to make OAuth work. Specifically, I am able to successfully request a token and set it with "Bearer " in the Authorization header, but no matter what I try I get 401 response with {"error":"Authentication failure."}. I've tried powershell and Postman from my own machine, and curl while logged into the koha server directly, but nothing I do seems to change anything. The user owning the API keys used with the request definitely has the needed permissions, and I even tried issuing an API key for a superlibrarian just to be sure. The RestPublicAPI and RESTOAuth2ClientCredentials system preferences are both enabled. What could I be missing? *Joel Coehoorn* Director of Information Technology *York University* Office: 402-363-5603 | jcoehoorn(a)york.edu | york.edu *Please contact helpdesk(a)york.edu <helpdesk(a)york.edu> for technical assistance.* The mission of York University is to transform lives through Christ-centered education and to equip students for lifelong service to God, family, and society

2 1

Syndetics Unbound.
by Raymund Delahunty 15 Dec '23

15 Dec '23

We have been a Syndetics user for years and have the features enabled via the Syndetics system preference. But we have been offered the Syndetics Unbound upgrade, and have been told we can enable the Unbound service by adding a piece of javaScript in opac-detail.tmpl in the opac-tmpl/modules directory. But our support company has said they no longer make modifications to page template files as these deviate from the community code and are often unsustainable on upgrade. And anyway our OPAC is massively customised. I am struggling to understand how our OPAC will look like if we did add the JS, given how the OPAC in the documentation looked like. It showed Unbound content all over the OPAC page shown (the LMS system was undefined in the screen grabs). Has anyone enabled the Syndetics Unbound service in a significantly customised OPAC? Ray Delahunty University of the Arts London This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of UAL Short Courses Limited the following also applies: UAL Short Courses Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY

1 0