2013-10-10 conference call¶
Upcoming¶
- call next week at usual time (Th 9am PT&Tucson/12pm ET)
- Mark and Brian will be available
- Paul will be on the call to talk about geoscrubbing
- Bob is traveling but may drop in
Availability¶
- Mark and Brian will be back next week
- See the *Google spreadsheet* (and please add your availability for future weeks once it's known):
Loading Google Spreadsheet...
Decisions made¶
VegBank validation¶
- OK to validate just one plot per project type (otherwise there would be too many rows to check)
- OK to validate just the core subset that's central to BIEN (Mike Lee)
- OK to try validating as one table for all the occurrences instead of 3 separate tables
- Mike Lee can split the extract into 3 tables if necessary
- extract should have one line per stem class or cover value
CVS validation¶
- will refresh CVS before validating it
- there are most likely no changes to the CVS schema, so we do not need to worry about column renames/insertions
To do for Bob and Mike Lee¶
review list of VegBank input columns and decide which are critical to have in VegBIENsee feedback
To do for Mike Lee¶
- send updated CVS data (MS Access file named
cvs-archive-<date>.mdb
)
To do for Aaron¶
Brad's attribution document¶
make Ramona's corrections with track changes turned on
VegBank validation¶
send list of VegBank input columnsall columns (286 columns), subset planning to exclude (203 columns)write script to subset the input columns to just what's in the outputseetaxon_observation.**.sample
(83 columns)send one-table VegBank extract to Bob and Mike Lee by next MondayVegBank.2013-10-10.6_plots.xls .- if not ready by then, only Mike Lee would be able to validate it (Mike Lee busy next Tuesday)
create 3-table VegBank extract once that's done, if requested by Bob and Mike Lee"I think that one table [is] fine for now. We will let you know if there is a problem." (Bob Peet) .
CVS validation¶
apply VegBank fixes to CVS (which has a similar schema)load refresh from Mike Leecreate CVS extract- ideally by end of next week (depending on when we get the refresh)