Bug #2656

County lists should include ambiguous records

Added by Robert Peet over 15 years ago. Updated over 14 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


Currently ambiguous occurrences are not so annotated in the county lists. Also, ambiguous taxa are not handled properly in the list generation. For example, if you generate a list of taxa for Orange County, you get Acer rubrum, but not Acer drummondii. However, if you generate maps of these two taxa, both are present in Orange County only as ambiguous occurrences. The list should provide a result consistent with that of the maps.


#1 Updated by xianhua liu over 15 years ago

It is realy hard to do concept-based search by county. First step is to search all names recorded in all data sources in the county. Second step is to map all these names to Alan Weakley's concepts based on the standards the hosted data sources follow and the relationships of concepts in these standards to that of Alan Weakley's standard. If there is a relationship, even it is ambiguous, we can show the related Alan Weakley concept in the list. But what if there is no related Alan Weakley concept? Maybe we only show those that somehow related to Alan Weakley's concepts?

#2 Updated by Robert Peet over 15 years ago

Ambiguous county occurrences will need to be flagged as such.

Concepts not mapped to Weakley concepts should have their concept authors listed.

#3 Updated by Robert Peet about 15 years ago

My main concern is that this is such a complex query that performance will be terrible. I am willing to drop this bug if XIanhua considered the generated query too complex to achieve acceptable performance.

#4 Updated by Robert Peet over 14 years ago

Rethink we funding available

#5 Updated by Redmine Admin about 9 years ago

Original Bugzilla ID was 2656

Also available in: Atom PDF