<?xml version="1.0" encoding="UTF-8"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:lang="en">
  <teiHeader>
    <fileDesc>
      <titleStmt>
        <title>Metascape provides a biologist-oriented resource for the analysis of systems-level datasets</title>
        <author>Yingyao Zhou</author>
        <author>Bin Zhou</author>
        <author>Lars Pache</author>
        <author>Max Chang</author>
        <author>Alireza Hadj Khodabakhshi</author>
        <author>Olga Tanaseichuk</author>
        <author>Christopher Benner</author>
        <author>Sumit K. Chanda</author>
      </titleStmt>
      <publicationStmt>
        <p>Tag layer of the DHSS Meta-Tagging Project. The article text is reproduced from the
           staged copy named in sourceDesc and is not altered; the tags are held separately in
           standOff so that overlapping and nested spans are preserved.</p>
      </publicationStmt>
      <sourceDesc>
        <bibl>
          <title>Metascape provides a biologist-oriented resource for the analysis of systems-level datasets</title>
          <date>2019</date>
          <publisher>Nature Communications</publisher>
          <idno type="DOI">10.1038/s41467-019-09234-6</idno>
          
          <idno type="record">zhou2019-metascape-systems-level-datasets</idno>
          <note type="staged-file">zhou2019-metascape-systems-level-datasets.txt, the project's staged copy</note>
          <note type="text-sha1">23da0df0551331c36b1d3f1042fc5f67c7acb8c0</note>
          <note type="rights">cc-by</note>
        </bibl>
      </sourceDesc>
    </fileDesc>
    <profileDesc>
      <textClass><keywords><term>bioinformatics</term></keywords></textClass>
      <particDesc>
        <person xml:id="paper"><p>the paper's own words</p></person>
        <person xml:id="tagger"><p>the tag layer; a sentence written by the tagger about the
          paper, always anchored to a quotation but not itself a quotation</p></person>
      </particDesc>
    </profileDesc>
    <revisionDesc>
      <change when="2026-10-06"
              who="build_paper_edition.py">188 spans located by searching the stored text for the quote's exact words, allowing any whitespace between them</change>
    </revisionDesc>
  </teiHeader>
  <standOff>
    <spanGrp type="tags">
      <span xml:id="t0" from="#a1" to="#a2" type="object_of_study" ana="#object_of_study" resp="#paper">integrated annotation, enrichment, interaction-network, and comparative analysis of single or multiple OMICs gene lists</span>
      <span xml:id="t1" from="#a3" to="#a4" type="research_question" ana="#research_question" resp="#paper">how to replace a fragmented, stale, and difficult multi-portal gene-list workflow with an integrated system producing current and interpretable results</span>
      <span xml:id="t2" from="#a13" to="#a14" type="contribution" ana="#contribution" resp="#paper">Metascape, an integrated web portal combining more than 40 knowledgebases, gene annotation, membership search, enrichment clustering, interactome analysis, and multi-list comparison</span>
      <span xml:id="t3" from="#a1" to="#a2" type="claim_type" ana="#claim_type" resp="#paper">method</span>
      <span xml:id="t4" from="#a27" to="#a28" type="phenomenon" ana="#phenomenon" resp="#paper">fragmentation, knowledgebase staleness, ontology redundancy, network complexity, interpretability, and cross-list agreement in OMICs analysis</span>
      <span xml:id="t5" from="#a61" to="#a62" type="method" ana="#method" resp="#paper">system-or-tool-building<term>system-or-tool-building</term></span>
      <span xml:id="t6" from="#a15" to="#a16" type="mechanisms" ana="#mechanisms[0]" resp="#tagger" cert="0.95">Detects common identifier types without user specification.<term>automatic identifier recognition</term></span>
      <span xml:id="t7" from="#a15" to="#a16" type="mechanisms" ana="#mechanisms[1]" resp="#tagger" cert="0.95">Maps candidate lists into species-specific knowledge contexts.<term>automatic orthologue mapping</term></span>
      <span xml:id="t8" from="#a19" to="#a20" type="mechanisms" ana="#mechanisms[2]" resp="#tagger" cert="0.95">Maps source and deprecated identifiers to a unique Entrez Gene ID list.<term>Entrez-centered identifier conversion</term></span>
      <span xml:id="t9" from="#a23" to="#a24" type="mechanisms" ana="#mechanisms[3]" resp="#tagger" cert="0.95">Combines metadata from more than forty knowledgebases for large candidate lists.<term>integrated batch annotation</term></span>
      <span xml:id="t10" from="#a25" to="#a26" type="mechanisms" ana="#mechanisms[4]" resp="#tagger" cert="0.95">Matches requested concepts and emits gene-level binary membership flags.<term>keyword membership search</term></span>
      <span xml:id="t11" from="#a27" to="#a28" type="mechanisms" ana="#mechanisms[5]" resp="#tagger" cert="0.95">Hierarchically clusters related terms and absorbs redundancy into representative groups.<term>Kappa-based enrichment clustering</term></span>
      <span xml:id="t12" from="#a29" to="#a30" type="mechanisms" ana="#mechanisms[6]" resp="#tagger" cert="0.95">Connects term nodes above a Kappa threshold and renders the network in Cytoscape.<term>enrichment-network rendering</term></span>
      <span xml:id="t13" from="#a33" to="#a34" type="mechanisms" ana="#mechanisms[7]" resp="#tagger" cert="0.95">Extracts dense protein complexes from large candidate interaction networks and annotates them.<term>MCODE complex extraction</term></span>
      <span xml:id="t14" from="#a37" to="#a38" type="mechanisms" ana="#mechanisms[8]" resp="#tagger" cert="0.95">Merges candidates while retaining original-list identity as binary columns.<term>multi-list pivoting</term></span>
      <span xml:id="t15" from="#a39" to="#a40" type="mechanisms" ana="#mechanisms[9]" resp="#tagger" cert="0.95">Uses heatmaps and pie-chart network nodes to show shared and selective pathways.<term>multi-list visual encoding</term></span>
      <span xml:id="t16" from="#a43" to="#a44" type="mechanisms" ana="#mechanisms[10]" resp="#tagger" cert="0.95">Combines dependency-ordered automatic processing with manual QC approval.<term>two-phase synchronization</term></span>
      <span xml:id="t17" from="#a65" to="#a66" type="mechanisms" ana="#mechanisms[11]" resp="#tagger" cert="0.95">Tests whether ontology terms overlap the input list more than chance and corrects p-values.<term>hypergeometric enrichment</term></span>
      <span xml:id="t18" from="#a67" to="#a68" type="mechanisms" ana="#mechanisms[12]" resp="#tagger" cert="0.95">Runs modified MCODE and labels each complex using its top enriched terms.<term>interactome complex annotation</term></span>
      <span xml:id="t19" from="#a69" to="#a70" type="mechanisms" ana="#mechanisms[13]" resp="#tagger" cert="0.95">Treats repeated exact input-list groups as duplicate sessions before compiling usage statistics.<term>session deduplication</term></span>
      <span xml:id="t20" from="#a3" to="#a4" type="limitations" ana="#limitations[0]" resp="#tagger" cert="0.95">A complete workflow may require multiple portals, interfaces, formats, and manual output integration.</span>
      <span xml:id="t21" from="#a5" to="#a6" type="limitations" ana="#limitations[1]" resp="#tagger" cert="0.95">Multi-gene-list meta-analysis was often missing from existing tools.</span>
      <span xml:id="t22" from="#a9" to="#a10" type="limitations" ana="#limitations[2]" resp="#tagger" cert="0.95">Interface simplification must be balanced against access to statistical and computational settings.</span>
      <span xml:id="t23" from="#a7" to="#a8" type="limitations" ana="#limitations[3]" resp="#tagger" cert="0.95">Many portals rely on stale databases that can materially alter interpretation.</span>
      <span xml:id="t24" from="#a21" to="#a22" type="limitations" ana="#limitations[4]" resp="#tagger" cert="0.95">The mouse interactome described in the paper covers only a small fraction of available human interactions.</span>
      <span xml:id="t25" from="#a27" to="#a28" type="limitations" ana="#limitations[5]" resp="#tagger" cert="0.95">Ontology redundancy across and within sources complicates extraction of representative enrichment results.</span>
      <span xml:id="t26" from="#a29" to="#a30" type="limitations" ana="#limitations[6]" resp="#tagger" cert="0.95">A bar graph alone omits inter-cluster similarity and intra-cluster redundancy.</span>
      <span xml:id="t27" from="#a33" to="#a34" type="limitations" ana="#limitations[7]" resp="#tagger" cert="0.95">Large interaction networks can be significant yet yield little actionable insight without prior expectations.</span>
      <span xml:id="t28" from="#a31" to="#a32" type="limitations" ana="#limitations[8]" resp="#tagger" cert="0.95">Single-list specialist tools may retain additional gene-signature collections that Metascape does not replace.</span>
      <span xml:id="t29" from="#a43" to="#a44" type="limitations" ana="#limitations[9]" resp="#tagger" cert="0.95">Automatic synchronization may miss subtle source inconsistencies that fail to trigger exceptions.</span>
      <span xml:id="t30" from="#a55" to="#a56" type="limitations" ana="#limitations[10]" resp="#tagger" cert="0.95">Some competing meta-analysis portals support only two or three lists or restricted organisms.</span>
      <span xml:id="t31" from="#a59" to="#a60" type="limitations" ana="#limitations[11]" resp="#tagger" cert="0.95">Default p-value ranking has acknowledged limitations and may need q-values or enrichment factors.</span>
      <span xml:id="t32" from="#a69" to="#a70" type="limitations" ana="#limitations[12]" resp="#tagger" cert="0.95">Usage statistics require deduplication of repeated inputs and retain sampling uncertainty.</span>
      <span xml:id="t33" from="#a1" to="#a2" type="concepts" ana="#concepts[0]" resp="#paper" cert="0.95">Metascape<term>Metascape</term></span>
      <span xml:id="t34" from="#a1" to="#a2" type="concepts" ana="#concepts[1]" resp="#paper" cert="0.95">systems-level studies<term>systems-level studies</term></span>
      <span xml:id="t35" from="#a1" to="#a2" type="concepts" ana="#concepts[2]" resp="#paper" cert="0.95">enriched biological pathways<term>enriched biological pathways</term></span>
      <span xml:id="t36" from="#a1" to="#a2" type="concepts" ana="#concepts[3]" resp="#paper" cert="0.95">protein complexes<term>protein complexes</term></span>
      <span xml:id="t37" from="#a1" to="#a2" type="concepts" ana="#concepts[4]" resp="#paper" cert="0.95">OMICs datasets<term>OMICs datasets</term></span>
      <span xml:id="t38" from="#a1" to="#a2" type="concepts" ana="#concepts[5]" resp="#paper" cert="0.95">biological databases<term>biological databases</term></span>
      <span xml:id="t39" from="#a1" to="#a2" type="concepts" ana="#concepts[6]" resp="#paper" cert="0.95">analytical pipeline<term>analytical pipeline</term></span>
      <span xml:id="t40" from="#a1" to="#a2" type="concepts" ana="#concepts[7]" resp="#paper" cert="0.95">web-based portal<term>web-based portal</term></span>
      <span xml:id="t41" from="#a1" to="#a2" type="concepts" ana="#concepts[8]" resp="#paper" cert="0.95">functional enrichment<term>functional enrichment</term></span>
      <span xml:id="t42" from="#a1" to="#a2" type="concepts" ana="#concepts[9]" resp="#paper" cert="0.95">interactome analysis<term>interactome analysis</term></span>
      <span xml:id="t43" from="#a53" to="#a54" type="concepts" ana="#concepts[10]" resp="#paper" cert="0.95">gene annotation<term>gene annotation</term></span>
      <span xml:id="t44" from="#a25" to="#a26" type="concepts" ana="#concepts[11]" resp="#paper" cert="0.95">membership search<term>membership search</term></span>
      <span xml:id="t45" from="#a1" to="#a2" type="concepts" ana="#concepts[12]" resp="#paper" cert="0.95">comparative analyses<term>comparative analyses</term></span>
      <span xml:id="t46" from="#a17" to="#a18" type="concepts" ana="#concepts[13]" resp="#paper" cert="0.95">Express Analysis<term>Express Analysis</term></span>
      <span xml:id="t47" from="#a17" to="#a18" type="concepts" ana="#concepts[14]" resp="#paper" cert="0.95">Custom Analysis<term>Custom Analysis</term></span>
      <span xml:id="t48" from="#a3" to="#a4" type="concepts" ana="#concepts[15]" resp="#paper" cert="0.95">fragmented user experience<term>fragmented user experience</term></span>
      <span xml:id="t49" from="#a3" to="#a4" type="concepts" ana="#concepts[16]" resp="#paper" cert="0.95">multiple portals<term>multiple portals</term></span>
      <span xml:id="t50" from="#a5" to="#a6" type="concepts" ana="#concepts[17]" resp="#paper" cert="0.95">orthogonal OMICs approaches<term>orthogonal OMICs approaches</term></span>
      <span xml:id="t51" from="#a5" to="#a6" type="concepts" ana="#concepts[18]" resp="#paper" cert="0.95">comprehensive assessment<term>comprehensive assessment</term></span>
      <span xml:id="t52" from="#a5" to="#a6" type="concepts" ana="#concepts[19]" resp="#paper" cert="0.95">false positive/negative activities<term>false positive/negative activities</term></span>
      <span xml:id="t53" from="#a5" to="#a6" type="concepts" ana="#concepts[20]" resp="#paper" cert="0.95">meta-analysis of multiple gene lists<term>meta-analysis of multiple gene lists</term></span>
      <span xml:id="t54" from="#a7" to="#a8" type="concepts" ana="#concepts[21]" resp="#paper" cert="0.95">obsolete database content<term>obsolete database content</term></span>
      <span xml:id="t55" from="#a7" to="#a8" type="concepts" ana="#concepts[22]" resp="#paper" cert="0.95">potential new biological insights<term>potential new biological insights</term></span>
      <span xml:id="t56" from="#a11" to="#a12" type="concepts" ana="#concepts[23]" resp="#paper" cert="0.95">graphical summaries of results<term>graphical summaries of results</term></span>
      <span xml:id="t57" from="#a11" to="#a12" type="concepts" ana="#concepts[24]" resp="#paper" cert="0.95">global interpretation of complex OMICs datasets<term>global interpretation of complex OMICs datasets</term></span>
      <span xml:id="t58" from="#a15" to="#a16" type="concepts" ana="#concepts[25]" resp="#paper" cert="0.95">automatic orthologue mapping<term>automatic orthologue mapping</term></span>
      <span xml:id="t59" from="#a21" to="#a22" type="concepts" ana="#concepts[26]" resp="#paper" cert="0.95">Ortholog mapping<term>Ortholog mapping</term></span>
      <span xml:id="t60" from="#a21" to="#a22" type="concepts" ana="#concepts[27]" resp="#paper" cert="0.95">built-in feature<term>built-in feature</term></span>
      <span xml:id="t61" from="#a19" to="#a20" type="concepts" ana="#concepts[28]" resp="#paper" cert="0.95">Entrez Gene ID list<term>Entrez Gene ID list</term></span>
      <span xml:id="t62" from="#a27" to="#a28" type="concepts" ana="#concepts[29]" resp="#paper" cert="0.95">Kappa similarities<term>Kappa similarities</term></span>
      <span xml:id="t63" from="#a27" to="#a28" type="concepts" ana="#concepts[30]" resp="#paper" cert="0.95">enriched terms<term>enriched terms</term></span>
      <span xml:id="t64" from="#a65" to="#a66" type="concepts" ana="#concepts[31]" resp="#paper" cert="0.95">non-redundant groups<term>non-redundant groups</term></span>
      <span xml:id="t65" from="#a27" to="#a28" type="concepts" ana="#concepts[32]" resp="#paper" cert="0.95">enrichment clustering<term>enrichment clustering</term></span>
      <span xml:id="t66" from="#a29" to="#a30" type="concepts" ana="#concepts[33]" resp="#paper" cert="0.95">enrichment networks<term>enrichment networks</term></span>
      <span xml:id="t67" from="#a29" to="#a30" type="concepts" ana="#concepts[34]" resp="#paper" cert="0.95">Cytoscape<term>Cytoscape</term></span>
      <span xml:id="t68" from="#a33" to="#a34" type="concepts" ana="#concepts[35]" resp="#paper" cert="0.95">MCODE<term>MCODE</term></span>
      <span xml:id="t69" from="#a33" to="#a34" type="concepts" ana="#concepts[36]" resp="#paper" cert="0.95">large network<term>large network</term></span>
      <span xml:id="t70" from="#a33" to="#a34" type="concepts" ana="#concepts[37]" resp="#paper" cert="0.95">hairball networks<term>hairball networks</term></span>
      <span xml:id="t71" from="#a37" to="#a38" type="concepts" ana="#concepts[38]" resp="#paper" cert="0.95">Circos plot<term>Circos plot</term></span>
      <span xml:id="t72" from="#a35" to="#a36" type="concepts" ana="#concepts[39]" resp="#paper" cert="0.95">Venn diagram<term>Venn diagram</term></span>
      <span xml:id="t73" from="#a47" to="#a48" type="concepts" ana="#concepts[40]" resp="#paper" cert="0.95">enrichment heatmaps<term>enrichment heatmaps</term></span>
      <span xml:id="t74" from="#a41" to="#a42" type="concepts" ana="#concepts[41]" resp="#paper" cert="0.95">unexpected changes<term>unexpected changes</term></span>
      <span xml:id="t75" from="#a41" to="#a42" type="concepts" ana="#concepts[42]" resp="#paper" cert="0.95">outdated portals<term>outdated portals</term></span>
      <span xml:id="t76" from="#a51" to="#a52" type="concepts" ana="#concepts[43]" resp="#paper" cert="0.95">automated robot crawling phase<term>automated robot crawling phase</term></span>
      <span xml:id="t77" from="#a51" to="#a52" type="concepts" ana="#concepts[44]" resp="#paper" cert="0.95">supervised human review phase<term>supervised human review phase</term></span>
      <span xml:id="t78" from="#a59" to="#a60" type="concepts" ana="#concepts[45]" resp="#paper" cert="0.95">p -value<term>p -value</term></span>
      <span xml:id="t79" from="#a59" to="#a60" type="concepts" ana="#concepts[46]" resp="#paper" cert="0.95">q -value<term>q -value</term></span>
      <span xml:id="t80" from="#a65" to="#a66" type="concepts" ana="#concepts[47]" resp="#paper" cert="0.95">hypergeometric test<term>hypergeometric test</term></span>
      <span xml:id="t81" from="#a65" to="#a66" type="concepts" ana="#concepts[48]" resp="#paper" cert="0.95">Benjamini-Hochberg p -value correction algorithm<term>Benjamini-Hochberg p -value correction algorithm</term></span>
      <span xml:id="t82" from="#a63" to="#a64" type="concepts" ana="#concepts[49]" resp="#paper" cert="0.95">backend knowledgebase<term>backend knowledgebase</term></span>
      <span xml:id="t83" from="#a63" to="#a64" type="concepts" ana="#concepts[50]" resp="#paper" cert="0.95">relational database<term>relational database</term></span>
      <span xml:id="t84" from="#a63" to="#a64" type="concepts" ana="#concepts[51]" resp="#paper" cert="0.95">web resource<term>web resource</term></span>
      <span xml:id="t85" from="#a57" to="#a58" type="concepts" ana="#concepts[52]" resp="#paper" cert="0.95">more recent human interactome datasets<term>more recent human interactome datasets</term></span>
      <span xml:id="t86" from="#a57" to="#a58" type="concepts" ana="#concepts[53]" resp="#paper" cert="0.95">tripling of human interactome coverage<term>tripling of human interactome coverage</term></span>
      <span xml:id="t87" from="#a61" to="#a62" type="concepts" ana="#concepts[54]" resp="#paper" cert="0.95">wider adoption of Metascape<term>wider adoption of Metascape</term></span>
      <span xml:id="t88" from="#a61" to="#a62" type="concepts" ana="#concepts[55]" resp="#paper" cert="0.95">biological interpretation<term>biological interpretation</term></span>
      <span xml:id="t89" from="#a49" to="#a50" type="concepts" ana="#concepts[56]" resp="#paper" cert="0.95">existing specialized tools<term>existing specialized tools</term></span>
      <span xml:id="t90" from="#a31" to="#a32" type="concepts" ana="#concepts[57]" resp="#paper" cert="0.95">existing functional enrichment analysis portals<term>existing functional enrichment analysis portals</term></span>
      <span xml:id="t91" from="#a59" to="#a60" type="concepts" ana="#concepts[58]" resp="#paper" cert="0.95">g:Profiler<term>g:Profiler</term></span>
      <span xml:id="t92" from="#a59" to="#a60" type="concepts" ana="#concepts[59]" resp="#paper" cert="0.95">Metascape and DAVID<term>Metascape and DAVID</term></span>
      <span xml:id="t93" from="#a57" to="#a58" type="concepts" ana="#concepts[60]" resp="#paper" cert="0.95">Babelomics<term>Babelomics</term></span>
      <span xml:id="t94" from="#a9" to="#a10" type="unhoused_relations" ana="#unhoused_relations[0]" resp="#tagger" cert="0.95">well-designed interface → barrier to entry<note>Fewer required interactions reduce the barrier to entry.</note></span>
      <span xml:id="t95" from="#a5" to="#a6" type="unhoused_relations" ana="#unhoused_relations[1]" resp="#tagger" cert="0.95">orthogonal OMICs approaches → false positive/negative activities<note>Using orthogonal approaches reduces platform-specific false positives and negatives.</note></span>
      <span xml:id="t96" from="#a27" to="#a28" type="unhoused_relations" ana="#unhoused_relations[2]" resp="#tagger" cert="0.95">enrichment clustering → confounding data interpretation issues<note>Clustering eliminates interpretation problems created by redundant ontologies.</note></span>
      <span xml:id="t97" from="#a25" to="#a26" type="unhoused_relations" ana="#unhoused_relations[3]" resp="#tagger" cert="0.95">membership search → reliance on existing hierarchical ontologies<note>Membership search reduces reliance on fixed ontology hierarchies.</note></span>
      <span xml:id="t98" from="#a19" to="#a20" type="unhoused_relations" ana="#unhoused_relations[4]" resp="#tagger" cert="0.95">source identifiers → Entrez Gene ID list<note>Source identifiers are mapped onto a unique Entrez Gene ID list.</note></span>
      <span xml:id="t99" from="#a37" to="#a38" type="unhoused_relations" ana="#unhoused_relations[5]" resp="#tagger" cert="0.95">multiple gene lists → one list<note>Multiple lists are merged while their origins are retained as binary columns.</note></span>
      <span xml:id="t100" from="#a43" to="#a44" type="unhoused_relations" ana="#unhoused_relations[6]" resp="#tagger" cert="0.95">last known compatible copy → timely completion<note>Reusing the last compatible source prevents one conflict from stopping the update cycle.</note></span>
      <span xml:id="t101" from="#a33" to="#a34" type="unhoused_relations" ana="#unhoused_relations[7]" resp="#tagger" cert="0.95">Metascape → protein complexes<note>Metascape uses MCODE to extract protein complexes embedded in a large network.</note></span>
      <span xml:id="t102" from="#a59" to="#a60" type="unhoused_relations" ana="#unhoused_relations[8]" resp="#tagger" cert="0.95">p -value → q -value<note>A q-value is offered as an alternative to default p-value ranking.</note></span>
      <span xml:id="t103" from="#a51" to="#a52" type="unhoused_relations" ana="#unhoused_relations[9]" resp="#tagger" cert="0.95">automated robot crawling phase → supervised human review phase<note>The synchronization workflow combines automated crawling with supervised review.</note></span>
      <span xml:id="t104" from="#a53" to="#a54" type="senses" ana="#senses[0]" resp="#tagger" cert="0.95">gene annotation as batch metadata extraction rather than enrichment analysis</span>
      <span xml:id="t105" from="#a25" to="#a26" type="senses" ana="#senses[1]" resp="#tagger" cert="0.95">membership search as dynamic functional highlighting when pre-integrated metadata are absent</span>
      <span xml:id="t106" from="#a17" to="#a18" type="senses" ana="#senses[2]" resp="#tagger" cert="0.95">Express Analysis as streamlined defaults and Custom Analysis as parameter-level control</span>
      <span xml:id="t107" from="#a27" to="#a28" type="senses" ana="#senses[3]" resp="#tagger" cert="0.95">enrichment clustering as redundancy absorption into representative process groups</span>
      <span xml:id="t108" from="#a29" to="#a30" type="senses" ana="#senses[4]" resp="#tagger" cert="0.95">enrichment network as a term-similarity graph rather than a bar-chart ranking</span>
      <span xml:id="t109" from="#a33" to="#a34" type="senses" ana="#senses[5]" resp="#tagger" cert="0.95">hairball network as statistically significant but poorly actionable interaction structure</span>
      <span xml:id="t110" from="#a35" to="#a36" type="senses" ana="#senses[6]" resp="#tagger" cert="0.95">multi-list meta-analysis as comparison at gene, pathway, and protein-complex levels</span>
      <span xml:id="t111" from="#a43" to="#a44" type="senses" ana="#senses[7]" resp="#tagger" cert="0.95">future-proofing as recurring synchronization of changing dependent knowledgebases</span>
      <span xml:id="t112" from="#a59" to="#a60" type="senses" ana="#senses[8]" resp="#tagger" cert="0.95">interpretability as concise non-redundant and biologically actionable output</span>
      <span xml:id="t113" from="#a49" to="#a50" type="senses" ana="#senses[9]" resp="#tagger" cert="0.95">Metascape as an integrator of specialized tools rather than their replacement</span>
      <span xml:id="t114" from="#a13" to="#a14" type="claim_relations" ana="#claim_relations[0]" resp="#tagger" cert="0.95">builds-on → best practices of OMICs data analyses from the preceding decade<note>note: The integrated portal consolidates established analysis practices.</note></span>
      <span xml:id="t115" from="#a3" to="#a4" type="claim_relations" ana="#claim_relations[1]" resp="#tagger" cert="0.95">critiques → fragmented multi-portal systems-level analysis workflows<note>note: The paper identifies fragmentation, integration burden, and omitted knowledge.</note></span>
      <span xml:id="t116" from="#a37" to="#a38" type="claim_relations" ana="#claim_relations[2]" resp="#tagger" cert="0.95">extends → single-gene-list annotation and enrichment<note>note: The architecture generalizes the workflow to comparative analysis of arbitrary list counts.</note></span>
      <span xml:id="t117" from="#a31" to="#a32" type="claim_relations" ana="#claim_relations[3]" resp="#tagger" cert="0.95">contrasts-with → single-purpose enrichment portals<note>note: The authors position Metascape as integrative rather than a replacement for specialized collections.</note></span>
      <span xml:id="t118" from="#a45" to="#a46" type="claim_relations" ana="#claim_relations[4]" resp="#tagger" cert="0.95">supports → the utility of a streamlined default workflow<note>note: Observed selection of Express Analysis supports the default-setting design.</note></span>
      <span xml:id="t119" from="#a59" to="#a60" type="claim_relations" ana="#claim_relations[5]" resp="#tagger" cert="0.95">qualifies → p-value ranking as a sufficient account of enrichment<note>note: The paper retains p-values by default but explicitly points to corrected and context-sensitive alternatives.</note></span>
      <span xml:id="t120" from="#a61" to="#a62" type="claim_relations" ana="#claim_relations[6]" resp="#tagger" cert="0.9">predicts → improved biological interpretation through wider Metascape adoption<note>note: The conclusion states an expectation about future impact.</note></span>
      <span xml:id="t121" from="#a1" to="#a2" type="concept_edges" ana="#concept_edges[0]" resp="#tagger" cert="0.95">Metascape —is-a→ web-based portal<note>the relation itself is separately evidenced · strength of the relation: 1 · note: Direct categorical statement. · the relation stated: Metascape is a web-based portal.</note><term>Metascape</term><term>web-based portal</term></span>
      <span xml:id="t122" from="#a21" to="#a22" type="concept_edges" ana="#concept_edges[1]" resp="#tagger" cert="0.95">Ortholog mapping —is-a→ built-in feature<note>the relation itself is separately evidenced · strength of the relation: 1 · note: Direct categorical statement. · the relation stated: Ortholog mapping is a built-in feature.</note><term>Ortholog mapping</term><term>built-in feature</term></span>
      <span xml:id="t123" from="#a63" to="#a64" type="concept_edges" ana="#concept_edges[2]" resp="#tagger" cert="0.95">backend knowledgebase —is-a→ relational database<note>the relation itself is separately evidenced · strength of the relation: 1 · note: Direct categorical statement. · the relation stated: The backend knowledgebase is a relational database.</note><term>backend knowledgebase</term><term>relational database</term></span>
      <span xml:id="t124" from="#a63" to="#a64" type="concept_edges" ana="#concept_edges[3]" resp="#tagger" cert="0.95">Metascape —is-a→ web resource<note>the relation itself is separately evidenced · strength of the relation: 1 · note: Direct categorical statement. · the relation stated: Metascape is a web resource.</note><term>Metascape</term><term>web resource</term></span>
      <span xml:id="t125" from="#a17" to="#a18" type="concept_edges" ana="#concept_edges[4]" resp="#tagger" cert="0.95">Custom Analysis —contrasted-with→ Express Analysis<note>the relation itself is separately evidenced · strength of the relation: 1 · note: Categorical workflow alternative. · the relation stated: Custom Analysis is presented as an alternative to Express Analysis.</note><term>Custom Analysis</term><term>Express Analysis</term></span>
      <span xml:id="t126" from="#a37" to="#a38" type="concept_edges" ana="#concept_edges[5]" resp="#tagger" cert="0.95">Circos plot —contrasted-with→ Venn diagram<note>the relation itself is separately evidenced · strength of the relation: 0.95 · note: Flat gradable comparison. · the relation stated: The Circos plot is described as more intuitive and scalable than a Venn diagram.</note><term>Circos plot</term><term>Venn diagram</term></span>
      <span xml:id="t127" from="#a3" to="#a4" type="concept_edges" ana="#concept_edges[6]" resp="#tagger" cert="0.95">multiple portals —causes→ fragmented user experience<note>direction on the measure: increases · the relation itself is separately evidenced · strength of the relation: 0.95 · note: Direct positive causation of the named fragmentation state. · the relation stated: Requiring multiple portals leads to a fragmented user experience.</note><term>multiple portals</term><term>fragmented user experience</term></span>
      <span xml:id="t128" from="#a11" to="#a12" type="concept_edges" ana="#concept_edges[7]" resp="#tagger" cert="0.95">graphical summaries of results —causes→ global interpretation of complex OMICs datasets<note>status: tend to · direction on the measure: increases · the relation itself is separately evidenced · strength of the relation: 0.7 · note: The hedge &#x27;tend to&#x27; lowers weight. · the relation stated: Graphical summaries tend to enhance global interpretation.
