Comment 11 for bug 1736419

My testing for comment 9 was on an unpatched system. I have since applied the patch and am now seeing the following for a record with a located uri:

In the staff client:

- The record is retrieved in the scope of the located uri
- The record is retrieved in the cons scope
- The record is retrieved in another branch's scope but the link does not display

In the public catalog:

- The record is retrieved in the scope of the located uri
- The record is retrieved in the cons scope
- The record is not retrieved in another branch's scope

This behavior is the same for existing, new and edited records.

The problem I see with the patched behavior is the staff client behavior where the record appears in a scope that does not match the located uri. Otherwise, the visibility is behaving as expected.

We have the opac.located_uri.act_as_copy flag enabled.