Records with located URIs are retrieved in Copy Location and Copy Location Group searches
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
High
|
Unassigned | ||
3.1 |
Fix Released
|
High
|
Unassigned |
Bug Description
Evergreen 3.0
Records with located uris at the CONS level are retrieved in searches in all Copy Location Groups.
Additionally, when a Copy Location Group is owned by the same org unit (or parent) as a located URI, the record with that located uri will be retrieved in searches limited to that Copy Location Group.
This is occurring in both the public opac and staff client.
To reproduce on a concerto system:
- Create a copy location group called "My BR1 Group" owned by BR1. It's not necessary to add any copy locations to the group.
- Perform a search on "tolkien" - the stock Tolkien records with located uris at the CONS level will be retrieved
Next:
- Create a record with title "My BR1 URI" with a located URI for BR1
- Create a second Copy Location Group called "My BR3 Group" owned by BR3
- Perform a search for "My BR1 URI" in location group "My BR1 Group" - the record is retrieved.
- Perform the search for "My BR1 URI" in location group "My BR3 Group" - the record is not retrieved.
Records with only uris should not be retrieved in any searches that are limited to Copy Location Groups.
tags: | added: opacvisibility |
Changed in evergreen: | |
status: | New → Confirmed |
summary: |
- Records with located URIs are retrieved in Copy Location Group searches + Records with located URIs are retrieved in Copy Location and Copy + Location Group searches |
tags: | added: signedoff |
Changed in evergreen: | |
milestone: | none → 3.0.8 |
tags: |
added: searchvisibility removed: opacvisibility |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Adding a note that located uris are also retrieved in searches limited to individual Copy Locations belonging to the same org unit from the Advanced Search page.