Terminology used within the Briarvexen system
This page explains the key terms and concepts used to describe the Briarvexen platform on this website and within the interface. Understanding these terms helps users interpret platform descriptions accurately.
How to use this reference
The definitions below correspond to how each term is used within the context of Briarvexen specifically. Some terms have broader meanings in other contexts; the definitions here reflect their application to this platform. The list is ordered to follow the logical structure of the platform rather than alphabetically.
The organisational structure that governs how information is arranged within Briarvexen. The framework defines the categories, subcategories, and relationships between them. Information is assigned a position within this framework when it enters the system. The framework itself is not visible to users as a separate object; it is experienced through the category structure presented by the interface.
A named grouping within the classification framework. Categories contain records and may contain subcategories. A top-level category represents a broad subject area; subcategories within it represent more specific divisions of that area. When users navigate the interface, they move between categories and into the records they contain.
A category that exists within another category. Subcategories allow the classification framework to represent distinctions within a broader area without creating a flat list of unrelated entries. A subcategory inherits context from its parent category and adds more specific classification criteria of its own.
An individual item of information within a category. A record may contain text, structured fields, or other content depending on the category it belongs to. Records are the most granular unit of information accessible through the interface. Users examine records in the detail view when they wish to review specific content.
One level of depth within the classification framework. Moving from a top-level category into a subcategory moves the user one layer deeper. The Briarvexen system supports multiple classification layers, allowing complex subject areas to be represented with appropriate depth. The number of layers varies by category.
A signal presented within the interface that two or more records or categories share a meaningful relationship. Connection indicators are generated by the system based on the classification attributes of each record. They are informational and do not constitute a verified assertion that the connected items are related in any particular sense beyond the classification axis identified by the system.
The category or combination of categories to which a user has been given access through the enquiry process. Different users may have different access types reflecting different subsets of the classification framework. The access type is determined during the enquiry process and confirmed before the user begins navigating the interface.
A map of the classification framework showing the available categories and their arrangement. The index view provides an orientation reference for users navigating the interface. It shows which categories are available to the current user and how they relate to each other within the hierarchy. The index view does not show individual records.
A period of active navigation within the Briarvexen interface. A review session begins when a user enters the interface and ends when they exit. The system may record information about review sessions for operational purposes. Session context — such as which categories have been visited — may or may not persist between sessions depending on the access arrangement.
A record that has been generated through a defined review process and assigned to a specific classification position based on that process. Structured observations differ from general reference records in that they represent the output of a defined analytical step rather than a description of a subject area. The methodology behind a structured observation is not independently verified by Briarvexen.
A message sent to the Briarvexen support team through the contact form on the Enquire page. An enquiry may be a request for access, a support question, or a general question about the platform. Submitting an enquiry does not constitute an agreement or guarantee any particular outcome. The support team reviews each enquiry and responds as appropriate.
The Briarvexen Technologies Ltd team responsible for responding to enquiries, managing access arrangements, and assisting users who have questions about the interface or the content they encounter. The support team can be reached via the enquiry form or by email at [email protected].