- Koha - lists.katipo.co.nz

Fwd: update error
by Katrin Fischer 29 Mar '22

29 Mar '22

Hi Ana, please always keep conversation on the mailing list, so others can help you too. It looks like REGEXP_REPLACE might be a feature only available in newer MySQL versions. It doesn't seem to appear in the 5.7 manual, but only in the 8.0 manual, but I am having trouble finding the version it was introduced in. What OS are you using and is updating the DBMS or switching to MariaDB an option? Katrin -------- Forwarded Message -------- Subject: RE: update error Date: Tue, 4 Jan 2022 12:10:58 +0000 From: anabela semedo <anabela556(a)hotmail.com> To: Katrin Fischer <katrin.fischer.83(a)web.de> Hi Katrin, thanks for your time. I use the mysql, version 5.7.38 I still couldn't solve it. do I have to uninstall everything? Upgrade to 21.05.00.016 [14:16:28]: Bug 24387 - Rename opac_news with additional_contents ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: FUNCTION koha.biblioteca.REGEXP_REPLACE does not exist at /usr/share/koha/lib/C4/Installer.pm line 738 Thanks again, Ana Bela *De:*Katrin Fischer [mailto:katrin.fischer.83@web.de] *Enviada:* sábado, 1 de janeiro de 2022 10:53 *Para:* anabela semedo <anabela556(a)hotmail.com>; Koha <koha(a)lists.katipo.co.nz> *Assunto:* Re: update error Hi Ana, better to copy the error into the email as attachments will be removed on the mailing list: Upgrade to 21.05.00.016 [14:16:28]: Bug 24387 - Rename opac_news with additional_contents ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: FUNCTION koha.biblioteca.REGEXP_REPLACE does not exist at /usr/share/koha/lib/C4/Installer.pm line 738 Are you using MySQL or MariaDB and which is the version? Katrin On 30.12.21 17:36, anabela semedo wrote: hello ever one i have a problem here, trying to update koha to the latest version and i have this error here that i am not able to resolve. can anybody help me? thankyou. Ana Bela Semedo

3 2

Re: [Koha] FW: How to link authority data via existing number?
by Michael Kuhn 29 Mar '22

29 Mar '22

