InterPro
Collect protein family, domain, and functional-site annotations.
InterPro
InterPro is EMBL-EBI's public integrated database of protein families, domains and functional sites; this connector searches it directly from inside RxCubed. It's available under Collect files. Look an entry up by name, InterPro accession, or a UniProt accession — “carbonic anhydrase”, for example. See File Collection for the shared search, shortlist and save flow every connector here uses.
Identifier lookup, not ranked search
InterPro is an identifier lookup: you name a family, domain, or protein and get the matching entries back rather than a ranked list. There is no AI scoring, no Qualities, and no importance controls.
What to compare
The card shows accession, name, type, source database, parent entry, and GO terms.
Type is the field to read first, because it says what kind of thing the entry is:
- Family — a group of evolutionarily related proteins;
- Domain — a distinct structural or functional unit within a protein;
- Homologous superfamily — related by structure where sequence similarity has faded;
- Site — a small functional feature such as an active or binding site;
- Repeat — a short unit that recurs within a protein.
InterPro is an integration of several member databases (Pfam, PROSITE, CDD and others). Database names which one an entry came from, and Parent entry shows where a member-database signature has been integrated into a broader InterPro entry.
Files
- Entry/match list (TSV) — the entries and where they match, selected by default. Opens in any spreadsheet.
- Entry/match list (JSON) — the same content with full structure, for when you need everything.
Papers
InterPro entries cite the literature behind their definitions. Tick them under Papers in the shortlist, or use Group ▾ on a saved row afterwards, to save them as literature evidence in the same group.
What to do next
Domain boundaries are useful context for reading a structure: they tell you which part of a UniProt sequence or a PDB structure is doing what. Use them when interpreting pocket detection results, to check whether a predicted pocket sits in a known functional site.
