Terminology Used in the Snolarkew Interface
This page explains the terms used throughout the Snolarkew platform and its supporting documentation. Understanding these terms will help you navigate the interface and interpret the information it presents.
Key terms and their meanings
Each term below is defined as it is used specifically within the Snolarkew context. Some terms may have different meanings in other settings.
Record
A single unit of information within the Snolarkew platform. A record consists of one or more fields, each containing a piece of information associated with the record's subject. Records are the basic building blocks of the platform's information store and are always assigned to a category before they are displayed in the interface.
Category
A defined grouping of records that share a common subject or type. Categories are created and maintained by the Snolarkew team. Each record belongs to exactly one primary category, though it may carry secondary tags that connect it to related areas. The category structure determines how records are presented in the navigation.
Classification
The process by which a record is reviewed and assigned to a category. Classification is performed by the team using internal criteria. It takes place before a record is made visible in the interface. Classification is not a public-facing process; users encounter its results when they browse the platform's categories.
Tag
A secondary label that can be applied to a record in addition to its primary category. Tags are used to highlight characteristics that the category label alone does not capture. A record may have no tags, one tag, or several. Tags are visible in the record display where they have been applied.
Intake
The process by which new information enters the Snolarkew system. During intake, the team carries out a preliminary assessment to determine whether the information falls within the platform's current scope. Information that does not meet the scope criteria is not retained and does not proceed to classification.
Review interface
The part of the Snolarkew platform through which users browse categories and read individual records. The review interface is a read-only environment: users can examine records but cannot modify them. The interface is designed to present information in a consistent, structured format regardless of the category being viewed.
Enquiry
A message sent to the Snolarkew team through the form provided on the Enquiry page. Enquiries may relate to a specific record, a category, an access request, a correction, or a general question about the platform. All enquiries are received and reviewed by the team and answered by email.
Access request
A specific type of enquiry in which a user asks to view or receive information from the platform that is not already openly available through the review interface. Access requests are reviewed individually by the team. The team determines whether access can be provided and in what form, based on the nature of the request and the category of information sought.
Correction request
A specific type of enquiry in which a user submits what they believe to be an error in a displayed record and requests that the team review and potentially correct it. Correction requests are assessed by the team, who will determine whether a change to the record is appropriate. The final decision rests with the team.
Scope
The defined boundary of information that the Snolarkew platform covers. The scope determines which records are eligible for intake and classification. Information that falls outside the scope is not included in the platform, regardless of its relevance to records already held. The scope is set by the team and may be revised over time.
Field
A named data element within a record. Each record contains one or more fields, and each field holds a specific piece of information about the record's subject. Field names are consistent across all records within a category, allowing users to compare records within the same category more easily.
Routing
The process by which an incoming enquiry is directed to the most appropriate member of the Snolarkew team. Routing is based primarily on the request type selected by the user in the enquiry form. It is an internal process and is not visible to the user; the user will simply receive a response from the team member who reviewed their request.
Terms specific to how the interface is described
What is meant by "available through the interface"?
When this document or any other page on the site refers to information being "available through the interface", it means that the information has been classified and can be viewed by navigating the review interface without submitting an access request. Not all information held by the platform is available through the interface in this way.
What does "determined by the team" mean in practice?
Several aspects of the platform — including access decisions, classification, and the scope of records displayed — are described as being "determined by the team". This means that a member of the Snolarkew team makes the relevant decision using internal criteria and professional assessment, rather than the decision being made automatically or delegated to the user.
Is there a difference between a "question" and an "enquiry"?
In everyday language, the terms are interchangeable. Within the Snolarkew platform, "enquiry" is the formal term used to describe any message submitted through the enquiry form, whether it is a question, an access request, a correction submission, or a general request for support. All such communications are handled through the same channel.
What is the difference between a "summary" and a "full record"?
In some categories, a brief summary of each record is displayed in the category listing page. The summary includes only a subset of the record's fields — typically the most identifying or descriptive ones. The full record contains all fields associated with the record. Whether the full record is available through the interface or requires an access request depends on the category and the team's access policy for that category.
Platform introduction
Return to the homepage for a summary of what Snolarkew provides and how to navigate the interface.
Platform OverviewScope and service structure
Read the full overview to understand what categories the platform covers and how the interface is structured.
FunctionsClassification and review capabilities
Learn how information moves through the intake, classification, review, and access stages of the platform.