vufind-tech Mailing List for VuFind®

Hello, everyone!

VuFind® 11.1.1 has been released today. This is a patch release containing around 70 minor bug fixes and some dependency updates. If you are using 11.1.0, it should be a painless upgrade, though note that a fix related to inconsistent capitalization of the getILLPickupLibraries method might impact users who have custom ILL configurations and use the ComposedDriver for their ILS connection (a very rare combination).

As always, please let me know if you have any questions, concerns, or problems!

thanks,
Demian

Here are the minutes from today's Community Call:

https://vufind.org/wiki/community_call:minutes20261103

The next call will be Tuesday, December 1, 2026 at 9am Eastern Standard Time (14:00 GMT).

- Demian

Moin Demian,

 

Good to know that you are aware oft the issue!

 

Cheers,

  -- David

 

Von: Demian Katz <dem...@vi...> 
Gesendet: Montag, 26. Oktober 2026 13:06
An: 'vuf...@li...' <vuf...@li...>; Maus, David <dav...@su...>
Betreff: Re: [EXTERNAL] [VuFind-Tech] VuFind 11 broken dependency graph?

 

David,

 

This is a known problem, captured by this PR:

 

https://github.com/vufind-org/vufind/pull/5499

 

The bottom line is that we need to finish our Laminas renovations before we can sort it out — this is currently a top priority!

 

thanks,

Demian

 

  _____  

From: Maus, David via Vufind-tech <vuf...@li... <mailto:vuf...@li...> >
Sent: Monday, October 26, 2026 7:03 AM
To: 'vuf...@li...' <vuf...@li... <mailto:vuf...@li...> >
Subject: [EXTERNAL] [VuFind-Tech] VuFind 11 broken dependency graph? 

 

Moin everyone,

VuFind 11 defines the Supported PHP Version to be 8.2 per composer.json.

{ "config": { "platform": { "php": "8.2" } } }

PHP 8.2 is end of life.

If I bump config.platform.php to 8.3 and run `composer check-platform-reqs` I see that I need to update browsecap/browsecap-php as well because its platform is < 8.3.0.

If I do this and bump browsecap to 7.5 which supports PHP 8.3, I get a conflict with laminas/laminas-cache.

Browsecap requires psr/simple-cache 2.x or 3.x while Laminas Cche requires psr/simple-cache 1.x.

The version 3.14.1 is the last version Laminas Cache's ' 3.x series and still requires psr/simple-cache 1.x.

Composer itself recommends running check-platform-req when using config.platform.php.

If I remove the config.platform setting alltogether, I run into the same issue when calling composer update.

So... The dependency graph of VuFind 11 is broken, isn't it?

Cheers,
  -- David

David Maus
Leiter Discovery-Systeme und BMS-Entwicklung
Staats- und Universitaetsbibliothek Hamburg Carl von Ossietzky
Von-Melle-Park 3, 20146 Hamburg
Tel.: +49 (40) 300393-341
Mail: dav...@su... <mailto:dav...@su...> 

Die Geschlechtsidentität von Menschen ist weder über Aussehen noch
über Namen verlässlich abzuleiten. Gerne können Sie mir mitteilen,
wie ich Sie ansprechen darf. Meine Pronomen sind er/ihm (he/him).

#gerneperDu

Hello, everyone!



The October, 2026 VuFind® newsletter is now available:



https://vufind.org/wiki/community:newsletter:2026-10



Additionally, the next Community Call will be held on Tuesday, November 3, 2026 at 9am Eastern Daylight Time (13:00 GMT).



Here is the full agenda:



  1.  Development Planning
     *   Newsletter Highlights
     *
Follow-Up to Past Discussions
        *
Solr Upgrade
        *
Laminas MVC End of Life
        *
Dark Mode PR
        *
Extension Module Skeleton / Best Practices
     *
11.1.1 Release
     *
12.0.0 Progress
        *
Ticket/PR Review
        *
GVI Support
  2.
Accessibility SIG
  3.
Contributor License Agreement
  4.
Security Auditing
  5.
Open Q&A / Other Topics?
     *
php2shell



All are welcome to join the free online call, or to suggest additional agenda items. You can find information on joining here:



https://vufind.org/wiki/community_call



See you next week!



- Demian

David,

This is a known problem, captured by this PR:

https://github.com/vufind-org/vufind/pull/5499

