Tip #47: Beta PubMed translation tool in Embase

By

 I grabbed the following announcement from Embase.com. It appears to be available in Beta now!


"The tool streamlines the process, saving time and reducing potential errors in query translation, making it a valuable resource for researchers and medical professionals looking to access the extensive and focused content available in Embase.

Key Features:

  • Seamless Transition: It offers a seamless and intuitive platform to effortlessly translate your PubMed queries into Embase queries. No need for manually reformatting your search strings; our tool does it for you.
  • MeSH to Emtree Mapping: Take advantage of our unique mapping feature that automatically converts MeSH terms to Emtree terms. This ensures that your search is as precise as possible, capturing a more extensive range of relevant literature in the Embase database.
  • Time-Saving: Save valuable time with our tool, which streamlines the search process. Quickly and accurately adapt your PubMed queries to the Embase database, allowing you to focus on what truly matters - your research.
  • Unparalleled Database Access: Gain access to Embase's vast database, renowned for its in-depth coverage of pharmacology, drug research, toxicology, and biomedical literature, among other areas.
  • User-Friendly Interface: Our tool features a user-friendly interface, designed with researchers in mind. Whether you're a experiences professional or a newcomer to Embase, you'll find the translation tool very easy to use."

Comments

  1. Andy HicknerJanuary 5, 2024 at 3:56 PM

    I would love to see Ovid develop something like this (we have Ovid for both MEDLINE and Embase). It will be interesting to see how reliable the controlled vocabulary mapping is once people start to kick the tires.

    ReplyDelete

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