Project

General

Profile

Bug #705 ยป notes_beta_comm.txt

Michael Lee, 04/23/2003 01:09 PM

 
1
COMMUNITY LOADING COMMENTS (Lee):
2
---------------------------
3
db structure comments
4
-------------------------------
5
commConcept.conceptDescription should be renamed commDescription
6
commStatus.partyComments should be renamed commPartyComments
7
*Status.*parent_ID are named *Status.*parent (fullstop) - we should pick a name and go with it.  
8
  How painful is it for you to change to without the "_ID" at the end of the parent fields?  I have a fair amount of code on top of it, but not too much.  One of us must change.
9

    
10

    
11
ERRORS IN LOADING:
12
--------------------------------------------------
13
*****Usage loads name_ID as the same number for each system of a plant, but loads the commName as different names.
14
     Name_ID should always match commName field, as commName field is a denormalization of commName_ID in a table.
15
     For example:
16
     PK     commname_id  commname            cmconc_id usagestrt usagestop cmnmstat  commprty  classsystem
17
     17530  17718        CEGL004677          6153      11/26/97            Standard  19        CEGL
18
     17531  17718        Andropogon ger...   6153      11/26/97            Standard  19        NVC
19
     17532  17718        Big Bluestem - (... 6153      11/26/97            Standard  19        English Common
20
     
21
     CommName 17718 corresponds to "Andropogon gerardii..." name, so the middle record is OK.
22
     The top record should have commName_ID = 17719
23
     the last record should have commNaME_ID = 17720
24

    
25
questions, mostly for Bob:
26
---------------------------
27
***Do we want to keep the KEY values from ecoArt like "G.4" and "SC.13" and "SG.36" -- these not currently stored with us, just "V.A.5" type names, except for Alliance and Assoc, which have A.xxx and CEGLxxxxxx
28

    
29
Subgroup names will be repeated, as they are always one of : "Natural/Semi-natural" or "Planted/Cultivated"
30
*** Do we want to add the Group name to the front of this so as to make the subgroup names unique for each subgroup.  Otherwise, we have duplicated names per classSystem per Party with a status of "Standard" which seems not useful.
31

    
32

    
33
picky items:
34
------------
35
reference records should really contain a "shortName" of "USDA2000" or "EcoArt2002" to help id ref's in queries
36
not sure I like classSystem names.  "NVC" seems like an inherently unspecific name - NVC what?.  Does "CEGL" really apply to names like "A.196" and "V.1.N.a" ? wouldn't "formation" be better?  Also, we need to be careful with "common names" vs. "scientific names-translated" (They seem similar, but slightly different)
37

    
38

    
39
summary of what I'm looking at:
40
-------------------------------
41
(ASSOC)
42
concept# : 6153, based on "CEGL004677", reference = EcoArt [correct]
43
status   : parent = correct Alliance, level=Assoc (correct), status="standard" (correct) startdate good, similarly as alliance below, this updated after originDate, use the update value for date?
44
usage    : errors as name_ID does not match name - see above
45
correlation: empty, but that's ok for now for communities
46
---
47
(ALLNC)
48
concept# : 916, alliance that is parent of above assoc., reference = Ecoart, based on name = "A.1192" [correct]
49
staus    : parent good , allianceOriginDate used for date, but the EcoArt update field is later - maybe use Update field instead ??
50
usage    : same name_ID issue as above. otherwise OK
51
---
52
(FORMATION)
53
concept# : 539, formation that is parent of above alliance, ref = ecoArt, based on name "V.A.5.N.a" [correct]
54
status   : parent good, date good
55
usage    : same issue as above with name_ID otherwise OK
56
---
57
(SUBGRP)
58
concept# : 299, ref= "ecoart", based on "V.A.5.N" [good]
59
status   : parent good, date good
60
usage    : same issue as name_ID above.  Here, we also run into a new issue in that the name is "Natural/Semi-natural" may not be the name we want, as it will be reused for many other subgroups. It seems to rely on the group name to get a real name, ie. "Temperate or subpolar grassland -- Natural/Semi-natural"   Is the latter what we really want?
61
---
62
(GRP)
63
concept# : 168, ref='ecoArt', baed on "V.A.5" [good]
64
status   : parent good, date good
65
usage    : same name_ID issue, otherwise OK
66
---
67
(SUBCLASS)
68
concept# : 54, ref EcoAry, basd on "V.A" [good]
69
status   : good
70
usage    : same name_Id issue, otherwise OK
71
---
72
(CLASS)
73
conecpt# : 43, ref EcoArt, based on "V" [good]
74
status   : good
75
usage    : same name_ID issue, otherwise OK
76
-----
77
summary of concepts queried above:
78
concid    name_id ref_id      commname (that concept is based on)
79
43        86        1         V
80
54        108       1         V.A
81
168       336       1         V.A.5
82
299       598       1         V.A.5.N
83
539       1078      1         V.A.5.N.a
84
916       2024      1         A.1192
85
6153      17719     1         CEGL004677
    (1-1/1)