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

Merging - a special case (Erratum) #3675

Open
ksachs opened this issue Oct 8, 2018 · 0 comments
Open

Merging - a special case (Erratum) #3675

ksachs opened this issue Oct 8, 2018 · 0 comments

Comments

@ksachs
Copy link
Contributor

ksachs commented Oct 8, 2018

arXiv:1809.08737 is an erratum for Phys. Rev. Lett. 113,142301 (2014) / arXiv:1404.6185
I.e. the resulting record will have 2 arXiv numbers, the merger can not know which is the 'main' record and which is the erratum. I guess a cataloger has to decide which information is added / overwritten.

Current Behavior

The merge was halted in the HP with upload conflicts. All conflicts were about authors - no surprise with a collaboration. Basically that always happens and you don't check 300 authors. So I clicked 'reject all'. Which is wrong - I want to keep the existing information. This is the result:
https://inspirehep.net/record/edit/compare_revisions?recid=1292132&rev1=20171124004039&rev2=20181002103219

Authors and references are overwritten.

Expected Behavior

More power to the cataloger - let her decide what to do with the new information / check which information was changed.

Or:

Way more intelligent merger. I.e. only a revised version (same source, same ID) can overwrite information, a merge (different source or different ID) usually adds information, superior source overwrites (e.g. journal authors overwrite arXiv authors).
I.e. in this case it would be nice to add the arXiv comment - having one for 1404.6185 and one for 1809.08737. Do we need / want the ID (arXiv-number/DOI) in the source field?

Or:

Any other way to handle such a case. With the current tools I have no idea how to do it other than very basically adding + editing single fields with the editor.

With BibEdit + holdingpen Invenio1 this would be strait forward, since you can field-by-field decide to add / overwrite / ignore a change.

@ksachs ksachs added this to the Holding Pen Usability milestone Oct 8, 2018
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