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

Need help with bug 26247
by Mark Alexander 05 May '22

05 May '22

It used to be that at our library, we could check the status of a pile of books by using "Search the catalog" in the search box at the top of most pages. You could just keep scanning barcodes without having to do anything with the mouse or keyboard. This is very useful when you have a library with volunteers who are not very careful about checking in returned books. Then at some point, Koha 20.05 broke this functionality by always populating the search box with the last barcode scanned. Now you have to manually erase everything in the search box before scanning each book. We are now using 20.05.15, but the same bug exists in 21.11.02. I have been struggling for several days with trying to find a temporary fix for this problem. There was a suggested quick fix in Javascript at the end of bug 26247, but that didn't work for me, as I mentioned in a comment on that bug. Then I tried hacking the function keep_text in staff-global.js, because in bug 19046, which was supposedly the source of the problem, keep_text seemed like where the action was taking place. But hacking that function had no effect; in fact, when I set a breakpoint in that function in Firefox, it was never hit. I think this is because keep_text is only triggered by a mouse click event, not by a form reload. So now I've been trying to find out where the search box is getting filled with the last search string after you hit the Search button. I am not super-familiar with the Koha code, but I'm comfortable hacking on it if I know where to look. Any help with finding the source of the search box autofill would be greatly appreciated. -- Maybe I'm lucky to be going so slowly because I may be going in the wrong direction. --Ashleigh Brilliant

3 5

Using ETag for detecting mid-air collisions when cataloguing
by dcook＠prosentient.com.au 04 May '22

04 May '22

Hey folk, I'm just working on some caching for a non-Koha project, and I was just thinking. maybe we could use the ETag and If-Match HTTP headers to detect whether or not we've got a mid-air collision when editing bib records. It's not something I'd be looking to work on, but I figure it's an interesting idea. Alternatively, one could implement their own app-based hash mechanism to do the same thing. 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

1 0

Biblio Auto-Increment location
by Bruce A. Metcalf 04 May '22

04 May '22

Greetings, Sorry to post a support question here. No one else seems to know, but many think folks here might: Thanks to help from our library cat, a biblio number was inserted that's several orders of magnitude greater than those in use. I have not found a way to reset this. It's my guess that the highest previous value is stored somewhere, and incremented for each additional biblio. If someone could tell me where it's stored, I could reset it to the current value and not have a huge gap in the numbering. Yes, I do appreciate that the numbers are just data-less markers, but I'd sill like to fix this. Any help most appreciated. Regards, / Bruce / Bruce A. Metcalf Augustan Library

3 2

iTiva messaging
by Nick Clemens 03 May '22

03 May '22

Hi All, We just wanted to get a sense of how widespread use of iTiva is? We were considering that it may be better as a plugin than a script within Koha Thanks for any feedback, Nick -- 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>

1 0

Is the support of multiple LDAP servers in koha-conf.xml planned?
by Uwe Dierolf 03 May '22

03 May '22

Hi all, at the moment C4::Auth_with_ldap supports only one ldap-server. If the authentication against this ldap-server fails, koha tries to use the credentials to authenticate by using the internal koha accounts. In some cases it would be practical if we could use multiple blocks like so in the koha-conf.xml: <ldapserver id="ldapserver-1" ...> </ldapserver> .... <ldapserver id="ldapserver-2" ...> </ldapserver> and if koha would try to authenticate with the given credentials using all ldapservers and at the end the internal koha accounts. Best regards, Uwe -------------------------------------------------------------------------- Uwe Dierolf Karlsruher Institut für Technologie (KIT) KIT-Bibliothek Telefon: +49 721 608-46076 --------------------------------------------------------------------------

1 0

Adding recent (current/past year) statistics to the items table
by Nick Clemens 29 Apr '22

29 Apr '22

Hi All, We have had several requests recently for an easy way to access current/last year's circulation stats for items, without having to create reports totalling these numbers. The numbers here are used for weeding, state reporting, etc. Other systems have fields: 'Year to date circ' and 'last year circ' We have discussed several possible developments: - a new table to track these - adding a new field, or altering 'issues' to use JSON and storing circ/renewal counts by year - adding two new fields to the items table and use a cronjob to move 'current year' circ to 'last years circ' at the end of the year. We wanted to check in with the community to see if this is a request that others have or have seen, and how they handle these. Thanks for any info. Nick (kidclamp) -- 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>

4 3

Koha releases are available 🎁
by Mason James 29 Apr '22

29 Apr '22

kia ora community, the latest Koha packages are available an installation guide is below... https://wiki.koha-community.org/wiki/Koha_on_Debian cheers, Mason

1 0

Roles for 22.11 open
by Fridolin SOMERS 28 Apr '22

28 Apr '22

Hi dear community. 22.05 cycle comes to an end, time to think of next cycle. The roles for the 22.11 release cycle are now opened : https://wiki.koha-community.org/wiki/Roles_for_22.11 The vote will take place during next general IRC meeting on May 4th. The description of the roles can be found at this wiki page : https://wiki.koha-community.org/wiki/Project_roles << Join us in the dark side, we have cookies >> Best regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

1 1

Koha::Item->is_notforloan (see Bug 30636)
by dcook＠prosentient.com.au 28 Apr '22

28 Apr '22

Hi all, While working on https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30636, I noticed that our usage of Koha::Item->notforloan is problematic. Sometimes we use it as a Boolean and sometimes we use it for descriptive information. When we use it as a Boolean, we really should be taking into account the "Not for loan" status by "Item Type" as well. I'm noticing there are places in Koha which show an item as "Available" if the item is "Not for loan" by item type and that's a problem. (It looks like the new recalls feature from Bug 19532 has this same problem.) Anyway, I'm thinking a new method like Koha::Item->is_notforloan might be a good idea for covering the Boolean condition rather than trying to remember to implement Koha::Item->notforloan and Koha::Item->notforloan_per_itemtype (this method doesn't even exist) for all relevant use cases. One way or another, I'll be fixing the ILS-DI API locally, but I'd like to get people's input first, so that it's easier for me to upstream and benefit everyone else too. 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

2 1

Koha Community Newsletter: April 2022
by Koha Newsletter 28 Apr '22

28 Apr '22

The Koha Community Newsletter for April 2022 is here: https://koha-community.org/koha-community-newsletter-april-2022/ Many thanks to everyone who submitted articles and news to this newsletter! Please feel free to email me with any corrections or suggestions. -- Michael Kuhn Editor, Koha Community Newsletter

1 0