Comment 10 for bug 1878984

Tested three different scenarios during Feedback Fest -- all worked as expected using merge profile with preserve specifications.

Scenario #1
490 on existing bib in db; no 490 on new record; 490 field was preserved during merge

Scenario #2
no 490 on existing bib in db; 490 on new record; 490 field was not loaded from new record during merge and, therefore, the state of the existing record was preserved

Scenario #3
245a on existing bib is good and should be preserved; 245a on new record is not correct and should not be loaded; good 245a was preserved during merge

I have tested this code and consent to signing off on it with my name, Jennifer Weston, and my email address, <email address hidden>