Summary: | We should bundle an up to date RangeMessage.xml for Business::ISBN | ||
---|---|---|---|
Product: | Koha | Reporter: | Martin Renvoize <martin.renvoize> |
Component: | Architecture, internals, and plumbing | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | magnus |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20244 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14287 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13192 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35729 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35755 |
||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: |
Description
Martin Renvoize
2018-11-13 13:38:06 UTC
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? |