Cognatrix 1.5.2

Cognatrix creates and maintains monolingual thesauri, dictionaries, taxonomies or similar information structures.
Supports Preferred Terms, Variant Terms, Facets and user-defined Attributes. Relationship types include Broader, Narrower, Related, Use, Synonym, Obsoletes. No design limits on number of: terms (education version 500 terms max); user-defined fields (eg Scope Note); user-defined attributes; or relationships. No design limit on tree depth.
Term names and user-defined fields can store up to 2 gigabytes of Unicode data. Exports XML in Zthes or Cognatrix formats (extensible helper application imports a number of XML formats).
Cognatrix generates publication-ready HTML using customizable templates and is completely self-contained
Main features:
- Maximum term length 2,147,483,646 bytes (~2 gigabytes). In other words, effectively unlimited.
- Length of scope notes 2,147,483,646 bytes (~2 gigabytes). In other words, effectively unlimited.
- Classification codes. User-defined attributes fulfill this requirement. Create a "Classification" attribute list, populate it with attributes, and attach them to the your terms.
- Notes on term history. There is no special field for maintaining term history. Simply create a user-defined field called "Term History".
- Notes on term usage. There is no special field for describing term usage. Simply create a user-defined field called "Term Usage".
- Origin/authority for terms. There is no special field for origin/authority information. In most cases, authority information can be described using attributes and origin information can be maintained in a user-defined field named "Origin". Note that all user-defined fields can hold active URLs.
- Term status (e.g. candidate). Candidate terms would normally be placed within an unpublished group. Other status information is typically best expressed using attributes.
- Other predefined attributes There are no predefined attributes. All attributes are user-defined.
- User-defined attributes Unlimited (see note).
- Case preserved.
- Case significant. All sorting and tracking of duplicate names occurs in a case-insensitive manner. All relationships are formed using unique IDs so the case of names is largely irrelevant.
- Symbols and spaces allowed in terms. Unicode® is supported in both item names and user-defined fields.