[Babase] conversion run?

Karl O. Pinc kop at meme.com
Thu Jun 7 14:32:45 EDT 2007


On 06/07/2007 12:48:04 PM, Lacey Maryott wrote:
> YAY!!!! no errors!!! :-D  Thats really great.  In that case, shall I  
> go ahead and add in the other years today and tomorrow (through 88)?

Ok.  I've two compare files.

papio.biology.duke.edu:/biology/groups/babase/biograph.diff
papio.biology.duke.edu:/biology/groups/babase/members.diff

I'm not bothering to compare other tables because I don't
see where they would be changed by the census update,
although I can if anybody wants me to.   (BIOGRAPH
gets Statdate updated.)

Falstaff is changed in BIOGRAPH.  I think you did this
manually.

There's a couple of hundred of differences in MEMBERS.
These need to be reviewed for accuracy, unless you
want to wait and do it all at once when you're done.
(Again, I think Falstaff shows up in a lot of rows.)

At least some of the differences seem to be at the end of the
time period.  Individuals wind up in group 9.0 because
they've not been censused in a while.  I'd expect them
to be back in the right group once you put in more data.
(The "old" census rows don't interpolate so won't
keep individuals out of the unknown group (9.0)
if there's no recent "regular" censuses.)

There's always the option of adding manual census
rows (Status of M or N) to get the interpolation "right",
although of course you need to know what the interpolation
is doing to tell if it's really wrong.

Note that I've not compared MEMBERS.Origin and
MEMBERS.Interp because they'll obviously be different.

I'll give a call and we'll see where we go from here.

Karl <kop at meme.com>
Free Software:  "You don't pay back, you pay forward."
                  -- Robert A. Heinlein



More information about the Babase mailing list