Found in the re-review of #260. Optional, but it changes whether a backlog row is closeable.
GO:0009878 and GO:0015992 sit in reports/research_grounding_backlog.tsv as UNRESOLVED, which tells a curator the identifier is bogus. It isn't — both were merged into successor terms. The answer the curator wants is the replacement id, and UNRESOLVED sends them off to re-research a question the ontology already answers.
OAK exposes this directly via term replaced by / obsoletes_migration_relationships.
Fix: on an unresolved id, look for a replacement and emit it as its own verdict (MERGED, say) carrying the successor CURIE, so the row can be closed by substitution rather than by investigation.
Found in the re-review of #260. Optional, but it changes whether a backlog row is closeable.
GO:0009878andGO:0015992sit inreports/research_grounding_backlog.tsvasUNRESOLVED, which tells a curator the identifier is bogus. It isn't — both were merged into successor terms. The answer the curator wants is the replacement id, andUNRESOLVEDsends them off to re-research a question the ontology already answers.OAK exposes this directly via
term replaced by/obsoletes_migration_relationships.Fix: on an unresolved id, look for a replacement and emit it as its own verdict (
MERGED, say) carrying the successor CURIE, so the row can be closed by substitution rather than by investigation.