Which report were you using? If it was an xml report you have written yourselves, you will need to take account of the fact that observations could be input using different lists. System supplied reports should take account of this if ‘Use Full Translation to Preferred Term’ on the General tab on Tools - Options is ticked although the places for occurrences report doesn’t, as Dave Giffen at KMBRC and others have found. This is a longstanding problem that I have been alerting users to on the training courses I run for years. It is a pity John’s fix http://forums.nbn.org.uk/viewtopic.php?pid=5419#p5419 didn’t make it into v6.15. Unfortunately JNCC’s resources don’t run to fixing all reported problems so they aim to fix the highest priority ones. The release notes that accompany each release will indicate what has been fixed but not always in terms that are easy to understand unless you are familiar with the reported problem. If, as John says, it is a fairly small task to change this report to use the NameServer, we may see it included in a release sooner rather than later although the places for occurrences report could do with a more comprehensive overhaul.

Hi Rob,
I don't disagree there is a bug here, but I think the analysis is not quite right. The way reporting works in Recorder is that there are 3 components. Firstly, the filter (what records go in the report). Secondly, what attributes are being included. Thirdly, what will be done with the output (results grid, printable layout, snapshot etc). When you define a report in the Wizard, you are specifying all 3 of these components. But when you re-use that report in various ways, you are replacing one of the components. For example, if you select this report as an existing attribute selection whilst using the Report Wizard, you are only choosing to re-use the attributes part of the report. When you right click on any node in a hierarchy and select the Quick Report option, you are specifying a complete replacement filter for the report but re-using the attribute selection and output of the report. You can't expect it to hybridise the original method of selecting the records to include with your new one. If you wanted to run Report X as it was originally intended then you have the Run Reports dialog.

BUT, that does not get us away from the fact that you would quite rightly expect the use of a taxon in the hierarchy as a report filter to fully respect the Use Full Translation to Preferred Term option. As far as I can see you are right, this option is being ignored. I will make sure this is added to the buglist for consideration for the next version.

An update on this - the Quick Reports generated by the Taxon Dictionary will properly respect the Use Full Translation to Preferred Term option in the next release of Recorder.