We've found another instance where biblio.record_entry.vis_attr_vector is not updating. If you add or change a bib source when either editing or creating a MARC record, this field does not update. Existing records with a bib source will get a value in this field as a result of the 3.0 upgrade script, but these values don't change with any future changes of the bib source.
Here are some further notes from mmorgan:
On insert or update on biblio.record_entry, the function asset.cache_copy_visibility() should run
asset.cache_copy_visibility() says that if the table that changed is biblio.record_entry, then run the function biblio.calculate_bib_visibility_attribute_set(id). That function should update biblo.record_entry.vis_attr_vector
But it looks like that if loop pertaining to a change in record_entry is stuck inside an if loop pertaining to a change in copy or unit. So I don't see that the part that updates biblo.record_entry.vis_attr_vector is ever getting called
We've found another instance where biblio. record_ entry.vis_ attr_vector is not updating. If you add or change a bib source when either editing or creating a MARC record, this field does not update. Existing records with a bib source will get a value in this field as a result of the 3.0 upgrade script, but these values don't change with any future changes of the bib source.
Here are some further notes from mmorgan:
On insert or update on biblio. record_ entry, the function asset.cache_ copy_visibility () should run copy_visibility () says that if the table that changed is biblio. record_ entry, then run the function biblio. calculate_ bib_visibility_ attribute_ set(id) . That function should update biblo.record_ entry.vis_ attr_vector entry.vis_ attr_vector is ever getting called
asset.cache_
But it looks like that if loop pertaining to a change in record_entry is stuck inside an if loop pertaining to a change in copy or unit. So I don't see that the part that updates biblo.record_