Audit 2026-09-28: DOUBTFUL - read against its full span and kept, but the span says such platforms TEND to enhance interpretation; hedged.</note><term>graphical summaries of results</term><term>global interpretation of complex OMICs datasets</term></span>
      <span xml:id="t129" from="#a41" to="#a42" type="concept_edges" ana="#concept_edges[8]" resp="#tagger" cert="0.95">unexpected changes —causes→ outdated portals<note>direction on the measure: increases · the relation itself is separately evidenced · strength of the relation: 0.95 · note: Direct result statement. · the relation stated: Unexpected synchronization changes eventually result in outdated portals.</note><term>unexpected changes</term><term>outdated portals</term></span>
      <span xml:id="t130" from="#a57" to="#a58" type="concept_edges" ana="#concept_edges[9]" resp="#tagger" cert="0.95">more recent human interactome datasets —causes→ tripling of human interactome coverage<note>direction on the measure: increases · the relation itself is separately evidenced · strength of the relation: 0.95 · note: Direct result statement. · the relation stated: Integrating recent human interactome datasets results in a tripling of coverage.</note><term>more recent human interactome datasets</term><term>tripling of human interactome coverage</term></span>
      <span xml:id="t131" from="#a61" to="#a62" type="concept_edges" ana="#concept_edges[10]" resp="#tagger" cert="0.9">wider adoption of Metascape —causes→ biological interpretation<note>status: We expect · direction on the measure: increases · the relation itself is separately evidenced · strength of the relation: 0.6 — the record marks this weak · note: Explicit future expectation, not an observed effect. · the relation stated: The authors expect wider adoption to enhance biological interpretation.
