X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhtml%2FwebServices%2Furllinks.html;h=d99633a6bf3aba2fd704c9c75d782413b5c2b6d5;hb=0fcc08f1f633aa9eae854ebe0c78b5fb75471898;hp=7ac76c1ddbf7b71a90505f958018e440e782d1de;hpb=e390c310cb1391beba4b0238645120f772a99b98;p=jalview.git

diff --git a/help/html/webServices/urllinks.html b/help/html/webServices/urllinks.html
index 7ac76c1..d99633a 100644
--- a/help/html/webServices/urllinks.html
+++ b/help/html/webServices/urllinks.html
@@ -93,6 +93,21 @@
     the sequence ID for the sequence (<em>since Jalview 2.10.1</em>).
   </p>
   <p>
+    <strong><a name="warning">Warning dialog about updating
+        your configured URL links</a></strong><br /> In the desktop
+    prior to Jalview 2.10.1, the only way to configure custom links for
+    a particular database cross-reference for a sequence was to give it
+    a name that
+    <em>exactly</em> matched the database source, and a regular
+    expression for filtering out any spurious matches generated when the
+    custom linked was tested against the Sequence's ID string. Since the
+    introduction of the $DB_ACCESSION$ token, however, $SEQUENCE_ID$
+    will not be used for database cross-reference accession strings, and
+    if you have custom links configured, Jalview will raise a warning
+    message so let you know that you may need to update your links to
+    use $DB_ACCESSION$.
+  </p>
+  <p>
     <strong>Regular Expression Substitution</strong><br> A url may
     contain a string of the form $SEQUENCE_ID=/<em>regular
     expression</em>/=$ or $DB_ACCESSION=/<em>regular expression</em>/=$.