Additional Notes
About This Page
This page collects terminology definitions, notes on information architecture, and supplementary guidance that may be helpful to users who are preparing to use the Mundrabeli platform or who want to understand more about how the system works in practice. It is not a duplicate of any other page on this site — it covers topics that are referenced elsewhere but not explained in full detail on the main pages.
Terminology
Category
A category is a named slot in the platform's classification hierarchy. Every record in the system is assigned to a category. Categories are defined by the platform configuration and cannot be created or modified by end users.
Domain Category
A domain category is a top-level classification — the broadest level of the hierarchy. It describes the general subject area of the records it contains. Domain categories are visible at the top level of the category panel in the review interface.
Sub-category
A sub-category is a classification level below a domain category. Sub-categories refine the classification further, grouping records by more specific characteristics within the broader domain. The hierarchy may include more than one level of sub-categories depending on the depth of the configuration.
Record
A record is a single item of information within the system. It belongs to exactly one category and displays a set of fields defined by the category's view configuration. Records are the atomic units that users review and act upon.
Field
A field is a named attribute of a record. For example, a record might have fields such as a title, a date, a status, or a reference identifier. Which fields are displayed in a view, and in what order, is determined by the category's configuration.
View
A view is the presentation of records belonging to a particular category within the review interface. Each category has a default view that shows a defined set of fields in a default sort order. Users can apply filters and change the sort order within a view without changing the view's configuration.
Access Level
An access level is a set of permissions associated with a user account. It determines which categories are visible to that user, which fields within those categories are displayed, and which actions are available. Access levels are assigned by the support team as part of the access process.
Enquiry
An enquiry is a message submitted through the contact form on the Enquiries page. It may be a question, an access request, a support request, or another type of message. Enquiries are categorised by the type selected in the form and routed to the appropriate part of the support team.
Information Architecture
The information architecture of the Mundrabeli platform is built around the principle that navigating information should be as predictable as possible. This means that the structure users encounter in one session should be identical to the structure they encounter in any other session, unless a deliberate configuration change has been made.
The hierarchy of domain categories and sub-categories is determined by the deployment's configuration. The configuration is designed to reflect the natural structure of the information being organised, so that classification decisions are consistent with how a knowledgeable user would intuitively group the same records.
Where the natural structure of a body of information is ambiguous — for example, where a record could plausibly belong to more than one category — the classification rules favour specificity over breadth. A record is assigned to the most specific category that accurately describes it, rather than a broader category that also includes it.
Navigating the Interface
New users sometimes find that the category panel is the most efficient starting point. By expanding domain categories and sub-categories from the top level down, it is possible to identify the right classification level for a task quickly, without needing to know in advance which category a specific record belongs to.
Once the right category is found, the view in the main area can be refined using the filter controls to narrow the display to records with specific field values. This combination of category navigation and field filtering is the primary approach the interface is designed to support.
Users who already know the category and field values they are looking for can often proceed directly to the relevant view using the category panel, skipping the top-level exploration step.
Preparing for Access
Before submitting an access request, users are encouraged to review the capabilities page to confirm that the platform's functions match their intended use case. This helps the support team respond more efficiently and reduces the likelihood that an access level needs to be adjusted after it has been assigned.
If you are unsure whether Mundrabeli is the right tool for your use case, the team is available to answer questions through the enquiries page before you submit a formal access request. There is no requirement to submit an access request before making general enquiries.
Contact
For any questions about the terms or concepts described on this page, please contact the support team:
Mundrabeli Information Technologies Inc.
1200 Bay Street, Suite 1700
Toronto, ON M5R 2A5
Canada
[email protected]
+1 (416) 555-0183