Installation
This section on 'Installation' can really be written only after the rest is complete. The contents of this page is just a set of ideas that may well have been deprecated already.
This page should only document the generic stuff. Any installation details that are specific to a tool SHOULD be documented in the page(s) that document the particular tool. Obviously, this page could mention the tools for which that is the case, and link to the associated sections.
TEv2 is a tool for curating terminology-related data from the perspective of a single scope. Installation comprises
- setting up, or appointing an (online) directory that will serve as a scope directory;
- creating a Scope Administration File (SAF), and providing the configuration of the scope and its terminology;
- installing the tev2-toolbox;
- integrating the tools with other tools, such as a CI/CD pipeline on github or gitlab, static site generators such as github pages or Docusaurus, etc. See also: Using the Tools.
Structure of Scope Directories
Depending on the other tooling that is going to be used, a scope directory has to be specified that is part of the (online) directory in which the terminology has to be used. The scope's scope administration file (SAF) specifies whatever needs to be administered for that scope; this file is maintained by the curators of the scope (using a regular text editor).
Curators must also specify a location (directory) within the scope directory where glossaries will be located. This directory, which is called the glossary directory or glossarydir is located within the scopedir, and contains all glossaries that are generated by and/or needed within the scope - as well as perhaps some other stuff.Integrating Scope Directories and the ToIP Terminology Toolbox
Content to be produced
Integrating Scope Directories and Third Party Rendering Tools
Semantic units are intended to also be used by/within third party rendering tools, such as [github pages](https://pages.github.com/), [Docusaurus](https://docusaurus.io/docs/docs-introduction), or LaTeXContent to be produced