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

Re: [Koha-devel] barcodes issue
by Michael Hafen 25 Sep '23

25 Sep '23

Most likely you don't have a barcode input filter since I think the default is to not have one. So that's fine. I'm curious where you put the barcode now that you report it is not in the 'p' subfield. The 'p' subfield is the standard place for barcodes in Koha, and circulation won't be able to find the barcode if it's put anywhere else, unless you change how the databases items.barcode field is mapped to the Marc subfields. On Mon, Sep 25, 2023 at 11:06 AM Nasr Alyas <nasralyashassan(a)gmail.com> wrote: > Hi Michael, thanks for your respond, I am using koha version 22.11.03 and > Mysql version 8.0.34. > and for this: Did you put the barcode in a field other than the item > record 'p' subfield? and answer is no. > and for this: Do you have a barcode input filter set? I don't anything > about it! > > في الاثنين، ٢٥ أيلول، ٢٠٢٣, ٧:٥٤ م Michael Hafen < > michael.hafen(a)washk12.org> كتب: > >> Which version of Koha are you using? Which version of MySQL / MariaDb? >> Did you put the barcode in a field other than the item record 'p' >> subfield? Do you have a barcode input filter set? >> >> On Mon, Sep 25, 2023 at 10:51 AM Nasr Alyas <nasralyashassan(a)gmail.com> >> wrote: >> >>> Hi, I have a problem with my Koha system I have some books in my system and I have assigned a barcode to each book in opac I have the barcode for each book but the issue is when I want to check out one of the books it gives me this barcode does not available in the database and when I go to the database there is no barcodes. >>> >>> So how can I fix this? >>> any help! >>> >>> _______________________________________________ >>> 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/ >>> >> >> >> -- >> Michael Hafen >> Washington County School District Technology Department >> Systems Analyst >> >> -- Michael Hafen Washington County School District Technology Department Systems Analyst

1 0

barcodes issue
by Nasr Alyas 25 Sep '23

25 Sep '23

Hi, I have a problem with my Koha system I have some books in my system and I have assigned a barcode to each book in opac I have the barcode for each book but the issue is when I want to check out one of the books it gives me this barcode does not available in the database and when I go to the database there is no barcodes. So how can I fix this? any help!

2 1

Re: [Koha-devel] cannot display branchname and patron category description in card layout
by Michael Hafen 25 Sep '23

25 Sep '23

If you are looking at the code, look at C4/Patroncards/Lib.pm in the get_borrower_attributes() function. That's where the branchcode to branchname conversion is handled, I figure that would be the place to do a categorycode to category description conversion. On Thu, Sep 21, 2023 at 12:17 AM Zahid Iqbal <zahidiqbal.isb(a)gmail.com> wrote: > thanks for the response. > i have checked the branchcode, it is displaying correctly in patron card > as you told. 👍 > but i cannot find any solution for categorycode. I will still look into > code. Maybe I will find a solution for that. > > On Wed, Sep 20, 2023 at 9:08 PM Michael Hafen <michael.hafen(a)washk12.org> > wrote: > >> I have a layout using "<sort2>" in the text box for field 2. Looks like >> the code will change "<branchcode>" into the library name. No such luck in >> current code for patron category though. >> >> On Tue, Sep 19, 2023 at 11:17 PM Zahid Iqbal <zahidiqbal.isb(a)gmail.com> >> wrote: >> >>> 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* >>> _______________________________________________ >>> 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/ >>> >> >> >> -- >> Michael Hafen >> Washington County School District Technology Department >> Systems Analyst >> >> > > -- > *Zahid* > -- Michael Hafen Washington County School District Technology Department Systems Analyst

3 4

Carrousel display issue on sandbox
by Shi Yao Wang 22 Sep '23

22 Sep '23

Hello, Our carrousel plugin display is broken on koha sandbox and it's due to the plugin's js/image files not being found (on webpage inspect console). Tested this on 2 sandboxes with the exact same errors. Any idea how this could be fixed on the sandboxes? Thanks, Shi Yao Wang

4 10

Re: [Koha-devel] ktd and persistent data
by januszop＠gmail.com 20 Sep '23

20 Sep '23

Hi Jonathan, Thank you very much for you kind reply and explanation. This is really comforting—at least I can be sure this was not because of my ignorance that it did not work. As to the merge request, if I understand it correctly, we would have to edit the .env file and put there the environment variable USE_EXISTING_DB by hand after creating the db (i.e. before the second run of kp)? Why not to put the environment variable in the docker-compose.persistent.yml file (by adding there a value for the key services//koha//environment//USE_EXISTING_DB) and then conditionally skip the creation of the database in populate_db.pl if 1) the variable is set AND 2) the database exists and is not empty (which could be tested as it is now, with prefs_count or $patrons_count, for instance)? In addition, in this case probably an alias should be created for ‘docker volume rm koha_db-data’ to easily delete the volume if necessary… Wouldn’t it be a possibility? Best greetings, Janusz From: Jonathan Druart <jonathan.druart(a)gmail.com> Sent: Monday, September 18, 2023 11:36 AM To: januszop(a)gmail.com Cc: koha-devel(a)lists.koha-community.org Subject: Re: [Koha-devel] ktd and persistent data Hi Janusz, It does not work. There is a merge request however: https://gitlab.com/koha-community/koha-testing-docker/-/merge_requests/410 Cheers, Jonathan Le sam. 16 sept. 2023 à 00:42, <januszop(a)gmail.com <mailto:januszop@gmail.com> > a écrit : 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 <http://populate_db.pl> line 103. Indeed, the populate_db.pl <http://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 _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha-community.org <mailto:Koha-devel@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/

2 1

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 17 Sep '23

17 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