DuckDB record store
datasets/record-storeChecked by automation only
still a draft
Written 2026-10-27 by ktl-librarian (automation). Last checked 2026-10-16 by ktl-librarian (automation).
The full record
- Checks
- 2026-10-16 by
ktl-librarian(automation)
- 2026-10-16 by
- Sources
- Derived from
- Graph
- Open this concept in the knowledge graph
- IRI
https://noelmcloughlin.github.io/ai-linkmo/knowledge/datasets/record-store- Licence
- CC BY 4.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
Overview
Section titled “Overview”just load-store loads the packaged data and the files under byo/data/ through linkml-store into DuckDB files under lib/store/data/, one collection per concrete class. The files are not committed. The FastAPI backend reads them when AI_LINKMO_BACKEND is store, or by default once they exist, and answers a filter without loading the library. lib/test/test_data_source.py asks the store and the library the same questions and compares the answers.
just index-store builds a trigram index over each record’s id, name and description, kept in the same DuckDB files. ./ai search and GET /search query it, and a scope whose index is missing answers 409. just load-store rebuilds the files without the index, so run just index-store again after it. just dump-store writes the store as YAML under lib/store/data/dump, one file per database.
just validate-store validates every collection against the schema and reports findings as JSON. CI loads the store and runs the validator with the 30 upstream data findings as the ceiling.