CINXE.COM

<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1">  <meta name="description" content=""> <meta name="author" content=""> <link rel="preload" href='https://fonts.googleapis.com/css?family=Didact Gothic' rel='stylesheet'> <link rel="preload" href="https://fonts.googleapis.com/css?family=Ubuntu|Ubuntu+Condensed|Ubuntu+Mono" rel="stylesheet"> <link rel='shortcut icon' href='/assets/images/tor_ibin_icon.ico' /> <link rel="stylesheet" href="/assets/css/bootstrap.min.css"> <link rel="stylesheet" href="/assets/css/jquery-ui.min.css"> <link rel="stylesheet" href="/assets/css/jquery.qtip.css"> <link rel="stylesheet" href="/assets/css/main.css"> <script src="/assets/js/jquery-2.1.4.min.js"></script> <link rel="stylesheet" href="/assets/css/bootstrap.min.css"> <link rel="stylesheet" href="/assets/css/jquery-ui.min.css"> <link rel="stylesheet" href="/assets/css/main.css"> <link rel="stylesheet" href="/assets/css/about.css"> <link rel="stylesheet" href="/assets/css/faq.css"> <title>HuRI | FAQ</title> </head> <body> <header> <nav class="navbar navbar-default main_header" style="background-color: #a51c30;position:relative"> <svg id="svg2" style="position: absolute; top: 28%; transform: translateY(-50%); right: 0; left: 0;" class="main_logo left " xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://www.w3.org/2000/svg" height="40.026" width="69.124" version="1.1" xmlns:cc="http://creativecommons.org/ns#" xmlns:dc="http://purl.org/dc/elements/1.1/"> <metadata id="metadata7"> <rdf:RDF> <cc:Work rdf:about=""> <dc:format>image/svg+xml</dc:format> <dc:typerdf:resource ="http://purl.org/dc/dcmitype/StillImage"/> <dc:title /> </cc:Work> </rdf:RDF> </metadata> <g id="g3770" stroke-miterlimit="4" stroke-dasharray="none"> <path id="path2987" d="m48.576,17.582c0,9.2489-7.5012,16.746-16.754,16.746-9.2532,0-16.754-7.4977-16.754-16.746,0-9.2489,7.5012-16.746,16.754-16.746,9.2532,0,16.754,7.4977,16.754,16.746z" stroke-opacity="0.56084655000000005" class="parent" stroke="#000000" stroke-width="0.04307067000000000" fill="#bbbbbb" /> <path id="path2991-1" d="m31.367,23.78c0,2.992-2.4267,5.4175-5.42,5.4175-2.9934,0-5.42-2.4255-5.42-5.4175s2.4267-5.4175,5.42-5.4175c2.9934,0,5.42,2.4255,5.42,5.4175z" class="child" stroke="#ffffff" stroke-width="0.08252774" fill="#ffffff" /> <path id="path2991-7" d="m42.899,13.341c0,2.992-2.4267,5.4175-5.42,5.4175-2.9934,0-5.42-2.4255-5.42-5.4175s2.4267-5.4175,5.42-5.4175c2.9934,0,5.42,2.4255,5.42,5.4175z" class="child" stroke="#ffffff" stroke-width="0.08252774" fill="#ffffff" /> <path id="path2991-4" d="m67.986,29.163c0,2.992-2.4267,5.4175-5.42,5.4175-2.9934,0-5.42-2.4255-5.42-5.4175s2.4267-5.4175,5.42-5.4175c2.9934,0,5.42,2.4255,5.42,5.4175z" class="child" stroke="#ffffff" stroke-width="0.08252774" fill="#ffffff" /> <path id="path2991-0" d="m10.903,34.545c0,2.992-2.4267,5.4175-5.42,5.4175-2.9934,0-5.42-2.4255-5.42-5.4175s2.4267-5.4175,5.42-5.4175c2.9934,0,5.42,2.4255,5.42,5.4175z" class="child" stroke="#ffffff" stroke-width="0.08252774" fill="#ffffff" /> <path id="path3807" stroke-linejoin="miter" d="m25.95,23.82-20.47,10.76" class="child" stroke="#ffffff" stroke-linecap="butt" stroke-width="1.07676673" fill="none" /> <path id="path2991-9-45" d="m69.063,5.4793c0,2.992-2.4267,5.4175-5.42,5.4175-2.9934,0-5.42-2.4255-5.42-5.4175s2.4267-5.4175,5.42-5.4175c2.9934,0,5.42,2.4255,5.42,5.4175z" class="child" stroke="#ffffff" stroke-width="0.08252774" fill="#ffffff" /> <path id="path3807-1" stroke-linejoin="miter" d="m63.64,5.5195-25.848,7.5356" class="child" stroke="#ffffff" stroke-linecap="butt" stroke-width="1.07676673" fill="none" /> <path id="path3807-1-5" stroke-linejoin="miter" d="m62.56,29.2-24.77-16.15" class="child" stroke="#ffffff" stroke-linecap="butt" stroke-width="1.07676673" fill="none" /> </g> </svg> <div style="padding: 12px; margin-left:80px;"> <h3 style="color: #ffffff; font-weight: bold; font-family: 'Ubuntu', sans-serif;"> The Human Reference Protein Interactome Mapping Project </h3> </div> </nav> </header> <header> <nav class="navbar navbar-default"> <div class="container-fluid"> <div class="navbar-header tor_ibin_header" > <h5 class="nav-header" style="color: #a51c30">HuRI</h5> <button type="button" class="navbar-toggle right" data-toggle="collapse" data-target="#myNavbar" style="margin-left: 30px;" > <span class="icon-bar"></span> <span class="icon-bar"></span> <span class="icon-bar"></span> </button> </div> <div id="myNavbar" class="collapse navbar-collapse" style="padding-left: 0px; font-family: Century Gothic, sans-serif"> <ul class="nav navbar-nav "> <li><a href="/">Home</a></li> <li><a href="/search">Search</a></li> <li><a href="/download">Dataset Downloads</a></li> <li><a href="/about/">About</a></li> <li class="active"><a href="/faq/">FAQ</a></li> <li><a href="/contact/">Contact</a></li> </ul> <ul class="nav navbar-nav navbar-right"> <li><a href="/register">Register</a></li> <li style="margin-left: 0px;"><a href="/login">Login</a></li> </ul> </div> </div> <div class="shadow"></div> </nav> </header> <main> <div class="row" style="position: relative;"> <div class="outer_panel" style="overflow: auto;"> <div class="container" style="width:80%;"> <div class="row"> <h3 style="color: #a51c30">FAQ</h3> </div> <div class="row"> <p class="MsoNormal" style="text-align: justify;"><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;">Where does the interaction data available for search and download on this web portal come from?</span></strong></span></p> <p><span style="font-family: arial, helvetica, sans-serif; font-size: 14pt;">The interaction data comes from two sources. The majority comes from a series of systematic screens of human open reading frame (ORF) clone collections performed in the Vidal, Tavernier and Roth labs at Dana-Farber Cancer Institute/Harvard Medical School, Vlaams Instituut voor Biotechnologie/Ghent University and University of Toronto, respectively. These interactions were found using a systematic binary mapping pipeline based upon a high-throughput yeast two-hybrid assay as the primary screen, followed by pairwise retesting in quadruplicate of all primary pairs, and subsequent validation of a random subset using two or more orthogonal assays.<br />The remainder of the data are from databases of curated interactions reported in the literature. The publicly available interaction data was filtered to identify the high-quality binary interactions as described in the</span><span style="font-family: arial, helvetica, sans-serif; font-size: 14pt;"> <a href="https://doi.org/10.1038/s41586-020-2188-x">HuRI paper</a>.<br /></span></p> <p class="MsoNormal" style="text-align: justify;"><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;">Does the interaction data originate from experiments and/or predictions?</span></strong></span></p> <p><span style="font-family: arial, helvetica, sans-serif; font-size: 14pt;">All of the systematic data come from our systematic experimental screening pipeline and have at least one piece of supporting experimental evidence. This systematic dataset has been shown to have quality (fraction correct) that is on par with high-quality literature curated binary interactions, defined by having at least two pieces of experimental evidence from original publications, curated from the literature.</span></p> <p><span style="font-family: arial, helvetica, sans-serif; font-size: 14pt;"><span style="font-size: 14pt;"><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;"><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;">Why is the number of interactions for a given dataset different from the number reported in the original publication?</span></strong></span></span></strong></span></span></span></p> <p><span style="font-family: arial, helvetica, sans-serif; font-size: 14pt;">We map our ORF sequences to GENCODE (v27) gene annotation models to identify the gene, transcript, and protein to which our ORF belongs to. Because the genome is highly redundant, and genome annotation is difficult, there are changes between different GENCODE versions which can result in changes in the genes and proteins to which our ORFs map best. Furthermore, we only provide interactions for ORFs that, based on the gene annotation model, map to protein coding genes. The identification of which genes encode proteins is also subject to change between different gene annotation models.</span></p> <p class="MsoNormal" style="text-align: justify;"><span style="font-size: 14pt;"><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;">I have my query genes in a different identifier format (neither gene symbols nor Uniprot IDs). What can I do to still use them as query on this web portal?</span></strong></span><em><span style="font-family: Helvetica, sans-serif;"> <br /></span></em></span></p> <p><span style="font-size: 14pt; font-family: arial, helvetica, sans-serif;">Currently our portal can only be searched using either gene symbols or UniProt accession numbers. You can convert your list of query genes into gene symbols or UniProt IDs at these websites (<a href="http://www.uniprot.org/uploadlists/">http://www.uniprot.org/uploadlists/</a>, <a href="https://david.ncifcrf.gov/conversion.jsp)">https://david.ncifcrf.gov/conversion.jsp)</a>.</span></p> <p class="MsoNormal" style="text-align: justify;"><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;">Why does my search not return any PPIs?</span></strong></span></p> <p class="MsoNormal" style="text-align: justify;"><span style="font-family: arial, helvetica, sans-serif; font-size: 14pt;">We have tested the ORFs corresponding to over 17,000 human protein-coding genes using our binary interaction mapping pipeline (a full list of the genes we have tested is available at http://horfdb.dfci.harvard.edu/). However, we may not have screened your gene of interest yet because we do not currently have an ORF clone available for this gene.<br />The other possibility is that even though we have screened for PPIs with an ORF from your gene of interest, the expressed protein may not have resulted in any PPIs. While our binary interaction mapping pipeline is designed to be systematic and unbiased, there are some proteins which may prove to be refractory to the assays used. For example, (i) proteins that are secreted, are intrinsic membrane proteins or require significant post-translational modification may not form stable interactions under our assay conditions, (ii) some human proteins may be unstable or not fold correctly when expressed in yeast, (iii) some proteins may only interact as parts of large complexes and not as binary pairs, or (iv) some proteins may be incapable of interaction due, e.g., to errors or natural sequence variation in the clones, or due to the influence of the fused tags.<br /></span></p> <p class="MsoNormal" style="text-align: justify;"><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;">What would be a good confidence score cutoff to filter the interactions?</span></strong></span></p> <p class="MsoNormal" style="text-align: justify;"><span style="font-size: 14pt;"><span style="font-family: arial, helvetica, sans-serif;">All CCSB datasets have been validated of their high biophysical quality by testing random subsets of PPIs in independent assays. The confidence score is intended to further rank the identified interactions, for example in cases where too many PPIs result and only a subset of all identified interactions can be used for experimental follow-up. In that sense, a cutoff can be defined based on the number of interactions that a user wants to consider. This score quantifies only a small part of the variance in biophysical quality within the dataset and therefore should not be used to discard PPIs for quality concerns.</span></span></p> <p class="MsoNormal" style="text-align: justify;"><span style="font-size: 14pt;"><span style="font-family: arial, helvetica, sans-serif;"><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;">In which format do I need to save the search results for upload into Cytoscape?</span></strong></span></span></span></p> <p class="MsoNormal" style="text-align: justify;"><span style="font-size: 14pt;"><span style="font-family: arial, helvetica, sans-serif;">To upload the search results into Cytoscape, export them as a .csv file.</span></span></p> <p class="MsoNormal" style="text-align: justify;"><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;">Why is there not a confidence score for every PPI? </span></strong></span></p> <p><span style="font-family: arial, helvetica, sans-serif; font-size: 14pt;">The confidence score of a pair is calculated based on several features of how the interaction was detected during screening. This data is only available for pairs detected in the most recent screens (HuRI), and hence we are only able to calculate confidence scores for these pairs.</span></p> <p><span style="font-family: arial, helvetica, sans-serif; font-size: 14pt;"><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;">How should I cite the interaction data and web portal?<br /></span></strong></span></span></p> <p><span style="font-family: arial, helvetica, sans-serif; font-size: 14pt;">A manuscript describing the web portal itself is in preparation. When using previously or recently published interaction data, please cite the corresponding publication as indicated in the Downloads and About section.</span></p> <p class="MsoNormal" style="text-align: justify;"><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;">How can I get information on the clone used to identify an interaction returned from my search?</span></strong></span></p> <p class="MsoNormal" style="text-align: justify;"><span style="font-family: arial, helvetica, sans-serif; font-size: 14pt;">The clones used in our screens come from the Human ORFeome clone collection assembled at</span><span style="font-family: arial, helvetica, sans-serif; font-size: 14pt;"><span style="font-family: arial, helvetica, sans-serif; font-size: 14pt;"> <a href="http://horfdb.dfci.harvard.edu">CCSB</a> and via the <a href="http://www.orfeomecollaboration.org">ORFeome Collaboration</a></span>. Clicking the ORF identifiers will redirect the user to our ORFeome web portal where details on the cloning strategy, source material and nucleotide sequence are provided.</span></p> <p><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;"><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;">How can I get detailed experimental information on an interaction of interest?</span></strong></span></span></strong></span></p> <p><span style="color: #000000; font-size: 14pt; font-family: arial, helvetica, sans-serif;"><span style="font-family: arial, helvetica, sans-serif; font-size: 14pt;">By clicking on the edge that represents the interaction of interest in the network visualization on the results page, the user can obtain information on the individual experiments in which that interaction was identified along with information on the corresponding ORF identities. <br /></span></span></p> <p><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;">Isn't yeast two-hybrid data full of false positives?</span></strong></span></p> <p><span style="font-family: arial, helvetica, sans-serif; font-size: 14pt;">Like any other experimental approach, the quality of the data generated is dependent on the careful design of the experiment and rigorous attention to detail in performing the experiments. We first remove all proteins which can autoactivate the yeast reporter genes (i.e., a single protein (as bait or prey in Y2) is able to induce reporter gene expression in the absence of any other partner protein). In addition, our modern binary interaction mapping pipeline contains numerous quality control measures implemented after primary screening, including pairwise verification (regenerating and retesting mated diploids from fresh glycerol stocks) and sequencing to confirm ORF identity. A random sample of verified primary yeast two-hybrid datasets are validated by testing a subset of interactions in at least two orthogonal assays that have been calibrated using positive and random reference sets. We only consider a dataset validated if the biophysical quality of the dataset is equal to, or greater than, a representative sample of interactions selected from the literature.<br />We note that this process can establish that our interactions are of high biophysical quality, meaning that the reported pair of proteins is highly likely to interact when both proteins are expressed together. The assays employed however, cannot inform on whether the identified interactions are physiologically or biologically relevant. Demonstrating such relevance for an individual PPI requires an additional battery of molecular and cellular assays, which we are unable to perform on the more than 60,000 PPIs reported. However, we show that our datasets are highly enriched in linking proteins of similar functional annotation compared to random networks and in follow-up studies we provide evidence for the functional relevance of a number  of PPIs (see our published work). Integration of Y2H interactome data with current data on contextual gene and protein expression and protein localization data can prioritize PPIs that are more likely to be physiologically relevant in the selected cellular context. However, one should not necessarily rule out any PPI in our dataset because of lack of contextual data due to the overall incompleteness of those datasets.<br /></span></p> <p><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;">How complete is your map?</span></strong></span></p> <p><span style="font-size: 14pt; font-family: arial, helvetica, sans-serif;">Estimating the level of completeness of our interactome data is difficult given how little we know about the composition of the human protein interactome and methodological biases associated with all interactome mapping assays including Y2H. As described in our HuRI paper, we estimate that HuRI currently covers 2-11% of the human binary protein interactome. Part of the PPIs that we are missing are those that depend on post-translational modifications that the yeast cell does not catalyze (at least under the conditions we used). Furthermore, our estimate of interactome coverage is only valid for binary protein interactions, and therefore does not include PPIs that depend on additional interaction partners (cooperative binding) and protein interactions that represent indirect associations in protein complexes. Complementary interactome mapping efforts, e.g., affinity purification followed by mass spectrometry, that can also be implemented at human proteome scale are needed to further complement and complete the binary interaction maps we provide.</span></p> <p><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;">Is your dataset depleted for protein interactions that are part of stable protein complexes?</span></strong></span></p> <p><span style="font-size: 14pt;">By integrating our data with three dimensional structural information from protein complexes we observed that our interaction detection platform can detect interactions that are part of stable protein complexes across a wide range of protein complex sizes and we only observe a mild depletion for very large protein complexes (30+ subunits).</span></p> <p><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;">How do the various datasets available for download relate to each other?</span></strong></span></p> <p><span style="font-size: 14pt;">The full descriptions of all various datasets in the “Dataset Downloads” page can be found in the “About” page. “HI-union” is the union of all published datasets (i.e. HI-I-05, HI-II-14, HuRI, Venkatesan-09, Yu-11, Yang-16, and Test space screens-19) except Lit-BM. The total number of PPIs and proteins listed on the homepage is the union of all datasets, published and unpublished.</span></p> <p><span style="color: #4985c9; font-size: 18pt;"><strong><span style="font-family: Helvetica, sans-serif;">How was this project funded?</span></strong></span></p> <p><span style="font-size: 14pt;">This work was primarily supported by a National Institutes of Health (NIH) National Human Genome Research Institute (NHGRI) grant U41HG001715 with additional support from NIH grants P50HG004233, U01HL098166, U01HG007690, R01GM109199, Canadian Institute for Health Research (CIHR) Foundation Grants, the Canada Excellence Research Chairs Program and an American Heart Association grant 15CVGPS23430000. <br />For further information, please see the acknowledgement section of the HuRI paper. <br /><br /></span></p> <p> </p> <p> </p> <p> </p> <p><span style="font-size: 14pt;"> </span></p> </div> </div> </div> </div> </div> </main> <footer> <div class="shadow"></div> <p style="text-align: center;"> </p> <p style="text-align: center;"><span style="font-family: Arial; font-size: 14.6667px; white-space: pre-wrap;">The HuRI project is directed from the Center for Cancer Systems Biology as a joint effort between the </span><span style="color: #2b83ba;"><a style="font-family: Arial; font-size: 14.6667px; white-space: pre-wrap; color: #2b83ba;" href="https://ccsb.dana-farber.org/" target="_blank">Vidal</a></span><span style="font-family: Arial; font-size: 14.6667px; white-space: pre-wrap;">, </span><a style="font-family: Arial; font-size: 14.6667px; white-space: pre-wrap;" href="http://llama.mshri.on.ca/" target="_blank"><span style="color: #2b83ba;">Roth</span>,</a> <span style="color: #2b83ba;"><a style="font-family: Arial; font-size: 14.6667px; white-space: pre-wrap; color: #2b83ba;" href="http://www.vib.be/en/research/scientists/Pages/Jan-Tavernier-Lab.aspx" target="_blank">Tavernier</a></span><span style="font-family: Arial; font-size: 14.6667px; white-space: pre-wrap;">, and </span><span style="color: #2b83ba;"><a style="font-family: Arial; font-size: 14.6667px; white-space: pre-wrap; color: #2b83ba;" href="http://www.baderlab.org" target="_blank">Bader</a></span><span style="font-family: Arial; font-size: 14.6667px; white-space: pre-wrap;"> labs.</span></p> </footer>   <script src="/assets/js/jquery-ui.min.js"></script> <script src="/assets/js/jquery.qtip.min.js"></script> <script src="/assets/js/bootstrap.min.js"></script> <script src="/assets/js/jquery-2.1.4.min.js"></script> <script src="/assets/js/jquery-ui.min.js"></script> <script src="/assets/js/bootstrap.min.js"></script> <script src="http://cdn.jsdelivr.net/particles.js/2.0.0/particles.min.js"></script> <script src="/assets/js/main.js"></script> <script src="/assets/js/faq.js"></script> <script> (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) })(window,document,'script','https://www.google-analytics.com/analytics.js','ga'); ga('create', 'UA-387720-9', 'auto'); ga('send', 'pageview'); </script> </body> </html>