Created attachment 16094 [details] [review] Bug 9810 - Search limit 'available' does not hide damaged or withdrawn items Test Plan: 1) Perform a search that will return an a damaged item and a withdrawn item ( for simplicity, have those items be the only one on each record, respectively ) 2) Run the same search but limit to available items only 3) Note those items still appear in the search results 4) Apply this patch 5) Run the search again 6) Note the items no longer appear in the search results
It would also be nice to hide waiting items with the availability limit, but that is more difficult. I think it would require adding a 'waiting' field to the items table, mapping it to a marc field, making sure Koha updates the field properly, adding it to the zebra indexes, and then adding it to the availability limit code.
Created attachment 16402 [details] [review] Bug 9810 - Search limit 'available' does not hide damaged or withdrawn items Test Plan: 1) Perform a search that will return an a damaged item and a withdrawn item ( for simplicity, have those items be the only one on each record, respectively ) 2) Run the same search but limit to available items only 3) Note those items still appear in the search results 4) Apply this patch 5) Run the search again 6) Note the items no longer appear in the search results Signed-off-by: Matthias Meusburger <matthias.meusburger@biblibre.com>
QA comment: The patch works but not out of the box! With an UNIMARC installation, the damaged and withdrawn indexes are not defined. So the patch causes an empty results page. Marked as Failed QA.
I will propose a patch for that
Created attachment 16542 [details] [review] Bug 9810: Add indexes withdrawn and damaged for UNIMARC After applying this patch, the zebra's index should be rebuild!
Note for RM: The zebra's index should be rebuild on each UNIMARC installation after applying these patches. Switch back to Needs Signoff
1 - I apply this patch 2 - I create WITHDRAWN list with 0 and 1 values 3 - I change item cataloguing by introduction a 995$3 field link to this list 4 - I modify two item in filling 995$3 with witdrawn = 1 5 - Rebuild zebra index was done 6 - Items are still visible in OPAC and their status is "available"
(In reply to comment #8) > 1 - I apply this patch > 2 - I create WITHDRAWN list with 0 and 1 values > 3 - I change item cataloguing by introduction a 995$3 field link to this list > 4 - I modify two item in filling 995$3 with witdrawn = 1 > 5 - Rebuild zebra index was done > 6 - Items are still visible in OPAC and their status is "available" Did you apply changes to the zebra config file (record.abs)?
Comment on attachment 16542 [details] [review] Bug 9810: Add indexes withdrawn and damaged for UNIMARC These indexes have already been added by a different commit. This patch is no longer needed.
Created attachment 28526 [details] [review] Bug 9810 [Followup] - Hide items with notforloan < 0 when limiting to available items Not for loan statuses of less then 0 are considered 'unavailable' in Koha parlance, whereas items with a not for loan status greater than 0 are considered available, but not checkout-able ( i.g. reference items ). This should be taken into account by the availability filter.
Created attachment 29579 [details] [review] Bug 9810 - Search limit 'available' does not hide damaged or withdrawn items Test Plan: 1) Perform a search that will return an a damaged item and a withdrawn item ( for simplicity, have those items be the only one on each record, respectively ) 2) Run the same search but limit to available items only 3) Note those items still appear in the search results 4) Apply this patch 5) Run the search again 6) Note the items no longer appear in the search results Signed-off-by: Matthias Meusburger <matthias.meusburger@biblibre.com> Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Created attachment 29580 [details] [review] Bug 9810 [Followup] - Hide items with notforloan < 0 when limiting to available items Not for loan statuses of less then 0 are considered 'unavailable' in Koha parlance, whereas items with a not for loan status greater than 0 are considered available, but not checkout-able ( i.g. reference items ). This should be taken into account by the availability filter.
Both patches work fine for me. But I wonder if the second patch will work for UNIMARC. (I do not find notforloan in the record.abs of UNIMARC) Could a UNIMARC user confirm this please? No problems for qa tools. Changing status to Failed QA for need of clarification.
Small additional remark (apparently outside the scope of this report but observed while testing it): If I toggle the status of Available items and All items, the first time it works but the second time it does no longer work. As you can see below, the query contains kw: the second time, resulting in 0 hits. First URL for limiting to available: /cgi-bin/koha/catalogue/search.pl?q=london%20india%20%23relevance_dsc&sort_by=relevance_dsc&limit=available Second URL: /cgi-bin/koha/catalogue/search.pl?q=kw%3Alondon%20india%20%23relevance_dsc&sort_by=relevance_dsc&limit=available
(In reply to M. de Rooy from comment #14) > Both patches work fine for me. But I wonder if the second patch will work > for UNIMARC. (I do not find notforloan in the record.abs of UNIMARC) > Could a UNIMARC user confirm this please? The notforloan index does not seem to exist, I confirm. I added a patch for withdrawn and damaged indexes (see comment 6).
Jonathan, with no notforloan index, does the feature fail gracefully for unimarc? That is, it may not resolve the issue, but it doesn't break anything. If so, I think we can push the patch and file a separate bug to add the notforloan index for unimarc users. (In reply to Jonathan Druart from comment #16) > (In reply to M. de Rooy from comment #14) > > Both patches work fine for me. But I wonder if the second patch will work > > for UNIMARC. (I do not find notforloan in the record.abs of UNIMARC) > > Could a UNIMARC user confirm this please? > > The notforloan index does not seem to exist, I confirm. > I added a patch for withdrawn and damaged indexes (see comment 6).
(In reply to Kyle M Hall from comment #17) > Jonathan, with no notforloan index, does the feature fail gracefully for > unimarc? I don't get an "internal server error", but the result list is empty.
(In reply to Jonathan Druart from comment #18) > (In reply to Kyle M Hall from comment #17) > > Jonathan, with no notforloan index, does the feature fail gracefully for > > unimarc? > > I don't get an "internal server error", but the result list is empty. Thanks, Jonathan. Sorry, Kyle, but that means that this cannot pass qa in the current form. We would introduce more misinformation (no hits) for unimarc users than only showing a damaged item or so too much. Could you adjust the follow-up and make this notforloan part non-unimarc specific?
Created attachment 29644 [details] [review] Bug 9810: Add index notforloan for unimarc This patch adds the notforloan index for UNIMARC (GRS-1 and DOM). Not that the original patch does not work out of the box: the notforloan, withdrawn and damaged indexes are not defined in the frameworks and mapping. Signed-off-by: Jonathan Druart <jonathan.druart@biblibre.com>
(In reply to M. de Rooy from comment #19) > (In reply to Jonathan Druart from comment #18) > > (In reply to Kyle M Hall from comment #17) > > > Jonathan, with no notforloan index, does the feature fail gracefully for > > > unimarc? > > > > I don't get an "internal server error", but the result list is empty. > > Thanks, Jonathan. > Sorry, Kyle, but that means that this cannot pass qa in the current form. We > would introduce more misinformation (no hits) for unimarc users than only > showing a damaged item or so too much. > Could you adjust the follow-up and make this notforloan part non-unimarc > specific? I wouldn't want to see a test (if marc21 else) here. I would prefer to see this patch pushed to master. I will try to provide a patch for bug 11586 soon (that will fix the problem with the last patch). Switch back to need QA.
Former QA and Jonathan's last patch and a small followup for item:w-consistency between notforloan and damaged, withdrawn, etc. in unimarc setup, should altogether be sufficient to make this patch set pass QA now, while looking forward to subsequent work in bug 11586.
Created attachment 30573 [details] [review] Bug 9810 - Search limit 'available' does not hide damaged or withdrawn items Test Plan: 1) Perform a search that will return an a damaged item and a withdrawn item ( for simplicity, have those items be the only one on each record, respectively ) 2) Run the same search but limit to available items only 3) Note those items still appear in the search results 4) Apply this patch 5) Run the search again 6) Note the items no longer appear in the search results Signed-off-by: Matthias Meusburger <matthias.meusburger@biblibre.com> Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Created attachment 30574 [details] [review] Bug 9810 [Followup] - Hide items with notforloan < 0 when limiting to available items Not for loan statuses of less then 0 are considered 'unavailable' in Koha parlance, whereas items with a not for loan status greater than 0 are considered available, but not checkout-able ( i.g. reference items ). This should be taken into account by the availability filter. Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Created attachment 30575 [details] [review] Bug 9810: Add index notforloan for unimarc This patch adds the notforloan index for UNIMARC (GRS-1 and DOM). Not that the original patch does not work out of the box: the notforloan, withdrawn and damaged indexes are not defined in the frameworks and mapping. Signed-off-by: Jonathan Druart <jonathan.druart@biblibre.com> Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Created attachment 30576 [details] [review] Bug 9810: Follow-up for UNIMARC notforloan item:w consistency To make the index defs and record.abs more consistent, adding item:w to notforloan. Please see also damaged, withdrawn, etc. Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
I'm sorry, this one is not an urgent one and needs regression tests. After the release, I can work on them (we need to make the big tests function run on NORMARC and UNIMARC so this is testable on both).
Still valid in 16.11. Anyone works on this? Regards, Marjorie
Hello, It looks like this might be solved by the patch in bug 11677. Is that the case?
(In reply to Margaret from comment #29) > Hello, > It looks like this might be solved by the patch in bug 11677. Is that the > case? Hi, I tested it on 19.05.04 and i have same problem. Items not for loan (authorized value <>0) are still displayed in search results. I miss something? Regards, Marjorie
Created attachment 105399 [details] available
> Hi, > > I tested it on 19.05.04 and i have same problem. > > Items not for loan (authorized value <>0) are still displayed in search > results. > > I miss something? > > Regards, > > Marjorie I Marjorie - I believe this is not a bug for (or not false behaviour) for all libraries. Available != checked out. You might still be able to use the reference collection marked not for loan in the library.
Our staff members mentioned this recently. When they select the Showing only available items
Sorry network issue when posting a comment. This is what the final message should have read. Our staffers still consider this an issue, can we have any items with the not for loan statuses appear further down in the search results and have have available status appear first? So any material with a Not for Loan status <>0, displays after material with a Not for loan status of 0 or NULL.
This is an issue for us as well, as withdrawn items still show up in searches.
Patch doesn't apply anymore