Project

General

Profile

Actions

Bug #1767

closed

Loading plots causes duplication of stratumType for extant stratumMethods

Added by Michael Lee about 20 years ago. Updated about 18 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
userLoad
Target version:
Start date:
11/09/2004
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
1767

Description

not sure how the loader decides how to, but there are an unpredictable number of
duplicate stratumTypes that get created during XML loads. Needs to not do this


Related issues

Blocks VegBank - Bug #1049: need XML uploader to work with Usage as child of StatusResolvedP. Anderson04/25/2003

Actions
Actions #1

Updated by Michael Lee almost 20 years ago

fixes for xml loader also can be found on bug 1049

Actions #2

Updated by Michael Lee almost 20 years ago

This is different from most "matching" done between XML entities and VegBank
entities, which is done via AccessionCodes. For stratumType, there is no
accession code, but only the StratumIndex within the strautmMethod, which is
matched via accessionCode. So, stratumIndex should NOT be duplicated within one
stratum Method (our business rules page checks for this). This bug is here
because the loader is adding stratumTypes that are already in the database,
meaning that there are duplications of stratumIndex across different stratumType
records, all within the same StratumMEthod

Actions #3

Updated by P. Anderson almost 20 years ago

Appears to be fixed now.

Actions #4

Updated by Redmine Admin over 11 years ago

Original Bugzilla ID was 1767

Actions

Also available in: Atom PDF