- Koha-devel - lists.koha-community.org

cannot display branchname and patron category description in card layout
by Zahid Iqbal 20 Sep '23

20 Sep '23

Hi, In koha 22.11 can someone guide to print branchname and patron category description on pdf file for patron card creator 1. print branchname not branchcode 2. print patron-category-description not categorycode what are the values i have to type in text box for field1 and field2 in patron card layout for printing branchname and patron-category-description? i am stuck with this problem and cannot find any other solution Can anyone suggest that i have to change the code or is there any other way that it can be solved? I am not an expert in coding, any help will be appreciated. Best Regards -- *Zahid Iqbal*

1 0

Warning: KTD problems with latest master
by Tomas Cohen Arazi 19 Sep '23

19 Sep '23

Hi all. Today we pushed to master a needed upgrade for Cypress. The new Cypress configuration file that is included in the master branch IS NOT COMPATIBLE with older Cypress versions, and thus you need to pull the latest KTD image in order for things to work. I didn't expect a `ktd up` to fail because of this, but that's where we are at. If someone has the time/bandwidth to look for options to overcome this, much appreciated! [1] Otherwise, just pull the latest images as usual: `ktd pull` Kind regards [1] We could be running Cypress on a separate container instead, but it requires some ideating as it would evolve refactoring how we run tests in Jenkins as well i.e. a single run to launch the tests vs. launching KTD and then sequentially running some tests and then the cypress ones. It should be doable, but tricky and needs a lot of thinking. -- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

3 2

unsubscribe please
by Muhammad Shafiq Rana 17 Sep '23

17 Sep '23

Thanking you, *Dr. M. SHAFIQ RANA Ph.D.(Homeopath)* *M.Phil.-LIS, UOS* *DHMS-NCH, HRMP (**Member LMHI**)* *Dental Hygienist-PMF, RDH **(**Member PDHA**)* *LIS Trainer, Career Counselor, Motivational & **Spiritual* *Speaker* *Mobile: +92-333-521 61 65* www.shafiqpk.blogspot.com

1 0

ktd and persistent data
by januszop＠gmail.com 16 Sep '23

16 Sep '23

Hi All, This is (probably) my first post on this list. I had the pleasure of meeting some of you recently in Helsinki (and before that in Dublin in 2019). I live in Krakow, Poland and take care of several Koha installations in medium-sized scientific and theological libraries. Much of my time is spent analyzing and correcting bibliographic data. However, if my libraries encounter any problems in Koha, I try to report them in Bugzilla and, if possible, provide patches as well (I sent the first official patch in 2011). Sometimes I don't have enough patience or time and I patch problems locally (forgive me, I feel guilty here)... The Helsinki meeting encouraged me to use ktd more intensively. Here, however, I run into a problem trying to use persistent data (kp command as described at https://gitlab.com/koha-community/koha-testing-docker/-/wikis/Koha-Testing-D ocker). Docker creates the koha_db-data volume as expected. However, after shutting down the test environment (with kd command), when trying to run it again (kp), the koha container does not start properly -- it ends with the message: Database is not empty! at /kohadevbox/misc4dev/populate_db.pl line 103. Indeed, the populate_db.pl script is executed unconditionally when starting this container. Question: what am I doing wrong or what did I not understand? What should be the scheme of working with persistent data? I would appreciate a hint. Greetings, Janusz

2 1

Call for news - Newsletter September 2023
by Koha Newsletter 13 Sep '23

13 Sep '23

Hi I'm collecting news for the September 2023 Koha Community Newsletter. Please send anything noteworthy to: kohanews (at) gmail (dot) com News criteria: * News items can be of any length. * Images are fine. * Anything and everything Koha. * Submit by the 26th of the month. Text format criteria: * Just structured plain text, or * HTML text to include tables or similar For events: * Consider adding your event to the Koha Community calendar at https://koha-community.org/calendar/ Thank you! Michael Kuhn Editor, Koha Community Newsletter

1 0

stuck emails to koha-devel?
by Philippe Blouin 12 Sep '23

12 Sep '23

Hi! Someone here (Shi Yao) has been trying to write to koha-devel starting two weeks ago. The emails never got through, nor he got any followup from koha-devel-owner. Anyone could help? That would be greatly appreciated. -- Philippe Blouin, Directeur de la technologie Tél. : (833) 465-4276, poste 230 philippe.blouin(a)inLibro.com inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>

5 4

Timeout trying to edit SQL Reports Library
by David Cook 11 Sep '23

11 Sep '23

Hey folks, Has anyone tried editing the SQL Reports Library wiki for a while? I'm getting the following error when I try now: Error contacting the Parsoid/RESTBase server: (curl error: 28) Timeout was reached It's too bad because I just wrapped up a nice little report.. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

3 2

