Uh oh!
There was an error while loading. Please reload this page.
models: HostBib: Properly handle 774s without $w - #53
Conversation
anarchivist
left a comment
There was a problem hiding this comment.
r+; looks like a reasonable change. do we need another spec/fixture to handle testing 774s without subfield $w?
the rubocop failure appears unrelated.
239aef5 to
1d52b43Compare
davezuckerman
left a comment
There was a problem hiding this comment.
Other than the rubocop issue it looks good to go.
awilfox
commented
Jul 14, 2026
v2:
|
awilfox
commented
Jul 14, 2026
Yeah, I think that's a good idea. I'll add one. |
awilfox
commented
Jul 14, 2026
Since this should be processed like the other records, I'm not sure where to add it in |
1d52b43 to
e30346eCompareawilfox
commented
Jul 14, 2026
v3:
|
e30346e to
b874d26Compareawilfox
commented
Jul 16, 2026
v4:
|
Using `.empty?` still requires the value to not be `nil`. There is at least one record that has no `w` and therefore has a `nil` value; using `.present?` checks for nil *and* empty values. Additionally, ensure no `nil` values escape into the subfields list. Fixes: LIBIT-10644 Ref: AP-778
b874d26 to
a617ac2Compareawilfox
commented
Jul 16, 2026
v5:
|
Uh oh!
There was an error while loading. Please reload this page.
Using
.empty?still requires the value to not benil. There is at least one record that has nowand therefore has anilvalue; using.present?checks for nil and empty values.Fixes: LIBIT-10644
Ref: AP-778