Integrity/completeness of "GENE_PROTEIN:" filter

[Shintaro Katayama]

Hi,

I want to find articles with a gene symbol in the Results section using the Articles RESTful API & the Annotations API.

For example, in the Articles RESTful API, there were 7 hits by "GENE_PROTEIN:HNRNPU" [*1] and 1,103 hits by "RESULTS:HNRNPU" [*2]. However, in the Annotations API, "MED:41674383" [*3], which is one of the 1,103 and not in the 7 although, had "type":"Gene_Proteins","section":"Results (http://purl.org/orb/Results)". Why the Article RESTful API could not find MED:41674383?

The integrity/completeness of the "GENE_PROTEIN:" filter would be important for us. E.g., in the Articles RESTful API, there were 1,345,776 hits by "RESULTS:SET" [*4] but only 4,751 hits by "GENE_PROTEIN:SET" [*5]. We should call only 4,751 times of the Annotations API, not 1,345,776 times, but for the strategy "GENE_PROTEIN:" in the Articles RESTful API, the result should be complete.

I would be grateful if you could check it. Or it would be nice if we could search such articles only from the Articles RESTful API (e.g. by "GENE_PROTEIN:RESULTS:SET" notation).

Sincerely,
Shintaro

*1 https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=GENE_PROTEIN%3AHNRNPU&resultType=idlist&cursorMark=*&pageSize=25

*2 https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=RESULTS%3AHNRNPU&resultType=idlist&cursorMark=*&pageSize=25

*3 https://www.ebi.ac.uk/europepmc/annotations_api/annotationsByArticleIds?articleIds=MED%3A41674383&type=Gene_Proteins&subType=uniprot&section=Results&provider=Europe%20PMC

*4 https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=RESULTS%3ASET&resultType=idlist&cursorMark=*&pageSize=25

*5 https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=GENE_PROTEIN%3ASET&resultType=idlist&cursorMark=*&pageSize=25

[Madhumiethaa Jayaprabha Palanisamy]

Hi Shintaro,

Thank you for reaching out. Ideally, the GENE_PROTEIN field should return the expected results shown in the Annotations API.
This appears to be an indexing issue, and we are currently investigating it. We expect it to be fixed soon.

Thanks,
Madhu