- Koha - lists.katipo.co.nz

Template toolkit question.
by Raymund Delahunty 21 Sep '23

21 Sep '23

We are having some successes in using TT code to improve notices. Dealing with singular / plural issues, different wording of notices for different patron categories... that sort of thing. What we would like to do is to use TT to send the WELCOME notice to staff only. Has any TT expert any tips how we could set up the WELCOME notice (and potentially other ones usually sent to all, like MEMBERSHIP_EXPIRY) so that emails are only sent to some patrons, based on IF-type rules? 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

3 3

KOHA is not sending mails through SMTP server
by Nirmit Krishnatray 21 Sep '23

21 Sep '23

Hi, Hope you're well. KOHA is not sending mails when a user is checking out or checking in. I checked the notices and it displayed Unhandled email failure, check the logs for further details. Please support on this Best Regards

2 1

Documentation - Are automated screenshots the way to go?
by Caroline Cyr La Rose 21 Sep '23

21 Sep '23

Hello dear community, TLDR; We have a potential way of automating the screenshots of the manual that has interesting benefits. However, we are not sure if it would work with our screenshots. I would like to ask for your help analyzing the screenshots, to know if they are easy or difficult to automate. See https://docs.google.com/document/d/1wscmVmficQSpCmUDPNEYLp-TFJoR3gay2O6zS8q… for how to analyze a screenshot. Read on for more information and a kitty at the bottom! In the documentation team, we're looking at the possibility of automating the screenshot taking for the manual. If you've visited the manual before, you surely have stumbled upon screenshots of the interface that don't look anything like your interface. Our manual contains more than 1600 screenshots, with more being added with every new feature. This means that if there is a change in the interface, we must retake the screenshot. After the redesign of 22.11, all our screenshots were suddenly out of date. We are updating them little by little, but it is time consuming for the very small team of documenters that we are, so it is unimaginable to think that we can update all of them every version. We would rather spend our time documenting exciting new features than retaking screenshots simply because the interface looks different. And if you're thinking, "Well, we can live with screenshots from version 22.05 or even 20.11, it's not that bad!" take a look at this screenshot that is currently still in the latest manual as I write this https://koha-community.org/manual/latest/en/html/_images/fastadd.png (in the fast add cataloguing section https://koha-community.org/manual/latest/en/html/circulation.html#fast-add-… ; this section hasn't had any new features for a while so we never went over it to update it). Do you recognize it? :D At Kohacon23, Jonathan Druart proposed a way to automate the screenshot taking using Cypress and Cypress Studio. Cypress is a tool mainly used by web developers for what is called end-to-end testing, where they write up a bunch of commands, input that into a browser and the browser will execute the commands as if it was a normal user. Cypress Studio is an extension of Cypress to be able to use Cypress without knowing how to write up the bunch of commands, i.e. for people like me who don't code. When using Cypress Studio, it records all the clicks and key presses that you do and converts it into code (that needs to be cleaned according to Jonathan). You can then feed that code into the browser and the browser will click where you clicked and type what you typed. (It does it super fast too, it's really cool to watch it go!) For our purposes, anyone in the documentation team (or any motivated community member willing to help! *wink wink*) would take the screenshot using Cypress Studio. Then a developer would go in and clean the code generated by Cypress Studio. Then, every time we create a new manual (or whenever we want), we would run the Cypress scripts and all the screenshots would be automagically updated! As well as having nice, up-to-date screenshots in our manual, this method has other advantages: - It would allow us to have translated screenshots in the translated manuals. - It would allow us to take the screenshot once and have it updated for every version with minimal additional work (admittedly it takes a lot more time to take the automated screenshot, but hopefully, this time would be saved in the future by not having to manually take the screenshot again). - It would allow us to catch regressions in Koha (if something that should be there suddenly isn't there anymore, for example). As the automation would be as time-consuming, if not more, than the manual way in the short-term, and would implicate developers as well as the documentation team, we would like to analyze the difficulty of automating before jumping in. Some screenshots are super easy to get to: you go into Cataloguing, click 'New record' and bam!, you're ready to take this screenshot https://koha-community.org/manual/latest/en/html/_images/catalogingform.png . Some screenshots need more preparation, like you need to turn on a system preference, then add a fine to a patron account, then try to check out an item to that patron and *now* you can take this screenshot https://koha-community.org/manual/latest/en/html/_images/patrondebt.png . If the majority of existing screenshots are hard or impossible to automate, it is not worth the trouble. However, if the majority of existing screenshots are easy, automation could be a way to save time in the long run. The thing is that we don't know how many are easy and how many are difficult. This is where I would like to ask for your help. We would like to analyze the difficulty of about 10% of the images (around 100 to 150) in order to determine if the automation would be worth investing into. We currently have a Google spreadsheet with a list of about 1600 images. Anyone can go in and analyze an image. If several people analyze 2 or 3 images each, we'll be done in no time! It is not too difficult to analyze a screenshot, but you do need to know how to use Koha and know how to read HTML at least a little bit (just to spot the IDs or classes of the tags). I wrote up a procedure on how to do it in the Google drive https://docs.google.com/document/d/1wscmVmficQSpCmUDPNEYLp-TFJoR3gay2O6zS8q… After we determine if automation is the way to go, there are still a lot of things that would need to be ironed out before jumping in. Like what data to use, is the sample data enough? Do we only do the easy ones? When running the scripts, how do we determine that the screenshots have been correctly generated? Where do we store the Cypress scripts? When do we generate the screenshots? But all those questions will come later. First we must decide if we do it or not, and for that we need to analyze the images. If you have opinions on this, or would like to help, or would simply like to know more about the Koha manual, there is an upcoming Documentation meeting on September 27, at 14 UTC. Everyone is welcome! (I swear we are very nice!) https://wiki.koha-community.org/wiki/Documentation_meeting_27_September_2023 Thank you for reading all the way to the bottom! :) Caroline As promised, here is the kitty! :) ⠀⠀⠀⠀⠀⠀⠀⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⣧⡑⢄⡀⠀⠀⠀⠀⠀⠀⢀⡴⣪⠁⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⣽⡨⠆⠉⠊⠉⠀⠈⠉⠐⠉⠮⣰⡇⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⢠⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢃⠀⠀⠀⠀ ⠀⠀⠐⠠⠄⡀⡈⠀⠀⡰⠂⡄⠀⠀⠀⠀⡔⢢⡄⠀⠘⣀⡀⠤⠒ ⠀⠀⠠⠤⠤⠤⡯⢥⡆⠑⠛⠁⢀⣻⣃⡀⠙⠛⠁⣶⢭⡧⠤⠤⠤ ⠀⠀⢀⡠⠄⠒⠙⡅⠀⠀⠀⠀⠈⠉⠉⠀⠀⠀⠀⠀⡝⠁⠒⠠⠄ ⠀⠀⠀⠀⠀⠀⠀⡨⠂⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢺⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⡰⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠱⡀⠀⠀⠀ ⠀⠀⠀⠀⠀⢰⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢡⠀⠀⠀ ⠀⠀⠀⠀⠀⡆⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡆⠀⠀ ⢀⠖⠐⢢⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡇⠀⠀ ⡆⠀⠀⠀⡄⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡇⠀⠀ ⢡⠀⠀⠀⡇⢡⠀⠀⠰⡄⠀⠀⠀⠀⡀⠀⠀⠀⡆⠀⠀⢠⠓⡀⠀ ⠈⡄⠀⠀⠸⡀⠣⡀⠀⡇⠀⠀⠀⠀⡇⠀⠀⢠⠁⠀⡠⡇⠀⢡⠀ ⠀⠈⢄⠀⠀⠑⢄⠈⠢⢴⡀⠀⢠⠀⡇⠀⠀⣌⠠⠚⣡⠃⠀⣸⠀ ⠀⠀⠀⠳⣀⠀⠀⠑⠂⠤⢙⣛⡋⠉⢙⣣⣊⠀⠤⠊⠁⠀⡠⠃⠀ ⠀⠀⠀⠀⠀⠑⠠⢀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⡠⠐⠁⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠁⠒⠒⠂⠀⠀⠐⠒⠂⠉⠀⠀⠀⠀⠀⠀ Caroline Cyr-La-Rose, M.L.I.S. (she/her) Librarian | Product Manager 1-833-INLIBRO (465-4276), ext. 221 caroline.cyr-la-rose(a)inlibro.com https://www.inLibro.com

