write tests about assets/misc/neon_nmdc_term_mapping.tsv divergence from schema

[turbomam]

assets/misc/neon_nmdc_term_mapping.tsv is still mentioning quality_control_report.status, which will be removed in the pending release

We shouldn't have any artifacts that mention patterns that are illegal in the released schema

• What is the role of assets/misc/neon_nmdc_term_mapping.tsv?
• Is it being programmatically accessed?
  • UPDATE: No, @sujaypatil96 uses files like these as inspiration for writing code with hard-coded configurations
  • UPDATE: It's hard to believe that a TSV file would ever provide the required flexibility and expressiveness
• Are there any related files that might be getting stale in the same way?

[turbomam]

Mark could write tests (that generate warnings, not failures) over the mapping files, but that will only check if nmdc-schema paths still exist, not if the mappings are proper.

Could just add a README to the mappings directory

[turbomam]

depth mapping is interesting too

depth source would ideally be lakeSampleDepth1 etc. but there is a lots of inter-field dependency here

TLDR flat file doesn't really capture the mapping!

[turbomam]

see also

• move all Neon mapping files to a single path #1719

[turbomam]

long term: could use linkml-transformer