anchor.diff:              <td><h2><A NAME="sources">Sources</A></h2></td>
               <td align="right"><a href="#"><img src="<%= request.getContextPath() %>/images/up_arrow.jpg" width="16" height="16" border="0" alt="top" /></td>
             </tr></table>
  -          Click on the <b>Sources</b> link at the top of the page to bring up a separate window showing the list of sources
  +          Click on the
  +          <a href="#" onclick="javascript:window.open('<%=request.getContextPath() %>/pages/source_help_info.jsf',
  +          '_blank','top=100, left=100, height=740, width=780, status=no, menubar=no, resizable=yes, scrollbars=yes, toolbar=no, location=no, directories=no');">
  +          <b>Sources</b></a>
  +          link at the top of the page to bring up a separate window showing the list of sources
             included in the current release of NCI Metathesaurus.  Sources are listed alphabetically  by abbreviation, showing
  -          full source names and other details.
  +          full source names and other details. Use restrictions are described for proprietary sources.
           </p>
           <p class="textbody">
             <table width="100%" cellpadding="0" cellspacing="0" border="0"><tr>
               <td><h2><A NAME="knownissues">Known Issues</A></h2></td>
               <td align="right"><a href="#"><img src="<%= request.getContextPath() %>/images/up_arrow.jpg" width="16" height="16" border="0" alt="top" /></td>
             </tr></table>
  -          There are important known issues in data, functionality and documentation that we are working to address for release 2.
  -          These include the following:
  -          <ul>
  -            <li><b>Data</b>: NCI Metathesaurus data were significantly abbreviated in the LexEVS 5.0 implementation. Of particular
  -            importance,
  +          This release, based on LexEVS 5.1, addresses most known issues in data and performance.  We are still working on remaining issues of data,
  +          functionality and documentation,  which include the following:
  +          <ul>
  +            <li><b>Data</b>: NCI Metathesaurus has a few remaining gaps in data, plus some issues of best interpretation and presentation. Of particular importance,
               <ul>
  -              <li>Relationship data are not consistently stored and linked, and are represented incompletely as described in the
  -              browsers
  +              <li>o Relationship data are represented somewhat differently in different sources, and the summary labels, described in the browsers
                 <a href="#" onclick="javascript:window.open('<%= request.getContextPath()%>/pages/rela_help_info.jsf',
                         '_blank','top=100, left=100, height=740, width=780, status=no, menubar=no, resizable=yes, scrollbars=yes, toolbar=no, location=no, directories=no');">
                 Relationship Attribute Help</a>.
  -              This also made it impossible to reliably display individual source hierarchies within their broader NCIm context.
  -              <li>The display of history data has been postponed until the next release.
  -              <li>Other source specific concept data were also only partly loaded.
  +              sometime appear to be inappropriate. This also complicates efforts to reliably display individual source hierarchies within their broader NCIm context.
  +              <li>The display of history data has been postponed until a future release.
  +              <li>Some additional categories of source specific concept data are not included, but are being considered for inclusion in future releases.
               </ul>
  -            These problems should be fixed with the LexEVS 5.1 release in late 2009.<br>
  -            <li><b>Functionality</b>: Performance problems have been partly designed around but are still an important issue that
  -            we intend to fix.  The ranking of search results best matches first could not achieve acceptable performance and was
  -            made a user option with warning attached.  The Relationship and By Source tabs are also too slow. User-settable options
  -            and the ability to search other concept data and relationships are needed, and should be part of forthcoming browser
  -            releases.
  +            <li><b>Functionality</b>: Performance has greatly improved and remaining problems have been partly designed
  +            around, but there are still issues with extensive relationship and hierarchy data that we intend to fix.
  +            User-settable options and the ability to search other concept data and relationships are needed, and should
  +            be part of forthcoming browser releases.
               <li><b>Documentation</b>: Online and standalone documentation are still under development.
               <li>For the latest updates of known issues, <a href="https://wiki.nci.nih.gov/display/EVS/NCI+Metathesaurus+Browser+1.1+Release+Notes" target="_blank"> see NCI Metathesaurus Browser 1.1 Release Notes</a>.
             </ul>
  
positive.code:           is shown directly without first listing results.) Some details:
            <ul>
              <li>All matching concepts are returned.
              <li>Results are listed alphabetically unless the <b>Rank</b> option is selected.
              <li>If <b>Rank</b> is selected, results are listed from best match to weakest. For example, a <b>Contains</b> search on
              <i>melanocyte</i> returns <i>melanocyte</i> at the top, followed by concepts with two word matches (e.g.,
              <i>Spindle Melanocyte</i>), followed by concepts whose terms have more non-<i>melanocyte</i> content.  An additional
              column displays the semantic type(s) assigned to each concept.
              <li>The match will often be to synonyms or codes only visible on the concept details page (e.g.,
              searching <b>Begins With</b> <i>melanoma</i> will show <i>Corneal Melanoma</i> in the results list because that
              concept contains a synonym of <i>Melanoma of the Cornea</i>.) A future release will show these matches in the
              results window.
              <li>If there are too many to show on one page, you can page through the results with a default of 50 per page.
              To change the default number, use the <b>Show results per page</b> drop-down menu at the bottom of the results
              page.
              <li>Click on the name to see a concepts details.
            </ul>
          </p>
  
negative.code:           <ul>
              <li>You can search for a concepts name, synonyms, acronyms, or codes.
              <li><b>Exact Match</b> is the default: Only terms or codes that are identical will match.
              <li><b>Begins With</b> can be selected to find all terms that start with the words or characters you enter, or codes that match exactly.
              <li><b>Contains</b> will search for what you enter at the beginning or end of any word or exactly matching any code (e.g.,
              <i>carcinoma</i> will match <i>adenocarcinoma</i>) but not <i>adenocarcinomas</i>
              (Embedded substring search is currently too slow; it will either be sped up or added as an advanced search option in a future release.)
              <li>Concept Unique Identifiers (CUIs) and codes from individual sources will only match if they exactly match what you enter, even if you select <b>Begins With</b> or <b>Contains</b>.
              <li>Search is not case sensitive (e.g., aids will match <i>aids</i>,
              <i>Aids</i>, and <i>AIDS</i>).
  