The bottom line is that we need to finish our Laminas renovations before we can sort it out — this is currently a top priority!

thanks,
Demian

________________________________
From: Maus, David via Vufind-tech <vuf...@li...>
Sent: Monday, October 26, 2026 7:03 AM
To: 'vuf...@li...' <vuf...@li...>
Subject: [EXTERNAL] [VuFind-Tech] VuFind 11 broken dependency graph?

Moin everyone,

VuFind 11 defines the Supported PHP Version to be 8.2 per composer.json.

{ "config": { "platform": { "php": "8.2" } } }

PHP 8.2 is end of life.

If I bump config.platform.php to 8.3 and run `composer check-platform-reqs` I see that I need to update browsecap/browsecap-php as well because its platform is < 8.3.0.

If I do this and bump browsecap to 7.5 which supports PHP 8.3, I get a conflict with laminas/laminas-cache.

Browsecap requires psr/simple-cache 2.x or 3.x while Laminas Cche requires psr/simple-cache 1.x.

The version 3.14.1 is the last version Laminas Cache's ' 3.x series and still requires psr/simple-cache 1.x.

Composer itself recommends running check-platform-req when using config.platform.php.

If I remove the config.platform setting alltogether, I run into the same issue when calling composer update.

So... The dependency graph of VuFind 11 is broken, isn't it?

Cheers,
  -- David

David Maus
Leiter Discovery-Systeme und BMS-Entwicklung
Staats- und Universitaetsbibliothek Hamburg Carl von Ossietzky
Von-Melle-Park 3, 20146 Hamburg
Tel.: +49 (40) 300393-341
Mail: dav...@su...

Die Geschlechtsidentität von Menschen ist weder über Aussehen noch
über Namen verlässlich abzuleiten. Gerne können Sie mir mitteilen,
wie ich Sie ansprechen darf. Meine Pronomen sind er/ihm (he/him).

#gerneperDu

Moin everyone,

VuFind 11 defines the Supported PHP Version to be 8.2 per composer.json.

{ "config": { "platform": { "php": "8.2" } } }

PHP 8.2 is end of life. 

If I bump config.platform.php to 8.3 and run `composer check-platform-reqs` I see that I need to update browsecap/browsecap-php as well because its platform is < 8.3.0.

If I do this and bump browsecap to 7.5 which supports PHP 8.3, I get a conflict with laminas/laminas-cache. 

Browsecap requires psr/simple-cache 2.x or 3.x while Laminas Cche requires psr/simple-cache 1.x.

The version 3.14.1 is the last version Laminas Cache's ' 3.x series and still requires psr/simple-cache 1.x.

Composer itself recommends running check-platform-req when using config.platform.php.

If I remove the config.platform setting alltogether, I run into the same issue when calling composer update.

So... The dependency graph of VuFind 11 is broken, isn't it?

Cheers,
  -- David

David Maus
Leiter Discovery-Systeme und BMS-Entwicklung
Staats- und Universitaetsbibliothek Hamburg Carl von Ossietzky
Von-Melle-Park 3, 20146 Hamburg
Tel.: +49 (40) 300393-341
Mail: dav...@su...

Die Geschlechtsidentität von Menschen ist weder über Aussehen noch 
über Namen verlässlich abzuleiten. Gerne können Sie mir mitteilen, 
wie ich Sie ansprechen darf. Meine Pronomen sind er/ihm (he/him).

#gerneperDu

Hello, everyone --

In case you're not already following the Solutions Showcase Series (which covers strategies for dealing with the aggressive crawler bots that have been causing trouble for many of us in recent years), you might be interested to see that a VuFind®-themed session is coming up next month! See below for details.

- Demian

________________________________
From: Arran Griffith <Arr...@ly...>
Hi All,

We are excited to share details about the next two Solutions Showcases in our series. This will make the 13th and 14th Solutions Showcases in the Series, and we couldn’t be more excited.

If you’re new to this event, The Solutions Showcase Series is a regular virtual event, bringing together individuals and institutions from across the cultural heritage sector to demo practical solutions they've implemented to mitigate the negative impacts of AI bot activity and harvesting on their systems, including repositories, websites, catalogues, and more.

Details:


Solutions Showcase #13 - How VuFind® Users are Blocking the Bots

Date: Tuesday, November 3rd, 2026

Time: 10:00am Eastern

