Status records duplicated when loading NatureServe comms
Concepts are successfully not duplicated, but status records (1 per concept) are
loaded each time they come up.
Should check to see if new status and if so load. NOT new if already in DB or
previously added in same transaction
Updated by Michael Lee over 17 years ago
this has to do with XML that NatureServe generates to load communities (and maybe plants, too) into VegBank. Since it's not VegBranch, there are oddites, such as a lack of primary keys in the XML document. This causes the loader problems, as the PK is used to track what's the same element and what isn't within the XML doc.