Review and Classification Tools in the Dromelwyn System
Dromelwyn provides four main tools for working with organised information. Each is described here in detail — what it does, how it fits within the system, and what users can expect when engaging with it.
The Four Tools Explained
These tools represent the current scope of the Dromelwyn system. They are not exhaustive of all possible information-review approaches, but they address the primary ways users interact with classified content.
Content Mapping
Content mapping is the process by which the system establishes how different categories of information relate to one another. Before a user can navigate the system effectively, the system must first define the shape of its information space — which categories exist, how they connect, and what boundaries separate them.
In practice, content mapping produces the navigational structure that users encounter when they enter the system. Items appear in locations determined by their classification, and adjacent items share defined relationships. This makes it possible to move from one category to related categories without needing to return to a top-level menu at each step.
The map is not a visual diagram that users interact with directly. It is the underlying logic that determines where information sits and what the system treats as equivalent, adjacent, or separate. Users benefit from it through the consistency and predictability of the interface.
- Establishes relationships between information categories
- Determines navigational proximity of content items
- Allows sequential review of related categories
- Reduces reliance on keyword or free-text search
Item-Level Inspection
Item-level inspection is the function through which users examine a single item in detail. When a user selects an item from the classification view, the system opens a detailed view that presents all available descriptive information associated with that item.
The inspection view is formatted to make comparison straightforward. Where an item has multiple attributes, they are displayed in a consistent order across all items of the same type. This means that reviewing several items in sequence does not require re-learning the layout for each one — the same fields appear in the same positions regardless of which specific item is open.
Inspection is read-only. Users cannot edit, annotate, or submit changes to item information through this function. The function is designed for review and information-gathering, not for data entry or modification of the system's records.
- Presents structured detail for selected items
- Applies consistent field layout across all item types
- Supports sequential comparison of multiple items
- Does not allow modification or annotation of content
Category Filtering
Category filtering allows users to narrow the scope of what they are reviewing without navigating away from the current view. By applying one or more filters, users reduce the number of visible items to those that match specific attributes. Items that do not match the active filters are hidden from view but are not removed from the system.
Filters can be applied in combination. A user reviewing items within a particular classification can apply a secondary filter based on a different attribute, producing a refined view that reflects both criteria simultaneously. Removing a filter restores the items it had hidden.
The filtering function is intended to help users manage large sets of categorised content without requiring expertise in the system's underlying structure. It is a practical tool for directed review rather than an analytical or reporting function. The results it produces reflect the content available in the system at the time of use.
- Reduces visible items to those matching selected criteria
- Supports multiple simultaneous filters
- Does not permanently remove or archive items
- Restores hidden items when filters are cleared
Enquiry Handling
Enquiry handling is the function through which users communicate with the Dromelwyn support team. It receives submitted enquiry forms, routes them to the appropriate team member, and provides a structured record of the request.
When a user submits an enquiry through the Connect page, the request is received by the support team rather than processed automatically. A team member reviews the enquiry and provides a response that addresses the specific points raised. The time taken to respond will vary depending on the volume of enquiries and the complexity of the request.
Enquiry handling does not produce automated determinations. The system does not assess, score, or categorise enquiries algorithmically before a team member reviews them. All responses are composed by the support team based on the content of the enquiry and the information available to the team at the time of response.
- Receives and routes user-submitted enquiry forms
- Routes requests to the appropriate team member
- Responses are composed by the support team, not automated
- Does not generate automatic determinations or assessments
How Access to the System Works
Access to the Dromelwyn system follows a defined sequence. Understanding this sequence before submitting an enquiry helps ensure that requests are processed efficiently.
-
Read the available system documentation
Before submitting any enquiry, users should review the system overview and this functions page. This ensures that expectations are aligned with what the system actually provides, and that the enquiry is relevant to the system's scope.
-
Identify the specific area of interest
Enquiries are easier to process when they specify the part of the system or the type of information relevant to the user's situation. General enquiries about the system can be answered with reference to the documentation, so enquiries that go beyond publicly available information are more useful.
-
Submit a detailed enquiry through the Connect page
Use the contact form on the Connect page to send a structured request. Include a description of what you are looking for, your reason for enquiring, and any relevant context that might help the support team provide a useful response.
-
Await review by the support team
The support team reviews each enquiry in the order it is received. Response time depends on enquiry volume. The team may request clarification if the enquiry requires additional context before it can be addressed.
-
Receive a response and follow any next steps indicated
The team's response will address the enquiry directly and, where appropriate, outline what further steps are available. Access to specific system areas, where applicable, is confirmed separately following the team's review of the enquiry.
Questions About the System?
If the available documentation does not answer your question, the support team is available to help. Use the Connect page to send your enquiry.