- Koha - lists.katipo.co.nz

transformation templates marc
by Victor Barroso Oliveira 08 Apr '22

08 Apr '22

Good afternoon, I received a demand to import MARC records (without the 952 in the marc) into a Library on Koha. I initially thought of creating an action in the "transformation templates marc" (as shown in the image), and then "Batch Record Editing" using the created template, however it didn't matter to the Library. How could I carry out this process? Thanks, MARC TRANSFORMAÇÃO.png <https://drive.google.com/file/d/1ZsEIxGNbas1_CkTO8z_Xir9Y81i7CnoN/view?usp=…>

1 0

2022 koha-US Annual Conference / KohaCon22 Webpage
by BRANNON, CHRISTOPHER 06 Apr '22

06 Apr '22

Good news! The 2022 koha-US Annual Conference / KohaCon22 webpage is now live. Visit the page at https://koha-us.org/events/conferences/kohacon22/, and be sure to check back as we update the site with more details. Christopher Brannon koha-US

1 0

koha-US Board Meeting reminder: Wednesday, April 6, 2022
by Jennifer Marlatt 05 Apr '22

05 Apr '22

The next koha-US Board Meeting is Wednesday, April 6, 2022. When: 8:30a PT / 11:30a ET (time converter <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.timea…> ) Where: https://us02web.zoom.us/j/293750042?pwd=SGQzS2pmU3prNFhYRHNaeTFhOHN4QT09 Agenda: https://docs.google.com/document/d/1c2Qh0Ksg44xE5KznbbRwW_5lhRSz5EvynF_ldsX… If you have additional topics for the agenda, please send them to secretary(a)koha-us.org Meetings are held via Zoom video conferencing. A microphone and webcam are recommended but not required. Zoom is available for Windows, Mac, and Linux on desktops, and Android and iOS on mobile devices. For help getting started, visit: https://support.zoom.us/hc/en-us/categories/200101697 <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.z…> These meetings are always free and open to any and all. Jennifer Marlatt koha-US Secretary secretary(a)koha-us.org

1 0

Re: [Koha] Database upgrade problems from KOHA 19.05 to KOHA 21.11 - solved
by Katrin Fischer 03 Apr '22

03 Apr '22

