Additional Notes
Supplementary guidance on terminology and interface conventions used within Nettlewyck.
Purpose of this page
This page provides supplementary explanations of the terminology, structural concepts, and interface conventions used across the Nettlewyck service. It is intended to help new users orient themselves before beginning an active session, and to clarify language that may be used differently in this context than in everyday usage.
The definitions and descriptions here are specific to the Nettlewyck service and may not correspond to how the same terms are used in other systems or technical documentation.
Information architecture in Nettlewyck
The Nettlewyck service is built around a layered information architecture. At the broadest level, data is organised into domains — broad subject areas that define the outer boundary of what is held within a given section of the interface. Within each domain, data is divided into categories, which are more specific groupings of related records.
Within a category, individual items are called records. Each record contains one or more fields, which hold the specific pieces of information associated with that item. The relationship between domains, categories, records, and fields forms the structural backbone of the interface.
This layered approach is intended to make navigation predictable. Once a user understands the domain and category structure relevant to their account, they can locate specific records more efficiently than in an unstructured list.
Classification and labelling
The classification system assigns one or more labels to each record based on the content of its fields and its relationship to the category structure. Labels are applied by the service's classification logic and are visible in the interface alongside each record.
Labels are descriptive rather than evaluative. They indicate what a record is, not whether it is significant or actionable in any particular way. Decisions about the significance of a record remain with the user.
Where a record fits more than one classification, all applicable labels are displayed. Users can filter by label to see all records sharing a particular classification across categories.
Glossary of service terms
Domain
The top-level organisational grouping within the Nettlewyck interface. Domains define broad subject areas and contain one or more categories. Users navigate between domains using the main navigation panel.
Category
A subdivision within a domain. Categories group records that share common characteristics relevant to the domain's subject area. A domain will typically contain several categories.
Record
An individual data entry within a category. Records contain one or more fields and may be linked to records in other categories where a relationship exists.
Field
A specific data point within a record. Fields hold individual pieces of information such as dates, identifiers, descriptions, or numerical values, depending on the record type.
Classification label
A descriptor assigned to a record by the Nettlewyck classification system. Labels indicate the type or character of a record and can be used as filter criteria when browsing the interface.
Summary panel
A consolidated view that aggregates key information from a category or domain. Summary panels are designed to give users an overview before entering detailed record review.
Filter
A control that narrows the visible set of records based on one or more criteria. Filters can be applied sequentially and removed individually without resetting the broader navigation state.
Session
An active period of use within the Nettlewyck interface. The session history records which records and categories have been visited, allowing users to return to earlier points without re-navigating from the start.
Access enquiry
A request submitted through the enquiry form to initiate the access review process. Submitting an access enquiry does not confer access; it begins a review that may lead to access being configured.
Notes on the enquiry and review process
Users who are new to the service often have questions about what to include in an access enquiry. The most useful enquiries describe the type of information the user needs to organise, the approximate scale of the dataset they intend to work with, and any particular classification or review requirements they have in mind.
It is not necessary to describe technical requirements in detail. The Nettlewyck team will ask clarifying questions if more information is needed before the account can be configured appropriately.
The enquiry form accepts general enquiries as well as access requests. Users who simply want to ask a question about the service before committing to a formal access request are welcome to do so. There is no obligation to proceed further once an enquiry has been submitted.