Audit 2026-09-28: DOUBTFUL - read against its span and kept, but the authors EXPECT wider adoption to enhance interpretation; causes is hedged.</note><term>wider adoption of Metascape</term><term>biological interpretation</term></span>
      <span xml:id="t132" from="#a49" to="#a50" type="concept_edges" ana="#concept_edges[11]" resp="#tagger" cert="0.95">Metascape —contrasted-with→ existing specialized tools<note>the relation itself is separately evidenced · strength of the relation: 1 · note: Flat categorical positioning statement. · the relation stated: Metascape is not intended to replace existing specialized tools.
Audit 2026-09-28: DOUBTFUL - read against its full span and kept, but the span says Metascape was not developed to REPLACE them; contrasted-with is loose.</note><term>Metascape</term><term>existing specialized tools</term></span>
      <span xml:id="t133" from="#a31" to="#a32" type="concept_edges" ana="#concept_edges[12]" resp="#tagger" cert="0.95">Metascape —contrasted-with→ existing functional enrichment analysis portals<note>the relation itself is separately evidenced · strength of the relation: 1 · note: Flat categorical scope statement. · the relation stated: Metascape is not designed to supersede existing functional enrichment portals.
Audit 2026-09-28: DOUBTFUL - read against its full span and kept, but the span says Metascape is not designed to SUPERSEDE them; contrasted-with is loose.</note><term>Metascape</term><term>existing functional enrichment analysis portals</term></span>
      <span xml:id="t134" from="#a59" to="#a60" type="concept_edges" ana="#concept_edges[13]" resp="#tagger" cert="0.95">Metascape and DAVID —contrasted-with→ g:Profiler<note>the relation itself is separately evidenced · strength of the relation: 0.95 · note: Flat methodological comparison. · the relation stated: Metascape and DAVID use dynamic clustering, by contrast with g:Profiler&#x27;s ontology hierarchy.</note><term>Metascape and DAVID</term><term>g:Profiler</term></span>
      <span xml:id="t135" from="#a57" to="#a58" type="concept_edges" ana="#concept_edges[14]" resp="#tagger" cert="0.95">interactome analysis —distinct-from→ Babelomics<note>the relation itself is separately evidenced · strength of the relation: 0.95 · note: The article explicitly says it is distinguished by two features. · the relation stated: Metascape&#x27;s interactome analysis is distinguished from the comparison portals.
