In addition to running a search against RNAcentral, we need to run a search against Rfam. This will tell the users what Rfam models a sequence matches (a sequence can match one or more Rfam families).
The interface should be shown on the RNAcentral website (this repo) and also in the embeddable widget. Once it works, we can turn off Rfam sequence search altogether and use the embeddable widget in Rfam.
The Rfam search should run asynchronously and should be shown as soon as the results are available (it should not wait for the RNAcentral results).
In addition to running a search against RNAcentral, we need to run a search against Rfam. This will tell the users what Rfam models a sequence matches (a sequence can match one or more Rfam families).
The Rfam search runs on the EBI infrastructure: https://www.ebi.ac.uk/Tools/rna/infernal_cmscan/
It has a REST API (see an example Python script): https://raw.githubusercontent.com/ebi-wp/webservice-clients/master/python/infernal_cmscan.py
REST API documentation: https://www.ebi.ac.uk/seqdb/confluence/display/JDSAT/Infernal+cmscan+Help+and+Documentation#InfernalcmscanHelpandDocumentation-RESTAPI
The simplest version of the interface could look like this: https://rfam.org/search/sequence/F24DC36C-0AC1-11EA-B8BA-765DD1B96DDE
The interface should be shown on the RNAcentral website (this repo) and also in the embeddable widget. Once it works, we can turn off Rfam sequence search altogether and use the embeddable widget in Rfam.
The Rfam search should run asynchronously and should be shown as soon as the results are available (it should not wait for the RNAcentral results).