Project

General

Profile

Bug #2007

Status records duplicated when loading NatureServe comms

Added by Michael Lee over 17 years ago. Updated about 16 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
userLoad
Target version:
Start date:
03/10/2005
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
2007

Description

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


Related issues

Blocked by VegBank - Bug #1853: Need view for NatureServe to link to using their UIDs for comms and plantsResolved01/07/2005

Blocked by VegBank - Bug #1942: Implement ongoing automatic updates with NatureServeNew02/02/2005

History

#1 Updated by Michael Lee over 17 years ago

ditto for usages, which are children of status

#2 Updated by Michael Lee over 17 years ago

this fixed in the XSL for NEW plants and communities, but the update file WILL
still need some special processing.

#3 Updated by Michael Lee over 16 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.

#4 Updated by Redmine Admin over 9 years ago

Original Bugzilla ID was 2007

Also available in: Atom PDF