Extending the coverage of the peer non-unknown refereed instances #342
No reviewers
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
RDGraph
RSAC
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: D-Net/dnet-hadoop#342
Loading…
Reference in New Issue
No description provided.
Delete Branch "peer_reviewed"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR incorporates in the graph cleaning procedure the logic used in the stats DB to set the peer field
result.instance[].refereed
.I am attaching the SQL currently in use to populate the
result_peerreviewed
table in the stats DB.Note that the procedure operates only on the instances where the refereed field is set to unknown, hence it would not override and value set by the transformation rules, operating by vocabulary mapping on the original records. So, if I well read the SQL, on top of the existing
peerReviewed
and thenonPeerReviewed
values, we would end up considering as non peer reviewed all the material that does not come (also) from Crossref. This is quite a strong assertion and I can imagine many cons, like discriminating all the peer reviewed journals that are not in Crossref... but let's discuss about it.