Tip #20: Stop Words within Phrases in Ovid

By

 This week's tip is brought to us by Ursula Ellis from the University of British Columbia. She credits her colleague Mathew Vis-Dunbar for coming up with this solution! Thanks to you both!

"If you search for an exact phrase which contains a stopword in Ovid, the stopword will be ignored and other words will be searched in the order entered, within 2 words of each other. For instance, line 1 of this search finds "treatment and prevention," "treatment or prevention," etc, but not "prevention and treatment" which is found by line 2:

This is not ideal for many phrases in which the stopword is a critical piece of the search phrase.

There are two options to solve this issue in Ovid. One is to get in touch with your rep and ask them to turn off "runtime stopword processing," as described here: https://wkhealth.force.com/ovidsupport/s/article/Stopwords-and-phrase-searching-in-Ovid-databases

However, for large institutions, it is likely not feasible to have this option turned off long-term. A workaround for phrases involving one of these words:

and, as, for, from, is, of, that, the, this, to, was, were

...is to truncate the stopword:" 

 

Comments

  1. Layal HneinyJune 13, 2022 at 11:56 AM

    Nice!!!! thanks for sharing

    ReplyDelete
  2. elgraOctober 27, 2022 at 12:51 PM

    Last year, I asked Ovid support to turn off temporarily "runtime stopword processing". It was turned off, but actually, it didn't work, the results were the same than when it was on. They were never able to really turn off this option. I tested it, the person from Ovid tested it and we came to the same conclusion. Maybe it changed since then, but that was quite disappointing.

    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