Hi, a lot of database changes are also about adding data like new system preferences. But there is another way to see where your database is actually at: Administration > System preferences > Tab Local Use > Version Entries in Local use cannot be searched for, so you need to navigate to it. A mismatch between this pref in the database and the installed version is what triggers the installer actually. Hope that helps, Katrin On 03.04.22 14:41, Harald Schaefer wrote: > > Thanks for your answers, it seems that the database upgrade was > successful up to Version 21.11, even if the last steps are not visible > in the apt_term.log files. > > I have compared the list of tables and columns for the test and the > production installation. > > The proposal of Mason shows only one missing upgrade > > Harald > > Am 01.04.22 um 17:57 schrieb Tomas Cohen Arazi: >> Those lines are only printed if it upgraded the db correctly. So it >> doesn't really look like it stopped. >> >> What is pointing you to the conclusion something went wrong? Is it >> that Koha keeps prompting you too do an upgrade? If such is the case >> then it is a caching issue and Mason's advice should fix it! >> >> El jue, 31 mar 2022 20:48, Harald Schaefer <fechsaer(a)gmail.com> escribió: >> >> Thanks for the answer. >> >> I omitted same parts of the test run, it ends with >> >> Upgrade to 21.11.02.004 [17:49:53]: Bug 29943 - Fix typo in >> NOTIFY_MANAGER notice >> Upgrade to 21.11.03.000 [17:49:53]: Koha 21.11.03 release >> >> KOHA 21.11.03 is the release I want to upgrade to >> >> My question is: >> >> Is it save to run >> >> sudo perl >> /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl >> <http://updatedatabase.pl> >> >> to add the missing database steps from 21.05 to 21.11. >> >> Regards Harald >> >> Am 31.03.22 um 20:34 schrieb Katrin Fischer: >> > Hi, >> > >> > actually the test run is the one that looks a little odd: >> > >> > Upgrade to 21.06.00.000 [17:49:33]: Increase DBRev for 21.06 >> >  Run, rabbit run.  >> > Dig that hole, forget the sun, >> > And when at last the work is done >> > Don't sit down it's time to dig another one. >> > >> > Is the first database change after the release of 21.05 and it >> marks the >> > begin of the development cycle. >> > >> > Upgrade to 21.05.00.000 [19:01:13]: Koha 21.05.00 release >> > >> > Is correct as the last update step for 21.05, a stable release. >> > >> > Hope this helps >> > >> > Katrin >> > >> > I am not sure what might have happened, maybe a difference in how >> > >> > On 31.03.22 12:15, Harald Schaefer wrote: >> >> Dear all, >> >> >> >> now I am promoted from a plain KOHA user to the system >> administrator >> >> of the computer hosting a KOHA installation of a railway museum in >> >> Germany. >> >> >> >> My first task was to upgrade the system from Ubuntu 16.04 to >> 20.04 and >> >> upgrading the KOHA system. I have tried this first twice on >> some local >> >> copies. In the test runs the database upgrade works fine. >> >> >> >> In the update run of the production system it stops at this point: >> >> >> >> Upgrade to 20.12.00.049 [19:01:13]: Bug 28108 - Move action logs >> >> 'SERIAL CLAIM' and 'ACQUISITION CLAIM' to a new 'CLAIMS' module >> >> Upgrade to 20.12.00.050 [19:01:13]: Bug 28108 - Add new >> >> systempreference OpacHiddenItemsHidesRecord >> >> Upgrade to 21.05.00.000 [19:01:13]: Koha 21.05.00 release >> >> >> >> Log started: 2022-03-29 19:04:34 # some other program >> >> >> >> In thetest runs it continues >> >> >> >> Upgrade to 21.05.00.000 [17:49:33]: Koha 21.05.00 release >> >> Upgrade to 21.06.00.000 [17:49:33]: Increase DBRev for 21.06 >> >>  Run, rabbit run.  >> >> Dig that hole, forget the sun, >> >> And when at last the work is done >> >> Don't sit down it's time to dig another one. >> >> >> >> The rabbitmq log show these entries for the time >> >> >> >> 2022-03-29 19:00:36.018 [info] <0.595.0> started TCP listener on >> >> [::]:5672 >> >> 2022-03-29 19:00:36.018 [info] <0.266.0> Running boot step >> >> cluster_name defined by app rabbit >> >> 2022-03-29 19:00:36.018 [info] <0.266.0> Running boot step >> >> direct_client defined by app rabbit >> >> 2022-03-29 19:00:36.158 [notice] <0.103.0> Changed loghwm of >> >> /var/log/rabbitmq/rabbit(a)tools.log to 50 >> >> 2022-03-29 19:00:36.496 [info] <0.8.0> Server startup complete; 0 >> >> plugins started. >> >> 2022-03-29 19:03:25.195 [info] <0.777.0> rabbit_stomp: default >> user >> >> 'guest' enabled >> >> 2022-03-29 19:03:25.281 [info] <0.793.0> started STOMP TCP >> listener on >> >> [::]:61613 >> >> 2022-03-29 19:03:25.329 [info] <0.765.0> Plugins changed; enabled >> >> [amqp_client,rabbitmq_stomp] >> >> 2022-03-29 19:03:27.678 [info] <0.800.0> RabbitMQ is asked to >> stop... >> >> >> >> Is there any way to continue the database upgrade? I have other >> >> applications running on the system and I do not want to start the >> >> complete upgrade process again. >> >> >> >> It seems that the not executed scripts are in >> >> /usr/share/koha/intranet/cgi-bin/installer/data/mysql/db_revs >> >> >> >> Basically the upgraded KOHA is running. >> >> >> >> Best regards Harald >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> Koha mailing list http://koha-community.org >> >> Koha(a)lists.katipo.co.nz >> >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> > _______________________________________________ >> > >> > Koha mailing list http://koha-community.org >> > Koha(a)lists.katipo.co.nz >> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha(a)lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >>

1 0

Database upgrade problems from KOHA 19.05 to KOHA 21.11
by Harald Schaefer 01 Apr '22

01 Apr '22

Dear all, now I am promoted from a plain KOHA user to the system administrator of the computer hosting a KOHA installation of a railway museum in Germany. My first task was to upgrade the system from Ubuntu 16.04 to 20.04 and upgrading the KOHA system. I have tried this first twice on some local copies. In the test runs the database upgrade works fine. In the update run of the production system it stops at this point: Upgrade to 20.12.00.049 [19:01:13]: Bug 28108 - Move action logs 'SERIAL CLAIM' and 'ACQUISITION CLAIM' to a new 'CLAIMS' module Upgrade to 20.12.00.050 [19:01:13]: Bug 28108 - Add new systempreference OpacHiddenItemsHidesRecord Upgrade to 21.05.00.000 [19:01:13]: Koha 21.05.00 release Log started: 2022-03-29 19:04:34 # some other program In thetest runs it continues Upgrade to 21.05.00.000 [17:49:33]: Koha 21.05.00 release Upgrade to 21.06.00.000 [17:49:33]: Increase DBRev for 21.06  Run, rabbit run.  Dig that hole, forget the sun, And when at last the work is done Don't sit down it's time to dig another one. The rabbitmq log show these entries for the time 2022-03-29 19:00:36.018 [info] <0.595.0> started TCP listener on [::]:5672 2022-03-29 19:00:36.018 [info] <0.266.0> Running boot step cluster_name defined by app rabbit 2022-03-29 19:00:36.018 [info] <0.266.0> Running boot step direct_client defined by app rabbit 2022-03-29 19:00:36.158 [notice] <0.103.0> Changed loghwm of /var/log/rabbitmq/rabbit(a)tools.log to 50 2022-03-29 19:00:36.496 [info] <0.8.0> Server startup complete; 0 plugins started. 2022-03-29 19:03:25.195 [info] <0.777.0> rabbit_stomp: default user 'guest' enabled 2022-03-29 19:03:25.281 [info] <0.793.0> started STOMP TCP listener on [::]:61613 2022-03-29 19:03:25.329 [info] <0.765.0> Plugins changed; enabled [amqp_client,rabbitmq_stomp] 2022-03-29 19:03:27.678 [info] <0.800.0> RabbitMQ is asked to stop... Is there any way to continue the database upgrade? I have other applications running on the system and I do not want to start the complete upgrade process again. It seems that the not executed scripts are in /usr/share/koha/intranet/cgi-bin/installer/data/mysql/db_revs Basically the upgraded KOHA is running. Best regards Harald

