-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write biblio details import lib #135
Comments
Also try EuroPMC - might give preprints too |
Coverage of the EuroPMC seems good: https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=DOI%3A10.1101%2F2020.02.29.970558&resultType=lite&cursorMark=*&pageSize=25&format=dc We can re-use Dublin Core response format of this service. |
Looks great. I like the idea of following DC response format as standard. Assume importing to triple-store => individual with IRI http://europepmc.org/abstract/PPR/PPR115538 ? We need to think through how to wire these up to Classes/Individuals - or if we don't, how to index so details can easily be retrieved by indexed ID. References to publications are commonly found in IRIs on definitions, e.g. see PMID here: "definition": [ May also be found on edges. Given that - maybe an indexed key lookup would be best? |
Our current structure is as follows: <owl:Axiom>
<owl:annotatedSource rdf:resource="http://www.semanticweb.org/brain_data_standards/AllenDendClass_CS202002013_1"/>
<owl:annotatedProperty rdf:resource="http://purl.obolibrary.org/obo/IAO_0000115"/>
<owl:annotatedTarget rdf:datatype="http://www.w3.org/2001/XMLSchema#string">A GABAergic interneuron ...</owl:annotatedTarget>
<oboInOwl:hasDbXref rdf:datatype="http://www.w3.org/2001/XMLSchema#string">DOI:10.1101/2020.02.29.970558</oboInOwl:hasDbXref>
<oboInOwl:hasDbXref rdf:datatype="http://www.w3.org/2001/XMLSchema#string">DOI:10.1101/2020.03.31.016972</oboInOwl:hasDbXref>
</owl:Axiom> I was planning to add one more annotation to this axiom using dc:source : <dc:source rdf:resource="http://europepmc.org/abstract/PPR/PPR115538/> Do you have a type recommendation for biblio instances (at worst we can use BibliographicResource)? In the vfb_dumps we can construct an explicit relation (dc:source?) between AllenDendClasses and the related biblio instances. |
Proposal: Add rdf as returned by EuroPMC API - dc structure, but add an additional triple with value query string. e.g. Add: http://europepmc.org/abstract/PPR/PPR115538 :DOI 10.1101/2020.02.29.970558 . Or PMID. |
skos:exactMatch relation used for storing query string: http://europepmc.org/abstract/PPR/PPR115538 skos:exactMatch "DOI:10.1101/2020.02.29.970558" Implementation of the related feature is completed and PR created |
(Ticket may not belong here)
We need a generic biblio details import extension for VFB pipeline2. This should use lookups via NCBI pubmed API or DOI to pull general bibliographic information into the integration layer (triplestore).
To investigate - can we follow/re-use some existing standard for this?
The text was updated successfully, but these errors were encountered: