Hi Koha community,
We were wondering, has anyone in the community looked at connecting
OCLC's Tipasa to Koha using NCIP?
The purpose of this would be so libraries do not have to manage
Inter-Library Loans (ILL) in two different places: Tipasa and Koha.
A few years ago, we got an NCIP server
Kia ora koutou/Hello everyone,
We have several Koha integrations that require third-party systems to
call Koha ILS-DI endpoints.
For example, Bolinda (BorrowBox) which calls the GetPatronInfo ILS-DI
endpoint for authenticating users. Or the EBSCO EDS integration, which
can use Koha ILS-DI en
am to try and look at the
bug you posted below. Clearly still needs addressing.
Thanks
Jonathan
On Thu, 12 Sept 2024 at 04:51, Alex Buckley via Koha-devel
wrote:
Kia ora koutou/Hello everyone,
We have several Koha integrations that require third-party systems
to call Koha ILS-
9212 0899
Online: 02 8005 0595
*From:*Koha-devel *On
Behalf Of *Alex Buckley via Koha-devel
*Sent:* Monday, 16 September 2024 9:32 AM
*To:* Field, Jonathan
*Cc:* koha-devel ;
kohat...@catalyst.net.nz
*Subject:* Re: [Koha-devel] Discussion around Koha ILS-DI endpoints
expecting a CSRF token from
Hi Michael,
We have encountered similar problems with Shibboleth. However, the
community has helpfully written an upstream fix for preventing
borrowers.updated_on being filled with -00-00 when a new patron is
created via LDAP or Shibboleth:
https://bugs.koha-community.org/bugzilla3/show_b
Great, thanks Michael!
On 20/11/24 11:31 pm, Michael Kuhn via Koha-devel wrote:
Hi Alex
Many thanks for your message! You wrote:
> We have encountered similar problems with Shibboleth. However, the
> community has helpfully written an upstream fix for preventing
> borrowers.updated_on being f
Kia ora/Hello Koha community,
Over the last few months we have been upgrading the OS of our Koha,
database, load balancer and VuFind servers from Debian 11 (Bullseye) to
Debian 12 (Bookworm).
We have noticed two things which we thought might be helpful for others:
1) Third-party integrations
milar fix as yours in the client.conf and server.conf
like this:
sslVersionMin = TLSv1.2
sslVersionMax = TLSv1.3
This eliminated the warn.
Regards,
Marcel
*Van:* Koha-devel namens
Alex Buckley via Koha-devel
*Verz
