Information Architecture: A Guide to Harvenlix Terminology

Purpose of This Page

This page introduces the terminology used within the Harvenlix platform and its supporting documentation. Understanding these terms helps users navigate the interface, interpret the information they encounter, and communicate clearly with the support team when raising an enquiry.

The definitions below reflect how each term is used within Harvenlix specifically. Some terms have broader meanings in other contexts; the definitions here apply to the platform's own information architecture.

Record

A record is a single unit of information within the Harvenlix platform. Each record represents one entry in the system and contains the structured data associated with that item. Records belong to one or more categories and carry a review state that indicates whether they have been examined by a user.

Records are the primary objects that users interact with when reviewing available information. They are displayed in a consistent format throughout the platform, regardless of their category.

Category

A category is a defined grouping of related records. The platform organises its information into categories based on shared attributes or subject matter. Each category has a label and a description that explains the type of records it contains.

Users navigate between categories using the platform's primary navigation. Within a category, records are presented in a structured list that can be browsed sequentially or filtered by relevant attributes.

Classification

Classification is the process by which incoming information is assigned to one or more categories within the platform. This process follows defined rules that are applied consistently across all records. The classification rules determine which attributes of a record are used to assign it to a category.

Classification is carried out when information enters the system. If an existing record's content changes in a way that affects its category assignment, it may be reclassified accordingly.

Review State

Each record in the platform carries a review state, which indicates its current position within the user's review workflow. The standard review states within Harvenlix are:

• Unreviewed — the record has not yet been opened or examined by a user in the current session.
• In review — the record has been opened and is being actively examined.
• Reviewed — the user has marked the record as having been examined.

Review states are user-facing indicators that help track progress through a set of records. They do not represent any form of external validation or quality assessment.

Enquiry

An enquiry is a submission made by a user through the platform's contact function. Enquiries may relate to access requests, questions about specific records or categories, technical questions about the interface, or general questions about the service.

Each enquiry is reviewed by the Harvenlix support team. The team may respond with additional questions, with the information requested, or with guidance on the appropriate next step. Enquiries are submitted through the enquiry page.

Interface Navigation

The Harvenlix interface is structured around a primary navigation system that allows users to move between categories and sections. Secondary navigation within each category allows users to access individual records and move between entries in a sequence.

Navigation follows a consistent layout throughout the platform. The position of primary navigation elements does not change between categories, which reduces the need for users to reorient themselves when moving between different sections of the platform.

Support Function

The support function within Harvenlix is the means by which users can raise questions, concerns, or requests directly with the support team. It is accessed through the enquiry page of this website. The support function is available to all users, whether or not they currently have access to the platform itself.

The support team can assist with questions about available categories, record interpretation, access arrangements, and interface use. It cannot guarantee any particular outcome in response to an enquiry.