Comment 9 for bug 1730758

I finally had a chance to apply this patch to a test system running clean master on a new database.

As Jeff noted, the patch does seem to address the narrow issue identified in this bug. It also addresses a small part of the search issues I identified in bug 1736419, but there are still significant search issues with this patch applied:

1. I still cannot retrieve any records in the public catalog.
2. Searching a record with located URIs for BR1, BR2 & BR3 in the web client, we fixed the issue where a search scoped to BR4, SYS1 or SYS2 was retrieving the records. However, I'm still able to retrieve it with the scope set to the Consortium.
3. I see no difference in which records are retrieved when the opac.located_uri.act_as_copy global flag is enabled.

I can outline my test results more thoroughly on bug 1736419. At this point, though, I'm thinking these two issues are separate bugs and that Mike's current code should be merged since it does fix the issue with vis_attr_vector not updating as expected. However, Mike, if you think it's better to fix both issues with the same branch, let me know and I'll hold off on merging it.

Needless to say, we consider this issue to be fairly critical. We made a decision today to hold off on a 3.0 upgrade scheduled for next week due to the problems identified in bug 1736419 and in bug 1736992.