inspirehep/inspire-next

Holdingpen: Update Conflicts: existing record as master, update as slave

Opened this issue · 0 comments

I had a look at a number of arXiv update conflicts in the holdingpen. The existing INSPIRE should be considered as basis. If there are conflicts, the question rather is whether the update should be applied than whether the old information might be added to the update - especially since the record has been curated (and enriched) befor the update.

Expected Behavior

If certain fields can not be matched. The unmatched ones from the existing INSPIRE record should stay (with the possibility to accept the removal of them) and the ones from the update should be accepted or rejected based on curator click.

Current Behavior

If certain fields can not be matched. The unmatched ones from the existing INSPIRE can be added or rejected by the curator by clicking, while the unmatched ones from the update sneaked into the record.

Steps to Reproduce (for bugs)

see holdingpens 1172843, 1172536, 1172906