The METPO-proposal generator here emits a definition_source (IAO:0000119) column. In v4 it correctly points at TraitMech provenance (e.g. TraitMech:data/.../ph_phenotype...yaml#...), which is right.
But where a proposed term aligns to an existing ontology class (OMP, MICRO, PATO, GO, ...), that equivalence is a mapping, not definition provenance, and should not go in definition_source. definition_source = "where the definition text came from"; cross-ontology equivalence is separate.
Proposal: emit ontology equivalents as mapping annotations with IRIs (skos:exactMatch / skos:closeMatch / skos:narrowMatch, or oboInOwl:hasDbXref) in a dedicated column; keep definition_source for citations (PMID/DOI/BacDive/ISBN/TraitMech URIs).
Cross-repo cleanup hub: berkeleybop/metpo#344.
🤖 Generated with Claude Code
The METPO-proposal generator here emits a
definition_source(IAO:0000119) column. In v4 it correctly points at TraitMech provenance (e.g.TraitMech:data/.../ph_phenotype...yaml#...), which is right.But where a proposed term aligns to an existing ontology class (OMP, MICRO, PATO, GO, ...), that equivalence is a mapping, not definition provenance, and should not go in
definition_source.definition_source= "where the definition text came from"; cross-ontology equivalence is separate.Proposal: emit ontology equivalents as mapping annotations with IRIs (
skos:exactMatch/skos:closeMatch/skos:narrowMatch, oroboInOwl:hasDbXref) in a dedicated column; keepdefinition_sourcefor citations (PMID/DOI/BacDive/ISBN/TraitMech URIs).Cross-repo cleanup hub: berkeleybop/metpo#344.
🤖 Generated with Claude Code