1

Re: TIXILIX and Preferred TIXILIX in Rucksacks

Their are many Taxon_list_item_keys (TIXILIX) for a taxon - each having a single PREFERRED_TIXILIX.

Our database has entered a taxon from a number of different lists.

I want to report on this taxon - and so build a rucksack using the preferred TIXILIX for this taxon.

Does this single key refer BACK to the multiple keys and hence report reliably on all the different ways of entering a taxon?

And hence I can safely build rucksacks from the Preferred TIXILIX?

Cumbria Biodiversity Data Centre
Tullie House Museum

2

Re: TIXILIX and Preferred TIXILIX in Rucksacks

Hi Matt

Your best bet is to join to the Index_Taxon_Name table and use the Recommended_Taxon_List_Item_Key, because this gives you a single preferred item for each group of synonymous taxa. If you use the preferred information within the Taxon_List_Item table that only gives you the preferred name within the list. For example, if there are 2 lists, each containing 2 names for the same species, the items will have a different preferred taxon list item key in the Taxon_List_Item table depending on the list they are from. They will, however, all have the same Recommended_Taxon_List_Item_Key.

Best Wishes

John van Breda
Biodiverse IT

3

Re: TIXILIX and Preferred TIXILIX in Rucksacks

Matt, the category under which you've posted would indicate that you're trying to write an XML Report. Is this indeed so, or are you referring to reporting (via the Report Wizard) within Recorder itself?

Charles Roper
Digital Development Manager | Field Studies Council
http://www.field-studies-council.org | https://twitter.com/charlesroper | https://twitter.com/fsc_digital

4 (edited by Matt_tullie 24-07-2008 12:15:25)

Re: TIXILIX and Preferred TIXILIX in Rucksacks

Im endeavouring to build a ruksak to cross reference from the report wizard.

I am only slowly moving towards tailor made xml reports.

It comes from the niggling thought that our observations aren't being reliably pullled out from the keys that Im providing.

This maybe a leftover from the data transfer from recorder3 - this put a lot of our bat data (for instance) in as  recorder 3 taxon terms.

When I was plotting bat distribution i needed to pull chiroptera from both MAMMALIA and RECORDER3 dictionaries to show all of our data.
This I didnt expect, thinking the preferred lists would reference everything else.

SO, I then wanted to report on (in this example) the bats. I build a ruksak from the rec_taxon_list_item_keys.
The question is whether the recommended taxon list item key (which is the same for noctule in both MAMM and Rec3 dictionaries) pulls out all noctules by referencing backwards through all three taxon_list_item_keys that the taxons have been added as.

So wider than that - I build a ruksak from the recommended_taxon_list_item_keys that are pulled out on the basis of legislation and it will report everything I expect it to report.

Thats what drives it. 

M

NB - Ive got Sally R here (on a training course obviously) who is furnishing me with accepted truths on this.

Cumbria Biodiversity Data Centre
Tullie House Museum

5

Re: TIXILIX and Preferred TIXILIX in Rucksacks

Yes, it's a good question. I don't know the definitive answer because I only very rarely use rucksacks. Hopefully John or Sally or Steve can post the answer on here.

Charles Roper
Digital Development Manager | Field Studies Council
http://www.field-studies-council.org | https://twitter.com/charlesroper | https://twitter.com/fsc_digital

6

Re: TIXILIX and Preferred TIXILIX in Rucksacks

Hi Matt

Rather than answer your question directly, if I can explain a bit of background I hope it will save you and others a lot of time. In theory, the Report Wizard is able to detect all the synonymous names for something when you report on it. For example, if you select Chiroptera from the Mammalia list with the Expand Taxon Groups checkbox checked, then anything within the branch of the list starting at Chiroptera will appear in your report, even if it is a synonym or a term from another list. The problem stems from the fact that the dictionary supports 2 methods of identifying when 2 terms from 2 different lists actually represent the same taxon. We have been discussing with JNCC changes for the next release that will standardise on one of these methods.

To test if this was your problem, I went to Rhinolophus ferrumequinum in the Taxon Dictionary and compared the entry in the Mammalia list with the Recorder 3.3 list. What I noticed was that the "Other checklists" section on the right for each entry did not include the entry from the other list. This indicates that the dictionary does not contain the correct links to identify these 2 terms as the same thing using the original method. Fortunately the new method (driven by the NAMESERVER table) does identify these as the same thing because they have the same recommended taxon list item key.

The good news is you can change an option in Recorder to change which of the 2 methods it will prioritise when trying to calculate the list of terms that mean the same as the item you have selected. Go to the Tools\Options dialog and check the box titled Use Full Translation of Preferred Term on the General tab. This will enable the NAMESERVER powered method which as you have observed, is generally a lot more accurate. Hopefully if you do this, you can then use the Report Wizard to report on Chiroptera from the Mammalia list and it will pick up any bats from any list including Recorder 3.3.

As to your original Rucksack question, if you use the recommended taxon list item key in the rucksack and report on it, then you will have the same issues as before unless you check the Full translation option, because the old method of identifying terms that mean the same probably won't recognise the Recorder 3.3 bats as being the same as the Mammalia bats.

Best Wishes

John van Breda
Biodiverse IT

7

Re: TIXILIX and Preferred TIXILIX in Rucksacks

John,

Thank you for that - very thorough.

It reiterates what Sally R was explaining last week (to give appropriate dues).

The full translation checkbox is the clincher.

(I slightly ponder why would you not want the full translation option but...'shrug')

The remaining call would be for documentation on the queries /searches /actions within recorder, and how the data model is utilised from within the program.
I know that 6.13 is becoming more intuitive but recorder retains odd behaviours that could do with a bit of explaining. Just one for the long term that.


MAtt

Cumbria Biodiversity Data Centre
Tullie House Museum

8

Re: TIXILIX and Preferred TIXILIX in Rucksacks

I agree, it would be nice to have more documentation on the model and how Recorder uses it. Also as to the full translation option, we have already been discussing this with JNCC with a view to removing the option so it is always enabled in the next release. So it is something we are well aware of.

Best Wishes

John van Breda
Biodiverse IT