Project

General

Profile

Bug #2636

Better labels for ambiguous occurrences

Added by Robert Peet over 12 years ago. Updated over 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
atlas
Target version:
Start date:
11/01/2006
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
2636

Description

This is an upgrade; not an error.

Ambiguous identifications have a legend entry that states the name that was found ambiguous. For example, Carya glabra in NCU is ambiguous and has a legend notation of "Ambiguous identification: Carya glabra". It would be far more informative if the legend were to read "Ambiguous identification: Carya glabra OR Carya ovalis". (I realize that when all sources are on one sees "Ambiguous identification: Carya glabra, Carya ovalis", but this still refers to the labels on the specimens and not the concepts according to Weakley. In effect, I am suggesting we label ambiguous ids by Weakley concept lists, whereas we keep the other ids linked to the names in the databases from which they derive.

History

#1 Updated by Robert Peet over 12 years ago

Peter White writes:
I wonder if it should be Carya glabra AND/OR Carya ovalis. If the
record is based on lumping, but splitting is the standard, couldn't both
taxa be present in a county? That is, a county dot map represents more
than one specimen. Obviously one specimen has almost never two species,
except when a collector has mounted two twigs on one sheet thinking they
are the same, but they are not (I have seen this myself).

RKP responds:
Good idea. I think this expresses the situation more clearly.

However, I have some concerns.
1. AND/OR takes up more valuable real estate.
2. Maps are from the perspective of a single taxon, so we don't really care if both are present in the county -- that can be deduced from looking at the other map.

Let's see if Xianhua thinks there is space enough. Could get complex with something like Andropogon virginicus where several taxa have to be concatinated for the ambiguous Radford counties.

#2 Updated by xianhua liu over 12 years ago

I guess this issue has been resolved by listing individual sources for ambiguous records instead of lumping them in one group.

#3 Updated by Robert Peet over 12 years ago

fixed

#4 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 2636

Also available in: Atom PDF