Super Issue: Evaluate OAK success, comparing SOIL curated terms, & values submitters have used for NCBI and NMDC mongo

[mslarae13]

OAK output for each environmental triad term & the soil query will go into google sheets

• 1 sheet for each environment (soil)

Tabs

• read me
• 3 separate tabs for environmental triad slots
  • Columns provided:
  • Envo term name found by OAK
  • Envo ID found by OAK
  • Term description
  • what part / how / why the query included it (possible programatic? if not, leave out)
  • Matched NMDC permissible value (from the submission portal enum)
    • Unmated items should still appear, (OAK & manually curated)
    • Matched NMDC mongo values
    • Unmated items should still appear
    • Matched NCBI values
    • Unmated items should still appear
  • Version / iteration of the query (HOW? TBD)
  • A free form notes column to add comments

When updating OAK queries based on feedback, specific terms should NOT be individually or manually removed. Elimination/manipulation should ALWAYS be done via a general change to the query. When the query is changed, the values in the google sheet will need updated.

• [ ] Query NMDC mongo and NCBI for values provided for each term and include in google sheet
• [ ] #847
• [ ] #848
• [ ] #849

TBD:

• Who / how to include values that exist in NMDC mongo and NCBI in these sheets? & match?
• How do we show / track the iteration of the OAK queries & each matched list?

[mslarae13]

@Natalie-Winans will share her work for mining NCBI for term uniqueness & use within an extension.