Home › Terminology

Terminology Used by Ashenquella

Definitions of the key terms used across this website and the Ashenquella service, explained in the context of information organisation.

Key Terms and Their Meanings

The following definitions explain how specific terms are used within the Ashenquella service and on this website. Where a term has a specific technical or operational meaning in this context, that meaning is described below.

Classification

The process of assigning an item of information to a defined category within the service's organisational structure. Classification determines where an item appears within the hierarchy and how it can be located by navigating the category tree.

Category

A defined grouping within the service's hierarchy. Categories may contain sub-categories and individual records. The category structure reflects the classification framework applied by the service to organise the information it holds.

Record

A single item of information within the service. Each record belongs to a category and is presented through the interface in a consistent format. Records are the individual units of information that users review when using the service.

Hierarchy

The organisational structure of the service, consisting of top-level categories, sub-categories, and individual records. The hierarchy determines how information is arranged and how users navigate from broad groupings to specific records.

Interface

The presentation layer through which users access and navigate the service. The interface reflects the underlying classification structure and provides a consistent view of categories and records at each level of the hierarchy.

Enquiry

A submission made by a user through the contact form. Enquiries may relate to access requests, questions about the service, requests concerning specific records, or other matters addressed to the support team. Each enquiry is reviewed individually.

Access Request

A specific type of enquiry in which a user asks to be granted access to the Ashenquella service. Access requests are reviewed by the support team. Access is not automatic and depends on the team's assessment of the request.

Support Team

The team at Ashenquella Limited responsible for receiving and responding to user enquiries. The support team reviews access requests, responds to questions, and handles requests relating to individual records. It can be contacted via the enquiry form or by email.

Structured Review

The process of examining records within the service using the interface's hierarchical navigation. Structured review is supported by the consistent formatting of records and the clear presentation of category relationships, allowing methodical inspection of available information.

Submission

Information provided to the service, either through the enquiry form or through the service's data entry mechanisms. Submissions are used to populate or update records within the classification structure, or to initiate an enquiry process with the support team.

Why Consistent Terminology Matters

The terms defined above are used consistently across this website and across the Ashenquella service. Using the same vocabulary when describing information or submitting an enquiry helps the support team understand your request accurately and reduces the likelihood of misunderstanding.

If you encounter a term on this site that is not defined above, or if the meaning of a term in a specific context is unclear, you are welcome to ask for clarification through the enquiry form. The support team will explain how the term applies in the context of your query.

The terminology used here reflects the service's design as an information-organisation system. Some terms may carry different meanings in other technical contexts. Where a term on this site could be interpreted in multiple ways, the definition given above reflects its intended meaning within the Ashenquella service.


Further reading: Service Overview · Platform Functions · Platform Details

Legal: Privacy Notice · Terms of Use