I didn't even realise that option was there. It terms of feeling the effects of its removal, we wouldn't miss it here. However, we definitely would miss being able to report on records entered against a certain list. We frequently use the report wizard to report on, say, all Odonata by choosing the Odonata list and selecting All taxa from list.

But I suspect that's not quite what you mean when you say, "this would also mean that users could not select to report on records only inputted from a particular list."

Charles

Hi there,

Not having access to R6 at the moment makes this slightly confusing, however reading between the lines here, how much of this is a work-round to Nameserver functionality not being fully operational?

The way I set up a few reports that included data which may have been inputted using different lists was to to do this:

Firstly, run a few test cases to find most common-used lists, then design a report which included everything on those lists.
Then export the lot into Excel & use a lookup function to narrow down duplicated species. Crude, but it worked!

Although I'd seen the 'Full Translation" option in the Tools menu, I'd never really pondered on it's implications.

Yes, that's right, with one clarification. The full translation option actually means "treat items as synonyms when they have the same recommended_taxon_list_item_key in index_taxon_name". This is slightly different than saying it just uses Nameserver, because the recommended_taxon_list_item_key population algorithms (that run when you rebuild indexes) actually revert to the old methods of identifying synonyms when taxa are not handled in the nameserver.

So, having full translation unchecked means:
"treat taxa as synonyms if they are identified as such using Index_Taxon_Synonym"

and checked means:
"treat taxa as synonyms if they are identified as such using the nameserver. If not in the nameserver, treat taxa as synonyms if they are identified as such using Index_Taxon_Synonym"

So, personally, I can't see the point of allowing this option to be turned off. Its even been turned on in Luxembourg when the nameserver table wasn't in use and there were no detrimental effects.

I have just discovered to that to extract all of our Arvicola terrestris records which for historic reasons were entered using a mixture of the preferred Mammalia checklist and the Recorder 3.3 checklist I had to select the species from both checklists in the report wizard, otherwise I only got the records from the one specified. I had been living in blissful ignorance of this issue until I spotted an anomaly in the records being reported, thinking up until now that I was getting all the records.

Having found this thread I ticked "Use full translation to Preferred Term" under Options->General and now I get all the records regardless of which list is specified.

I just thought I'd highlight this for anyone else that might think they are getting all the records for a species when they may only be getting a sub-set....

Regards, Keith