Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
fschwenn opened this issue Aug 15, 2018 · 0 comments
Open

Comments

@fschwenn
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant