<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[Forum — Rather serious usability issue]]></title>
		<link>https://forums.nbn.org.uk/viewtopic.php?id=67</link>
		<atom:link href="https://forums.nbn.org.uk/extern.php?action=feed&amp;tid=67&amp;type=rss" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Rather serious usability issue.]]></description>
		<lastBuildDate>Tue, 11 Jul 2006 14:19:52 +0000</lastBuildDate>
		<generator>PunBB 1.4.6</generator>
		<item>
			<title><![CDATA[Re: Rather serious usability issue]]></title>
			<link>https://forums.nbn.org.uk/viewtopic.php?pid=285#p285</link>
			<description><![CDATA[<p>Tweaking the sort order in the Taxon Find dialog would be a fairly simple change.&nbsp; I&#039;ll add it to the Future Developments list so hopefully it will get implemented in the not too distant future.&nbsp; I&#039;d suggest using the actual name then the preferred name to define the sort order, just in case a taxon rank gets added out of synch so the rank keys are not correctly ordered.</p><p>The second issue regarding defaulting back to Unrestricted searches sounds like a bug so I&#039;ve added it to the bug tracker to get fixed for version 6.9.</p>]]></description>
			<author><![CDATA[null@example.com (johnvanbreda)]]></author>
			<pubDate>Tue, 11 Jul 2006 14:19:52 +0000</pubDate>
			<guid>https://forums.nbn.org.uk/viewtopic.php?pid=285#p285</guid>
		</item>
		<item>
			<title><![CDATA[Re: Rather serious usability issue]]></title>
			<link>https://forums.nbn.org.uk/viewtopic.php?pid=283#p283</link>
			<description><![CDATA[<p>It might be straightforward to use the TAXON_RANK_KEY in the TAXON_LIST_ITEM table as a sort field. This is ordered hierarchically so species (NBNSYS....28) is earlier than subspecies (....31).</p><p>Bob Saville<br />Lothian Wildlife Information Centre</p>]]></description>
			<author><![CDATA[null@example.com (BobS)]]></author>
			<pubDate>Tue, 11 Jul 2006 12:49:20 +0000</pubDate>
			<guid>https://forums.nbn.org.uk/viewtopic.php?pid=283#p283</guid>
		</item>
		<item>
			<title><![CDATA[Re: Rather serious usability issue]]></title>
			<link>https://forums.nbn.org.uk/viewtopic.php?pid=282#p282</link>
			<description><![CDATA[<p>This is quite a serious problem as it has the potential to introduce errors into the database via data entry. Have a look at this screenshot (click to enlarge):</p><p><a href="http://www.flickr.com/photo_zoom.gne?id=187234222&amp;size=o">[img]http://static.flickr.com/72/187234222_8caf7e767c_t.jpg[/img]</a></p><p>You can see what I&#039;ve done is simply typed marbled white in and got back the list of possibilities. You should also notice that I&#039;ve stretched out the box so I can see what the two marbled white possibilities are from the LEPIDOPTERA list. Note how the subspecies comes first, presenting itself at the &#039;default&#039; option. The problem is I see this a lot in Recorder, mainly due to the basic sorting method used. Often, the most likely choice is found at the bottom of a long list of subspecies, making the selection process laborious and error prone.</p><p>My question is, what are the options for rectifying this problem? It presents a serious usability problem, and is extremely counter-intuitive for the beginner.</p><p>Thoughts anyone?</p><p>One other issue, while I&#039;m here. Recorder often seems to switch back to Unrestricted as the &#039;Restrict Searches To&#039; type. I&#039;ll often change to Preferred, only to find it back on Unrestricted a little while later after doing something else. I&#039;ve just nailed this down to searching in the dictionaries. If I click the bins icon to do a search in the taxon dictionary, it defaults the Restrict Searches To back to Unrestricted.</p><p>Charles</p>]]></description>
			<author><![CDATA[null@example.com (charlesroper)]]></author>
			<pubDate>Tue, 11 Jul 2006 12:32:30 +0000</pubDate>
			<guid>https://forums.nbn.org.uk/viewtopic.php?pid=282#p282</guid>
		</item>
	</channel>
</rss>
