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

Inspirehep JSON merger: GUI #2696

Closed
ksachs opened this issue Aug 30, 2017 · 2 comments
Closed

Inspirehep JSON merger: GUI #2696

ksachs opened this issue Aug 30, 2017 · 2 comments

Comments

@ksachs
Copy link
Contributor

ksachs commented Aug 30, 2017

Expected Behavior

Conflicting information can arise when merging records. This has to be solved manually.
Information from both records has to be presented to a cataloger with the possibility to select the information from one or the other. The possibility to modify the resulting record manually is an advantage. At least one record is already in INSPIRE. The other record can be

  • an other INSPIRE record
  • an incoming merge, e.g. journal version of the preprint
  • update from the same source

Current Behavior

Currently there are 2 tools:

  • BibMerge to merge 2 records in INSPIRE
  • BibEdit with the possibility to merge a record from the (old) holdingpen to an INSPIRE record (see screenshot)

Context

To merge incoming journal versions with the existing arxiv record, DESY relies heavily on the merge GUI in BibEdit. This feature is essential.

Screenshots (if appropriate):

bibedit_merge

@kaplun kaplun added this to the Inspire Json Merger milestone Sep 15, 2017
@jacquerie
Copy link
Contributor

The backend part was done in #3005, the frontend was done by @harunurhan in some PR of which I don't know the number, but now it would be a good idea to move from the dev branch to master...

@harunurhan
Copy link
Contributor

We have UI, which is similar to this one in a way now and support is released with ng2-json-editor months ago, now it is available on the official release of record-editor when you edit a workflow object.

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

4 participants