Audit 2026-09-28: DOUBTFUL - read against its full span and kept, but the span distinguishes METASCAPE&#x27;s interactome analysis from Babelomics&#x27;; the from-endpoint is loose.</note><term>interactome analysis</term><term>Babelomics</term></span>
      <span xml:id="t136" from="#a3" to="#a4" type="content_tags" ana="#content_tags.findings[0]" resp="#tagger" cert="0.95">A complete systems-level workflow generally requires multiple portals, creating a fragmented user experience.</span>
      <span xml:id="t137" from="#a3" to="#a4" type="content_tags" ana="#content_tags.findings[1]" resp="#tagger" cert="0.9">The fragmentation of sources and tools can cause existing biological knowledge to be omitted from OMICs interpretation.</span>
      <span xml:id="t138" from="#a5" to="#a6" type="content_tags" ana="#content_tags.findings[2]" resp="#tagger" cert="0.95">Multi-gene-list meta-analysis was often absent from the 25 surveyed tools.</span>
      <span xml:id="t139" from="#a7" to="#a8" type="content_tags" ana="#content_tags.findings[3]" resp="#tagger" cert="0.9">Obsolete portal databases were estimated to cause large losses of potential new biological insights.</span>
      <span xml:id="t140" from="#a11" to="#a12" type="content_tags" ana="#content_tags.findings[4]" resp="#tagger" cert="0.9">Graphical summaries tend to improve global interpretation of complex OMICs datasets.</span>
      <span xml:id="t141" from="#a15" to="#a16" type="content_tags" ana="#content_tags.findings[5]" resp="#tagger" cert="0.95">Automatic identifier recognition and orthologue mapping reduce the setup burden for users.</span>
      <span xml:id="t142" from="#a23" to="#a24" type="content_tags" ana="#content_tags.findings[6]" resp="#tagger" cert="0.95">Metascape integrates annotation information from more than 40 knowledgebases and exposes up to 47 metadata columns.</span>
      <span xml:id="t143" from="#a27" to="#a28" type="content_tags" ana="#content_tags.findings[7]" resp="#tagger" cert="0.95">Kappa-based hierarchical clustering absorbs redundant enrichment terms into representative clusters.</span>
      <span xml:id="t144" from="#a33" to="#a34" type="content_tags" ana="#content_tags.findings[8]" resp="#tagger" cert="0.95">MCODE extraction and functional annotation turn dense interaction networks into simpler interpretable complexes.</span>
      <span xml:id="t145" from="#a37" to="#a38" type="content_tags" ana="#content_tags.findings[9]" resp="#tagger" cert="0.95">A pivoted multi-list representation supports joint filtering, prioritization, and scalable Circos visualization.</span>
      <span xml:id="t146" from="#a43" to="#a44" type="content_tags" ana="#content_tags.findings[10]" resp="#tagger" cert="0.95">A two-phase synchronization workflow combines automatic processing with human QC while allowing monthly updates.</span>
      <span xml:id="t147" from="#a45" to="#a46" type="content_tags" ana="#content_tags.findings[11]" resp="#tagger" cert="0.95">Most observed users selected Express Analysis, while only a minority of sessions contained multiple gene lists.</span>
      <span xml:id="t148" from="#a51" to="#a52" type="content_tags" ana="#content_tags.findings[12]" resp="#tagger" cert="0.95">Most surveyed portals used knowledgebases more than one year old.</span>
      <span xml:id="t149" from="#a53" to="#a54" type="content_tags" ana="#content_tags.findings[13]" resp="#tagger" cert="0.95">Metascape batch-extracts metadata that otherwise require portal-by-portal or gene-by-gene queries.</span>
      <span xml:id="t150" from="#a55" to="#a56" type="content_tags" ana="#content_tags.findings[14]" resp="#tagger" cert="0.95">The multi-list architecture supports an arbitrary number of gene lists subject only to computing resources.</span>
      <span xml:id="t151" from="#a57" to="#a58" type="content_tags" ana="#content_tags.findings[15]" resp="#tagger" cert="0.95">Adding InWeb_IM and OmniPath tripled human interactome coverage relative to BioGrid alone.</span>
      <span xml:id="t152" from="#a65" to="#a66" type="content_tags" ana="#content_tags.findings[16]" resp="#tagger" cert="0.95">Metascape uses a hypergeometric test and Benjamini-Hochberg correction, then represents each cluster with its lowest-p term.</span>
      <span xml:id="t153" from="#a1" to="#a2" type="content_tags" ana="#content_tags.definitions[0]" resp="#tagger" cert="0.95">a web portal integrating gene-list annotation and analysis for experimental biologists<term>Metascape</term></span>
      <span xml:id="t154" from="#a53" to="#a54" type="content_tags" ana="#content_tags.definitions[1]" resp="#tagger" cert="0.95">batch extraction of diverse gene metadata rather than a synonym for enrichment<term>gene annotation</term></span>
      <span xml:id="t155" from="#a25" to="#a26" type="content_tags" ana="#content_tags.definitions[2]" resp="#tagger" cert="0.95">keyword matching against category names and descriptions followed by binary membership flags<term>membership search</term></span>
      <span xml:id="t156" from="#a17" to="#a18" type="content_tags" ana="#content_tags.definitions[3]" resp="#tagger" cert="0.95">a streamlined workflow encoding common options and default best practices<term>Express Analysis</term></span>
      <span xml:id="t157" from="#a17" to="#a18" type="content_tags" ana="#content_tags.definitions[4]" resp="#tagger" cert="0.95">the adjustable alternative exposing individual workflow steps<term>Custom Analysis</term></span>
      <span xml:id="t158" from="#a27" to="#a28" type="content_tags" ana="#content_tags.definitions[5]" resp="#tagger" cert="0.95">Kappa-based hierarchical clustering of related enriched terms<term>enrichment clustering</term></span>
      <span xml:id="t159" from="#a29" to="#a30" type="content_tags" ana="#content_tags.definitions[6]" resp="#tagger" cert="0.95">nodes for enriched terms connected when Kappa similarity exceeds 0.3<term>enrichment networks</term></span>
      <span xml:id="t160" from="#a33" to="#a34" type="content_tags" ana="#content_tags.definitions[7]" resp="#tagger" cert="0.95">large statistically significant interaction layouts with little direct actionability<term>hairball networks</term></span>
      <span xml:id="t161" from="#a21" to="#a22" type="content_tags" ana="#content_tags.definitions[8]" resp="#tagger" cert="0.95">casting model-organism candidates into a selected target species<term>Ortholog mapping</term></span>
      <span xml:id="t162" from="#a63" to="#a64" type="content_tags" ana="#content_tags.definitions[9]" resp="#tagger" cert="0.95">a MySQL relational knowledgebase with Angular and Python service layers<term>backend knowledgebase</term></span>
      <span xml:id="t163" from="#a3" to="#a4" type="content_tags" ana="#content_tags.quantities[0]" resp="#tagger" cert="0.95">25 — existing data-analysis portals examined</span>
      <span xml:id="t164" from="#a23" to="#a24" type="content_tags" ana="#content_tags.quantities[1]" resp="#tagger" cert="0.95">over 40 — knowledgebases integrated by Metascape</span>
      <span xml:id="t165" from="#a7" to="#a8" type="content_tags" ana="#content_tags.quantities[2]" resp="#tagger" cert="0.9">67% — estimated publications missing insights because of obsolete portal content</span>
      <span xml:id="t166" from="#a7" to="#a8" type="content_tags" ana="#content_tags.quantities[3]" resp="#tagger" cert="0.9">74% — estimated potential new insights missed in those publications</span>
      <span xml:id="t167" from="#a15" to="#a16" type="content_tags" ana="#content_tags.quantities[4]" resp="#tagger" cert="0.95">63% — analyses using human datasets</span>
      <span xml:id="t168" from="#a15" to="#a16" type="content_tags" ana="#content_tags.quantities[5]" resp="#tagger" cert="0.95">ten — model organisms whose identifiers are recognized or supported</span>
      <span xml:id="t169" from="#a21" to="#a22" type="content_tags" ana="#content_tags.quantities[6]" resp="#tagger" cert="0.95">~6% — mouse interactome size relative to the available human interactome</span>
      <span xml:id="t170" from="#a29" to="#a30" type="content_tags" ana="#content_tags.quantities[7]" resp="#tagger" cert="0.95">0.3 — Kappa similarity threshold for enrichment networks and term clusters</span>
      <span xml:id="t171" from="#a41" to="#a42" type="content_tags" ana="#content_tags.quantities[8]" resp="#tagger" cert="0.95">67% — compound reliability of forty independent 99%-reliable sources</span>
      <span xml:id="t172" from="#a45" to="#a46" type="content_tags" ana="#content_tags.quantities[9]" resp="#tagger" cert="0.95">~78% — recent users choosing Express Analysis</span>
      <span xml:id="t173" from="#a45" to="#a46" type="content_tags" ana="#content_tags.quantities[10]" resp="#tagger" cert="0.95">6% — recent analyses containing more than one gene list</span>
      <span xml:id="t174" from="#a51" to="#a52" type="content_tags" ana="#content_tags.quantities[11]" resp="#tagger" cert="0.95">60% — surveyed portals using knowledgebases older than one year</span>
      <span xml:id="t175" from="#a69" to="#a70" type="content_tags" ana="#content_tags.quantities[12]" resp="#tagger" cert="0.95">over 70,000 — deduplicated recent analysis sessions used for usage statistics</span>
      <span xml:id="t176" from="#a69" to="#a70" type="content_tags" ana="#content_tags.quantities[13]" resp="#tagger" cert="0.95">241 — publications used to estimate output usage</span>
      <span xml:id="t177" from="#a69" to="#a70" type="content_tags" ana="#content_tags.quantities[14]" resp="#tagger" cert="0.95">3% — maximum stated standard deviation of publication-use estimates</span>
      <span xml:id="t178" from="#a3" to="#a4" type="content_tags" ana="#content_tags.variables[0]" resp="#tagger" cert="0.95">database updates<term>database updates</term></span>
      <span xml:id="t179" from="#a3" to="#a4" type="content_tags" ana="#content_tags.variables[1]" resp="#tagger" cert="0.95">coverage of analyses<term>coverage of analyses</term></span>
      <span xml:id="t180" from="#a3" to="#a4" type="content_tags" ana="#content_tags.variables[2]" resp="#tagger" cert="0.95">interpretability of outputs<term>interpretability of outputs</term></span>
      <span xml:id="t181" from="#a9" to="#a10" type="content_tags" ana="#content_tags.variables[3]" resp="#tagger" cert="0.95">user interactions<term>user interactions</term></span>
      <span xml:id="t182" from="#a9" to="#a10" type="content_tags" ana="#content_tags.variables[4]" resp="#tagger" cert="0.95">statistical and computational criteria<term>statistical and computational criteria</term></span>
      <span xml:id="t183" from="#a27" to="#a28" type="content_tags" ana="#content_tags.variables[5]" resp="#tagger" cert="0.95">Kappa similarities<term>Kappa similarities</term></span>
      <span xml:id="t184" from="#a59" to="#a60" type="content_tags" ana="#content_tags.variables[6]" resp="#tagger" cert="0.95">p -values<term>p -values</term></span>
      <span xml:id="t185" from="#a59" to="#a60" type="content_tags" ana="#content_tags.variables[7]" resp="#tagger" cert="0.95">q -value<term>q -value</term></span>
      <span xml:id="t186" from="#a55" to="#a56" type="content_tags" ana="#content_tags.variables[8]" resp="#tagger" cert="0.95">available computing time and memory space<term>available computing time and memory space</term></span>
      <span xml:id="t187" from="#a45" to="#a46" type="content_tags" ana="#content_tags.variables[9]" resp="#tagger" cert="0.95">input identifier types<term>input identifier types</term></span>
    </spanGrp>
  </standOff>
  <text>
    <body>
        <p><anchor xml:id="a0"/> Metascape provides a biologist-oriented resource for the analysis of systems-level datasets</p>
        <p>Abstract</p>
        <p><anchor xml:id="a1"/>A critical component in the interpretation of systems-level studies is the inference of enriched biological pathways and protein complexes contained within OMICs datasets. Successful analysis requires the integration of a broad set of current biological databases and the application of a robust analytical pipeline to produce readily interpretable results. Metascape is a web-based portal designed to provide a comprehensive gene list annotation and analysis resource for experimental biologists. In terms of design features, Metascape combines functional enrichment, interactome analysis, gene annotation, and membership search to leverage over 40 independent knowledgebases within one integrated portal. Additionally, it facilitates comparative analyses of datasets across multiple independent and orthogonal experiments. Metascape provides a significantly simplified user experience through a one-click Express Analysis interface to generate interpretable outputs. Taken together, Metascape is an effective and efficient tool for experimental biologists to comprehensively analyze and interpret OMICs-based studies in the big data era.<anchor xml:id="a2"/></p>
        <p>Introduction</p>
        <p>It has become a standard practice to employ one or more OMICs assays to deconstruct the molecular mechanisms underlying a biological system. Since each study ultimately results in a list containing dozens or hundreds of gene candidates, it is essential to leverage existing biological knowledge through understanding the representation of known pathways or complexes within these datasets. Providing this molecular context can facilitate the interpretation of systems-level data and enable new discoveries. Common queries include: What pathways or biochemical complexes are enriched? 1 ; What are the functional roles of identified protein complexes? 2 ; Which candidate proteins are secreted, contain a transmembrane domain, or are otherwise druggable? 3 ; Or are there any chemical probes available for a rapid candidate validation 4 ? Critically, when multiple gene lists are analyzed, either from common or orthogonal platforms, the identification of consistent underlying pathways or networks can help decipher authentic signals above the experimental noise 5 . Conversely, pathways selectively enriched in specific lists can help elucidate critical molecular features that distinguish experimental conditions. Thus, gene-list analysis web portals have become a necessity for modern biological research. For example, DAVID 6 , a popular web-based annotation tool has been employed by more than 4000 published studies per year since 2014, underscoring the importance of OMICs analysis engines in biological research.</p>
        <p><anchor xml:id="a3"/>To guide the development of a next-generation tool, we studied 25 existing data analysis portals 7 , 8 , focusing on database updates, coverage of analyses, coherence of interfaces, and interpretability of outputs. While each platform maintains strong feature sets (Supplementary Data 1 ), multiple portals are required to accomplish a complete systems-level analysis workflow, leading to a fragmented user experience. For example, a user analyzing proteomics data may need to use one tool to convert protein identifiers into gene symbols, a second tool to perform pathway enrichment analysis, a third tool to assess protein interaction networks, followed by other tools to produce high-quality visualizations of the data. Users are not only required to learn the details behind how to use each interface successfully, but they must also learn how to integrate the outputs from multiple types of analyses and file formats in order to generate useful results. For the inexperienced user, this can pose a significant barrier to entry. Thus, it is likely that significant levels of existing biological knowledge are often inadvertently omitted during the analysis of OMICs datasets due to the disintegrated nature of data sources and analysis tools. Ideally, a broad range of biological relationships and classifications can be assessed within one integrated portal.<anchor xml:id="a4"/></p>
        <p><anchor xml:id="a5"/>Additionally, the increased accessibility of systems-level technology platforms has promoted experimental strategies that rely on orthogonal OMICs approaches, including transcriptome analysis, genetic screens, and proteomics, to interrogate an experimental system. This approach enables a more comprehensive assessment of the molecular features of a biological process and reduces false positive/negative activities associated with individual platforms 9 . Thus, meta-analysis of multiple gene lists to identify commonly-enriched and selectively-enriched pathways is likely to become an essential component of large-scale data analysis. Methods for the analysis of multiple gene lists continue to be an area of active investigation, which highlights the necessity to develop analytical strategies that extend beyond the consolidation and analysis of individual lists, and implement approaches that will enable emergent insights that cannot be extracted using current approaches 10 , 11 . Our survey found that multi-gene-list meta-analysis is a feature often missing from existing tools (Supplementary Data 1 ).<anchor xml:id="a6"/></p>
        <p><anchor xml:id="a7"/>In addition to a combination of diverse knowledgebases and the synthesis of analysis results across related gene lists, we propose that biologist-oriented portals would need to incorporate additional critical features, including future-proofing, usability, and interpretability, to maximize their utility. Specifically, analysis portals must continually be kept up to date, since using outdated databases can severely impact analysis and interpretation of OMICs data. It has been estimated that 67% of ~3900 publications in 2015 missed 74% of potential new biological insights as a consequence of the use of obsolete database content in many analysis portals 7 . This remains a concern to date, as the databases underpinning the interpretation of a majority of published studies are over 2 years old 12 .<anchor xml:id="a8"/></p>
        <p><anchor xml:id="a9"/>Additionally, a well-designed interface that requires a minimal number of user interactions (clicks) reduces the barrier to entry for new users, or those with limited computational training. Nevertheless, simplification must be balanced with providing users sufficient information to understand and, if required, adjust statistical and computational criteria within the analysis workflow. This feature would provide expanded access to data analysis tools and sources for experimentalists that have limited experience with OMICs analysis, while enabling more advanced users to adjust analytical parameters to customize analyses.<anchor xml:id="a10"/></p>
        <p><anchor xml:id="a11"/>Furthermore, it is essential that analysis results are readily decipherable, highlighting the key, non-redundant results that will be critical for informing future studies. Platforms that go beyond exporting tabular annotation information to produce graphical summaries of results tend to enhance the global interpretation of complex OMICs datasets. The resulting output analyses should also adopt presentation formats that facilitate data dissemination among scientists.<anchor xml:id="a12"/></p>
        <p><anchor xml:id="a13"/>With these design criteria in mind, we developed Metascape to harness the best practices of OMICs data analyses that have emerged over the last decade into one integrated portal. Here, we describe the features of this platform, which provide enhanced rendition of systems-level data, designed to promote the development of actionable hypotheses. These include data-engineering solutions for over 40 knowledgebases, as well as integrated and simplified workflows for gene annotation, membership search, and multi-list comparative analysis. Furthermore, we describe unique graphical outputs that enhance reporting and boost data comprehension. Taken together, Metascape provides an integrated and user-friendly web tool designed to facilitate multi-platform OMICs data analysis and interpretation for the experimental research community.<anchor xml:id="a14"/></p>
        <p>Results</p>
        <p>User experience overview</p>
        <p>To illustrate the features and capabilities of Metascape, we utilized three previously published influenza genetic screens 13 – 15 as examples in this study (see Methods). These studies utilize genome-wide RNAi screening in cells to identify host factors that modulate influenza replication rates. Specifically, single-gene-list analyses were performed with gene targets identified in the Brass et al. study 13 , and multi-gene-list analyses were performed with the combination of Brass et al., Karlas et al 14 ., and Konig et al. 15 target lists. The step-by-step illustration of the Metascape analysis interface for both single- and multiple-list input scenarios are available in Supplementary Figures 1 – 7 . While these examples showcase the analysis of RNAi functional genomics studies, Metascape is equally capable of analyzing lists of genes from multiple assay types, including transcriptomics, epigenetics, proteomics, and others.</p>
        <p>The primary Metascape user experience is provided through a one-click analysis interface (Express Analysis, Supplementary Fig. 1 ). The user first provides a single or multiple input gene lists, then launches an automated analysis workflow consisting of four major components: identifier c onversion, gene a nnotation, m embership search, and e nrichment analysis (CAME). An analysis report summarizing key results is produced, accompanied by an Excel workbook, a PowerPoint presentation, and a Zip package containing all supporting data files (Fig. 1 ).</p>
        <p>Schematic outline of the Metascape analysis workflow. Upon gene list submission, Custom Analysis enables users to navigate the analysis workflow and output a report. The Express Analysis instead takes a streamlined approach by running the analysis steps with popular default settings, simplifying the user experience</p>
        <p><anchor xml:id="a15"/>The Metascape interface was designed to limit user operations to a minimum number of interactions. Input data is automatically processed to recognize identifier types, such as Entrez Gene ID, gene symbol, RefSeq number, Ensembl ID, etc., without user specification. The file input supports multiple flexible formats (Supplementary Figure 1 ) and can incorporate an optional background gene list to customize the enrichment analysis. Gene identifiers from ten popular model organisms are recognized by Metascape (see Methods), and automatic orthologue mapping enables gene lists to be analyzed in the context of species-specific databases across any of these ten organisms. The target analysis species is human by default, since human-centric databases are often the most comprehensive. Importantly, we have observed that 63% of Metascape analyses to date utilize human datasets.<anchor xml:id="a16"/></p>
        <p><anchor xml:id="a17"/>The concept behind Express Analysis is to encapsulate the most widely used analysis options and best analysis practices into a streamlined approach. For example, Express Analysis automatically includes gene annotation metadata that are likely to provide valuable context for candidate interpretation in most cases, such as their brief description, key biological processes involved, protein functions, subcellular locations, and roles in canonical pathways (Supplementary Figure 3 ). It incorporates a core set of default ontologies for enrichment analysis, including GO processes 16 , KEGG pathways 17 , Reactome gene sets 18 , canonical pathways 19 , and CORUM complexes 20 (Supplementary Figure 5 ). Express Analysis also automatically sets statistical filters to remove ontology terms and interactome networks that do not meet minimal statistical requirements (Supplementary Figure 5 ). As an alternative to the Express Analysis, advanced users can control the four individual steps of the CAME workflow and overwrite default settings through the Custom Analysis workflow (Fig. 1 , Supplementary Figures 2 – 6 ).<anchor xml:id="a18"/></p>
        <p>Identifier conversion analysis</p>
        <p><anchor xml:id="a19"/>The first step of the Metascape analysis workflow is gene identifier conversion (Supplementary Figure 2 ). Metascape automatically recognizes the popular gene identifier types described above, as well as primary locus names from various model organism databases, such as SGD 21 , FlyBase 22 , WormBase 23 , etc. Source identifiers are mapped onto a unique Entrez Gene ID list prior to analyses, as a significant number of bioinformatics knowledgebases underlying Metascape rely on Entrez Gene IDs as their primary keys. Deprecated Entrez Gene IDs are also recognized and replaced by successor IDs when encountered.<anchor xml:id="a20"/></p>
        <p><anchor xml:id="a21"/>Many gene annotation, pathway, and protein interaction databases are primarily compiled for human genes/proteins. For instance, the size of the mouse interactome encompasses only ~6% of the available human interactome 24 , even though many of these interactions are likely conserved across species. Therefore, it can be beneficial to cast gene candidates obtained in model organisms into their human orthologs prior to analysis. Ortholog mapping is a built-in feature and can be triggered by explicitly choosing the target analysis species (Supplementary Fig. 1 ), which will instruct subsequent analysis steps to use resources for that particular species.<anchor xml:id="a22"/></p>
        <p>Gene annotation</p>
        <p><anchor xml:id="a23"/>Detailed annotations for genes provide biological context to serve as important selection criteria when choosing candidates for follow-up studies. Metascape integrates annotation information from over 40 knowledgebases (Supplementary Figure 8 , Supplementary Data 2 ), encompassing gene descriptions, gene summaries, disease implications, genomic variants, subcellular localizations, tissue expression, the availability of chemical probes, etc. Express Analysis delivers nine descriptive fields by default, however, as illustrated in Supplementary Figure 3 , the Custom Analysis feature allows the user to append up to 47 columns of metadata to a gene annotation spreadsheet.<anchor xml:id="a24"/></p>
        <p>To assimilate this level of information using current tools, the experimentalist is required to first identify the appropriate knowledgebases that contain the required information. Since many of these portals do not incorporate gene list upload features for batch annotation, users must, in certain cases, search individual gene candidates one at a time. For example, it becomes an onerous undertaking to identify all extracellular proteins through UniProt 25 , or all chemical probes through DrugBank 26 , using a list with hundreds of gene candidates. Thus, Metascape’s automated gene annotation feature provides users with detailed annotation information not otherwise easily accessible, aiding in data interpretation of large-scale datasets and providing prioritization criteria for candidate genes.</p>
        <p>Membership search</p>
        <p><anchor xml:id="a25"/>The membership search feature in the Custom Analysis workflow allows users to apply specific query keywords, such as “infection” or “kinase”, against knowledgebase category term names and description fields, then review and select those matched terms that most accurately describe the process of interest (Supplementary Figure 4 ). Metascape will then dynamically construct a column of binary flags indicating whether each gene in the input gene list is a member of the matched ontology terms. This allows the user to identify genes with specific functions or features, and reduces the reliance on existing hierarchical ontologies during data interpretation. For example, Metascape offers two approaches to identify transmembrane proteins candidates. First, there are pre-integrated transmembrane predictions provided by Ensembl 27 or UniProt that are extractable through the gene annotation feature as described above. An alternative is to use the Membership tools to search the keyword “transmembrane” within the GO Cellular Component catalog to identify member genes. Although these two approaches are complementary in this specific example, membership search becomes critical when metadata is not readily available through pre-integrated data sources. For instance, highlighting known infection-related genes for an influenza study cannot be accomplished via standard gene annotation. Despite the fact that this knowledge is embedded in the ontology databases, it has not been explicitly compiled in most annotation resources and, thus, is not readily accessible to experimentalists. The binary result data from membership searches can also be visualized within nested pie charts (Supplementary Figure 9 ).<anchor xml:id="a26"/></p>
        <p>Enrichment clustering</p>
        <p><anchor xml:id="a27"/>Enrichment analysis comprises the core of most existing gene annotation portals. During enrichment analysis, the input gene list is compared to thousands of gene sets defined by their involvement in specific biological processes, protein localization, enzymatic function, pathway membership, or other features. Gene sets whose members are significantly overrepresented in the input gene list are reported to users to serve as putative biological insights into their study. A neglected problem in most current analyses is that redundancies in descriptors and ontologies can often complicate interpretation of the output. For example, ontology terms found in GO form a hierarchical structure of increasing granularity, making the terms inherently redundant. Terms across different ontology sources, such as GO, KEGG, and MSigDB 19 , etc. can be closely related as well. As a result, functional enrichment analysis can identify overlapping or related terms, making it difficult to extract non-redundant and representative processes to report in the analysis output. This problem is demonstrated in examples from other analysis portals using the Brass list (Fig. 2a, b ), which report the enrichment of dozens of highly-related categories. During post-processing of data generated through the Metascape analysis, Kappa similarities 28 among all pairs of enriched terms are computed and used to first hierarchically cluster terms into a tree then cast subtrees into clusters of similar terms (see Methods). By absorbing most redundancies into representative clusters, enrichment clustering eliminates confounding data interpretation issues that can arise from the reporting of multiple ontologies.<anchor xml:id="a28"/></p>
        <p>Visualizations of functional enrichment and interactome analysis results. a Screenshot of a portion of the directed acyclic graph rendered by Babelomics 53 based on enriched GO terms. b Screenshot of a portion of the gene-term association matrix rendered by g:profile 42 , where enriched GO terms are organized hierarchically. c Screenshot of a portion of the tabular display of enriched terms rendered by DAVID based on all GO terms, KEGG pathways, Reactome, and CORUM. The terms related to “viral gene expression” were missed in the visualizations generated by Babelomics and g:profile, but were identified by DAVID (in cluster 8 with ranks around 20). d Metascape bar graph for viewing top non-redundant enrichment clusters, one per cluster, using a discrete color scale to represent statistical significance. e Metascape enrichment network visualization showing the intra-cluster and inter-cluster similarities of enriched terms, up to ten terms per cluster. Cluster annotations are shown in color code. f A complex interactome network generated by g:profile with the Brass gene list. g Metascape visualization of the interactome network formed by all 121 gene candidates from the Brass list, where the MCODE complexes are colored according to their identities. h Seven MCODE complexes automatically identified in Metascape, colored by their identities. Their functional labels are generated based on the top-three functional enriched terms, if available</p>
        <p><anchor xml:id="a29"/>In comparison with Fig. 2a–c, d shows the Metascape enrichment analysis results of the Brass list, where bars are discretely colored to encode p -values of increasing statistical significance. The bar graph representation nevertheless does not capture inter-cluster similarities and intra-cluster redundancies. To address this, we have implemented a visualization approach called enrichment networks. As shown in Fig. 2e , enrichment networks are created by representing each enriched term as a node and connecting pairs of nodes with Kappa similarities above 0.3, forming a network that can be depicted using Cytoscape 29 . Nodes can be colored to reflect either their statistical p -values or cluster memberships. Redundant terms within a cluster naturally drive the formation of tight local complexes due to their high intra-cluster similarities, while clusters are occasionally bridged through terms with similarities reflecting the relatedness of two separate processes.<anchor xml:id="a30"/></p>
        <p><anchor xml:id="a31"/>Although Metascape introduces the above features to facilitate the interpretation of enrichment analysis results, it is not designed to supersede existing functional enrichment analysis portals. For users solely conducting enrichment analysis for a single gene-list, some existing tools, such as Enrichr 30 and ToppFunc 31 , contain additional gene signature collections and they remain a powerful approach to enrichment analysis.<anchor xml:id="a32"/></p>
        <p>Protein network analysis</p>
        <p><anchor xml:id="a33"/>Analyzing gene lists in the context of protein interactions can help illuminate biochemical complexes or signal transduction components that govern biological outputs 32 . However, a typical gene list of a few hundred human proteins can form highly complicated network layouts, making interpretation difficult. This is readily exemplified by the network output of other analysis portals using the Brass list (Fig. 2f ). These are colloquially referred to as hairball networks. Although such large networks are generally statistically significant, they do not yield directly actionable insights unless the experimentalist has specific expectations of the data. To infer more biologically interpretable results, Metascape applies a mature complex identification algorithm called MCODE 33 to automatically extract protein complexes embedded in the large network. Taking advantage of Metascape’s functional enrichment analysis capability, the three most significantly enriched ontology terms are combined to annotate putative biological roles for each MCODE complex. As shown in the example, Metascape results are relatively simple to visualize and interpret (Fig. 2g, h ).<anchor xml:id="a34"/></p>
        <p>Multi-gene-list meta-analysis</p>
        <p><anchor xml:id="a35"/>The proliferation and general adaptation of orthogonal OMICs platforms, including proteomics, genomics, functional genetic screens, and metabolomics, has made the meta-analysis of multiple gene lists a critical and largely unaddressed need. Routine comparative approaches include the use of Venn diagrams to identify hits that are common or unique to certain gene lists. We, and others, have previously reported that an overlap between OMICs datasets is more readily apparent at the level of pathways or protein complexes 9 , 34 , 35 , which can be considerably more challenging to implement without extensive computational expertise.<anchor xml:id="a36"/></p>
        <p><anchor xml:id="a37"/>Metascape has been designed to allow cross comparison of an arbitrary number of gene lists across both gene identities and ontologies. Specifically, upon the submission of multiple gene lists, all candidates are merged into one list, while encoding the original lists as additional binary membership columns (Supplementary Fig. 10 ). This pivoted layout greatly simplifies the representation of analysis results, as both gene annotation and membership search can be applied to the combined list the same way as in a single gene list input. Using a single output spreadsheet to incorporate evidence collected from each gene list thus enables efficient global gene filtering and prioritization. The overlap among the gene lists is visualized using a Circos plot 36 (Supplementary Fig. 11 ), which is a more intuitive and scalable representation compared to a Venn diagram.<anchor xml:id="a38"/></p>
        <p><anchor xml:id="a39"/>To facilitate the understanding of pathways (and pathway clusters) that are shared between, or selectively ascribed to, specific gene lists, additional visualizations were developed for Metascape. First, Metascape depicts top enriched clusters and their enrichment patterns across multiple gene lists as a clustered heatmap (Fig. 3a ). The heatmap is complemented by an enrichment network where each network node is represented by a pie chart, where the sector size is proportional to the number of genes originated from each gene list (Fig. 3b ). This representation is designed to be a biologically intuitive illustration of selective or shared pathway clusters. Importantly, this approach can also be applied to visualize protein–protein interaction networks to enable the elucidation of common/selective complex components enriched across OMICs datasets (Fig. 3c , Supplementary Fig. 12 ).<anchor xml:id="a40"/></p>
        <p>Visualizations of meta-analysis results based on multiple gene lists. a Heatmap showing the top enrichment clusters, one row per cluster, using a discrete color scale to represent statistical significance. Gray color indicates a lack of significance. The category GO:0016032 (viral process) is common to all studies, while GO:0046777 (protein autophosphorylation) is enriched exclusively in a single study, and is therefore likely a process associated with one particular experimental system. b Enrichment network visualization for results from the three gene lists, where nodes are represented by pie charts indicating their associations with each input study. Cluster labels were added manually. Color code represents the identities of gene lists. The network shows that processes such as viral gene expression, nucleocytoplasmic transport, and cellular response to external stimuli are generally shared among all three lists. RNA metabolism is shared between the Brass and Karlas lists; cellular development processes are mostly shared between the Karlas and Konig lists. c Selected MCODE components identified from the combined list of 541 genes, where each node represents a protein with a pie chart encoding its origin. The complex related to viral process is shared among all three lists, while the complex related to the MAP kinase cascade is specific to the Konig list. Supplementary Figure 12 presents all MCODE components identified</p>
        <p>Maintaining updated data sources</p>
        <p><anchor xml:id="a41"/>Metascape integrates over 40 knowledgebases (Supplementary Fig. 8 ) to support comprehensive analyses over ten highly studied organisms. Over time, some underlying data sources may adopt new access mechanisms, rename file packages, or be impacted by modifications to cross-referenced databases. Even if each data source is 99% robust, a system relying on 40 independent sources can only be 67% reliable. As the result of this compound effect, unexpected changes are encountered during data synchronization processes at frequencies significant enough to hinder attempts to automate content updates, which eventually results in outdated portals. DAVID 6 , a heavily utilized annotation tool accounting for over 80% of all functional enrichment portal usage, was not updated between 2010 and 2016, and then again not since 2016 12 . Our latest analyses on DAVID indicated 4–10% of the input gene candidates (varied by identifier types) are not recognized. Further analysis of the human GO archive data indicated 44% of annotation records have been added or modified since its last update. This is in agreement with a semantic similarity measure suggesting that 20% of genes change their functional identity over a two-year period 37 . Along with other outdated portals, it was estimated that thousands of studies were affected, and the potential impact on follow-up studies could last for years to come 7 .<anchor xml:id="a42"/></p>
        <p><anchor xml:id="a43"/>Metascape has adopted a novel two-phase approach to overcome this critical issue and ensure monthly updates (Fig. 4 ). In the first phase, individual data sources are automatically crawled, wrangled, and assembled according to a predefined topological order of dependency, where gene identifier resources are processed before dependent annotation resources. When significant changes or unexpected errors occur while processing a data source, a database’s last known compatible copy from a previous update is reused, and an internal alert is issued to Metascape quality control (QC) developers (see below). Using this strategy, conflicts in any given database component will not stop the timely completion of the Metascape update cycle. It is important to note that more subtle inconsistencies in data content can be harder to detect and may not trigger these exceptions. For example, the accidental deletion of records for a certain model organism in NCBI 38 may go undetected. The Metascape pipeline automatically carries out a detailed comparison between the current database and the new updated database, summarizing count differences into a bar graph web report, indicating the number of data records that are added or removed as illustrated in Fig. 4 . In the second phase, a Metascape QC member inspects the graphical report for suspicious changes in record counts. If no concerning issues are identified, the release candidate is approved, and the database update goes to production. Alerts received during the whole process are manually examined and addressed in parallel. Taken together, this workflow ensures that Metascape users are not adversely impacted by outdated data sources.<anchor xml:id="a44"/></p>
        <p>Schematic diagram of the semi-automatic data synchronization workflow</p>
        <p>Usage and citation analysis</p>
        <p><anchor xml:id="a45"/>Metascape has been in development since 2014, and a beta version of the software was initially released in late 2015. The portal usage data, as well as feedback from users, have been decisive in correcting or refining underlying concepts that drove the architectural design and features of Metascape. Some usage statistics are particularly enlightening. Among all recently recorded analysis sessions, ~78% users chose Express Analysis over Custom Analysis, implying that Express Analysis successfully captures a set of core algorithms and settings suitable for the majority of analysis needs. Six percent of analyses contained more than one gene list, indicating a demand for meta-analysis in the current research landscape. Data collected on input identifier types indicates gene symbol and synonyms are the most widely used (77%), followed by Ensembl identifiers (11%), Entrez Gene ID (4%), and RefSeq (3%). The remaining IDs are mostly UniProt IDs and model-organism-specific IDs. Microarray IDs are hardly used (&lt;0.2%), likely reflecting the shift of the gene expression technology platform from microarrays to next-generation sequencing. About 63% of analyses were performed using human identifiers, followed by 31% using mouse. Other model organisms such as D. rerio, R. norvegicus, A. thalianai , etc. accounted for the remainder. Interestingly, 3% usage took advantage of the ortholog mapping feature to mostly cast mouse/rat gene lists into human context for analysis. These data validate a need to support multiple gene/protein identifiers and multiple model organisms.<anchor xml:id="a46"/></p>
        <p><anchor xml:id="a47"/>At the time of writing, our citation survey using Google Scholar identified 62% of the citations have adopted Metascape graphical outputs directly in publications (Supplementary Data 5 ), underscoring the utility of tools that generate high-quality data visualizations (Fig. 5a ). The top three most used visualizations are the enrichment bar graph, enrichment network, and enrichment heatmap, highlighting the utility of the tool for functional enrichment analyses (Fig. 5b ). In addition to graphical outputs, Metascape analysis generates two Excel spreadsheets providing gene annotation and functional enrichment results (Supplementary Data 3 , 4 , Supplementary Figure 7 ). These data outputs have been directly used in over 16% of publications as supplementary materials to support analysis conclusions (Supplementary Data 5 ). Since Circos plots and enrichment heatmaps are two visualization tools specifically designed for multiple gene lists only, and a bar graph is only used for a single gene list, we estimated that 70% of the published studies studied a single gene list and 30% studied multiple gene lists. This finding, together with our web portal usage data, highlight the increasing usage of multi-OMICs approaches in current studies, and suggest that meta-analysis has become an important tool for the analysis of OMICs datasets.<anchor xml:id="a48"/></p>
        <p>Citation statistics illustrating the use of Metascape visualizations in publications. a 62% of publications adopted visualizations prepared by Metascape. b Visualization types sorted according to their popularity, where the enrichment bar graph, network, and heatmap are frequently used to summarize functional enrichment outputs</p>
        <p>Discussion</p>
        <p><anchor xml:id="a49"/>The systematic categorization of genes by their functions by the Gene Ontology Consortium (GO) has initiated the widespread practice of functional enrichment analysis; many portals have been developed over the years and have led to the continual refinement of gene list analysis algorithms 39 – 41 . Metascape was not developed to replace existing specialized tools, but to provide a pipeline to assimilate many of the powerful features of these analysis platforms to enable integrative, end-to-end analysis of OMICs-level datasets.<anchor xml:id="a50"/></p>
        <p><anchor xml:id="a51"/>Our study of 25 existing analysis portals found that the underlying databases were often out-of-date (Supplementary Data 1 ). Although portals such as g:profile 42 , PANTHER 43 , TopFun 31 , InterMine 44 , GoEast 45 , and GeneTrail2 46 provide up-to-date knowledgebases, a significant portion of portals (60%) relied on knowledgebases older than one year (Supplementary Data 1 ). Due to the inclusion of over 40 unique data sources in Metascape, a fully automated synchronization pipeline becomes unstable due to changes in the underlying resources. This motivated us to develop a workflow that combines an automated robot crawling phase with a supervised human review phase (Fig. 4 ). This data-engineering solution has demonstrated success through our monthly data refresh cycles, providing a viable data synchronization model for complex portals facing similar challenges.<anchor xml:id="a52"/></p>
        <p><anchor xml:id="a53"/>In addition to regular database updates, gene annotation and membership search are two features that are not readily addressed by existing portals (Supplementary Data 1 ). Although the term gene annotation is occasionally used by existing portals as a synonym for enrichment analysis 44 , 47 , 48 , here we consider gene annotation as a method to extract a diverse set of metadata, such as identifying extracellular proteins or associated chemical probes, for hundreds to thousands of gene candidates at once. Membership search is a closely related yet complementary service that dynamically highlights genes known to be involved in specific biology, such as host-pathogen interactions. Typically, retrieving these metadata requires querying specific portals, often one gene at a time, and compiling outputs into a centralized format for analysis. Metascape enables the batch extraction of contents from over 40 databases in an extremely efficient manner (Supplementary Figures 3 – 4 ).<anchor xml:id="a54"/></p>
        <p><anchor xml:id="a55"/>Analyzing multiple gene lists simultaneously through robust meta-analysis is another unmet need in the current OMICs data analysis landscape (Supplementary Data 1 ). Evaluated portals provide no, or only limited, support for this activity. For example, GoEast 45 and agriGO 49 provide some meta-analysis functions using a two-step process, where users analyze gene lists individually first, then reupload their enrichment results for cross comparison. However, GoEast analyzes a maximum of three lists and agriGO only supports organisms of agricultural relevance. GeneCodis 50 supports a maximum of two lists. GoMiner 51 can compute enrichment terms for multiple lists in parallel, however, the separate outputs are not further integrated and cross compared. g:Cocoa, a component in g:profile, compiles a tabular output conceptually similar to Metascape’s enrichment heatmap. However, it currently lacks an enrichment clustering feature and does not support interactome meta-analysis (Fig. 2b ). Metascape’s architecture is designed to support a seamless user experience towards the analysis and visualization of an arbitrary number of gene lists, only limited by available computing time and memory space.<anchor xml:id="a56"/></p>
        <p>The integration of Circos plots overcomes the limitation of Venn diagrams to graphically visualize the overlaps among many lists (Supplementary Figure 11 ), and enrichment heatmaps (Fig. 3a ) are applicable to the number of lists encountered in practice (Fig. 3a ). Metascape also builds on previous implementations of enrichment network maps 52 by depicting enriched terms as pie charts, which more readily indicate common and selective pathways enriched across multiple gene lists (Fig. 3b ).</p>
        <p><anchor xml:id="a57"/>While interactome analysis is implemented in Babelomics 53 , Intermine 44 , and ConsensusPathDB 54 , Metascape’s interactome analysis is distinguished by two notable features. First, in addition to the BioGrid knowledgebase, Metascape integrates the more recent human interactome datasets InWeb_IM 55 and OmniPath 56 , resulting in a tripling of human interactome coverage (Supplementary Figure 13 ). Second, Metascape automatically extracts protein complexes and annotates their respective functions (Fig. 2h , Supplementary Figure 12 ). Compared to existing visualization approaches (Fig. 2f ), Metascape is designed to highlight dense interactome neighborhoods and facilitate the interpretation of interactome data in a biological context; it further integrates with Cytoscape 29 to leverage its rich set of visualization and interactive features.<anchor xml:id="a58"/></p>
        <p><anchor xml:id="a59"/>Critically, Metascape was designed to provide more interpretable and actionable results for experimentalists. The redundancy among ontology terms presents a significant obstacle in result interpretation. The primary strategy adopted by existing portals, as seen in g:Profiler 42 , WebGestalt 8 , Babelomics 53 , and others, is to utilize directed acyclic graph (DAG) or tree structures embedded within ontologies such as GO 16 (examples in Fig. 2a, b ). WebGestalt provides an option only using a subset such as GOSlim 16 to reduce redundancy. However, these strategies are not applicable to reduce redundancies across different ontology sources. Metascape and DAVID 6 , by contrast, adopt a dynamic clustering solution that avoids the above-mentioned shortcomings. Metascape further simplifies the result presentation via bar graph (Fig. 2d ) and heatmap (Fig. 3a ) visualizations, compared to DAVID’s tabular presentation (Fig. 2c ). Although p -value is used as the default representation metric for ranking enriched terms, it nevertheless has its limitations. Users may need to consider using alternative metrics, such as the multi-test corrected q -value or the biological context-sensitive enrichment factor. All popular enrichment metrics, including detailed gene counts, are computed and made available for offline analyses. Metascape further enhances the interpretability of analysis results through advanced graphical and spreadsheet outputs, a concise PowerPoint presentation (Supplementary Figure 7 ), and a journal-style web-based Analysis Report containing additional method descriptions and references (Supplementary Figure 7 ). Offline analysis is facilitated by a Zip export containing third-party compatible data files, such as the Cytoscape 29 and JTreeView 57 formats.<anchor xml:id="a60"/></p>
        <p><anchor xml:id="a61"/>In conclusion, Metascape has been designed for experimentalists (bench biologists) to apply powerful computational analysis pipelines to analyze and interpret large-scale datasets. To ensure that its content is kept current, a new knowledgebase synchronization pipeline was engineered. To address gaps in current analysis tools, Metascape introduces a workflow integrating gene annotation, membership analysis, and multi-gene-list meta-analysis capabilities. Its rich set of analysis tools are accessible through a convenient one-click Express Analysis interface and results are communicated via an article-like analysis report. We expect that the wider adoption of Metascape will significantly enhance biological interpretation of OMICs studies by enabling experimentalists to directly analyze their data to identify novel therapeutic targets, mechanisms of action, or molecular insight into disease. Metascape is an open-access resource available at http://metascape.org .<anchor xml:id="a62"/></p>
        <p>Methods</p>
        <p>Architecture and data source</p>
        <p><anchor xml:id="a63"/>Metascape is a web resource compatible with all major browsers. The backend knowledgebase is a relational database managed by MySQL. The front-end user interface is implemented by Angular JavaScript framework to provide a rich interactive user experience. The server-side computational logic is mostly implemented in Python and leverages several packages provided by the community ( https://pypi.org ). Each analysis request is associated with a randomly-generated unique session ID (Supplementary Figure 2 ), which can be used to access analysis results interactively through the web or to download all result data in a Zip package for offline use, before the data is removed from the server (Supplementary Figure 7 ).<anchor xml:id="a64"/></p>
        <p>The rich analyses of Metascape sit on top of over 40 bioinformatics knowledgebases maintained by the scientific community (Supplementary Figure 8 , Supplementary Data 2 ). A data synchronization pipeline, as described in Fig. 4 , is applied monthly to process data into an Entrez Gene ID-centric relational data format. Metascape currently supports ten organisms: H. sapiens , M. musculus , R. norvegicus , D. rerio , D. melanogaster , C. elegans , S. cerevisiae , A. thaliana , S. Pombe , and P. falciparum .</p>
        <p>Functional enrichment analysis</p>
        <p><anchor xml:id="a65"/>Metascape utilizes the well-adopted hypergeometric test 58 and Benjamini-Hochberg p -value correction algorithm 59 to identify all ontology terms that contain a statistically greater number of genes in common with an input list than expected by chance. By default, Metascape pathway enrichment analysis makes use of Gene Ontology 16 , KEGG 17 , Reactome 18 , MSigDB 19 , etc. Distinguishing it from many existing portals, Metascape automatically clusters enriched terms into non-redundant groups, where it implements similar logic as found in DAVID 6 . Briefly, pairwise similarities between any two enriched terms are computed based on a Kappa-test score 28 . The similarity matrix is then hierarchically clustered and a 0.3 similarity threshold is applied to trim the resultant tree into separate clusters. Metascape chooses the most significant (lowest p -value) term within each cluster (Supplementary Data 4 ) to represent the cluster in bar graph and heatmap representations. The analysis provides other popular enrichment metrics in addition to p -values.<anchor xml:id="a66"/></p>
        <p>Interactome analysis</p>
        <p><anchor xml:id="a67"/>Metascape utilizes physical protein–protein interactions captured in BioGrid 24 as the main data source. In addition, it integrates more recent human interactome datasets including InWeb_IM 55 and OmniPath 56 to provide additional interactome coverage (Supplementary Figure 13 ). Given a list of proteins, it first automatically extracts a protein interaction network formed by these candidates. Then for each connected network component, it iteratively applies the MCODE algorithm 33 , with modifications for performance improvements, to identify densely-connected complexes. For each complex, it further applies function enrichment analysis and uses the top three enriched terms for the annotation of its biological roles (Fig. 2h , Supplementary Figure 12 ). All network visualizations are generated with Cytoscape 29 and exported in multiple formats.<anchor xml:id="a68"/></p>
        <p>Datasets</p>
        <p>Previously published host factors that regulate influenza replication were used as example gene lists in this study. The 121 host factors identified by Brass et al. 13 were used as a single gene list input for all portals studied in Supplementary Data 1 and Fig. 2 . To demonstrate meta-analysis capabilities, three influenza gene lists were used as the input, including 121 host factors from Brass et al. 13 , 168 from Karlas et al. 14 , and 294 from Konig et al. 15 . All gene lists were downloaded from the IAV database 9 .</p>
        <p>User interface</p>
        <p>Supplementary Figures 1 – 7 describe the Metascape user interface step-by-step for gene-list analyses using the above-mentioned datasets. Screenshots specific to the single gene list analysis are outlined in orange; those specific to the multiple gene list meta-analysis are outlined in green; common screenshot components are outlined in gray. During the Express Analysis, the submission of gene list(s) (Supplementary Figure 1 ) directly leads to an analysis report (Supplementary Figure 7 ) without the need to step through the intermediate operations (Supplementary Figures 2 – 6 ). Conversely, the detailed analysis interface (Supplementary Figures 2 – 6 ) is only accessible through Custom Analysis.</p>
        <p>Usage statistics</p>
        <p><anchor xml:id="a69"/>To avoid statistics bias due to new users, who tested and learned Metascape using either example gene lists provided on the portal site or users’ own lists, all analysis sessions associated with an exact same input gene-list group were considered duplicates, regardless of users’ IP address and the time of submission. With such duplicates being removed first, statistics on web site analysis pattern were compiled based on over 70,000 most recent sessions by the time of writing. The relative percentage usage of Metascape visualizations and spreadsheets are derived based on a total of 241 publications (2016-current), implying a maximum standard deviation of 3% in the estimations.<anchor xml:id="a70"/></p>
        <p>Supplementary information</p>
        <p>Supplementary Information</p>
        <p>Description of Additional Supplementary Files</p>
        <p>Supplementary Data 1</p>
        <p>Supplementary Data 2</p>
        <p>Supplementary Data 3</p>
        <p>Supplementary Data 4</p>
        <p>Supplementary Data 5</p>
        <p>Acknowledgements</p>
        <p>M.C., L.P., C.B. and S.C. acknowledge support by NIH grants U19 AI106754, U19 AI135972, and R01 DA033773.</p>
        <p>Author contributions</p>
        <p>Y.Z., B.Z., M.C., L.P., A.H.K, O.T. implemented the Metascape web portal; Y.Z. and S.K.C. managed project; Y.Z. and B.Z. analyzed usage data; Y.Z., C.B. and S.K.C. wrote the manuscript.</p>
        <p>Data availability</p>
        <p>Gene lists referenced in this study are available in Supplementary Data 3 .</p>
        <p>Code availability</p>
        <p>Custom code used in this study is available from the corresponding authors upon reasonable request.</p>
        <p>Competing interests</p>
        <p>The authors declare no competing interests.</p>
        <p>Footnotes</p>
        <p>Contributor Information</p>
        <p>Yingyao Zhou, Email: yzhou@gnf.org.</p>
        <p>Sumit K. Chanda, Email: schanda@sbpdiscovery.org</p>
        <p>Supplementary information</p>
        <p>Supplementary Information accompanies this paper at 10.1038/s41467-019-09234-6.</p>
        <p>References</p>
        <p>Associated Data</p>
        <p>Supplementary Materials</p>
        <p>Supplementary Information</p>
        <p>Description of Additional Supplementary Files</p>
        <p>Supplementary Data 1</p>
        <p>Supplementary Data 2</p>
        <p>Supplementary Data 3</p>
        <p>Supplementary Data 4</p>
        <p>Supplementary Data 5</p>
        <p>Data Availability Statement</p>
        <p>Gene lists referenced in this study are available in Supplementary Data 3 .</p>
        <p>Custom code used in this study is available from the corresponding authors upon reasonable request.<anchor xml:id="a71"/></p>
    </body>
  </text>
</TEI>