Importing items with "foreign" branches fails badly
by Philippe Blouin 11 Sep '23

11 Sep '23

Hello! When importing a marc file where some items homebranch are not matching a branchcode in db, the import fails. Freeze-fail. Before, it used to just skip those items, but it seems (since 23.05) to just fail silently (with a constraint failure in the log, but nothing for the user). Is it our install or it's a known issue? When running "show engin innodb status", I get some row lock. Looking at the bug list, I found nothing. There are many ways to fix this, and we don't want to head into one to be told "ooh, this should be fixed there instead". * Upstream https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21272 Maybe there could be an option in staging to overwrite the homebranches that do not correspond? * Just ignore the item, as before. But at least leave some info about it in the result page. * Fail as soon as it happens. Do not import and tell the user to correct the data ? The first option doesn't solve bulkmarcimport.pl :( Feedbacks would be appreciated. -- Philippe Blouin, Directeur de la technologie Tél. : (833) 465-4276, poste 230 philippe.blouin(a)inLibro.com inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>

4 5

Re: [Koha-devel] koha-elasticsearch verbosity issue
by Nick Clemens 08 Sep '23

08 Sep '23

Can you provide some examples of the log messages? That might help identify where they are coming from. You could also raise the commit number to generate fewer requests/responses? On Fri, Sep 8, 2023 at 9:13 AM Nick Clemens <nick(a)bywatersolutions.com> wrote: > Hi Udo, > > What versions of ES are you using? We currently face an issue of > deprecation warnings as we have not resolved use of 'types' in ES > > Our systems found this was causing a large log on each reindex and piped > the logs through sed to remove the warnings > > -Nick > > On Thu, Sep 7, 2023 at 8:04 AM Udo Willke <udo.willke(a)kit.edu> wrote: > >> Hi koha developers, >> >> Quick introduction: As a system admin, I am part of the team that rolls >> out the koha software at KIT Karlsruhe. >> >> Currently I have an issue with the koha-elasticsearch script that is >> used to index the biblio and authorities data in elasticsearch. We have >> different test and development servers and on some of the severs I get >> extensive diagnostic output when running the command while on others I >> only get the errors and warnings. >> >> In every run /usr/sbin/koha-elasticsearch (which subsequently calls >> /usr/share/koha/bin/search_tools/rebuild_elasticsearch.pl) is definitely >> invoked without any "verbose" flag >> >> Unfortunately there is no output on stdout, but everything gets written >> to stderr. As we have 1.3M biblios and 600k authorities I would get tens >> of gigabytes of log file, which I would have to check. >> >> My question: is there somewhere a setting in koha that globally controls >> the debug level? Or how can the different behaviours be explained? >> >> All installations run koha Release 23.05.X on Ubuntu 22.04.3 LTS >> >> Any thoughts are welcome. >> >> Many thanks in advance >> >> Udo >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel(a)lists.koha-community.org >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : https://www.koha-community.org/ >> git : https://git.koha-community.org/ >> bugs : https://bugs.koha-community.org/ >> > > > -- > Nick Clemens > ByWater Solutions > bywatersolutions.com > Phone: (888) 900-8944 > Pronouns: (he/him/his) > Timezone: Eastern > Follow us: > <https://www.facebook.com/ByWaterSolutions/> > <https://www.instagram.com/bywatersolutions/> > <https://www.youtube.com/user/bywatersolutions> > <https://twitter.com/ByWaterSolution> > -- Nick Clemens ByWater Solutions bywatersolutions.com Phone: (888) 900-8944 Pronouns: (he/him/his) Timezone: Eastern Follow us: <https://www.facebook.com/ByWaterSolutions/> <https://www.instagram.com/bywatersolutions/> <https://www.youtube.com/user/bywatersolutions> <https://twitter.com/ByWaterSolution>

2 1

koha-elasticsearch verbosity issue
by Udo Willke 07 Sep '23

07 Sep '23

Hi koha developers, Quick introduction: As a system admin, I am part of the team that rolls out the koha software at KIT Karlsruhe. Currently I have an issue with the koha-elasticsearch script that is used to index the biblio and authorities data in elasticsearch. We have different test and development servers and on some of the severs I get extensive diagnostic output when running the command while on others I only get the errors and warnings. In every run /usr/sbin/koha-elasticsearch (which subsequently calls /usr/share/koha/bin/search_tools/rebuild_elasticsearch.pl) is definitely invoked without any "verbose" flag Unfortunately there is no output on stdout, but everything gets written to stderr. As we have 1.3M biblios and 600k authorities I would get tens of gigabytes of log file, which I would have to check. My question: is there somewhere a setting in koha that globally controls the debug level? Or how can the different behaviours be explained? All installations run koha Release 23.05.X on Ubuntu 22.04.3 LTS Any thoughts are welcome. Many thanks in advance Udo

1 0