Lots of libraries love the item search for its easy flexibility to retrieve results without having to write a report. In the item search, you can choose Damaged / Lost, but it would be great to see Withdrawn included to this list!
I agree; the item search would be even more powerful if you could also choose to ignore withdrawn items. Without this option, identifying withdrawn items can be time consuming and/or cumbersome. Thank you!
Created attachment 92651 [details] [review] Bug 23543: Adding Withdrawn to the Item Search This patch adds "Withdrawn" status to the item search form and item search results. To test you should have one or more items in your catalog which have a 'Withdrawn' status. Perform an item search and limit to a widthdrawn status. Verify that the search returns the correct results and that the withdrawn column in search results shows the correct information. Test the "Export results to CSV" button. The resulting file should contain the correct data, including withdrawn status.
Created attachment 93009 [details] [review] Bug 23543: Adding Withdrawn to the Item Search This patch adds "Withdrawn" status to the item search form and item search results. To test you should have one or more items in your catalog which have a 'Withdrawn' status. Perform an item search and limit to a widthdrawn status. Verify that the search returns the correct results and that the withdrawn column in search results shows the correct information. Test the "Export results to CSV" button. The resulting file should contain the correct data, including withdrawn status. Signed-off-by: joe <joe@flo.org>
Patch tested with a sandbox, by David Roberts <david.roberts@ptfs-europe.com>
Created attachment 93163 [details] [review] Bug 23543: Adding Withdrawn to the Item Search This patch adds "Withdrawn" status to the item search form and item search results. To test you should have one or more items in your catalog which have a 'Withdrawn' status. Perform an item search and limit to a widthdrawn status. Verify that the search returns the correct results and that the withdrawn column in search results shows the correct information. Test the "Export results to CSV" button. The resulting file should contain the correct data, including withdrawn status. Signed-off-by: joe <joe@flo.org> Signed-off-by: David Roberts <david.roberts@ptfs-europe.com>
Created attachment 93500 [details] [review] Bug 23543: Adding Withdrawn to the Item Search This patch adds "Withdrawn" status to the item search form and item search results. To test you should have one or more items in your catalog which have a 'Withdrawn' status. Perform an item search and limit to a widthdrawn status. Verify that the search returns the correct results and that the withdrawn column in search results shows the correct information. Test the "Export results to CSV" button. The resulting file should contain the correct data, including withdrawn status. Signed-off-by: joe <joe@flo.org> Signed-off-by: David Roberts <david.roberts@ptfs-europe.com> Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Created attachment 93506 [details] [review] Bug 23543: Adding Withdrawn to the Item Search This patch adds "Withdrawn" status to the item search form and item search results. To test you should have one or more items in your catalog which have a 'Withdrawn' status. Perform an item search and limit to a widthdrawn status. Verify that the search returns the correct results and that the withdrawn column in search results shows the correct information. Test the "Export results to CSV" button. The resulting file should contain the correct data, including withdrawn status. Signed-off-by: joe <joe@flo.org> Signed-off-by: David Roberts <david.roberts@ptfs-europe.com> Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de> Signed-off-by: Kelly <kelly@bywatersolutions.com>
Nice work! Pushed to master for 19.11.00
I've got the patches for this in the 18.05.x branch, and can release at any time.
(In reply to Liz Rea from comment #9) > I've got the patches for this in the 18.05.x branch, and can release at any > time. oh bother this is the wrong bug number.