- Table of contents
- 2013-08-01 conference call
2013-08-01 conference call¶
Upcoming¶
- call next week canceled due to low availability
- next call on 8/15 (the week after next)
- Ramona will organize it
- Brad will be available
- should discuss which of the normalized derived columns are critical for the October deadline, and which are value-added
Availability¶
- most people gone next week
- See the *Google spreadsheet* (and please add your availability for future weeks once it's known):
Loading Google Spreadsheet...
Decisions made¶
target schema¶
- will be VegBIEN for the October deadline
however, this is not to imply that VegBIEN is better than VegCore. this decision was made only because of time constraints. - don't want to be in middle of switching to VegCore at deadline
- however, VegCore is non-lossy: all source-specific columns are stored in an hstore
- also, VegCore is much more maintainable because it doesn't require column-based import or the XPaths .
- VegCore out of scope for October, but should be part of BIEN (Mark)
completion of DB¶
- done when
normalized schema can handle all datasources, and all datasources have been validated (Martha) - test VegBIEN by
constructing scientific viewsand checking rowcounts must have attribution info (Martha)should have scientific views, but not necessary for October
derived columns¶
- these are value-added services, less important than the core DB
- they should be independent of the BIEN schema where possible
prioritized, using section #s from BIEN3_derived_data_products.docx:
5. data provenance, ownership, attribution and access conditions: (all) necessity rather than value-add (Martha)
see Datasource conditions of use, which also includes citations, contacts, etc.1. taxonomy: 1st priority (after attribution) (Mark, Martha)3. geography: equal to TNRS in importance4. cultivated- 2. phylogeny: nice to have, but can be added after DB (Mark)
- Mark, Brad, Martha, Brian E, Bob should review priorities
Martha's notes¶