Tip #28: Exploding MeSH - PubMed vs. Ovid MEDLINE

By

 A few years ago I ran into a search quirk when translating a lengthy search from PubMed to Ovid MEDLINE. My Ovid results were significantly larger and it wasn't immediately obvious what was happening. After much testing and consulting with my colleagues (thanks, Mark MacEachern!), we finally pinned it down to a single MeSH term returning vastly different results between the two platforms. 


Ovid - exp Food/ 1,428,580 results

PubMed - "Food"[Mesh] 701,490 results

We figured out what was causing the difference, but there was nothing in the help documentation that explained why it was happening. Even though the searches appeared to be the same, both MeSH terms were exploded, the platforms appeared to be handling them differently. I had to reach out to Ovid to get an answer for my remaining question. Over the course of a few weeks and many emails, they were finally able to provide a clear explanation: Ovid was including “Drug Terms” in the explode, where PubMed was not doing this. Ovid included corresponding drug terms for: Food additives, Flavoring agents, Sweetening agents, Micronutrients, Trace elements and Vitamins.

Based on our interaction, the Ovid Database guide was updated to includes this explanation (https://ospguides.ovid.com/OSPguides/medline.htm#tools):

"Note about Pharmacological Actions and MeSH tree for Ovid MEDLINE:

Unlike PubMed, Ovid MEDLINE only has 1 hierarchical tree. Therefore the Pharmacological Actions are included in the Ovid MEDLINE tree display as "[Drug Terms (Non MeSH)]". Secondly the "explode function" on Ovid automatically includes Pharmacological Actions when applicable.

Example: exp air pollutants/

  • Includes all MeSH terms for Air Pollutants: Air Pollutants/, "Air Pollutants, Occupational"/, "Air Pollutants, Radioactive"/, "Greenhouse Gases"

  • Includes all Pharmacologic Actions MeSH terms: Gasoline/, Hydrogen Sulfide/, Particulate Matter/, Radon/, Sulfur Dioxide/, Vehicle Emissions

  • Does not include the Supplementary Concept terms for Air Pollutants: 1,6-hexamethylene diisocyanate, 2-nitrofluoranthene, 2-nitrofluorene, bisphenol A, methyl tert-butyl ether, silicon nitride."

Moral of the story: Make sure to confirm how a platform or database executes hierarchical explosions when translating a search!

 

 

Comments

Post a Comment

Popular posts from this blog

Tip #1: Bulk export from Google Scholar

By
Image
This post was updated on October 10, 2022 with new instructions for #3 under "For EndNote users..." For years, I kept hearing from colleagues that I should be searching Google Scholar as part of my systematic review projects. I didn't, for 3 reasons: I didn't know GS' search syntax GS notoriously does not allow bulk export to reference managers I didn't have a sense of how many results I should export.   Last fall, I finally said enough was enough and it was time to learn how to wrangle this beast. It turns out that there is now a third-party tool that facilitates bulk export from Google Scholar, Harzing's Publish or Perish . Here's how you get started: Download PoP for free Paste your query into the Keywords field Set your maximum number of results. I follow the guidelines on p. 135 of Wichor Bramer's dissertation , which is a great handbook for expert searching. Bramer suggests the first 200 results, or 100 if you are getting low numbers of res
Read more

Tip #23: PubMed's [tiab] vs. [tw]

By
Image
Search field tags are a quick way to specify the exact fields you would like to search when using keywords. For example, I can tell PubMed to search for my term only in the title field or only in the MeSH Terms field. You can view a list of available search fields from the drop down menu in PubMed's Advanced Search Builder. Specifying field tags for keywords is also a good practice in PubMed because keywords searched without field tags will be translated through Automatic Term Mapping which may reduce the precision of your results. Here are a few sample searches in my search history, including #4 which wasn't limited to a field (notice how it was translated in the expanded search details): The fields that are included in the [title/abstract] fields are pretty self-explanatory (words and numbers included in a citation's title, collection title, abstract, other abstract and author keywords), but what is actually included in the [Text Word] (can also be searched as [tw]) fi
Read more

Tip #4: Ovid MEDLINE Adjacency and Field Tags

By
Image
This tip was submitted by Kathryn Vanderboll (University of Michigan):  In Ovid MEDLINE, using adjacency with .kw. does not work the way you (probably) want - use .kf. instead! While searching (surg* adj (educat* or instruct* or learn* or teach* or train*)).kw., our team couldn't figure out why our sentinel article tagged with with the author supplied keyword "surgical teaching" wasn't showing up. Through trial and error, we learned that .kw. adjacency only works between lines . That is, how close keywords are to each other on different lines. For example, (surg* adj teach*).kw. picks up articles with keyword headings like:  But does NOT pick up articles that might have keyword headings like:   To use adjacency searching within a single keyword heading, you'll need to use .kf. The Ovid help documentation notes : "The Keyword Heading (KW) field contains the Keyword Headings assigned by authors. Keyword Headings are the author keywords. To retrieve every Key
Read more