1

Re: Recorder changes names

I had this problem reported to me today by one of our users and I've been able to reproduce here. Here are the steps to reproduce:

1. Bring up Data Entry > Enter a species record.
2. Look for the lichen called Cladonia coniocraea on the preferred checklist by typing clcon and hitting Enter.
3. Finish entering the record.
4. Look in the obs hierarchy for your record and you should see an observation for Cladonia humilis

Now, in the preferred checklist for lichens, Cladonia coniocraea is a synonym of Cladonia humilis, so I can see that the actual name is being displayed in the hierarchy. The recorded name is present in the determinations tab, so it looks like the preferred name of the taxon is being displayed in the hierarchy. The fact that there's a difference between the two is obviously going to be very confusing to users.

Is this correct behavior on the part of Recorder?

Charles

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

2

Re: Recorder changes names

It is correct, in that its as designed, but it might be confusing and might need redesigning!

What's happening here is that the search on a list includes the synonyms, so you have actually selected a non-preferred term from the preferred list - perhaps this is the first thing to change.

The second issue is that if you determine against a non-preferred term, then you can only see this in the determination record - the observation hierarchy node always shows the preferred term.

John van Breda
Biodiverse IT

3

Re: Recorder changes names

Thanks John. I did indeed get the sense that it was designed this way. It would be interesting to hear what others think, but, after bouncing it off one of our users here, this is how I think the design should work:

When the user selects a non-preferred name, a warning should pop stating something along the lines of "You have selected a non-preferred taxon name. The preferred name for [taxon user entered] is [the preferred name]. Would you like to change the name you entered to the preferred name?" Or something along those lines. Then I think the actual name that was entered should be displayed in the hierarchy. Having said this, it's still very useful being able to browse with preferred names visible, so perhaps an option in the same vein as the display common names option might be an idea; i.e. the user could choose whether to have preferred names visible or the actual name entered visible.

Charles

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