One run of concordance build: it validates the configuration and the lock it names, fetches the sources, runs the inference chain and the checks, writes the model, the build log and one fragment per entity, then renders the site from those files alone. The build: block of the configuration says where it writes (output, ./dist), when it fails (fail_on.errors, fail_on.unconverted_max), how many mentions a page carries inline (mentions_inline, 20) and how much of a note enters the search index (extracted_text_max_chars, 20 000). The build block of the model is its only dated part.
Build
Properties3
- Application
- Concordance command line
- Domain
- Ingestion
- Status
- valid
3 declared keys. The rest of the file is free text.
See the neighbourhood map6 pages6Neighbourhood mapBuild
Neighbourhood map Build
Distance1 hop
229 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- InferenceTermspecializes1
- ModelTermspecializes50
- ConfigurationTermspecializes32
- LockTermspecializes9
- CorpusTermspecializes10
- SourceTermspecializes49
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.