Records with Located URIs retrieved out of scope when org units are not OPAC visible
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
High
|
Unassigned |
Bug Description
Evergreen release 3.0
We're continuing to see record visibility issues in the public catalog on a production-data test system where records with Located URI are retrieved out of scope, even with the fixes from bug 1736419 and bug 1730758 applied. It appears to be an issue that occurs when org units are set to be OPAC invisible.
I confirmed the behavior on a Concerto test system by doing the following:
1. I added two test records to the system. The first has a located URI owned by BR1. The second has a located URI owed by BR2 and another located URI owned by SYS2
2. I set SYS1 to be OPAC invisible. Both records are retrieved out of scope.
3. When I reset SYS1 to be visible and set BR1 to be OPAC invisible, the record with a luri owned by BR2 and SYS2 is retrieved out of scope.
4. When I reset BR1 to be OPAC visible and set BR2 to be OPAC invisible, the record with a luri owned by BR1 is retrieved out of scope.
Adding an note that every time I just org unit visibility, I restarted autogen, OpenSRF services, and apache. These problems appear to be restricted to the public catalog. Searches from the staff client appear to be retrieving records as expected.
In our production systems, most of our system-level org units are not OPAC visible (we use the opac.org_
Changed in evergreen: | |
status: | New → Confirmed |
Changed in evergreen: | |
milestone: | none → 3.0.3 |
status: | Fix Committed → Fix Released |
Can either of you confirm that 1) all the test searches are being performed at the CONS level (well, at any org that is a common ancestor of the LURI owners) and 2) this only occurs with act_as_copy enabled? That's what I'm currently seeing. Thanks!