The Untargeted Metabolomics Workflow

During the past 2 years, the methodology that I have employed to make metabolite identifications using an untargeted metabolomics workflow has evolved. In 2008, not only were metabolite databases smaller, but they also did not have some of the advanced functionality that is available today. For example, searching for sodium and potassium adducts required manually calculating masses from the observed m/z values. We have come a long way with improvements in both metabolomics software and databases facilitating metabolite identification. Major databases emerging as the key players for untargeted studies are HMDB, Lipid Maps, and METLIN. Each, in my opinion, have their own advantages. I would like to start this blog by surveying which databases metabolomics investigators utilize the most frequently and why. HMDB, for example, provides so-called MetaboCards in which fundamental biological facts are introduced for queried molecules. This information can be particularly useful in filtering putative hits for metabolites that may not be relevant to the sample type being analyzed, such as a hit for a plant metabolite from bacterial cell results. Another new function that has been recently incorporated into METLIN is the ability to search fragment ions from MS/MS data. With this function, it is now possible to do MS/MS on all features of interest in a dataset prior to querying databases to potentially reduce false-negative hits. A few years ago, the workflow of identifying metabolites in a global MS-based study offered little room for creativity. I am certain today, however, that investigators are taking advantage of the various new database functionality in a multitude of innovative ways. I hope that by discussing and exchanging ideas about our untargeted workflows we can learn new ways to facilitate what I still would classify as the rate-limiting step in metabolomics, metabolite identification. So what process do you use to make metabolite identifications? How do you prioritize your feature lists? Do you search all the databases on the web, or do you refine yourself to an in-house library? I look forward to reading about your different points of view!