Location: Zoom - https://lyrasis.zoom.us/meeting/register/yobnJhWUSMOraw0JTebWUQ

  *   This session will feature a live demo and time for Q&A.

  *   Demos will span a diverse range of technical approaches, including open and non-open-source solutions.


The session will bring three VuFind® community users together to share how they are individually tackling aggressive bot traffic on their VuFind® instances at their institutions.

Demian Katz, Falvey Library - Falvey Library hosts multiple VuFind® instances (as well as various other PHP applications). They have built a custom PHP application-level firewall which can be included into the bootstrapper of any PHP application to perform checks to block bots. This tool allows us to quickly respond to changing behavior and implement custom solutions to urgent problems.

Maccabee Levine, Lehigh University Library - The library is using VuFind's built-in Rate Limiter including its integration with Cloudflare Turnstile. A brief overview explanation can be found here: https://vufind.org/wiki/administration:rate_limiting

Megan Schanz, Michigan State Library - Here, the library is making use of a layered approach for bot detection and blocking. They deploy the open-source tool go-away, which issues automated challenges that require no user interaction, alongside custom Traefik and Apache rules that filter out known bad URL patterns and checking against aggregated blocklists before requests hit our application layer.


Solutions Showcase #14 - Anubis Update with Xe Iaso

Date: Wednesday, December 2nd, 2026

Time: 1:00pm Eastern

Location: Zoom - https://lyrasis.zoom.us/meeting/register/PLCXoYLNRlKKJcaZFRWqbA


We are excited to bring Anubis back to the Solutions Showcase Series! Xe Iaso returns to provide an update what's new with the tool, and to talk openly about the hard parts of raising the bar for "bad" traffic without blocking the good. Xe will discuss the complications around detection, the dilemma of deploying tools that can become targets, and why accessibility tools and scrapers increasingly look alike.


To read more about the presenters, and see information about previous Solutions Showcases, check out our wiki space: https://wiki.lyrasis.org/display/cmtygp/Solutions+Showcase

________________________________

The Solutions Showcase Series is organized by the AI Discussions Group, a collaborative initiative that emerged from shared concerns about the impact of AI-driven web harvesting on academic institutions. While our initial focus was on academic repositories, we’ve since expanded our scope to include all corners of the GLAM sector.

Read more about some of our working group here: https://wiki.lyrasis.org/spaces/cmtygp/pages/364743611/Community+AI+Discussions+Working+Group

Have a solution to share?
We’re actively looking for additional presenters! If your institution has addressed AI bot scraping in a creative or effective way, we’d love to feature your work. Please reach out to Arran Griffith at arr...@ly...<mailto:arr...@ly...> to book a presentation slot.

Cheers,
Arran Griffith, on behalf of The AI Discussions Group

---
Arran Griffith
Program Manager, Fedora Program
Lyrasis
Book a time to meet with me<https://calendly.com/griffith-lyrasis/new-meeting>


[A picture containing logo  Description automatically generated]
https://fedorarepository.org/

Here are the minutes from today's Community Call:

https://vufind.org/wiki/community_call:minutes20261006

The next call will be Tuesday, November 3, 2026 at 9am Eastern Daylight Time (13:00 GMT).

- Demian

Hello, everyone!



The September, 2026 VuFind® newsletter is now available:



https://vufind.org/wiki/community:newsletter:2026-09



Additionally, the next Community Call will be held on Tuesday, October 6, 2026 at 9am Eastern Daylight Time (13:00 GMT).



Here is the full agenda:



  1.  Development Planning
     *   Newsletter Highlights
     *
Follow-Up to Past Discussions
        *
Solr Upgrade
        *
Laminas MVC End of Life
        *
Dark Mode PR
        *
Extension Module Skeleton / Best Practices
     *
11.1.1 Release
     *
12.0.0 Progress
        *
Ticket/PR Review
        *
Items to Defer
        *
GVI Support
  2.
Accessibility SIG
  3.
Installations Wiki Page
  4.
Security Auditing
  5.  Open Q&A / Other Topics?



All are welcome to join the free online call, or to suggest additional agenda items. You can find information on joining here:



https://vufind.org/wiki/community_call



See you next week!



- Demian

Hello, everyone --

Just a reminder that if you want to participate in this year's VuFind® Summit, you can join the stream for free using the link and password found on this wiki page:

https://vufind.org/wiki/community:conferences:summit_2026

While the Summit is running, the green banner at the top of every page of vufind.org will show you the start and end times converted into your local time zone.

I hope to see you there!

- Demian

Hello, everyone!



The August, 2026 VuFind® newsletter is now available:



https://vufind.org/wiki/community:newsletter:2026-08


Note that there will be no September Community Call because of the VuFind®

Summit at WOLFcon. The Summit will include a free livestream; you can find schedule and access information here:

https://vufind.org/wiki/community:conferences:summit_2026

I hope to see you there!

- Demian

Hello, everyone!

I will be on summer vacation starting tomorrow (Friday, August 7), returning to work on Monday, August 17.

As always, I'll be checking email as much as possible while away, but I probably won't have time to address particularly complex problems or complete a lot of code reviews. If others can assist in these areas during my absence, I will be grateful!

I hope everyone has a good week or so - and I'll see you again later in the month!

- Demian

The State and University Library Hamburg is inviting you to the German
VuFind® User Meetup on November 16th and 17th 2026. Over the span of two
days, VuFind® users get together to exchange knowledge, discuss challenges
and take a collaborative look towards the future. Whether you are new to the
world of VuFind® or have been a dedicated member of the community for quite
some time: You are very welcome to come together and reflect on how
Discovery Systems, especially VuFind®, manage to live up to the
ever-changing expectations of users, workforces and institutions.

With the transition to the new library management system FOLIO, an
evergrowing landscape of specialized information services, as well as the
rising digitalisation of library processes, owning a Discovery system as a
service platform has become more important than ever.

For that reason, we would love to discuss these and other future endeavours
with you. Just like last year, we are going to combine hands-on workshops
with exciting talks.

For convenience, the workshops will mainly be held on Nov 16th, and the
talks on Nov 17th.

Please submit your application via e-mail (dis...@su...)
until September 30th 2026.

For your application proposal, we require the following information:

- what kind of lecture (workshop or talk)
- intended language (german preferred)
- title
- brief description
- lecturer(s) (as well as their contact details)
- estimated duration
- maximum attendee capacity
- required (technological) equipment

Best regards,
  David Maus

David Maus
Leiter Discovery-Systeme und BMS-Entwicklung
Staats- und Universitaetsbibliothek Hamburg Carl von Ossietzky
Von-Melle-Park 3, 20146 Hamburg
Tel.: +49 (40) 300393-341
Mail: dav...@su...

Die Geschlechtsidentität von Menschen ist weder über Aussehen noch 
über Namen verlässlich abzuleiten. Gerne können Sie mir mitteilen, 
wie ich Sie ansprechen darf. Meine Pronomen sind er/ihm (he/him).

#gerneperDu

Here are the minutes from today's Community Call:

https://vufind.org/wiki/community_call:minutes20260804

The next call will be Tuesday, October 6, 2026 at 9am Eastern Daylight Time (13:00 GMT).

The September meeting has been canceled since it coincides with the VuFind® Summit at WOLFcon (which is free for all to join; see: https://vufind.org/wiki/community:conferences:summit_2026).

- Demian

Hello, everyone!

The August, 2026 VuFind® newsletter is now available:

https://vufind.org/wiki/community:newsletter:2026-07

Additionally, the next Community Call will be held on Tuesday, August 4, 2026 at 9am Eastern Daylight Time (13:00 GMT).

Here is the full agenda:


  1.  Development Planning
     *   Newsletter Highlights
     *   Follow-Up to Past Discussions

                                                               i.      Solr 9.10 Upgrade

                                                             ii.      Laminas MVC End of Life

                                                           iii.      Improving Abstract Factories

                                                           iv.      Dark Mode PR

                                                             v.      Extension Module Skeleton / Best Practices

     *   11.1.0 Release
     *   12.0.0 Progress

                                                               i.      Git Management

                                                             ii.      Language Versions

                                                           iii.      Scoping / Roadmapping the Release

                                                           iv.      Solr JSON Facet API

                                                             v.      GVI Support

  1.  Accessibility SIG
  2.  Open Q&A / Other Topics?

All are welcome to join the free online call, or to suggest additional agenda items. You can find information on joining here:

https://vufind.org/wiki/community_call

See you next week!

- Demian

Hello, everyone!

As previewed at the last Community Call, the VuFind(r) project's interim AI policy is now posted: https://vufind.org/wiki/ai_policy

If you have any questions or concerns, please feel free to share them with me (or any member of the Project Management Committee).

- Demian

Uwe,

It wouldn't be hard to revert to the older MySQL JDBC jar in your instance to test whether that is to blame. Since that jar is only used for importing, it will either work or not work, but it shouldn't have any surprising side effects elsewhere. 😊

- Demian

-----Original Message-----
From: Uwe Steinmann <vu...@st...> 
Sent: Tuesday, July 21, 2026 11:25 AM
To: Demian Katz <dem...@vi...>
Cc: vuf...@li...
Subject: Re: [EXTERNAL] [VuFind-Tech] Database error when importing marc data

Am Tue, Jul 21, 2026 at 11:37:43AM +0000 schrieb Demian Katz:
> Uwe,
> 
> As you say, when you turn on getFirstIndexed/getLastIndexed, the index tool needs to connect to MySQL to obtain details from the change_tracker table there. It uses the credentials in config.ini to make that connection.
> 
> When did you start seeing this problem? If things previously worked and it suddenly started, then I wonder if it relates to an update to your MySQL database or some change in configuration.
It's probably related to the MySQL database. I intially setup the same vufind 11 installation on a debian with mariadb and copied that on a redhat with mysql. So, it's probably the database change which causes it.

I searched the web for a solution and found

https://www.baeldung.com/java-mysql-error-public-key-retrieval

which has a fairly good explanation. Unfornately, the solution to fix it (turning tls/ssl on) is currently not an option on our system.

> I see that Megan Schanz ran into the same error message when setting up a test environment back in October; you can see some discussion in this Slack thread:
> 
> https://open-libr-foundation.slack.com/archives/C08K7F6M61E/p175975496
> 0552069
> 
> It sounds like the use_ssl setting in config.ini may be a factor, so you could try changing that and see what impact it has.
I'm pretty sure, use_ssl=true will fix it, if that parameter is used by the JDBC driver. Megan seemed to have switched to mariadb which doesnt' have that problem.
I'll see if we can turn on ssl for mysql in the long run. Currently, it's not an option.

> I also wonder, if this cropped up after server patching, whether this could be a sign that we need to update JDBC jar files to improve compatibility with newer database versions, though that's just a wild guess.
The same redhat system also hosts a vufind 10 installation which doesn't have that problem. May the update from mysql-connector-java-5.1.48-bin.jar
to mysql-connector-j-9.1.0.jar made the difference.

  Uwe

> -----Original Message-----
> From: Uwe Steinmann <vu...@st...>
> Sent: Tuesday, July 21, 2026 2:40 AM
> To: vuf...@li...
> Subject: [EXTERNAL] [VuFind-Tech] Database error when importing marc 
> data
> 
> Hello everyone,
> 
> when importing marc data I currently see a strange error, of which I 
> have no clue how to fix
> 
>  WARN [RecordIndexer-Thread-0] (Indexer.java:430) - Exception in 
> record: 002009817  WARN [RecordIndexer-Thread-0] (Indexer.java:431) - 
> while processing index specification:  custom, getFirstIndexed(001)  
> WARN [RecordIndexer-Thread-0] (Indexer.java:434) - 
> org.solrmarc.tools.SolrMarcIndexerException: Unable to connect to 
> VuFind database; Public Key Retrieval is not allowed ERROR 
> [RecordIndexer-Thread-0] (DatabaseManager.java:66) - Unable to connect 
> to VuFind database; Public Key Retrieval is not allowed  WARN 
> [RecordIndexer-Thread-0] (Indexer.java:430) - Exception in record: 
> 002009817  WARN [RecordIndexer-Thread-0] (Indexer.java:431) - while 
> processing index specification:  custom, getLastIndexed(001)  WARN 
> [RecordIndexer-Thread-0] (Indexer.java:434) - 
> org.solrmarc.tools.SolrMarcIndexerException: Unable to connect to 
> VuFind database; Public Key Retrieval is not allowed
> 
> I suppose the cause for this is the configuration in 
> local/import/marc_local.properties
> 
> # IMPORTANT: Indexing this extra information will make extra database calls during
> #            the indexing process and will likely slow things down significantly.
> first_indexed = custom, getFirstIndexed(001) last_indexed = custom, 
> getLastIndexed(001)
> 
> and the database used is the one configured in 
> local/config/vufind/config.ini
> 
> The indexing itself seems to be ok, but it takes for ever, due to the massive amount of errors.
> 
> Can somebody put me on the right path to fix this?
> 
>   Uwe

--
  MMK GmbH, Fleyer Str. 196, 58097 Hagen
  Uwe...@mm...
  Tel: 02331 840446    Fax: 02331 843920

Am Tue, Jul 21, 2026 at 11:37:43AM +0000 schrieb Demian Katz:
> Uwe,
> 
> As you say, when you turn on getFirstIndexed/getLastIndexed, the index tool needs to connect to MySQL to obtain details from the change_tracker table there. It uses the credentials in config.ini to make that connection.
> 
> When did you start seeing this problem? If things previously worked and it suddenly started, then I wonder if it relates to an update to your MySQL database or some change in configuration.
It's probably related to the MySQL database. I intially setup the same
vufind 11 installation on a debian with mariadb and copied that on a
redhat with mysql. So, it's probably the database change which causes
it.

I searched the web for a solution and found

https://www.baeldung.com/java-mysql-error-public-key-retrieval

which has a fairly good explanation. Unfornately, the solution to
fix it (turning tls/ssl on) is currently not an option on our system.

> I see that Megan Schanz ran into the same error message when setting up a test environment back in October; you can see some discussion in this Slack thread:
> 
> https://open-libr-foundation.slack.com/archives/C08K7F6M61E/p1759754960552069
> 
> It sounds like the use_ssl setting in config.ini may be a factor, so you could try changing that and see what impact it has.
I'm pretty sure, use_ssl=true will fix it, if that parameter is
used by the JDBC driver. Megan seemed to have switched to mariadb which
doesnt' have that problem.
I'll see if we can turn on ssl for mysql in the long run. Currently,
it's not an option.

> I also wonder, if this cropped up after server patching, whether this could be a sign that we need to update JDBC jar files to improve compatibility with newer database versions, though that's just a wild guess.
The same redhat system also hosts a vufind 10 installation which doesn't
have that problem. May the update from mysql-connector-java-5.1.48-bin.jar
to mysql-connector-j-9.1.0.jar made the difference.

  Uwe

> -----Original Message-----
> From: Uwe Steinmann <vu...@st...> 
> Sent: Tuesday, July 21, 2026 2:40 AM
> To: vuf...@li...
> Subject: [EXTERNAL] [VuFind-Tech] Database error when importing marc data
> 
> Hello everyone,
> 
> when importing marc data I currently see a strange error, of which I have no clue how to fix
> 
>  WARN [RecordIndexer-Thread-0] (Indexer.java:430) - Exception in record: 002009817  WARN [RecordIndexer-Thread-0] (Indexer.java:431) - while processing index specification:  custom, getFirstIndexed(001)  WARN [RecordIndexer-Thread-0] (Indexer.java:434) - org.solrmarc.tools.SolrMarcIndexerException: Unable to connect to VuFind database; Public Key Retrieval is not allowed ERROR [RecordIndexer-Thread-0] (DatabaseManager.java:66) - Unable to connect to VuFind database; Public Key Retrieval is not allowed  WARN [RecordIndexer-Thread-0] (Indexer.java:430) - Exception in record: 002009817  WARN [RecordIndexer-Thread-0] (Indexer.java:431) - while processing index specification:  custom, getLastIndexed(001)  WARN [RecordIndexer-Thread-0] (Indexer.java:434) - org.solrmarc.tools.SolrMarcIndexerException: Unable to connect to VuFind database; Public Key Retrieval is not allowed
> 
> I suppose the cause for this is the configuration in local/import/marc_local.properties
> 
> # IMPORTANT: Indexing this extra information will make extra database calls during
> #            the indexing process and will likely slow things down significantly.
> first_indexed = custom, getFirstIndexed(001) last_indexed = custom, getLastIndexed(001)
> 
> and the database used is the one configured in local/config/vufind/config.ini
> 
> The indexing itself seems to be ok, but it takes for ever, due to the massive amount of errors.
> 
> Can somebody put me on the right path to fix this?
> 
>   Uwe

-- 
  MMK GmbH, Fleyer Str. 196, 58097 Hagen
  Uwe...@mm...
  Tel: 02331 840446    Fax: 02331 843920

Uwe,

As you say, when you turn on getFirstIndexed/getLastIndexed, the index tool needs to connect to MySQL to obtain details from the change_tracker table there. It uses the credentials in config.ini to make that connection.

When did you start seeing this problem? If things previously worked and it suddenly started, then I wonder if it relates to an update to your MySQL database or some change in configuration.

I see that Megan Schanz ran into the same error message when setting up a test environment back in October; you can see some discussion in this Slack thread:

https://open-libr-foundation.slack.com/archives/C08K7F6M61E/p1759754960552069

It sounds like the use_ssl setting in config.ini may be a factor, so you could try changing that and see what impact it has.

I also wonder, if this cropped up after server patching, whether this could be a sign that we need to update JDBC jar files to improve compatibility with newer database versions, though that's just a wild guess.

- Demian

-----Original Message-----
From: Uwe Steinmann <vu...@st...> 
Sent: Tuesday, July 21, 2026 2:40 AM
To: vuf...@li...
Subject: [EXTERNAL] [VuFind-Tech] Database error when importing marc data

Hello everyone,

when importing marc data I currently see a strange error, of which I have no clue how to fix

 WARN [RecordIndexer-Thread-0] (Indexer.java:430) - Exception in record: 002009817  WARN [RecordIndexer-Thread-0] (Indexer.java:431) - while processing index specification:  custom, getFirstIndexed(001)  WARN [RecordIndexer-Thread-0] (Indexer.java:434) - org.solrmarc.tools.SolrMarcIndexerException: Unable to connect to VuFind database; Public Key Retrieval is not allowed ERROR [RecordIndexer-Thread-0] (DatabaseManager.java:66) - Unable to connect to VuFind database; Public Key Retrieval is not allowed  WARN [RecordIndexer-Thread-0] (Indexer.java:430) - Exception in record: 002009817  WARN [RecordIndexer-Thread-0] (Indexer.java:431) - while processing index specification:  custom, getLastIndexed(001)  WARN [RecordIndexer-Thread-0] (Indexer.java:434) - org.solrmarc.tools.SolrMarcIndexerException: Unable to connect to VuFind database; Public Key Retrieval is not allowed

I suppose the cause for this is the configuration in local/import/marc_local.properties

# IMPORTANT: Indexing this extra information will make extra database calls during
#            the indexing process and will likely slow things down significantly.
first_indexed = custom, getFirstIndexed(001) last_indexed = custom, getLastIndexed(001)

and the database used is the one configured in local/config/vufind/config.ini

The indexing itself seems to be ok, but it takes for ever, due to the massive amount of errors.

Can somebody put me on the right path to fix this?

  Uwe

Hello everyone,

when importing marc data I currently see a strange error, of which
I have no clue how to fix

 WARN [RecordIndexer-Thread-0] (Indexer.java:430) - Exception in record: 002009817
 WARN [RecordIndexer-Thread-0] (Indexer.java:431) - while processing index specification:  custom, getFirstIndexed(001)
 WARN [RecordIndexer-Thread-0] (Indexer.java:434) - org.solrmarc.tools.SolrMarcIndexerException: Unable to connect to VuFind database; Public Key Retrieval is not allowed
ERROR [RecordIndexer-Thread-0] (DatabaseManager.java:66) - Unable to connect to VuFind database; Public Key Retrieval is not allowed
 WARN [RecordIndexer-Thread-0] (Indexer.java:430) - Exception in record: 002009817
 WARN [RecordIndexer-Thread-0] (Indexer.java:431) - while processing index specification:  custom, getLastIndexed(001)
 WARN [RecordIndexer-Thread-0] (Indexer.java:434) - org.solrmarc.tools.SolrMarcIndexerException: Unable to connect to VuFind database; Public Key Retrieval is not allowed

I suppose the cause for this is the configuration in
local/import/marc_local.properties

# IMPORTANT: Indexing this extra information will make extra database calls during
#            the indexing process and will likely slow things down significantly.
first_indexed = custom, getFirstIndexed(001)
last_indexed = custom, getLastIndexed(001)

and the database used is the one configured in
local/config/vufind/config.ini

The indexing itself seems to be ok, but it takes for ever, due to
the massive amount of errors.

Can somebody put me on the right path to fix this?

  Uwe

FOR IMMEDIATE RELEASE

VuFind® 11.1 Released

Villanova, Pennsylvania - July 20, 2026 - Version 11.1 of the VuFind® Open Source discovery software has just been released. This minor release includes new features as well as many added configuration settings, accessibility enhancements and bug fixes.

Some key additions and changes:
- A configurable “Get This” service for highlighting options for obtaining items from the catalog in a pop-up window.
- The ability to configure global notices that display in the user interface.
- New and improved integrations, including support for Qualified Dublin Core records, a link resolver driver for EBSCO's LinkIQ, and added FOLIO and Koha features.
- A new user interface translation: Tamil.
- Improved compatibility with PHP 8.5.

Questions about the new release or VuFind® in general can be directed to Demian Katz, the chair of the VuFind® Project Management Committee and the Director of Library Technology at Villanova University. The software and its
documentation may be found at https://vufind.org.

Contact:
Demian Katz
dem...@vi...
Villanova University
Falvey Library
800 Lancaster Avenue
Villanova, PA 19085

###

Here are the minutes from today's Community Call:

https://vufind.org/wiki/community_call:minutes20260707

The next call will be Tuesday, August 4, 2026 at 9am Eastern Daylight Time (13:00 GMT).

- Demian

Hello, everyone -

Just a heads-up that I will be traveling for the next week or so - I will be departing tomorrow (July 3) and returning to the office on Monday, July 13. In the interim, I will try to check messages periodically but will have limited time to reply or perform reviews. Apologies in advance if things slow down for a while.

If others have time to help with reviews and support in my absence, I'm always grateful for any assistance. If not, I'll do my best to catch up when I return!

thanks,
Demian

Hello, everyone!

The June, 2026 VuFind® newsletter is now available:

https://vufind.org/wiki/community:newsletter:2026-06

Additionally, the next Community Call will be held on Tuesday, July 7, 2026 at 9am Eastern Daylight Time (13:00 GMT).

Here is the full agenda:


  1.  Development Planning
     *   Newsletter Highlights
     *   Follow-Up to Past Discussions

                                                               i.      Solr 9.10 Upgrade

                                                             ii.      Laminas MVC End of Life

                                                           iii.      Improving Abstract Factories

                                                           iv.      Dark Mode PR

                                                             v.      Extension Module Skeleton / Best Practices

                                                           vi.      FontAwesome 7

                                                          vii.      FOLIO Checkout Sorting

     *   11.1.0 Progress and Release Date
     *   12.0.0 Pull Request and JIRA Ticket Highlights

                                                               i.      Solr JSON Facet API

                                                             ii.      GVI Support

  1.  Accessibility SIG
  2.  Open Q&A / Other Topics?

All are welcome to join the free online call, or to suggest additional agenda items. You can find information on joining here:

https://vufind.org/wiki/community_call

See you next week!

- Demian

Amy,

I don’t think you have anything to worry about – when you index records into VuFind®’s Solr index, if they have an ID that matches an existing record, the new version simply replaces the old version. If you’re improving authorities and uploading modified records, the index will get updated accordingly, and this shouldn’t cause any problems. The separate authority index is only used for a limited number of things (mainly populating cross-references in the alphabetic browse system and the authority recommendation module); without an authority index, you can’t currently be using those features, so nothing you change will affect them.

I hope that helps, but please let me know if you still have any questions!

- Demian

From: Amy Boylan <amy...@ma...>
Sent: Friday, June 26, 2026 5:45 AM
To: vuf...@li...
Subject: [EXTERNAL] [VuFind-Tech] Authority deduplication in VuFind

Dear Demian,

My colleague Sue Hemmens recently retired from Marsh's Library and we are currently navigating looking after the VuFind catalogue she built so well. We use KOHA as our LMS and at the moment I am working with a colleague to merge duplicate authorities there. Once this is done I download the MARC records and then our IT support, interleaf, upload them to VuFind as I no longer have access to the server. I've tried it with a couple and it has worked, but I am concerned this piecemeal approach may have consequences for the index. Sue has told me that she did not import the authorities separately, rather they are imported with the bib record, so there is no authority index, but are there implications for the bib index? Any help would be much appreciated.

Thank you and all the best,

Amy
Amy Boylan
Assistant Director
Marsh's Library, St Patrick's Close, Dublin 8, Ireland
(01) 454 3511

Marsh's Library is a Registered Charity: RCN 20000752
Revenue Commissioners: CHY509