You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
The text was updated successfully, but these errors were encountered:
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...
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.
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
Current Behavior
Currently there are 2 tools:
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):
The text was updated successfully, but these errors were encountered: