Skip to content

Gallery

Public projects use linkml-term-validator in several patterns: CI gates, curation workflows, schema-edit hooks, anti-hallucination checks, and ontology-label validation for mapping tables.

This page is based on public GitHub code search results reviewed on July 2, 2026. It is illustrative rather than exhaustive; private repositories, package-index mirrors, generated traces, and incidental mentions are excluded.

Projects

Project How it uses linkml-term-validator Evidence
ai4curation/ai-gene-review Validates GO and other ontology term IDs/labels in mapping sets and gene-review YAML files. Several just recipes run validate-data with --labels and a project OAK config. justfile, src/ai_gene_review/cli.py
monarch-initiative/genesets Builds a multi-validator curation pipeline: LinkML structural validation, linkml-term-validator validate-data, reference validation, and a project-specific obsolescence sweep. python/genesets-workflows/src/genesets_workflows/curation/validate.py
monarch-initiative/mic-ingest Uses term validation as an anti-hallucination check for a micronutrient knowledge base. Recipes validate individual nutrient files and all nutrient files with labels and oak_config.yaml. justfile
monarch-initiative/dismech Wraps the CLI for stricter CI behavior, treating warning output as fatal when validating data terms. scripts/run_term_validator.sh
cmungall/nmdc-bermap Validates schema enum meanings, database terms, generated profile terms, and SSSOM profile mappings with project-specific OAK configuration. project.justfile
bridge2ai/data-sheets-schema Runs schema term validation from an editor/agent hook after schema-file edits, reporting ontology term issues during authoring. .claude/hooks/term_validator_hook.py
Cellular-Semantics/evidencell Declares linkml-term-validator as a dependency and includes smoke tests that pin expected CLI availability for project validation recipes. pyproject.toml, tests/test_tool_interfaces.py

Usage Patterns

These projects show several recurring patterns:

  • Schema authoring checks: run validate-schema after editing LinkML schemas.
  • Data curation gates: run validate-data against curated YAML files before merge or release.
  • Label-pair anti-hallucination: require both ontology ID and label to match.
  • Project OAK configs: keep ontology adapter choices in version-controlled oak_config.yaml.
  • Strict CI wrappers: treat warnings or unexpected validator output as release-blocking.

If your public project uses linkml-term-validator, open an issue or pull request with a stable repository link and a short description of the validation workflow.