From: Vladimir G. <vla...@du...> - 2010-03-16 18:17:56
|
On Mar 13, 2010, at 1:44 PM, William Piel wrote: > A artifact of the March migration was that trees did not get their > proper "Tree Type" designation (i.e. consensus vs single). I have > created an easy look-up table containing legacy tree IDs and their > tree type designation. These designations need to be converted to > integers before updating based on a matching the legacy ID values. > > http://www.treebase.org/treebase/migration/Mar-10/tree_types.txt Bill, Here are the treetype entries in the DB: tb2migrplay=> select * from treetype; treetype_id | version | description -------------+---------+------------- 1 | 1 | Single 2 | 1 | Consensus 3 | 1 | SuperTree Here are the counts of distinct treetype names in your file: tb2migrplay=> select treetypename, count(*) from phtrtype group by treetypename; treetypename | count --------------+------- consensus | 2279 | 1 single | 4274 Simple Tree | 15 Questions: (1) Are SuperTree (in the dictionary) and Simple Tree (in your file) the same thing? If so, which one should remain in the DB? (2) The tree with the missing treetype is T391c2x7x96c15c45c54 -- what's up with it? Thanks, --Vladimir |