2 1

Possible solution to 500 errors.
by Rudy Hinojosa 21 Sep '23

21 Sep '23

If you are running into 500 errors, and you've exhausted all means to verify you have a valid biblio, a valid item record and confirmed homebranch is populated, there may be one more spot you need check. Before I state what I found, this is a disclaimer. Do not attempt what I did without consulting with your Database Administrator or someone with technical experience. ===Discovery=== You may have an invalid XML structure in your table biblio_metadata->metadata field. Dump the xml content for the suspected record to your clipboard and visit any online xml validator checker tool. Paste it and see if it passes. I found 134 records with invalid xml properties. <datafield tag="500" ind1=" " ind2=" "> <subfield code=""">Based on the TV series SpongeBob SquarePants created by Stephen Hillenburg as seen on Nickelodeon"--T.p. verso.</subfield> </datafield> I found 134 records with triple double quotes as you see above to the left of the word Based. Your koha-rebuild-zebra command should alert you of all xml errors. You'll really want to fix those if you don't want to see 500 errors. Here's my code snippet I ran to fix this problem globally, now keep in mind, your xml errors may not be the same as mine, but you'll have to investigate your own solution: ====sql fix==== -- Step 1: Create a copy of biblio_metadata as reh_biblio_metadata CREATE TABLE reh_biblio_metadata AS SELECT * FROM biblio_metadata; -- Step 2: Update the metadata field in biblio_metadata UPDATE biblio_metadata SET metadata = REPLACE(metadata, '=""">', '="">') WHERE metadata LIKE '%=""%">%'; =========== then exit to system prompt and run your reindex: "koha-rebuild-zebra -f -a -b -v <your-koha-instance>" Cheers! -- photo Rudy E. Hinojosa CEO/President,Lightwave Library +1 737-372-7779 <tel:+1 737-372-7779> | lightwavelibrary.com <https://lightwavelibrary.com> rudy.hinojosa(a)lightwavelibrary.com <mailto:rudy.hinojosa@lightwavelibrary.com> 25101 Ronald W. Reagan Blvd #49, Georgetown TX 78633 <https://maps.google.com/?q=25101 Ronald W. Reagan Blvd #49, Georgetown TX 78633>

1 0

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

Error 500 when opening records with attached items
by bongiwe＠uks.co.za 18 Sep '23

18 Sep '23

Good day, Apologies if I am sending to an incorrect list. We have just migrated our database to another server with an upgraded version of KOHA (23.05.01.000). On the new server we encounter problems with opening bibliographic records in NORMAL view after performing a search. We get the "error 500". This only happens in records with attached items. Records with no items attached to them open successfully in this view. ISDB and MARC views are not an issue. These views open successfully for all records even those with attached items. We also cannot delete items from records. We get the same 500 error. Kind regards, Bongiwe Shongwe

3 3

Koha running number of background job process and CPU high usage
by JITHIN N 18 Sep '23

18 Sep '23

Am using Koha 22.11.07. My server running 6 instances. I noticed my disk was filling up because worker-output.log was getting several hundred of these per second: *[2023/09/17 22:41:14] [WARN] Frame not processed - malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "You must log in usin...") at /usr/share/koha/bin/workers/background_jobs_worker.pl <http://background_jobs_worker.pl> line 118. main::catch {...} /usr/share/koha/bin/workers/background_jobs_worker.pl <http://background_jobs_worker.pl> (120)* while checking the terminal it ran a number of background jobs and CPU usage became very high. can I have any solution for this? With Regards JIthin

2 1

Email for suggestion book
by Toni Afandi 18 Sep '23

18 Sep '23

Dear all, After upgrading to Koha 23 from koha 20, I noticed something strange about the suggestion notification email. Now I receive email when a patron suggestion is received or declined, but no to the patron who suggests. So where should I set the email so they would receive it? I noticed that koha made a notification, but it is set to me not to the patrons. Thank you *Toni Afandi* *Librarian* *STT SAAT* *(Southeast Asia Bible Seminary)* Jl. Bukit Hermon No 1, Tidar Atas Malang, Jawa Timur 65151 Indonesia www.seabs.ac.id

2 1

link_bibs_to_authorities
by Сычев Игорь Алексеевич 17 Sep '23

17 Sep '23

Hello! When executing "link_bibs_to_authorities.pl", the messages "oAuth error: Too many characters in search statement (11) Bib-1" are output. What's it? How can I see the details? Good Luck! Igor A. Sychev Tomsk Polytechnic University https://lib.tpu.ru/

1 0

Problem with SIP
by Gonzalo Córdova Mío 16 Sep '23

16 Sep '23

Hello. I have already configured the SIP for self-service and when making a loan from the loan equipment I get this error message. Anyone know what might be happening? 2023-09-15 15:10:03,817 INFO [SIP] MessageFormatter - Parsed: [64] Patron Information Response {patron_status = None, language = SpanishNA, transaction_date = 2023-09-15T15:10:04, hold_items_count = 0, overdue_items_count = 0, charged_items_count = 0, fine_items_count = 0, recall_items_count = 0, unavailable_holds_count = 0, institution_id = "BUCS", patron_identifier = #6da1f2e2, personal_name = #4414b04d, valid_patron = True, valid_patron_password = True, fee_amount = 0, fee_limit = 5, PC = "AL", PI = "Y", screen_message = "Greetings from Koha. "} 2023-09-15 15:10:03,819 TRACE [SIP] MessageProcessor - Response read for: Patron Information Response, elapsed=00:00:00.2712779 2023-09-15 15:10:03,821 ERROR [SIP] MessageProcessor - Invalid message received: The value for field "patron_identifier" in the response (patron_identifier = #6da1f2e2) is not the expected value (patron_identifier = #6a705781); requesting resend (1) 2023-09-15 15:10:03,823 TRACE [SIP] MessageProcessor - Writing request for: Request ACS Resend, timeout=00:00:19.6590000 -------- Gonzalo Córdova

1 0