Since 0.6.0 each extraction_method value carries an ECO term in the LinkML schema (meaning:, see docs/STANDARDS.md), but reports do not show them. Add an opt-in way to include the ECO code for every evidence item in a validation report, so downstream systems that speak ECO can use it directly.
Constraints
- Opt-in only. The default report must stay byte-for-byte identical, because committed benchmark results and audit hashes depend on it. Suggested:
bioevidence validate --annotate-eco and a matching keyword argument in Python.
- Read the codes from the schema (
SchemaView(...).get_enum("ExtractionMethod")), do not hard-code them, so the mapping has one source of truth.
Where to look
src/bioevidence_validator/engine.py (RecordValidator.validate builds the report), src/bioevidence_validator/cli.py
tests/test_standards.py shows how to read the meanings
Done when
Since 0.6.0 each
extraction_methodvalue carries an ECO term in the LinkML schema (meaning:, seedocs/STANDARDS.md), but reports do not show them. Add an opt-in way to include the ECO code for every evidence item in a validation report, so downstream systems that speak ECO can use it directly.Constraints
bioevidence validate --annotate-ecoand a matching keyword argument in Python.SchemaView(...).get_enum("ExtractionMethod")), do not hard-code them, so the mapping has one source of truth.Where to look
src/bioevidence_validator/engine.py(RecordValidator.validatebuilds the report),src/bioevidence_validator/cli.pytests/test_standards.pyshows how to read the meaningsDone when
docs/STANDARDS.mdanddocs/ENGINEERING.md