4 6

koha-US April 2022 Events & Meetings
by Jennifer Marlatt 01 Apr '22

01 Apr '22

koha-US online meetings and events are free and open to all. See our calendar for a full list: http://koha-us.org/calendar/. *Koha Community Challenge: Spring into Fitness * Join us for year two of this challenge, from wherever you are. Complete activities on your own time. Share those miles with the community! Learn more at https://runsignup.com/Race/CA/anywhere/KohaCommunityChallengeSpringintoFitn… *Meetings* Board Meeting - Wednesday, April 6 @ 8:30a PT / 11:30a ET / 15:30 UTC General Meeting - Wednesday, April 13 @ 8:30a PT / 11:30a ET / 15:30 UTC *Special Interest Groups* Circulation - Tuesday, April 5 @ 10:00a PT / 1:00p ET / 17:00 UTC Cataloging - April meeting has been canceled, next meeting May 5 System Administration - Tuesday, April 12 @ 8:00a PT / 11:00p ET / 15:00 UTC Acquisitions - Tuesday, April 19 @ 9:00a PT / 12:00p ET / 16:00 UTC Web Development - Thursday, April 21 @ 10:00a PT / 1:00p ET / 17:00 UTC Demonstration Instance - Tuesday, April 26 @ 8:00a PT / 11:00a ET / 15:00 UTC Books & Crafts - Wednesday, April 28 @ 5:00p PT / 8:00p ET / 00:00 UTC Visit http://koha-us.org/special-interest-groups/ to learn more and sign up for topic-specific mailing lists. Most meetings and events are recorded and made available at https://www.youtube.com/kohaus Jennifer Marlatt koha-US Secretary secretary(a)koha-us.org

1 0

Koha version 21.11.01 error 500 when saving authoratie
by Pedro Miguel Nunes Ferreira 01 Apr '22

01 Apr '22

Hello When i try to save an authoraty in the menu /cgi-bin/koha/authorities/authorities-home.pl and i make a change in the field 200, when i save i get error 500, but it saves the authoraity. If i change any other field instead of 200 , for example 300,400....and so on , it works perfectly The error i get in plack-error.log is, Can't call method "tag" on an undefined value at /usr/share/koha/lib/C4/Heading.pm line 69. What could be the problem. Thanks for the help --

1 0

The Terrific Every Other Thursday Training Video Season 2 / Episode 13: jQuery: Embiggening Your Selections
by BRANNON, CHRISTOPHER 31 Mar '22

31 Mar '22

Yes, you heard that right! You can now embiggen your selections to your hearts content. That is perfectly cromulent. Don't believe me? You'll just have to see for yourself. https://youtu.be/9Y0M0psOg0A Christopher Brannon koha-US

1 0

No CatSIG in Apr., next CatSIG May 5
by Hernandez, Heather H 30 Mar '22

30 Mar '22

Hello! Unfortunately I'll need to cancel the April Koha-US Cataloging SIG (I'll have to be traveling and a substitute host wasn't available), so the next Cataloging SIG will be on May 5, 8PT/11ET--there will be another email going out before then to confirm, remind, and provide details. So keep track of all those cataloging questions, comments, conundrums, and musings! Looking forward to May! Cheerio, h2 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ms. Heather Hernandez (she, her, hers) Technical Services Librarian Library catalog: https://keys.bywatersolutions.com/ San Francisco Maritime National Historical Park Research Center 2 Marina Blvd., Bldg. E, 3rd floor, San Francisco, CA 94123-1284 415-561-7032 (office generally M-W, telecommuting Th-F) heather_hernandez(a)nps.gov<https://webmail.lmi.net/src/compose.php?send_to=heather_hernandez%40nps.gov>

1 0

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