For bib records that existed prior to the upgrade, visibility behaves as expected in both the web staff client and the public catalog:
- A record with a located uri is retrieved in the scope of the located uri, but not in the scope of another branch.
Edited bib records that existed prior to the upgrade also behave as above.
For a newly added record with a located uri:
- In the web staff client, the record is retrieved in the scope of the located uri. The record is also retrieved (without the link) in the scope of another branch.
- In the public catalog, the record is not retrieved in any scope.
I did some testing on our 3.0.1 upgraded system.
For bib records that existed prior to the upgrade, visibility behaves as expected in both the web staff client and the public catalog:
- A record with a located uri is retrieved in the scope of the located uri, but not in the scope of another branch.
Edited bib records that existed prior to the upgrade also behave as above.
For a newly added record with a located uri:
- In the web staff client, the record is retrieved in the scope of the located uri. The record is also retrieved (without the link) in the scope of another branch.
- In the public catalog, the record is not retrieved in any scope.