Bring your own data (BYOD)
playbooks/bring-your-own-dataChecked by automation only
Written 2026-10-27 by ktl-librarian (automation). Last checked 2026-09-25 by ktl-librarian (automation).
The full record
- Checks
- 2026-09-25 by
ktl-librarian(automation)
- 2026-09-25 by
- Sources
- References
- Pointed to by
- Bring Your Own Data (related to)
- Graph
- Open this concept in the knowledge graph
- IRI
https://noelmcloughlin.github.io/ai-linkmo/knowledge/playbooks/bring-your-own-data- Licence
- CC BY 4.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
Bring your own data
Section titled “Bring your own data”- Author a YAML file conforming to the ai-atlas-nexus AI Risk Ontology schema (see the upstream util README).
- Drop it into
byo/data/, or add, edit or delete records there from the web UI’s curate mode (saved throughPUT /byo). The CLI, the API and the web UI pick it up with--byod. - Validate against the installed schema,
<site-packages>/ai_atlas_nexus/ai_risk_ontology/schema/ai-risk-ontology.yaml.docs/working-with-the-data.mdhas the commands: one finds that path for you, and the next runsuv run linkml validate byo/data/*.yaml -s "$SDIR/ai-risk-ontology.yaml".
The graph door is the exception. ./ai graph --export --byod writes the merged YAML graph including your files, but the Cypher export is built upstream from the packaged ontology, so ./ai graph cypher --export --byod is refused with a 400 rather than leaving your files out silently. just load-store and just build-browse-byod load your files into a database of their own beside the packaged data.
The nine byo/data/*.yaml files in the repository (FINOS AIGF plus eight framework encodings) are worked examples of this pattern, and each has a datasets/ concept in this bundle. Retired examples live in byo/olddata/.