anchor.diff:              <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>
  -          [To be completed closer to release: ] 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 was significantly abbreviated in the LexEVS 5.0 implementation.
  -            Of particular importance,
  +          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,
               <ul>
  -              <li>Relationships ...[to be written]
  -              <li>&nbsp;
  +              <li>Relationship data are not consistently stored and linked, and are represented incompletely as described in the
  +              browsers <a href="<%= request.getContextPath() %>/pages/rela_help_info.jsf">Relationship Attribute Help</a>.
  +              This also made it impossible to reliably display individual source hierarchies within their broader NCIm context.
  +              <li>Other source specific concept data were also only partly loaded.
               </ul>
  -            These problems should be fixed with the LexEVS 5.1 release in Fall 2009.
  -            <li><b>Functionality</b>: The default scoring for search matches will continue to be improved, and some
  -            user-settable options should be part of the forthcoming Advanced Search page.
  +            <br>These problems should be fixed with the LexEVS 5.1 release in late 2009.<br><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>Documentation</b>: Online and standalone documentation are still under development.
             </ul>
             Please report any bugs or suggestions using the browsers <a href="contact_us.jsf">Contact Us</a> page.
  
positive.code:           is shown directly without first listing results.) Some details:
            <ul>
              <li>All matching concepts are returned.
              <li>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.
              <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
  
negative.code:             <li><b>Begins With</b> can be selected to find all terms or codes that start with the words or characters you enter.
              <li><b>Contains</b> will search for what you enter anywhere within a term or code (e.g.,
              <i>carcinoma</i> will match <i>adenocarcinoma</i>).
              <li><b>Rank (Slow)</b> sorts results from best match to weakest if the check box is selected.  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.It is off by
              default due to poor performance.
              <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>).
  