Skip to content
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

Extract PMID supporting a relation #8

Open
maximeDelmas opened this issue Aug 4, 2021 · 3 comments
Open

Extract PMID supporting a relation #8

maximeDelmas opened this issue Aug 4, 2021 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@maximeDelmas
Copy link
Collaborator

Context

Currently, only the number of articles supporting the relation is displayed on the interface, in the column papers

Desired behaviour

As a user I would be able to extract the complete list of PMID that are supporting the relation

Solutions ?

Even if the complete list of PMID associated to each association is not stored in the SQL database (as it would involve a massive load of data), the information is encoded in the KG and could be extracted using SPARQL requests.

  • We could create URLs containing the SPARQL request allowing to extract PMIDs related to a specific PubChem/CheBI/ChemOnt-MeSH association as a GET/POST http request. This url could be added in a new column of the result table.

  • The request could also be part of the pre-filled SPARQL requests.

@maximeDelmas
Copy link
Collaborator Author

For the URL part, I will start to work on it. The idea is to provide a link to an http request that will send a request to the SPARQL endpoint to get the PMIDs associated to an assocition in the result table.
I think that for heavily supported associations (>1000 articles) we should set a limit in the number of articles returned when using the web interface as the SPARQL request can be really long. I will start to test some http requests.

To get all the PMID the user should use the SPARQL endpoint with the pre-filled SPARQL request. But, we have to discuss on how to implement pre-filled SPARQL request in the Virtuoso SPARQL endpoint with @ofilangi in a meeting soon.

@maximeDelmas
Copy link
Collaborator Author

Requests with ChEBI and ChemOnt can be very long, more than 5 minutes, which is incompatible with a request of the web interface ...

For PubChem - MeSH, it is more reasonable as the engine does not have to go through the chemical ontology...

I would also propose to pre-compute all the PMID sets, and if we can't store them in the database, we could provide the files on the ftp.

@maximeDelmas
Copy link
Collaborator Author

maximeDelmas commented Aug 25, 2021

When specifying graphs using FROM attributes, it seems to increase requests' speed

Maybe we do not need the limit 1000 also

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants