Project

General

Profile

Breadcrumb alternatives

  • We are using a new strategy to deal with the hierarchical structure of plots data, which now requires no modifications to the input data.
  • Previously, each nested level of data (e.g. stems) needed to be materialized with "breadcrumbs" for the primary keys of all ancestor tables (plots, projects) in addition to its immediate parent (organisms).
    This enabled the child table entries to be matched up properly with their parent entries in the DB, which themselves first needed to be looked up using their parent entries.
  • Now, every VegBIEN table with a sourceaccessioncode (input's primary key) also has a datasource_id, and the sourceaccessioncode is globally unique within the datasource.
    This enables the immediate parent of a child row to be looked up using just its own sourceaccessioncode, without needing its ancestors' sourceaccessioncodes as well.