New issue 449 by dustymc: Taxonomy: Expand nomenclatural code
http://code.google.com/p/arctos/issues/detail?id=449
Expand the functionality of Nomenclatural Code to allow collections to pick
any number of nomenclatural codes that are relevant to them, and show only
names that fall under those codes in picks.
This will allow us to:
1) Include non-compliant names in Arctos taxonomy (eg, Acer pseudo-platanus
as a non-compliant synonym of A. pseudoplatanus)
2) Filter collection picks to exclude non-compliant names, botanical names
for zoological collections, etc.
3) Include non-biological taxonomies (eg, for ethnology)
This can be funded as part of the UAM nonbiological collections grant.
Comment #1 on issue 449 by dust...@gmail.com: Taxonomy: Expand
nomenclatural code
http://code.google.com/p/arctos/issues/detail?id=449
Nomenclatural code may not be the right variable - we may need to do
something like let collections write sql ("PHYLCLASS IN ('.....')") or ???
to pick taxonomy.
May also need to partition taxonomy table for performance reasons.
Agree with comment 1. Ideally, collections could set filters on most
columns. A lepidopterist, for example, would probably pick the Order
Lepidoptera, and often be looking at substantially simplified picks, and
perhaps improved performance just in terms of loading the picks. Can't
think why anybody would go below order...