Reference

Further Information: Terminology and Interface Concepts

This page explains the terminology Brinqavelo uses across its interface and documentation, and describes how key concepts such as classification and navigation are applied within the service.

Core Terminology

Classification hierarchy

The classification hierarchy is the organisational structure Brinqavelo uses to arrange its content. It consists of levels: broad categories at the top, narrower sub-categories below them, and individual items at the lowest level. Users navigate the hierarchy by moving from broad to specific, or by following cross-references between related items at the same level.

Category

A category is a named grouping within the classification hierarchy. Each category contains items whose attributes qualify them for membership in that group. Categories have labels that describe their scope, and they may have a short description to help users assess relevance before exploring further.

Item

An item is an individual unit of content within the service. Each item is assigned to one or more categories. When a user opens an item, they see its content, its classification attributes, and links to related items. Items are the leaf nodes of the classification hierarchy.

Attribute

An attribute is a property associated with an item that determines how it is classified. Attributes may describe the item's type, subject, source, date, or other relevant characteristics. An item with multiple attributes may qualify for membership in more than one category, in which case it appears in all applicable categories.

Related content

Related content refers to items that share attributes with the item currently being viewed. The service surfaces related content automatically to help users explore connections within the classification structure without needing to navigate back to the category level and search manually.

Access request

An access request is a submission from a user who wishes to view areas of the service or content that is not publicly visible. Access requests are submitted through the Get in Touch page and are reviewed by the support team. The outcome of a request depends on the nature of what is being requested and the scope of the service.

Enquiry

An enquiry is a message submitted by a user through the contact form when the available organised content does not address their need, or when they have a question about the service that is not answered by the documentation. Enquiries are distinct from access requests, which are specifically about requesting permission to view restricted content.

How Classification Is Applied

When content is added to Brinqavelo, it is reviewed against the existing classification hierarchy to determine which categories it belongs to. The review considers the item's subject matter, its format, its intended audience where known, and any other relevant attributes.

Items that do not fit an existing category may lead to the creation of a new category, or they may be assigned to the nearest applicable category with a note that they extend beyond its usual scope. The classification process is not fully automated: human review is involved in making or confirming the most consequential placement decisions.

The classification hierarchy is not fixed permanently. As the content set grows or as the service's scope changes, categories may be added, renamed, merged, or retired. Users who notice that an item seems misplaced or that a relevant category appears to be missing are encouraged to report this through the support channel.

Navigation Conventions

Brinqavelo uses consistent navigation conventions throughout the interface. Users who learn these conventions in one area of the service can apply them in other areas without re-learning the layout.

The primary navigation structure is hierarchical. The top level presents the main categories. Selecting a category reveals its sub-categories and, at the lowest level, its items. At each level, the interface shows the user's current position within the hierarchy.

Cross-references between related items operate independently of the hierarchical structure. Following a cross-reference moves the user to a different item within the content set, which may be in a different category. The interface indicates this movement so that users do not lose their sense of where they are.

All navigation within the service uses the same set of controls. There is no area of the service that requires a different interaction model. This consistency is intentional and reflects the service's approach to making organised information accessible to users with varying levels of familiarity with the platform.

Questions about terminology

If a term used in the Brinqavelo interface or documentation is not explained here, please contact the support team through the Get in Touch page. We will clarify the term and consider adding it to this glossary.