Promotion workflow for records in hidden collections

[michamos]

Sometimes, we get user submissions for records that are already present in a hidden collection (e.g. HAL hidden), which regular users cannot be aware of.

Copy/pasted from https://github.com/inspirehep/inspire-next/pull/1989#pullrequestreview-25734123 :

• If the submitter is a cataloguer, she should be told that the record is already present in HAL Hidden.
• If the submitter is a regular user, it should not be rejected outright, as the fact that it is submitted by a user warrants reconsideration. Instead, there should be a promotion workflow: the record should be loaded into the holding pen, and a curator should choose whether to leave it in the hidden collection (-> reject message for the user), or promoted to the visible literature collection (-> accept message for the user).

[jmartinm]

@kaplun How do we control from Labs the actions that need to be taken in inspirehep.net when the record gets promoted? Send a bibupload just adding 980:HEP enough? Or we need to remove as well 980:Hal Hidden (in which case we need to read the record from inspirehep.net to get all 980 fields, modify them and send an update).

Also what to do with the user suggested content:

1) If we leave it in Hal Hidden - do we send a bibupload -o to send the update to the legacy holding pen to be merged? Is somebody going to do this merge?

2) Same if we promote it. Do we first do the promotion and then send an update with the user generated content?

We need to check in which RT queue this update appears, with what content and who will take care of it.