Business::ISBN::Data isn't especially maintained and suggests using an up to date RangeMessage.xml file from https://www.isbn-international.org/range_file_generation. We should bundle a more up to date RangeMessage file with koha and set the appropriate environment in both plack and apache to point to the bundled version. This would help with new ISBN's that are not yet in the shipped Business::ISBN::Data package.
In a mojo app I once build I had the followup in a bootstrap routine at application startup. # Ensure we're using an up to date set of data in Business::ISBN my $ISBN_RANGE_FILE = $app->home->rel_file('lib/Business/ISBN/RangeMessage.xml'); $ENV{'ISBN_RANGE_MESSAGE'} = "$ISBN_RANGE_FILE"; We could add similar to the plack start script and a SetEnv to the apache configs based on where we chose to store the file.. To keep this file up to date, I would envisage part of the release workflow being the download and replacement of the RangeMessage file.
I can confirm that this can fix a problem where ISBNs are not handled correctly by Business::ISBN, leading to fewer coverimages being shown in the OPAC.
This sounds logical, what is required for bundling the newer file exactly?