[koha-commits] main Koha release repository branch 19.11.x updated. v19.11.04-66-g2c2e229709
Git repo owner
gitmaster at git.koha-community.org
Fri Apr 3 19:49:53 CEST 2020
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "main Koha release repository".
The branch, 19.11.x has been updated
via 2c2e229709e723c7604fecf0a5607486ed1e6d14 (commit)
via df4811ae1f2ff5a21ea5a3a7db97b19ecfdc4f6d (commit)
via 5fbde57bbcb5c4035c6e7a5a7416ebbc407719e2 (commit)
via 120547748d4fe6497512169b4a7a8be895128f87 (commit)
via bfe923de3e57631ac59515c65e90e9253988de23 (commit)
via b32023b10109e9e487f5aa59d194fa5599231743 (commit)
from a9886168559f158a3c9bfcee859ffc28b6939354 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 2c2e229709e723c7604fecf0a5607486ed1e6d14
Author: Nick Clemens <nick at bywatersolutions.com>
Date: Mon Mar 9 09:41:26 2020 +0000
Bug 19288: Don't show patron info for item level holds on details.pl unless hold is waiting
This persists after bug 20948 - we can still display patron information even if this patron is not the one
who will receive the item upon checkin. The holds tab can give an overview of holds and information - I think
on the details page the only info we need is whether there might be a item level hold, not who it is for
To test:
1 - Place an item level hold for delivery at a branch not matching home branch of item
2 - Place a record level hold for delivery at homebranch of item placed on hold above
3 - Enable LocalHoldsPriority with 'pickup library' matches the item's 'home library'
4 - View the details for the page, it says the item has a hold for the patron with an item level hold
5 - Check in the item, the hold triggered is for the next available patron, ignore the hold
6 - Apply patch
7 - Check details page, 'There is an item-level hold (priority=1)' with no patron info
8 - Check in, next available hold is still the one triggered
Signed-off-by: Martin Renvoize <martin.renvoize at ptfs-europe.com>
Signed-off-by: Jonathan Druart <jonathan.druart at bugs.koha-community.org>
Signed-off-by: Martin Renvoize <martin.renvoize at ptfs-europe.com>
Signed-off-by: Joy Nelson <joy at bywatersolutions.com>
commit df4811ae1f2ff5a21ea5a3a7db97b19ecfdc4f6d
Author: Fridolin Somers <fridolin.somers at biblibre.com>
Date: Fri Jul 26 15:43:02 2019 +0200
Bug 23383: fix IdRef syspref test in XSLT
IdRef link is displayed via XSLT.
There is a test of syspref with just if value is defined.
But in installer/data/mysql/sysprefs.sql you see this pref will be 0 by default, which is true in XPATH.
We should test that pref is 1.
Test plan :
1) Create a fresh UNIMARC database
2) You have pref IdRef disabled
3) Simulate a SUDOC record:
Fill a 7..$3 field with a ppn (032581270 for example).
Fill the 009 field with an integer
4) Go to the opac detail page of the record => You don't see IdRef link
5) Enable IdRef syspref
6) Go to the opac detail page of the record => You see IdRef link
7) Disable IdRef syspref
8) Go to the opac detail page of the record => You don't see IdRef link
Signed-off-by: Martin Renvoize <martin.renvoize at ptfs-europe.com>
Signed-off-by: Jonathan Druart <jonathan.druart at bugs.koha-community.org>
Signed-off-by: Martin Renvoize <martin.renvoize at ptfs-europe.com>
Signed-off-by: Joy Nelson <joy at bywatersolutions.com>
commit 5fbde57bbcb5c4035c6e7a5a7416ebbc407719e2
Author: Andrew Fuerste-Henry <andrew at bywatersolutions.com>
Date: Wed Mar 11 00:54:03 2020 +0000
Bug 24838: Fix help link for patron categories
To test:
- go to admin/categories.pl
- click Help, confirm it takes you to manual main page
- apply patch
- restart all
- click Help, confirm it takes you to patron categories in manual
Signed-off-by: Sally <sally.healey at cheshiresharedservices.gov.uk>
Signed-off-by: Jonathan Druart <jonathan.druart at bugs.koha-community.org>
Signed-off-by: Martin Renvoize <martin.renvoize at ptfs-europe.com>
Signed-off-by: Joy Nelson <joy at bywatersolutions.com>
commit 120547748d4fe6497512169b4a7a8be895128f87
Author: Nick Clemens <nick at bywatersolutions.com>
Date: Fri Oct 25 13:49:05 2019 +0000
Bug 23521: (follow-up) Add quotes
Not only should terms from facets/limits be grouped, but order should probably matter
We build a different facet for "Dillinger Girl" or "Girl Dillinger"
The parens are possibly overkill now, but I think it makes it very clear and does not hurt
To test:
1 - Follow original plan
2 - Create a new record with 'Girl Dillinger' as author
3 - Search for 'Dill*'
4 - You get all three records (and maybe others that match)
5 - Limit by 'Girl Dillinger' - you get two records
6 - Same for 'Dillinger Girl'
7 - Apply patch
8 - Limits/facets for 'Dillinger Girl' and 'Girl Dillinger' now match a isngle record
Signed-off-by: Ere Maijala <ere.maijala at helsinki.fi>
Signed-off-by: Martin Renvoize <martin.renvoize at ptfs-europe.com>
Signed-off-by: Joy Nelson <joy at bywatersolutions.com>
commit bfe923de3e57631ac59515c65e90e9253988de23
Author: Alex Arnaud <alex.arnaud at biblibre.com>
Date: Thu Aug 29 15:06:14 2019 +0000
Bug 23521: Put parentheses arround limit terms
Test plan:
- Use Elasticsearch 6 (you'll need Bug 18969),
- create a biblio (#1) with "Dillinger Girl" in author and what you
want in title,
- create another biblio (#2) with the word "girl" in the title and
"Dillinger Escaplan" as author
- reindex
- search * and refine on "Dillinger Girl"
- Ko => Biblio #1 and #2 appear
- Apply this patch,
- search * and refine on "Dillinger Girl"
- Ok => anly biblio #1 appears
- use Elasticsearch 5 again
- check for no search regression
Signed-off-by: Séverine QUEUNE <severine.queune at bulac.fr>
Signed-off-by: Séverine QUEUNE <severine.queune at bulac.fr>
Signed-off-by: Nick Clemens <nick at bywatersolutions.com>
Signed-off-by: Ere Maijala <ere.maijala at helsinki.fi>
Signed-off-by: Martin Renvoize <martin.renvoize at ptfs-europe.com>
Signed-off-by: Joy Nelson <joy at bywatersolutions.com>
commit b32023b10109e9e487f5aa59d194fa5599231743
Author: Andrew Isherwood <andrew.isherwood at ptfs-europe.com>
Date: Mon Feb 3 11:14:50 2020 +0000
Bug 24565: Add patron profile to ILL list pages
We need the API call to get ILL requests on the patron profile page,
this commit allows this.
Test plan:
- Do not apply the patch.
- Go to the "Ill requests history" page for a patron who has made ILL
requests
- TEST: Observe that no requests are displayed
- Apply the patch
- Refresh the page
- TEST: Observe that requests are displayed
- Go to the main "ILL requests" page
- TEST: Observe that requests are displayed
Signed-off-by: Owen Leonard <oleonard at myacpl.org>
Signed-off-by: Martin Renvoize <martin.renvoize at ptfs-europe.com>
Signed-off-by: Joy Nelson <joy at bywatersolutions.com>
-----------------------------------------------------------------------
Summary of changes:
Koha/Manual.pm | 2 +-
Koha/SearchEngine/Elasticsearch/QueryBuilder.pm | 8 +++++++-
.../intranet-tmpl/prog/en/modules/catalogue/detail.tt | 10 ++++------
koha-tmpl/intranet-tmpl/prog/js/ill-list-table.js | 12 ++++++++++--
.../opac-tmpl/bootstrap/en/xslt/UNIMARCslimUtils.xsl | 2 +-
.../Koha/SearchEngine/Elasticsearch/QueryBuilder.t | 16 +++++++++++++++-
6 files changed, 38 insertions(+), 12 deletions(-)
hooks/post-receive
--
main Koha release repository
More information about the koha-commits
mailing list