Juser scraper #6
Loading…
Reference in a new issue
No description provided.
Delete branch "juser"
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?
To test run the current state:
(see https://juser.fz-juelich.de/search_generator.py)
The script prints the generated publication and person records instead of submitting them.
TODOs:
anything marked in the code as #TODO
add Juser-related secrets this the repo:
${{ secrets.JUSER_PW }},${{ secrets.JUSER_USER }}look up / mapping mechanism for 'rules' and 'about' (PoF topics)
figure out how to ingest grant information: Publications can acknowledge grants (I have yet to find one that does), but only if a Juser-specific record for the grant exists (under a Juser-specific ID), for which we then need to figure out the look-up as well (similar to looking up Julich IDs to match them with ORCIDs)
improve logging
implement and enable submission
record JulIDs as additional identifiers -> issued by ZB (which means we can get the entire INM-7 crew (or more people!) for free into the pool)
MARCXML author names should be 'display_label', not 'formatted_name'
Publications are 'generated_by' PoF Topics
ZB uses a controlled vocabulary for licenses: https://juser.fz-juelich.de/collection/HGFVOC?ln=en. Maybe this can be used for a look-up/mapping...
Example publication records:
Example person record:
In addition, we can get 'content type' from field 336 a. The "Content type term" however does not seem to follow a standard vocabulary (see below, and also note the various capitalizations between terms...). We can create a mapping with common types to our schema, e.g.,
'article' -> http://purl.org/ontology/bibo/AcademicArticle
'Preprint' -> ?
'lecture' -> http://purl.org/spar/fabio/Presentation
'Conference Paper' -> http://purl.org/ontology/bibo/Proceedings
'PATENT' -> http://purl.org/ontology/bibo/Patent
Licenses are even more difficult. They use field 915 for it, which is not a standard part of MARC but 'local bibliographic information'. Its also overloaded with everything else, from APCs to Peer Review types...
Of note: This submits records into different inbox collections of the same user:
Curation needs to take this into account.
okay, this is getting somewhere closer to a finished state. Finding and fixing bugs now.
WIP: Juser scraperto Juser scraper2c08f69aaftobafa0b45b5bafa0b45b5to2c08f69aafI'll merge this PR now, and toy around with the CI workflow. As all submissions only go into an inbox, they are sandboxed and this should be "safe", even if the CI runs the workflow successfully.