biblio.record_entry.vis_attr_vector not updated upon adding a locate URI
Bug #1730758 reported by
Galen Charlton
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned |
Bug Description
If a bibliographic record that has no reason to be OPAC-visible (e.g., not transcendent, no copies, etc.) is edited to add an 856 field specifying a located URI, vis_attr_vector on the bib is not updated to reflect the change in visibility.
Evergreen 3.0.1
Changed in evergreen: | |
milestone: | none → 3.0.2 |
importance: | Undecided → Medium |
summary: |
- biblio.record_entry.vis_attr_cache not updated upon adding a locate URI + biblio.record_entry.vis_attr_vector not updated upon adding a locate URI |
Changed in evergreen: | |
milestone: | 3.0.2 → 3.0.3 |
tags: |
added: pullrequest removed: needsrepatch |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Without looking at the code, I suspect we're blindly appending to the vector, but that doesn't work well when it's currently NULL. I can look tomorrow morning.