455 lines
34 KiB
HTML
455 lines
34 KiB
HTML
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
|
|
|
|
<head>
|
|
<meta http-equiv="X-UA-Compatible" content="IE=edge">
|
|
<meta name="twitter:card" content="summary_large_image">
|
|
<meta name="twitter:site" content="@NLM_NIH">
|
|
<meta name="twitter:title" content="MLA 2006: Questions and Answers. NLM Technical Bulletin. 2006 Jul–Aug">
|
|
<meta name="twitter:description" content=" The NLM Technical Bulletin is your source to stay informed about NLM products and services.">
|
|
<meta name="twitter:image" content="https://www.nlm.nih.gov/pubs/techbull/images/nlm_tech_bulletin_graphic_twitter.jpg">
|
|
<meta property="og:url" content="https://www.nlm.nih.gov/pubs/techbull/tb.html" />
|
|
<meta property="og:type" content="article" />
|
|
<meta property="og:title" content="MLA 2006: Questions and Answers. NLM Technical Bulletin. 2006 Jul–Aug" />
|
|
<meta property="og:description" content="The NLM Technical Bulletin is your source to stay informed about NLM products and services." />
|
|
<meta property="og:image" content="https://www.nlm.nih.gov/pubs/techbull/images/nlm_tech_bulletin_graphic_facebook.jpg" />
|
|
<title>MLA 2006: Questions and Answers. NLM Technical Bulletin. 2006 Jul–Aug</title>
|
|
<link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" title="The Dublin Core metadata Element Set" />
|
|
<meta name="DC.Title" content="MLA 2006: Questions and Answers" />
|
|
|
|
<meta name="DC.Publisher" content="U.S. National Library of Medicine" />
|
|
<meta name="DC.Date.Issued" content="2006-05-26" />
|
|
<meta name="DC.Date.Modified" content="2019-06-04" />
|
|
<meta name="NLMDC.Date.LastReviewed" content="2012-08-24" />
|
|
<meta name="NLM.Contact.Email" content="nlmtechbull@mail.nlm.nih.gov" />
|
|
<meta name="DC.Type" content="Newsletters" />
|
|
<meta name="NLM.Permanence.Level" content="Permanent: Stable Content" />
|
|
<meta name="DC.Rights" content="Public Domain" />
|
|
<meta name="DC.Language" content="eng" />
|
|
|
|
|
|
<meta name="DC.Subject.Keyword" content="Abstract" />
|
|
<meta name="DC.Subject.Keyword" content="Author" />
|
|
<meta name="DC.Subject.Keyword" content="Bookshelf" />
|
|
<meta name="DC.Subject.Keyword" content="Cancer" />
|
|
<meta name="DC.Subject.Keyword" content="Clinical Queries" />
|
|
<meta name="DC.Subject.Keyword" content="Cochrane Database of Systematic Reviews" />
|
|
<meta name="DC.Subject.Keyword" content="DOCLINE" />
|
|
<meta name="DC.Subject.Keyword" content="Editor" />
|
|
<meta name="DC.Subject.Keyword" content="Editor's Note" />
|
|
<meta name="DC.Subject.Keyword" content="E-mail" />
|
|
<meta name="DC.Subject.Keyword" content="Extensible Markup Language" />
|
|
<meta name="DC.Subject.Keyword" content="Filter" />
|
|
<meta name="DC.Subject.Keyword" content="Full Text" />
|
|
<meta name="DC.Subject.Keyword" content="Indexing" />
|
|
<meta name="DC.Subject.Keyword" content="Limits" />
|
|
<meta name="DC.Subject.Keyword" content="LinkOut for Libraries" />
|
|
<meta name="DC.Subject.Keyword" content="Medical Library Association" />
|
|
<meta name="DC.Subject.Keyword" content="Medical Literature Analysis and Retrieval System" />
|
|
<meta name="DC.Subject.Keyword" content="Medical Subject Headings" />
|
|
<meta name="DC.Subject.Keyword" content="MEDLINE" />
|
|
<meta name="DC.Subject.Keyword" content="MedlinePlus" />
|
|
<meta name="DC.Subject.Keyword" content="MeSH Database" />
|
|
<meta name="DC.Subject.Keyword" content="My NCBI" />
|
|
<meta name="DC.Subject.Keyword" content="National Training Center and Clearinghouse" />
|
|
<meta name="DC.Subject.Keyword" content="Publisher" />
|
|
<meta name="DC.Subject.Keyword" content="PubMed Central" />
|
|
<meta name="DC.Subject.Keyword" content="PubMed Unique Identifier" />
|
|
<meta name="DC.Subject.Keyword" content="PubMed" />
|
|
<meta name="DC.Subject.Keyword" content="Quick Tour" />
|
|
<meta name="DC.Subject.Keyword" content="Single Citation Matcher" />
|
|
<meta name="DC.Subject.Keyword" content="Subheading" />
|
|
<meta name="DC.Subject.Keyword" content="Subset" />
|
|
<meta name="DC.Subject.Keyword" content="Text Words" />
|
|
<meta name="DC.Subject.Keyword" content="Title/Abstract" />
|
|
<meta name="DC.Subject.Keyword" content="Training" />
|
|
|
|
|
|
<link rel="stylesheet" href="../techbulletin.css" />
|
|
<link rel="alternate" type="application/rss+xml" title="RSS" href="/rss/techbull.rss" />
|
|
<!-- Google Tag Manager -->
|
|
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src='//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);})(window,document,'script','dataLayer','GTM-MT6MLL');</script>
|
|
<!-- End Google Tag Manager -->
|
|
</head>
|
|
<body link="#476B47" alink="#476B47" vlink="#476B47" text="#000000" bgcolor="ffffff">
|
|
<!-- Google Tag Manager -->
|
|
<noscript><iframe src="//www.googletagmanager.com/ns.html?id=GTM-MT6MLL" height="0" width="0" style="display:none;visibility:hidden" title="googletagmanager"></iframe></noscript>
|
|
<!-- End Google Tag Manager -->
|
|
<a title="Skip the navigation on this page" href="#skipnav" class="skipnavigation">Skip Navigation Bar</a>
|
|
<a name="top" id="top"></a>
|
|
<div id="body" >
|
|
|
|
<div class="header">
|
|
<div class="shadow_bottom" align="left">
|
|
<div class="shadow_right">
|
|
<div class="shadow_corner">
|
|
<table class="title" width="100%" border="0" cellpadding="0" cellspacing="0" >
|
|
<col width="134" />
|
|
<col width="*" />
|
|
<tr>
|
|
<td>
|
|
<img src="../new_tb_graphics/tb_header_logo.gif" alt="" width="134" height="64" align="top" />
|
|
</td>
|
|
<td id="titleCell">
|
|
<img id="titleImage" src="../new_tb_graphics/tb_header_title.gif" alt="NLM Technical Bulletin"
|
|
title="" align="top" border="0" height="26" width="335"/>
|
|
<div id="titleText">NLM Technical Bulletin</div>
|
|
|
|
<div>
|
|
<a href="//www.nlm.nih.gov/">National Library of Medicine</a> |
|
|
<a href="//www.nih.gov/">National Institutes of Health</a>
|
|
</div>
|
|
</td>
|
|
</tr></table>
|
|
</div></div></div></div>
|
|
|
|
<div class="header">
|
|
<div class="shadow_bottom" align="left">
|
|
<div class="shadow_right">
|
|
<div class="shadow_corner">
|
|
<table class="grid" width="100%" border="0" cellpadding="0" cellspacing="0">
|
|
<tr class="search" >
|
|
<td colspan="2" align="right">
|
|
<form method="get" action="//search.nlm.nih.gov/techbull/query" target="_self" name="searchForm">
|
|
<label for="searchInput">Search</label>
|
|
<input name="PARAMETER" type="text" id="searchInput" size="12" align="middle"/>
|
|
<input type="submit" id="searchGo" value="GO" />
|
|
<input type="hidden" name="FUNCTION" value="search" />
|
|
<input type="hidden" name="MAX" value="250" />
|
|
<input type="hidden" name="DISAMBIGUATION" value="true" />
|
|
<a href="/vsearchfaq.html">Help</a>
|
|
</form>
|
|
|
|
<img src="../new_tb_graphics/spacer.gif" width="10" height="1" border="0" alt="" />
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td colspan="2">
|
|
2006 JULY–AUGUST; 351
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td class="gridBottomLeft">
|
|
<a href="ja06_issue_cover.html">Table of Contents</a>
|
|
</td><td class="gridBottomRight">
|
|
<a href="../tb.html" class="homeMenu">Home</a>
|
|
<a href="../back_issues.html" class="issuesMenu">Back Issues</a>
|
|
<a href="../new_index.html" class="indexMenu">Indexes</a>
|
|
</td>
|
|
</tr>
|
|
</table>
|
|
</div></div></div></div>
|
|
|
|
<!-- header_end-->
|
|
|
|
|
|
<div id="content" class="article">
|
|
<a id="skipnav" name="skipnav"></a>
|
|
<div class="actions">July 17, 2006 <span class="status">[posted]</span>
|
|
|
|
|
|
|
|
<br />
|
|
January 30, 2007
|
|
|
|
|
|
<span class="status">
|
|
[<a href="#note">Editor's note added</a>]
|
|
</span>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
<h1>MLA 2006:<br /> Questions and Answers</h1>
|
|
|
|
<em><a name = "note">[Editor's </a>Note: Several of the Questions and Answers pertain to the subheading consolidation proposal. Please see <a href="//www.nlm.nih.gov/pubs/techbull/jf07/jf07_technote.html#2">decision</a>].</em>
|
|
|
|
<dl>
|
|
|
|
<dt>NLM Online Users' Meeting</dt>
|
|
<dd><a href="//www.nlm.nih.gov/pubs/techbull/ja06/ja06_mla_dg.html">
|
|
Meeting Remarks - David Gillikin, Head, MEDLARS Management Section</a></dd>
|
|
|
|
<dd><a href="//www.nlm.nih.gov/pubs/techbull/ja06/ja06_mla_ppt.html">PowerPoint<sup><font size="-2">®</font></sup> Presentations for Meeting Remarks, MedlinePlus<sup><font size="-2">®</font></sup>, DOCLINE<sup><font size="-2">®</font></sup> and MeSH<sup><font size="-2">®</font></sup></a></dd>
|
|
|
|
<dd><img src="/pubs/techbull/tb_graphics/blutri.gif" alt="dot" height="10" width="10"/>Questions and Answers</dd>
|
|
|
|
<dt><a href="//www.nlm.nih.gov/pubs/techbull/ja06/ja06_mla_theater_ppt.html">NLM Theater PowerPoint<sup><font size="-2">®</font></sup> Presentations</a></dt>
|
|
|
|
<dt><a href="//www.nlm.nih.gov/pubs/techbull/ja06/ja06_mla_nlm_update_ppt.html">NLM Update PowerPoint<sup><font size="-2">®</font></sup> Presentation</a></dt>
|
|
|
|
|
|
</dl>
|
|
|
|
<hr />
|
|
|
|
|
|
|
|
<h2>Question:</h2>
|
|
<p>
|
|
I would like to get some input from the audience. As professional searchers, how many of you, when you are doing a comprehensive search, limit your search to just heading/subheading combinations? I would respectfully submit that the subheading combinations are for precision searching -- when you need to go through thirteen million PubMed citations and find a few things that have a specific role. If the general user does not use subheadings and the professional users do not use headings/subheadings for comprehensive searching then there is no reason to eliminate them even if some are not assigned by the indexers. Doing so will eliminate the precision for those of us who need to find a few ideal citations for our users in a specific area. Could you please explain why you are doing this when it doesn't seem to have anything but a negative effect on the searching capabilities of the database?
|
|
</p>
|
|
|
|
<h2>Answer - Dr. Nelson:</h2>
|
|
<p>I think I have explained a number of good reasons to revise the subheadings. I didn't suggest eliminating the subheadings. I explained about skewed meanings and inappropriate use of subheadings. I don't think you are completely accurate in saying that the only reason not to do it is to improve precision. That is not the case; we have other problems and I addressed those issues. I talked about representational integrity, about special meanings. These are serious issues. </p>
|
|
|
|
<h2>Question/Comment:</h2>
|
|
<p>This seems to be a wonderful opportunity to go evidence-based. I am wondering what thought has been given to some form of test database, focus groups or data-mining -- simulations that could be used to test the questions that are coming up. We can have different layers of users making sure that all of these changes proposed have good effects or optimal effects. Your work is extremely important but to a huge audience. If you don't stratify your users all of these questions don't make any sense. I think that we need to get an expert group together representing different stake holders in order to settle some of these questions before the work gets done. I know what the costs are and I would really like to see that we do this in a cost-effective way.</p>
|
|
|
|
<h2>Answer - Dr. Nelson:</h2>
|
|
<p>There are a lot of serious questions about how to change this. There are fundamental problems in the whole information retrieval paradigm of understanding when you have found something that's relevant. There are a lot of problems with trying to test this out. The only person who can really understand whether something is relevant to a search is the user. You can know something well, and, therefore, the article that you are looking at is not helpful at all; it's essentially irrelevant at that point. There are other times when you don't know very much so that an article is quite helpful. Even measuring relevancy which is fundamental to information retrieval is a difficult task. One of the things that I have done is look for and ask what other information is available. There is somebody at NLM who is looking at developing semi-automated methods for assigning subheadings. One of the things that person is doing is looking at the indexing consistency data to find where subheadings are frequently confused, to find which ones have been used consistently with a much higher standard than the average. Right now all we have are average numbers, but within that, I am sure we are going to see a broad spectrum of subheadings that are easily confused as well as ones that are highly consistent. I think that is probably the best thing we can go on right now in terms of evidence.</p>
|
|
|
|
|
|
<h2>Question/Comment:</h2>
|
|
<p>As a great MEDLINE<span class="registered">®</span> fan for many years, my comment relates to the <em>NLM Technical Bulletin</em> of February 2006, where it was announced that the PubMed search tag [AB] was removed. <em class="editorsnote">[Editor's Note: Please see <a href="//www.nlm.nih.gov/pubs/techbull/jf06/jf06_technote.html#11">Technical Notes. NLM Tech Bull. 2006 Jan-Feb;(348):e1.</a>] for the full announcement.]</em> I fully support the rationale behind removing the ability to tag with AB because it wasn't limiting the search to the abstract field at all and it seemed very sensible to remove that -- it was never a supported field limit. I think it was what you described as an alias for text word searching. Nonetheless, what my request is is that you actually instigate the ability to search in the abstract field. You are probably aware that the functionality exists at the moment to limit to both the title and the abstract concurrently with the [TIAB] tag, but for those of us who are interested in designing highly sensitive and highly precise search strategies, it is necessary to limit sometimes to the abstract only. For those of you who have seen the current issue of <em>Journal of the Medical Library Association (JMLA)</em>, we [Cochrane Collaboration] just have published a new highly sensitive search strategy for identifying Randomized Controlled Trials (RCTs) in MEDLINE. This relies on being able to search certain words in the abstract only, not the title and abstract. And, for example, that search strategy has improved the precision of the clinical queries that you currently have for the therapy filter from something like 25% to 40% precision, but you can only do this if you can search in the abstract only. We did the research in Ovid<span class="registered">®</span>, and for the benefit of people who don't have access to Ovid we translated this into PubMed. And of course we made the mistake of translating limits to abstract to the AB in square brackets. So I would like to request that you have a look at adding the ability to search only the abstract field.</p>
|
|
|
|
<h2>Answer - Mr. Gillikin:<!--(Annette)--></h2>
|
|
<p>We examined a number of searches using a "sensitive" search strategy to see if an abstract-only search tag in PubMed would yield results significantly different than using [TIAB]. We did not see this. We have, therefore, decided against adding a new search tag at this time.</p>
|
|
|
|
|
|
<h2>Question/Comment:</h2>
|
|
<p>I would like to say that from all of the subheading announcements that we saw prior to this meeting, I never got the impression that we should go through each subheading and make a case for or against its relevance or why it made sense. From part of the discussion it sounds like maybe that's the kind of feedback that you would really prefer. Something that caught my attention from the letters that we saw posted to MEDLIB-L was that some people were okay with not having the secondary subheading but then I read that one cancer librarian was very concerned about not having it. How you balance that really depends on the kind of searching you are doing and also the utility of the different subheadings that are available. The second question that I have is what happens to the system? How will changes in 2008 impact older citations? Will just everything from 2008 forward have the new subheadings? When I conduct a search will I need to take into account if it's abnormalities or birth defects? Do I also need to search with abnormalities for citations prior to 2008? Doesn't this make it more confusing and harder for people to find things when you have to know the cut off in your head to know how to construct your search?</p>
|
|
|
|
<h2>Answer - Dr. Nelson:</h2>
|
|
<p>Answering the second question first: Just as you do not have to change the MeSH<span class="registered">®</span> heading that you use to correspond to which year MeSH headings were assigned to MEDLINE citations, the same process will be applied to the subheadings. We do citation maintenance. It's a process which is not really well described. Susanne Humphrey wrote a paper about it a good number of years ago <em class="editorsnote">[Editor's Note: <a href="//www.ncbi.nlm.nih.gov/entrez/query.fcgi?cmd=PureSearch&db=pubmed&details_term=10299353%5BUID%5D">Humphrey S. File maintenance of MeSH headings in MEDLINE. J Am Soc Inf Sci. 1984 Jan;35(1):34-44. PMID: 10299353</a>]</em>. If you go to the MeSH Web site there is some other information including an XML of the actual transactions that we follow every year to do citation maintenance in order to maintain the upcoming year of MeSH. I expect to do exactly the same thing with subheading revisions so that, no, you won't have use two different systems of subheadings. <!--<em class="editorsnote">[Editor's Note: As a concrete example of what will happen during annual citation maintenance, let's look at one of the proposed subheading changes - the merger of /transmission into /etiology. If that is approved, then at year-end processing time when NLM edits the journal citations and monographic records to align them with the upcoming new year of MeSH, all occurrences of /transmission will be physically replaced with /etiology, retaining any stars for the main point emphasis. The string "transmission" will no longer be present as a subheading on the journal citations or monographic records. The string "transmission" will become an entry term to /etiology so that PubMed/NLM Catalog searches using /transmission, or transmission [sh], or transmission with no search tag will map to /etiology. The approximately 80,000 MEDLINE/PubMed citations currently having /transmission will be retrievable among the larger set of /etiology (nearly 1.5 million citations not exploded), yet the specific subheading /transmission will no longer be in the citation.]</em>-->
|
|
</p>
|
|
|
|
|
|
<p>
|
|
In reference to the first comment, the article that is on the <a href="//www.nlm.nih.gov/mesh/whatsnew.html">MeSH Web site</a> addressed the idea that I wanted to hear comments about usability, reproducibility and understandability. I really do welcome those kinds of comments. I look at it from the point of view of a professional who works in vocabulary development and I say that this system needs repair and needs to evolve. But for resolution, I look at the comments. What I do most of the time is look at requests, comments from the Index Section, comments from the catalogers, comments from people who deal with the users, and comments from individuals who work with the system. I try to balance all those things out. I will read the comments carefully and consider them. I want you to know that I do have an open mind about where we are. I was deliberately provocative in the draft that was sent out. I wanted to make people stop and think about everything being on the table. Let's think about what it is that we really want, what is it that we really need, and how do we make what we have better?</p>
|
|
|
|
<h2>Question:</h2>
|
|
<p>And so does that mean that you're open to adding subheadings instead of just eliminating them?</p>
|
|
|
|
<h2>Answer - Dr. Nelson:</h2>
|
|
<p>If you can make the case that it is useful, understandable and can be done reproducibly, then I am open to it. However, the more subheadings you have the less likely it is to be reproducible.</p>
|
|
|
|
<h2>Comment from David Gillikin:</h2>
|
|
<p>For those of you who have been sending comments to MEDLIB-L, please do not assume that NLM is reviewing comments from MEDLIB-L. If you have a comment, please go to the <a href="//www.nlm.nih.gov/mesh/">MeSH homepage</a> and follow the instructions for sending in comments. They then are forwarded to Dr. Nelson. <em class="editorsnote">[Editor's Note: The deadline for comments was June 16, 2006.]</em></p>
|
|
|
|
<h2>Comment/Question:</h2>
|
|
<p>I did send Dr. Nelson a comment on /chemically induced with respect to Lupus and I'm happy to see that's been moved over into the save column. Thank you very much. My question has to do with searching. Are there any plans to make true adjacency searching possible in PubMed and if not, why, when so many other databases allow you to do this? </p>
|
|
|
|
<h2>Answer - Mr. Gillikin:<!--Annette--></h2>
|
|
<p>While there are no plans currently to add another method for adjacency searching, we are always interested in examining how to make PubMed a better search tool. It will help us considerably if you can send us searches that do not work for you using the current method of <a href="//www.ncbi.nlm.nih.gov/books/NBK3827/#pubmedhelp.Searching_for_a_phra">phrase searching</a>. Please send your search examples for adjacency to: <a href="mailto:custserv@nlm.nih.gov">custserv@nlm.nih.gov</a>.
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<h2>Question/Comment:</h2>
|
|
<p>My question is actually more of a request. We are finding that our clinicians and medical students are using Google<span class="registered">™</span>
|
|
Scholar. It's easy for them to get to Google Scholar when they are on-site -- our open URL links show up. We have open URL in PubMed as well and we use LinkOut<span class="registered">®</span>. I find that Clinical Queries is very popular among these clinicians and I would like to be able to have a direct link either from the Library Web page or hopefully some of the hospital
|
|
Internet sites directly into Clinical Queries that would access our open URL links and our LinkOut. It's not realistic for everybody to go through and set up My NCBI filters throughout the hospital on the hospital computers so that those links are available. I'd like to see some sort of capacity for an individual link like we have through the Library Web site for our holdings to be available through Clinical Queries.
|
|
</p>
|
|
|
|
|
|
<h2>Answer - Mr. Gillikin:</h2>
|
|
<p>Libraries can display the LinkOut icon through the Clinical Queries page. To do this, enter Clinical Queries using the following URL:</p>
|
|
|
|
<dl>
|
|
<dd>
|
|
<a href="//www.ncbi.nlm.nih.gov/entrez/clinicalx.cgi?holding=NameAbbr">//www.ncbi.nlm.nih.gov/entrez/clinicalx.cgi?holding=NameAbbr</a>
|
|
</dd>
|
|
|
|
<dd>Replace NameAbbr with the provider's LinkOut User Name</dd>
|
|
</dl>
|
|
|
|
<p>
|
|
Details can be found at the <a href="//www.ncbi.nlm.nih.gov/entrez/linkout/doc/liblinkout.html">LinkOut homepage</a>. Click on Libraries and then on Localize PubMed.</p>
|
|
|
|
<p>
|
|
Additional information can also be found in the Technical Note, <a href="//www.nlm.nih.gov/pubs/techbull/jf05/jf05_technote.html#tool">Displaying LinkOut and Outside Tool Icons When Using Single Citation Matcher and Clinical Queries. NLM Tech Bull. 2005 Jan-Feb;(342):e1. </a>
|
|
</p>
|
|
|
|
<h2>Question/Comment:</h2>
|
|
<p>I do a lot of PubMed training and I know that the National Training Center & Clearinghouse (NTCC) staff in its 8-hour PubMed class provides a brief overview of MeSH. As I travel around and train I find that most people are self taught when it comes to the MeSH vocabulary and I think that may be one of the problems. I think it would behoove the National Library of Medicine to develop a training class specifically on MeSH because at this time people are getting just a few minutes in the NTCC class. When I was reviewing comments about the subheadings I noticed that people were unaware of the fact that the subheadings are arranged in families and that they explode automatically in PubMed. This is basic information about using the MeSH vocabulary and it is not being effectively transmitted to people so a MeSH class would be helpful. This would be the logical vehicle to get the word out when the annual MeSH changes are made and instruct people on how those changes may effect their searching.</p>
|
|
|
|
|
|
<h2>Answer - Mr. Gillikin <!--Janet Zipser-->:</h2>
|
|
<p>Thank you for the suggestion. The current PubMed training class devotes one and one half hours to MeSH. In addition it is frequently discussed throughout other portions of the class. Also, please see the 12-minute video <em><a href="//www.nlm.nih.gov/bsd/disted/video/">Branching Out: The MeSH<sup><font size="-2">®</font></sup> Vocabulary</a></em> and the newest MeSH instructional resource, the Basics of Medical Subject Headings (MeSH).
|
|
</p>
|
|
|
|
|
|
<h2>Question/Comment:</h2>
|
|
<p>I would like to see healthcare administration journals added as a separate subset in PubMed. We have a graduate healthcare administration program and we don't have many of the clinical journals in our library. I would like our students to be able to identify the journals that we are more likely to have and to be pertinent to their search.</p>
|
|
|
|
|
|
<h2>Answer - Mr. Gillikin <!--Sara Tybaert and Ione Auston-->:</h2>
|
|
<p>NLM doesn't have any plans to develop a healthcare administration subset for PubMed; however, if your library is a LinkOut participant you can establish a filter for your library's holdings. This filter can be part of a shared My NCBI account. The following links will take you to more details about LinkOut and creating a filter for a shared account:</p>
|
|
|
|
<ul>
|
|
<li>The LinkOut for Libraries Web page:<br /> <a href="//www.ncbi.nlm.nih.gov/entrez/linkout/doc/liblinkout.html">//www.ncbi.nlm.nih.gov/entrez/linkout/doc/liblinkout.html</a> </li>
|
|
|
|
<li>Library LinkOut Filters Quick Tour:<br /> <a href="//www.nlm.nih.gov/bsd/viewlet/myncbi/library_linkout_filter.html">//www.nlm.nih.gov/bsd/viewlet/myncbi/library_linkout_filter.html</a> </li>
|
|
|
|
|
|
<li><em>NLM Technical Bulletin</em> article:<br /> <a href="//www.nlm.nih.gov/pubs/techbull/ja05/ja05_share_my_ncbi.html"><em>Share My NCBI Account Settings. NLM Tech Bull. 2005 Jul-Aug;(345):e7. </em></a> </li>
|
|
|
|
</ul>
|
|
|
|
<h2>Comment:</h2>
|
|
<p>I would like to thank you very much. I'm a huge fan of PubMed and enjoy the resources and I appreciate all your hard work.</p>
|
|
|
|
<h2>Question/Comment:</h2>
|
|
<p>When I teach doctors or students I tell them to be aware when using MeSH because all in-process and publisher-supplied citations are not indexed. I tell them to use a keyword search term instead of going to the MeSH database. I say that because we tend to teach doctors to use MeSH and we emphasize it. If you want the most recent citations to the hot topics or those articles that just came in (and NLM does a wonderful job of putting them in for us to access -- there are a large number that are supplied by publisher and are available only electronically) these are not indexed yet as well. When I look in the Details I also realize that when you use MeSH you don't cover some of the terms that are being used by the author that are not really matching with the MeSH. I find it makes a big difference. Librarians might want to be aware of that.</p>
|
|
|
|
<h2>Answer - Mr. Gillikin:
|
|
<!--From Annette:--></h2> <p>
|
|
That is a good point. In fact, most PubMed searchers use "Google-style" subject searching, i.e., they enter the topics of interest and do not specify terms as being MeSH. Example:</p>
|
|
<dl>
|
|
<dd>
|
|
<strong>behcet disease small bowel</strong>
|
|
</dd>
|
|
</dl>
|
|
<p>
|
|
Users are comfortable searching using their own terminology and while many seem to appreciate the value of MeSH vocabulary and NLM's indexing, they do not rely on it for searching. This is OK because PubMed has extensive mapping capabilities that allow it to recognize the user's terminology as entry terms for MeSH headings or subheadings and incorporate them into the search.</p>
|
|
|
|
<h2>Answer - Dr. Nelson:</h2>
|
|
<p>I think what you are talking about is trying to go from a MeSH heading to a query expansion to get other types of commonly used text words and phases. Is that essentially what you are suggesting?</p>
|
|
|
|
<h2>Attendee:</h2> <p>Yes.</p>
|
|
|
|
<h2>Answer - Dr. Nelson:</h2>
|
|
<p>What you do need to know is that there is a mapping file that sits behind the scenes and maps free text searching to MeSH and it's quite a large file. It's about 500,000 lines, each line being a single mapping. If there are terms in the vernacular or colloquial terms or frequently used terms that you don't find getting mapped to MeSH headings, please send those to me as a suggestion. We have the ability to add things to that file. Going from telling someone to use a MeSH heading and then to pull in other text words I think will likely cause problems. Most experiments that were done in that regard have shown that it actually detracts from the quality of the retrieval.</p>
|
|
|
|
|
|
<h2>Question/Comment:</h2>
|
|
<p>I teach classes for nurses and anytime you type in <em>hospice nursing</em> you get breast feeding articles because of that mapping of nursing and breast feeding. I have sent several e-mails to the MeSH section and NLM with no response. I just wanted to let you know formally that I hope this can be changed.</p>
|
|
|
|
<h2>Answer - Dr. Nelson:</h2>
|
|
<p>I suspect that what is happening is that nursing is being mapped to breast feeding. In fact, that is a common use and there are many times in the mapping file where there are mappings to several different meanings. For example, "cold" gets mapped three different ways. The problem is your users want a specific meaning and they want to exclude the other meaning of the same word. Unfortunately, we can't do that because the next person that comes along is going to want the other meaning for that specific word and that's where it becomes a problem.</p>
|
|
|
|
|
|
<h2>Comment:</h2>
|
|
<p>Thank you very much for making available products like PubMed Central<span class="registered">®</span> and Bookshelf. They are wonderful. </p>
|
|
|
|
|
|
<h2>Question/Comment:</h2>
|
|
<p>I am a grassroots librarian now after having run some big libraries. I love that you added the capability to limit searches to PubMed citations having links to either full text or free full text. It is really wonderful for our small college because we have ten doctoral students who don't have the money to go out and get the full text and we don't have the money to pay commercial services so this is just a great capability that you recently added. <em class="editorsnote">[Editor's Note: For further information on limiting your search results to include full text see: <a href="//www.nlm.nih.gov/pubs/techbull/ma06/ma06_limits.html"><em>PubMed<span class="registered">®</span> Limits Page Updated. NLM Tech Bull. 2006 Mar-Apr;(349):e2. </em></a>]</em>
|
|
|
|
<em class="editorsnote">[Editor's Note: At this point, the taping service failed to capture the remaining portion of the meeting. The following questions were recreated from staff notes.]</em> I would like more Oriental Medicine titles to be added to the database. I would like training telecasts and more distance education.</p>
|
|
|
|
<h2>Question:</h2>
|
|
Is it a rumor that MeSH was developed by linguists?
|
|
|
|
|
|
<h2>Answer - Ms. Humphreys:</h2>
|
|
<p>Yes, it is a rumor. MeSH reflects influences from a variety of disciplines (including linguistics), but the person most responsible for its development was former NLM Director Frank Bradway Rogers, M.D., M.L.S. Winifred Sewell, Ph.D. was its first full-time editor. Those who are interested in the early development of MeSH and the work that led up to the development of MEDLARS should consult Scott Adams' 1972 Janet Doe lecture, "The Way of the Innovator: Notes Toward a Pre-History of MEDLARS" published in the <em>Bulletin of the Medical Library Association</em> and available in PubMed Central at: <a href="//www.pubmedcentral.gov/pagerender.fcgi?artid=197742&pageindex=1#page">//www.pubmedcentral.gov/pagerender.fcgi?artid=197742&pageindex=1#page</a></p>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<p class="authors">
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<img src="../new_tb_graphics/black_pixel.gif" width="450" height="1" alt="" />
|
|
|
|
<!--************************CHANGE CITATION INFORMATION BELOW*****************************-->
|
|
<p class="citation">MLA 2006: NLM<span class="registered">®</span> Online Users' Meeting 2006: Questions and Answers. NLM<span class="registered">®</span> Tech Bull. 2006 Jul-Aug;(351):e3c. </p>
|
|
<!--************************END CITATION INFORMATION**************************************-->
|
|
|
|
</div><!-- end of content -->
|
|
|
|
<div class="header" align="center">
|
|
<div class="shadow_bottom" align="left">
|
|
<div class="shadow_right">
|
|
<div class="shadow_corner">
|
|
<table class="grid" width="100%" border="0" cellpadding="0" cellspacing="0">
|
|
<tr>
|
|
<td>
|
|
|
|
<a href="ja06_mla_theater_ppt.html" title="Previous Page">PREVIOUS</a>
|
|
|
|
</td><td>
|
|
<span class="issueDateMenu" >
|
|
2006 JULY–AUGUST</span> No. 351
|
|
</td>
|
|
<td class="gridNext">
|
|
|
|
<a href="ja06_mla_ppt.html" title="Next Article">NEXT</a>
|
|
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td>
|
|
<a href="/pubs/techbull/stay_current.html" class="gridBottomLeft">Stay Current <img src="/pubs/techbull/new_tb_graphics/footer_icons_14h.gif" alt="E-Mail Sign Up"/></a>
|
|
</td><td class="gridBottomRight" colspan="2">
|
|
<a href="../tb.html" class="homeMenu">Home</a>
|
|
<a href="../back_issues.html" class="issuesMenu">Back Issues</a>
|
|
<a href="../new_index.html" class="indexMenu">Indexes</a>
|
|
</td>
|
|
</tr>
|
|
</table>
|
|
</div></div></div></div>
|
|
|
|
<!-- BEGIN NLM FOOTER -->
|
|
<div class="footer">
|
|
<a href="/">National Library of Medicine</a> 8600 Rockville Pike, Bethesda, MD 20894
|
|
<br>
|
|
<a href="//www.nlm.nih.gov/socialmedia/index.html">Connect with NLM</a>,
|
|
<a href="//www.nlm.nih.gov/web_policies.html">Web Policies</a>,
|
|
<a href="//www.nlm.nih.gov/careers/jobopenings.html">Careers</a>,
|
|
<a href="//www.nlm.nih.gov/accessibility.html">Accessibility</a>,
|
|
<a href="//www.usa.gov/">USA.gov</a>,
|
|
<a href="//www.hhs.gov/vulnerability-disclosure-policy/index.html">HHS Vulnerability Disclosure</a>
|
|
<br>
|
|
<a href="//www.nih.gov/">NIH</a>,
|
|
<a href="https://www.hhs.gov/">HHS</a>,
|
|
<a href="//www.nih.gov/institutes-nih/nih-office-director/office-communications-public-liaison/freedom-information-act-office">FOIA</a>,
|
|
<a class="supportLink" href="//support.nlm.nih.gov?from=" target="_blank">NLM Support Center</a>
|
|
</div>
|
|
|
|
</div><!-- body -->
|
|
<script src="//assets.nlm.nih.gov/jquery/jquery-latest.min.js"></script>
|
|
<script src="/scripts/support.js"></script>
|
|
<script src="/core/nlm-notifyExternal/1.0/nlm-notifyExternal.min.js"></script>
|
|
</body>
|
|
</html>
|
|
|
|
|