annetteholtkamp
commented
7 years ago Shouldn’t we include a matching step where a cataloguer is presented with possible candidates in HEP? We can be quite lenient when creating stub records but should be more strict when promoting a stub to a HEP record. At least in the beginning I wouldn’t think about daemonising this.
- Annette
On 7 Nov 2016, at 15:00, Samuele Kaplun notifications@github.com wrote:
After #1714 https://github.com/inspirehep/inspire-next/issues/1714 is implemented, we need workflow for catalogers to promote a given stub record to a real one.
Ideally the cataloguer would e.g. see a button "Promote to real record" in the brief/detailed format of each stub record which would initiate a holding-pen workflow that would:
pre-fill a record with the stub record try to fetch a corresponding PDF run all the usual record enrichment pause for a record-editing step instantiate the actual record as a real one merge the stub-one into the real one (thus making all reference so far created towards the stub record to now point to the real one). If we assume that DOI can be fetched, and that record is actually non-core, we can even avoid the record-editing step and just fully automatize the process.
Actually the process could also be fully initiated with a deamon (without cataloguer to actually clicking on a button at all), by acting an all those stub records that are actually cited above a given threshold.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/inspirehep/inspire-next/issues/1715, or mute the thread https://github.com/notifications/unsubscribe-auth/AM1-OyQAAwq3TQnfiOZyhcq6scb72tVXks5q7y70gaJpZM4KrPa6.
After #1714 is implemented, we need workflow for catalogers to promote a given stub record to a real one.
Ideally the cataloguer would e.g. see a button "Promote to real record" in the brief/detailed format of each stub record which would initiate a holding-pen workflow that would:
If we assume that DOI can be fetched, and that record is actually non-core, we can even avoid the record-editing step and just fully automatize the process.
Actually the process could also be fully initiated with a deamon (without cataloguer to actually clicking on a button at all), by acting an all those stub records that are actually cited above a given threshold.