Bug 22971 - New location isn't displayed in OPAC for items added in a course reserves
Summary: New location isn't displayed in OPAC for items added in a course reserves
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Course reserves (show other bugs)
Version: Main
Hardware: All All
: P3 normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-23 09:18 UTC by Koha Team University Lyon 3
Modified: 2021-06-14 21:29 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Koha Team University Lyon 3 2019-05-23 09:18:37 UTC
When adding an item in a activated course reserves and you go to see the item details in the OPAC, who can't see the location label after the holding location.
Comment 1 Koha Team University Lyon 3 2019-05-23 09:31:29 UTC
Test plan :
1. Select an item and go to see it on the OPAC : you will see the location after the holding branch 
2. Add a course reserves and activate it
3. Add the selected item on this course reserve and change the holding library
4. Go back to the OPAC and you will see that the location isn't dislayed anymore
Comment 2 Rogan Hamby 2020-09-18 19:16:15 UTC
I'm not successfully duplicating this on 20.05.  Here is my testing:

Item '4444' in OPAC detail view:

Current location: Centerville Fiction 
Collection: Fiction 

1.)  Add as course reserve changing 

- Collection to Reference 
- Shelving location to Staff Office 
- Holding librarty to Fairview 

save new item to the course 

2.)  Refresh OPAC view of item details 

item now shows Current location: Fairview Staff Office 
Collection: Reference 

This is what I would expect.
Comment 3 Katrin Fischer 2020-09-20 21:59:38 UTC
We had quite a lot of bugfixes for the change of item values in course reserves since this was reported - I think it's likely to assume RESOLVED FIXED after Rogan's testing.