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

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

Koha version 19.11.29 released
by Chris Cormack 26 Apr '22

26 Apr '22

Hello everyone! The Koha community is proud to announce the release of version 19.11.29. The full release notes can be found at: https://koha-community.org/koha-19-11-29-released/ Thank you to everyone involved! Cheers, Chris Cormack (Standing in for Te Wainui)

1 0

Koha 20.11.18 released
by Victor Grousset/tuxayo 26 Apr '22

26 Apr '22

Hello! :) The Koha Community is happy to announce the release of Koha 20.11.18 The full release notes can be found at: https://koha-community.org/koha-20-11-18-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo

1 0

Koha 21.05.14 Release
by Andrew Fuerste-Henry 26 Apr '22

26 Apr '22

The Koha community is proud to announce the release of version 21.05.14. This is a maintenance release and contains bug fixes. For full details and release notes, please see https://koha-community.org/koha-version-21-05-14-released/ Thanks! Andrew -- Andrew Fuerste-Henry Educator (he/they) ByWater Solutions bywatersolutions.com Phone:(888)900-8944 <(888)%20900-8944> What is Koha? <http://bywatersolutions.com/what-is-koha/>

1 0

Does anyone use "Item circulation alerts"?
by dcook＠prosentient.com.au 26 Apr '22

26 Apr '22

I think today is the first time in 10 years that I've bumped into "Item circulation alerts". By default, they're enabled for everyone and everything, and that seems to work. However, today, I noticed a library where they're disabled alerts for most categories and item types, and then wondered why they weren't getting item circulation emails. I wonder if this functionality causes more harm than good these days? Looks like it was introduced in 2009 and never touched again? Of course, removing this functionality would probably be easier said than done, as it would be a behaviour change. so maybe it would need to be deprecated over time. If no rules exist, we could just hide it. If rules do exist, we'd alert the staff that this functionality was going away in a future version? 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 2