- Koha - lists.katipo.co.nz

koha-US General Meeting Minutes for September 22, 2023
by Jennifer Marlatt 28 Sep '23

28 Sep '23

Hello, Here's a link to the minutes from the koha-US General Meeting held on Friday, September 22, 2023 during the third day of the 2023 Annual koha-US Conference - https://docs.google.com/document/d/1x_rrqLbAmnmpNZ4npb7lKi-uf4Po_Q-xsa7b6DV…. The recording for the general meeting has been posted, there's a link to the recording in the minutes. koha-US meetings are open to all! The next board meeting will be on October 4, 2023 at 8:30 am PT / 9:30 am MT / 10:30 am CT / 11:30 am ET. The next general meeting will be on October 11, 2023 at 8:30 am PT / 9:30 am MT / 10:30 am CT / 11:30 am ET. Jennifer Marlatt koha-US Secretary <secretary(a)koha-us.org>secretary(a)koha-us.org

1 0

output of authors' subfields
by Сычев Игорь Алексеев ич 27 Sep '23

27 Sep '23

Hello! How to do if 7xx $g and $b are filled, output only $g? Both subfields are being displayed now. Is this reaction only in Unimarc? Example: 700 $aAufderstraße $bH. $gHartmut https://koha.lib.tpu.ru/cgi-bin/koha/opac-detail.pl?biblionumber=667189 https://koha.lib.tpu.ru/cgi-bin/koha/opac-detail.pl?biblionumber=22141 https://koha.lib.tpu.ru/cgi-bin/koha/opac-detail.pl?biblionumber=634386 Good Luck! Igor A. Sychev Tomsk Polytechnic University https://lib.tpu.ru

3 2

Any other Koha libraries having difficulty with the EDS API plugin?
by Myka Kennedy Stephens 27 Sep '23

27 Sep '23

Hello, Lancaster Theological Seminary Library in Pennsylvania, USA has been a longtime user of the EDS API plugin. This allows us to do EBSCO Discovery searches directly from Koha and display the search results within Koha. Sometime since our update to 22.11, the plugin is no longer correctly constructing URLs to records provided by the EDS API plugin. Are other libraries having this experience? We've submitted a case with EBSCO and also have submitted a case on Github. More information about what we're experiencing is here: https://github.com/ebsco/edsapi-koha-plugin/issues/130 After raising this issue more than a week ago, we're anxious to find a solution. If you also use this plugin, please share your current experience so that we can learn more about what's going on. Thank you, Myka -- Deaconess Myka Kennedy Stephens, MDiv, MSLIS Consulting Librarian Lancaster Theological Seminary | Moravian Theological Seminary Moravian University 717-290-8738 mkstephens(a)lancasterseminary.edu https://library.lancasterseminary.edu

1 0

Coded fields
by Сычев Игорь Алексеевич 26 Sep '23

26 Sep '23

Hello! The search by "physical representation" does not work if the subfields 182 of the Unimarc field are filled in. It works if you fill out 106, but these subfields are outdated. 106 CODED DATA FIELD: TEXTUAL RESOURCE - FORM OF ITEM $a Form of resource Item: Coded Data:Medium Designator i = multimedia (e.g. a resource an item in regular print with a microfiche supplement) (obsolete) This code is replaced by field 182 Coded Data Field - Media type, $a/0 code "m"= "multiple media". s = electronic (obsolete) This code is replaced by field 182 Coded Data Field - Media type, $a/0 code "b"= "electronic". To be used when resource Item is intended for manipulation by a computer. The resource item may reside in a carrier accessed either directly or remotely, in some cases requiring the use of peripheral devices attached to the computer. This code is not used for items that do not necessarily require the use of a computer (e.g. music compact discs, videodiscs). t = microform (obsolete) This code is replaced by field 182 Coded Data Field - Media type, $a/0 code "c"= "microform". https://cdn.ifla.org/wp-content/uploads/files/assets/uca/unimarc_updates/BI… https://cdn.ifla.org/wp-content/uploads/files/assets/uca/unimarc_updates/BI… https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34919 Good Luck! Igor A. Sychev Tomsk Polytechnic University https://lib.tpu.ru

1 0

Koha not compatible with Plesk Control Panel?
by Alessandro Tedesco 25 Sep '23

25 Sep '23

Hi, I have tried to install previous Releases of Koha, and I have found that the "javascript-common package" seems to have been introduced since the 22.05 Release (because I am able to install Koha 21.11 in the VPS running Ubuntu with Plesk without problems). What is this "javascript-common package" for? Is it strictly necessary for Koha to work? Is there no way to introduce an option to exclude it from the Release 23.05 installation? Thanks and Kind Regards Alessandro

1 0

Has NFC vs. NFD encoding changed for Unicode in koha?
by Jesse Savage 24 Sep '23

24 Sep '23

This is probably a question for a developer, but I'm not one, so don't really want to join the koha-devel list (and they probably wouldn't want me to), and I know a lot of developers frequent this list. My apologies to anyone who might not be interested in this question. I recently got a new Windows laptop on which I installed (I think) a newer version of WSL/Ubuntu, and I see that records exported with the "MARC (Unicode/UTF-8)" option (as *utf8 files, which look to be basically *mrc) apparently use NFD (or "decomposed") encodings for Unicode characters (in my case, mainly Spanish and French titles) and thus don't display properly in *less*, *grep*, or *cat* (the diacritic follows the standard-Latin character, rather than integrated with it) as do files encoded with NFC characters, and the characters also can't be *grep*'d with searches like "grep $'\u16A0'." The program I use to update records for uploading also outputs NFD, even if the records it takes for input contain NFC. (I'm waiting on the answer to the present questions to see whether that program has an option hidden somewhere to output NFC instead, which I'd prefer.) So, is this a systematic change in koha? *Should I ensure that *.mrc files for batch uploading ALWAYS include only NFD characters, or do the underlying processes standardize NFC vs. NFD?* The system on which the catalog lives (but which I don't administer) currently has koha 23.05.00.000 and runs on "SMP Debian 5.10.179-1 (2023-05-12) x86_64". Please feel free to respond directly if you feel the answer won't interest anybody else. Thanks very much in advance! Jesse --------------------- Jesse Savage (pronouns he, him, his) jessava(a)gmail.com

2 2

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

23 Sep '23

Thanks Michael that will be very helpful. I will look into the code and get back to you. For now i am working on picture uploading (restrict image not more than 4KB and not more then 150 Height Width dimension) so the database does not get heavy. On Thu, Sep 21, 2023 at 9:38 PM Michael Hafen <michael.hafen(a)washk12.org> wrote: > 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 > > -- *Zahid*

1 1

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