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
Also I'm not sure whether we want to try to manually match records that were already rejected.
If the update comes with an ID we have already and can be matched automatically, that's fine.
But I'm not sure we have enough catalogers left to manually deal with old stuff.
Of course that depends on the volume and how smart the matcher is.
The text was updated successfully, but these errors were encountered:
Example:
arXiv:1802.02799
had the original harvest (which was rejected) on 2018-02-09.
There were updates on 2018-02-10, 2018-07-03, 2018-07-04
The last 2 updates
https://labs.inspirehep.net/api/holdingpen/1108287 and
https://labs.inspirehep.net/api/holdingpen/1110642
both had
arXiv:1412.5337 (recid:1334778) as a match-candidate, which is not in the list of
previously_rejected_matches
0 1108287
1 891579
2 890534
3 1108287
though 1334778 was rejected yesterday (afais).
There might be something wrong.
Also I'm not sure whether we want to try to manually match records that were already rejected.
If the update comes with an ID we have already and can be matched automatically, that's fine.
But I'm not sure we have enough catalogers left to manually deal with old stuff.
Of course that depends on the volume and how smart the matcher is.
The text was updated successfully, but these errors were encountered: