Accession ids for the given sequence names. It is important to realise
that many DAS sources only use Uniprot accession ids, rather than
Swissprot/Uniprot sequence names.<br>
-<p><strong>The Sequence Identification Process</strong></p>
-The method of Uniprot accession id discovery is the same method which
-earlier Jalview versions used for sequence feature retrieval, and is now
-also used for
-<a href="viewingpdbs.html">PDB ID discovery</a>
-. Essentially, Jalview will try to retrieve Uniprot records via the
-EBI's WSDbFetch interface using each sequence's ID string (or each
-string in the ID separated by the '∣' symbol).
-</p>
-<p>If a uniprot record (or set of records) is found for a sequence,
-then the sequence is aligned to the one in the Uniprot record to
-determine the correct start and end residue positions (which are
-displayed when the 'Show Full Sequence ID' option is set).</p>
-<p>If the alignment reveals differences between the sequence in the
-alignment and the one in the record, then Jalview will assume that the
-aligned sequence is not the one in the uniprot record.</p>
-<p>In some cases, the ID used to retrieve Uniprot records may be out
-of date and a dialog box will be opened indicating that a 100% match
-between the sequence and a Uniprot record was identified, but the
-sequence name is different. In this case, the ID must be manually
-changed (by right clicking on the sequence ID and selecting <strong>Sequence→Edit
-Name</strong>), before Jalview will show its sequence features.
+The <a href="../webservices/dbreffetcher.html">database reference
+fetcher</a> documentation describes how Jalview discovers what database
+references are appropriate for the sequences in the alignment.
<ul>
<li><em>Note</em><br>
Please remember to save your alignment if either the start/end
- numbering, or the sequence IDs were updated during the Uniprot ID
+ numbering, or the sequence IDs were updated during the ID
retrieval process.</li>
</ul>
<p>