{
  "version": "https://jsonfeed.org/version/1.1",
  "title": "chem-bla-ics",
  "description": "Chemblaics (pronounced chem-bla-ics) is the science that uses open science and computers to solve problems in chemistry, biochemistry and related fields.",
  "home_page_url": "https://chem-bla-ics.linkedchemistry.info/",
  "feed_url": "https://chem-bla-ics.linkedchemistry.info/2026/01/10/where-does-the-wikipathways-cited-in-information-come-from.json",
  "icon": "https://chem-bla-ics.linkedchemistry.info/assets/images/chem-bla-ics_logo.png",
  "language": "en",
  "authors": [
    {
      "name": "Egon Willighagen",
      "url": "https://orcid.org/0000-0001-7542-0286",
      "_orcid": "0000-0001-7542-0286"
    }
  ],
  "items": [

    {
      "id": "https://doi.org/10.59350/0xxqw-90533",
      "url": "https://chem-bla-ics.linkedchemistry.info/2026/01/10/where-does-the-wikipathways-cited-in-information-come-from.html",
      "title": "Where does the WikiPathways Cited In information come from?",
      "content_html": "<p>I have been wanting to blog about this since this summer, but with everything going on, I never really got around to it.\nWhat is this <em>Cited In</em> feature of <a href=\"https://wikipathways.org/\">WikiPathways</a> and where does that information come from?\nIf you have not noticed this yet, this is what it looks like for <a href=\"https://www.wikipathways.org/instance/WP4846\">WP4846</a>:</p>\n\n<p><img src=\"/assets/images/wp_cited_in.png\" alt=\"\" /></p>\n\n<p>Recently, I was close to writing up the context, because it is related to a new feature of the profile pages, where you\nnow can look up citations to pathways that you first authored (see\n<a href=\"https://chem-bla-ics.linkedchemistry.info/2025/11/30/wikipathways-curation-reports-on-profile-pages.html\">this post</a>).\nAnd it also relates to the data I have been collecting around <a href=\"https://chem-bla-ics.linkedchemistry.info/tag/cito\">citation intention annotations</a>:\narticles that cite one of the WikiPathways papers and mention a specific pathway, could be considered <em>cito:usesDataFrom</em>\n(see doi:<a href=\"https://doi.org/10.1186/s13321-023-00683-2\">10.1186/s13321-023-00683-2</a>).</p>\n\n<p>A third angle to citations to specific WikiPathways is the following. WikiPathways is used a lot in data analyses and\nputting experimental data in biological context. How researchers do this varies a lot, in multiple ways. But just\nthinking about this factually, research output cite specific biological pathways. And there are some interesting\nphenomena there. Back in 2015 at the Metabolomics Society meeting in San Francisco (apparently, I only\nblogged about the meeting only <a href=\"https://chem-bla-ics.blogspot.com/2015/06/metsoc2015-converting-smiles-annotation.html\">once</a>?),\nwhen I visited the 500+ posters looking for interesting biological pathways, there were a lot of studies\non different species, different diseases, different toxicities. The biological response had one thing in common:\nit always was the TCA cycle that was key (see doi:<a href=\"https://doi.org/10.1096/FJ.11-203091\">10.1096/FJ.11-203091</a> for\na 2012 comparison of TCA models).</p>\n\n<p>Thus, with so many articles mentioned specific pathways and deriving biological knowledge from this, what is\nreasonable to expect? Do we expect <em>co-citation</em> effects? That is, if two articles found the same set of pathways\nof interest to their data, is the data showing a similar biological response? Do we expect a similar thing\nlike the above TCA cycle in metabolomics, something similar to the notion of <em>frequent hitters</em> (see\ndoi:<a href=\"https://doi.org/10.1021/jm010934d\">10.1021/jm010934d</a>)?</p>\n\n<p>Of course, to test this hypothesis we need data and the <em>Cited In</em> feature comes in. At the time of\nwriting of this blog post, we can see on <a href=\"https://www.wikipathways.org/browse/citedin.html\">this page</a>\nthat 878 pathways have been cited a total of 2715 times. We are getting somewhere. This blog\npost will not analyze this data, which is one reason why I had not blogged about it. But from the\nabove you can understand that I want to :)</p>\n\n<h2 id=\"the-cited-in-feature\">The Cited In feature</h2>\n\n<p>This <em>Cited In</em> feature was introduced along with the new website (see doi:<a href=\"https://doi.org/10.1093/nar/gkad960\">10.1093/nar/gkad960</a>),\nwhere we change how GPML files are stored and how web pages are created from that.\nBecause we are no longer confined to the MediaWiki platform (which has served the project for very long,\nvery effectively), it is easier to integrate information from other sources. For example,\nfrom literature databases. This feature was developed by <a href=\"https://orcid.org/0000-0001-5706-2163\">Alex Pico</a>\nat the Gladstone Institutes (see <a href=\"https://github.com/wikipathways/wikipathways-database/commit/840234adfd581730d86553910c078401351606ce\">this 2022 commit</a>),\nwhere he uses the <a href=\"https://www.ncbi.nlm.nih.gov/books/NBK25497/\">NCBI eUtils API</a> to access\n<a href=\"https://pmc.ncbi.nlm.nih.gov/\">PubMed Central</a>.\nThe data is then collected into <a href=\"https://github.com/wikipathways/wikipathways-database/blob/main/downstream/citedin_lookup.yml\">this YAML file</a>\nwhich then gets used to generate webpage content (like the section in the above screenshot\nand the page mentioning the current statistics).</p>\n\n<h2 id=\"where-is-the-data-coming-from\">Where is the data coming from?</h2>\n\n<p>As just explained, originally the data was only coming from NCBI.\nHowever, because I found many articles citting specific pathways that were not picked up by this\napproach, and I wanted more data, so I started searching <a href=\"https://europepmc.org/\">Europe PMC</a> the European\npartner of PubMed Central. However, I am not automating this. I want to see the data, the articles, and\nhow people cite the pathways. I need to see that so that I can better understand how people are\nusing the data/knowledge from WikiPathways. I cannot keep up with checking why people are citing\nmy own research, but <a href=\"https://chem-bla-ics.linkedchemistry.info/2010/10/31/citeulike-cito-use-case-1-wordles.html\">I once was</a>.\nI learn(-ed) a lot from that.</p>\n\n<p>I normally use a search that requires the word “WikiPathways” to be\n<a href=\"https://europepmc.org/search?query=wikipathways\">mentioned in the article</a> (in most, but\nnot all of them; citing literature you extend sounds like a core scholarly value, but is factually\nnot systematically complied with), and then manually searching for “WP”. With close to 1000\nPubMed Central articles mentioning WikiPathways in 2025 and that these are mostly full texts,\nI can see if the cite specific pathways. A good number of article mentions the WikiPathways\nidentifier, e.g. the aforementioned <code class=\"language-plaintext highlighter-rouge\">WP4846</code>. If the article only mentions a pathway title,\nI cannot confidently identify which pathway is cited, so I exclude that.</p>\n\n<p>I originally started out manually editing the YAML file where the citations are collected,\nbut by now use <a href=\"https://github.com/wikipathways/wikipathways-database/blob/main/scripts/citedin_fromFile.R\">a script similar to Alex’ R script</a>.\nThis makes it far easier to scale up, as I just have to populate a three column TSV file,\nwhich is used by my R script to update the YAML file. This manual approach ensures that\nI am not looking at text mining results, but see the citation of the WikiPathways identifier\nwith my own eyes. That’s just how I like it.</p>\n\n<p>The full history of the YAML file content can be found on <a href=\"https://github.com/wikipathways/wikipathways-database/commits/main/downstream/citedin_lookup.yml\">this GitHub page</a>\nand <a href=\"https://github.com/wikipathways/wikipathways-database/blame/main/downstream/citedin_lookup.yml\">this <em>git blame</em></a>\ntells you if the information came from PubMed Central via the API, or was added by me:</p>\n\n<p><img src=\"/assets/images/wp_cited_in_git_blame.png\" alt=\"\" /></p>\n\n<p>This is Open Science in action: added transparency and making it easier for anyone to verify,\nso that no one needs to be stuck in (dis)trust.</p>\n\n<p>Of course, as we know from the CiTO ontology and real-world data, there are so\nmany different reasons why journal articles are cited (just <a href=\"https://chem-bla-ics.linkedchemistry.info/2024/08/07/cito-updates.html\">an example</a>),\nthe data in the YAML file and on the WikiPathways website in the <em>Cited In</em> feature\ndoes not have direct meaning. Just like a high citation count for an article or\neven a journal impact factor cannot be directly interpreted (despite so many researchers\njust blindly doing just that).</p>\n\n<h2 id=\"whats-next\">What’s next?</h2>\n\n<p>Well, while I did not do any analysis yet, and do not even know yet how much citations we need to\nreach some level of statistical significance, there are some observations I can mention:</p>\n\n<ul>\n  <li>if your analysis included anything like linking your data to pathways, citing those pathways is\na good way to give credit to the researchers that created that pathway</li>\n  <li>if you cite data, please cite that as accurately as possible, see e.g. DataCite</li>\n  <li>I wish all journal articles citing specific pathways from WikiPathways would include the pathway identifier</li>\n  <li>I congratulate those authors that even mentioned the revision of the pathway! well done!</li>\n</ul>\n\n<p>And about biological interpretation, our group has long published that some genes with\ndifferential data mapping to a pathway does not imply that that pathway is really affected.\nGene-set enrichment and over-representation analysis are a starting point; not a conclusion.\nI wish more people were more aware of the work in our (now)\n<a href=\"https://cris.maastrichtuniversity.nl/en/organisations/translational-genomics/\">Translational Genomics research group</a>.\nLike that of <a href=\"https://orcid.org/0000-0002-7699-8191\">Martina Kutmon</a> (now as\n<a href=\"https://www.maastrichtuniversity.nl/research/maastricht-centre-systems-biology-and-bioinformatics\">MaCSBio<sup>2</sup></a>),\nwhom I have had the pleasure of collaborating with for quite some years now (and long time\narchtect of WikiPathways).</p>\n\n<p>There is so much more I want to write up about WikiPathways, but I leave it to this\nfor now.</p>\n\n<h4>References</h4>\n<div class=\"csl-bib-body\">\n    <div class=\"csl-entry\">Agrawal, A., Balcı, H., Hanspers, K., Coort, S. L., Martens, M., Slenter, D. N., Ehrhart, F., Digles, D., Waagmeester, A., Wassink, I., Abbassi-Daloii, T., Lopes, E. N., Iyer, A., Acosta, J. M., Willighagen, L. G., Nishida, K., Riutta, A., Basaric, H., Evelo, C. T., … Pico, A. R. (2023). WikiPathways 2024: next generation pathway database. <i>Nucleic Acids Research</i>, <i>52</i>(D1), D679–D689. https://doi.org/10.1093/nar/gkad960 <a href=\"https://doi.org/10.1093/NAR/GKAD960\">CrossRef</a> <a href=\"https://qlever.scholia.wiki/doi/10.1093/NAR/GKAD960\">Scholia</a></div>\n    <div class=\"csl-entry\">Roche, O., Schneider, P., Zuegge, J., Guba, W., Kansy, M., Alanine, A., Bleicher, K., Danel, F., Gutknecht, E.-M., Rogers-Evans, M., Neidhart, W., Stalder, H., Dillon, M., Sjögren, E., Fotouhi, N., Gillespie, P., Goodnow, R., Harris, W., Jones, P., … Schneider, G. (2001). Development of a Virtual Screening Method for Identification of “Frequent Hitters” in Compound Libraries. <i>Journal of Medicinal Chemistry</i>, <i>45</i>(1), 137–142. https://doi.org/10.1021/jm010934d <b>[cito:obtainsBackgroundFrom]</b> <a href=\"https://doi.org/10.1021/jm010934d\">CrossRef</a> <a href=\"https://qlever.scholia.wiki/doi/10.1021/jm010934d\">Scholia</a></div>\n    <div class=\"csl-entry\">Stobbe, M. D., Houten, S. M., van Kampen, A. H. C., Wanders, R. J. A., &#38; Moerland, P. D. (2012). Improving the description of metabolic networks: the TCA cycle as example. <i>The FASEB Journal</i>, <i>26</i>(9), 3625–3636. https://doi.org/10.1096/fj.11-203091 <b>[cito:citesAsDataSource]</b> <a href=\"https://doi.org/10.1096/FJ.11-203091\">CrossRef</a> <a href=\"https://qlever.scholia.wiki/doi/10.1096/FJ.11-203091\">Scholia</a></div>\n    <div class=\"csl-entry\">Willighagen, E. (2023). Two years of explicit CiTO annotations. <i>Journal of Cheminformatics</i>, <i>15</i>(1). https://doi.org/10.1186/s13321-023-00683-2 <a href=\"https://doi.org/10.1186/S13321-023-00683-2\">CrossRef</a> <a href=\"https://qlever.scholia.wiki/doi/10.1186/S13321-023-00683-2\">Scholia</a></div>\n  </div>",
      "summary": "I have been wanting to blog about this since this summer, but with everything going on, I never really got around to it. What is this Cited In feature of WikiPathways and where does that information come from? If you have not noticed this yet, this is what it looks like for WP4846:",
      "image": "https://chem-bla-ics.linkedchemistry.info/assets/images/wp_cited_in.png",
      "date_published": "2026-01-10T00:00:00+00:00",
      "date_modified": "2026-01-10T00:00:00+00:00",
      "tags": ["wikipathways","europepmc"],
      "_references": [
        
          
          
            { "url": "https://doi.org/10.1186/S13321-023-00683-2", "doi": "10.1186/S13321-023-00683-2"
             }
            ,
          
        
          
          
            { "url": "https://doi.org/10.1096/FJ.11-203091", "doi": "10.1096/FJ.11-203091"
            , "cito":
              
              
                [ 
                  "citesAsDataSource"
                  
                 ]
              
             }
            ,
          
        
          
          
            { "url": "https://doi.org/10.1021/jm010934d", "doi": "10.1021/jm010934d"
            , "cito":
              
              
                [ 
                  "obtainsBackgroundFrom"
                  
                 ]
              
             }
            ,
          
        
          
          
            { "url": "https://doi.org/10.1093/NAR/GKAD960", "doi": "10.1093/NAR/GKAD960"
             }
            
          
        ],
      
      
      
      
      
      
        "authors": [ { "name": "Egon Willighagen", "url": "https://orcid.org/0000-0001-7542-0286" } ]
      
    }

  ]
}