Hi Ray Thanks for your message! Today you wrote: > Has anyone else responded- I don't see anything in the Koha List, and > I am a bit shy (zurückhaltend?) to respond on-list. No, unfortunately noone has responded until now. Thus I was looking through the mailinglist archive and eventually found posting https://lists.katipo.co.nz/public/koha/2021-January/055713.html where Katrin Fischer said to her knowledge there is currently no way to avoid this renumbering. > I've never quite liked the policy of the bibliographic record control > number in Koha being 999$c rather then being in MARC 001. So most of > our records moved from the Voyager LMS had the old Voyager RCN remain > in 001 (and so were utterly useless), and the new RCN > (biblio.biblionumber) was added as 999$c as the record was added at > migration. But the authority record control number appears to be > different. Unlike it being in the AUTH 999$c (there's nothing so nice > as consistency!) it appears to be the MARC 001. > > So is it a situation that when the authority records have been loaded > into Koha, the authid written to the authority 001 starts at 1 and > increased sequentially has over-written the local (former LMS) > authority control number? No it does not overwrite a number already existing in MARC 001. An authority record with content in MARC 001 just remains unlinked. If MARC 001 is empty the linker adds a new number and links title data records to that new number. With "linker" I mean the Perl script "link_bibs_to_authorities.pl" using the following system preference (standard) settings: * CatalogModuleRelink: Don't * LinkerKeepStale: Don't * LinkerModule: default * LinkerOptions: (empty) * LinkerRelink: Do > If that's what's going on, and if the authority for Ralph Lansky is > the 704th authority record loaded, the AUTH 001 will be 704 and > STA101744 will be thrown away? Then when the relinker runs it will > create an biblio 100 thus: > > 100 1\$9 704$a Lansky, Ralph > > You ask: "How can we successfully link title data records via existing > numbers in MARC 001 of the authority record?". I have no idea... maybe > you can't, and you have to accept the Koha-assigned authid. For the moment I believe it is not possible to load existing authority data with given numbers and link them in a proper way to existing title data records using these numbers. Instead it is only possible to use the linker which indeed produces links but not according to the original linking. So the produced links are in many ways wrong and the linker leaves many authority records unlinked. Of course this will be a problem for example when you have two (or more) identical names which don't identify the same person/corporation/topic. It is an even bigger problem in other cases but I won't go deeper into that. Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch > -----Original Message----- > From: Koha <koha-bounces(a)lists.katipo.co.nz> On Behalf Of Michael Kuhn > Sent: 18 March 2022 20:43 > To: Koha <koha(a)lists.katipo.co.nz> > Subject: [Koha] How to link authority data via existing number? > > Hi > > In our library we are migrating from our current system to Koha 21.11. > > We have migrated existing authority data and created for example > > Title data record > * MARC 100$9 STA101744 > * MARC 100$a Lansky, Ralph > > Authority data record (PERSO_NAME) > * MARC 001 STA101744 > * MARC 100$a Lansky, Ralph > > Both kinds of records were successully loaded, after that we tried to link these records using script "link_bibs_to_authorities.pl" but it failed. We expected this would create a link between title record and authority record via number STA101744 but instead the content of MARC > 001 of the authority record was surprisingly replaced by a new number and it linked only to one title record that didn't have content in MARC > 100$9 but did contain (another) "Lansky, Ralph" in MARC 100$a. While the actual records containing MARC 100$9 STA101744 were not linked to the authority record and seem to have been ignored. > > How can we successfully link title data records via existing numbers in MARC 001 of the authority record? > > Best wishes: Michael > -- > Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch

1 0

Koha Community Newsletter: March 2022
by Koha Newsletter 28 Mar '22

28 Mar '22

The Koha Community Newsletter for March 2022 is here: https://koha-community.org/koha-community-newsletter-march-2022/ Many thanks to everyone who submitted articles and news to this newsletter! Please feel free to email me with any corrections or suggestions. -- Michael Kuhn Editor, Koha Community Newsletter

1 0

Re: [Koha] Forgiving all overdue fines
by Charles Kelley 25 Mar '22

25 Mar '22

Hello, Raymund! In our latest exchange, on 25 Mch. 2022 at 08:01 [JST], I read this from you through the Koha Discussion Group: We do not have any write access to the tables and any database updates are > done by our support company. I understand they have a script they run to do > the business. > > I think what PTFS were offering was a simple report for us to run to > provide that ‘report for posterity’, but I had already obtained those > details when I asked senior management for approval to have the fines > removed. They may also have wanted to see how big the job would be for > their script. > > I doubt very much if the report processor would accept UPDATE clauses, > even if I was logged in as a user that had write access to the tables. I > know I have to be very careful not to include words like UPDATE or DELETE > when writing reports (say, in tips to users running a report where they > have to enter something like a date range). Use of these bad words causes > an error in the SQL. > I didn't think Koha would include SELECT, SET, DELETE, and UPDATE statements (and other SQL statements) because it's all too easy to damage or delete a large portion of the database. Even seasoned database professionals have been know to lose a large portion of their database. GUIs mitigate against that possible outcome even though it can still happen. Thanks for your response. -- よろしくお願いします。 -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.

1 0

Koha 19.11.28 released
by Wainui Witika-Park 24 Mar '22

24 Mar '22

Hello everyone! The Koha community is proud to announce the release of version 19.11.28. The full release notes can be found at: https://koha-community.org/koha-19-11-28-released/ Thank you to everyone involved! Cheers, Wainui Witika-Park (she/her)

1 0

Re: [Koha] Item Inventory Number Error 500
by Tadas G 24 Mar '22

24 Mar '22

Hello, I found that inventory number MARC frameworks (add screenshots): https://we.tl/t-6bUXaU5LCT 995 j in Advanced constraints: not have Koha link Koha to MARC mapping: items.stocknumber 995 j Inventory number Other screen shots i add to other post: https://lists.katipo.co.nz/pipermail/koha/2022-March/057534.html Thanks for the help

2 1

Introduction
by Thiago Souza 24 Mar '22

24 Mar '22

I would like to add a company on the paid support list Here are the details: Company Name: Neki Contact Person: Thiago Souza Contact email: thiago.souza(a)neki-it.com.br Website: https://www.neki-it.com.br Telephone: +55 79 999209364 best regards, * THIAGO SOUZA* *ACERVOS DIGITAIS* t.+55 (24) 2237-1839 c.+55 (79) 99920-9364 http://www.neki-it.com.br <https://www.neki-it.com.br/>

2 1

Koha 21.05.13 released
by Andrew Fuerste-Henry 24 Mar '22

24 Mar '22

The Koha community is proud to announce the release of version 21.05.13. This is a maintenance release and contains many bug fixes and enhancements. As always you can download the release from: https://download.koha-community.org Thank you very much to everyone involved in this release. For further details, please see this blog post <https://koha-community.org/koha-version-21-05-13-released/>. -- Andrew Fuerste-Henry Educator (he/they) ByWater Solutions bywatersolutions.com Phone:(888)900-8944 <(888)%20900-8944> What is Koha? <http://bywatersolutions.com/what-is-koha/>

1 0

Koha 20.11.17 released
by Victor Grousset/tuxayo 24 Mar '22

24 Mar '22

Hello! :) The Koha Community is happy to announce the release of Koha 20.11.17 The full release notes can be found at: https://koha-community.org/koha-20-11-17-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo

1 0

Koha 21.11.04 released!
by Kyle Hall 24 Mar '22

24 Mar '22

The Koha community is proud to announce the release of version 21.11.04. Thank you very much to everyone involved in this release! The release notes can be found at https://koha-community.org/koha-21-11-04-released/ Kyl*e*

1 0