Like bug 35696, this is another missed case where items.transfer should have been switched to transfer in the template.
Created attachment 161615 [details] [review] Bug 35934: Correct missed case of switching items.transfer to transfer in detail.tt To test: 1. Put an item with no holds/recalls in transit (manually or by checking it in at a branch other than its homebranch to trigger a ReturnToHome) 2. Go to the item's bib record --> Note that the item's status will display as something like, "In transit from X to Y since 01/29/2024 Available" 3. Apply patch and refresh the page --> Note that item now shows only the transit status, but not "Available"
Created attachment 161698 [details] [review] Bug 35934: Correct missed case of switching items.transfer to transfer in detail.tt To test: 1. Put an item with no holds/recalls in transit (manually or by checking it in at a branch other than its homebranch to trigger a ReturnToHome) 2. Go to the item's bib record --> Note that the item's status will display as something like, "In transit from X to Y since 01/29/2024 Available" 3. Apply patch and refresh the page --> Note that item now shows only the transit status, but not "Available" Signed-off-by: Lucas Gass <lucas@bywatersolutions.com>
Created attachment 163185 [details] [review] Bug 35934: Correct missed case of switching items.transfer to transfer in detail.tt To test: 1. Put an item with no holds/recalls in transit (manually or by checking it in at a branch other than its homebranch to trigger a ReturnToHome) 2. Go to the item's bib record --> Note that the item's status will display as something like, "In transit from X to Y since 01/29/2024 Available" 3. Apply patch and refresh the page --> Note that item now shows only the transit status, but not "Available" Signed-off-by: Lucas Gass <lucas@bywatersolutions.com> Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Pushed for 24.05! Well done everyone, thank you!
Pushed to 23.11.x for 23.11.04
Backported to 23.05.x for upcoming 23.05.10