Appearance
Introduction to NOOSAdmin
What NOOSAdmin does
NOOSAdmin is a configurable application platform that brings together data, processing tools and independent services. It provides capabilities for managing access, collecting and exploring data, running processing workflows, and presenting information through dashboards and branded portals.
A project may have a database, an analytical model and several services developed by different teams. Making these components useful to people requires a shared application: a place to submit information, inspect records, initiate computation and view results. NOOSAdmin supplies these capabilities around the project's data and connected components.
The platform follows the project's data model. Tables describe the information being managed, ingress brings data into those tables, and processing tools produce results that can be explored or presented to users. Organisations, roles and user groups control access to platform functionality and entities.
Who it is for
Project teams and platform owners can use this guide to understand how NOOSAdmin could support an application and which capabilities are relevant to their work. Administrators can learn how data structures, access and user-facing content fit together. Technical contributors can see where external data sources, TypeScript processing and Docker-based computation participate in the platform.
The guide explains features and workflows conceptually. It does not require programming knowledge, although configuring scripts and integrating external computation involve technical work.
Main capabilities
| Capability | What it enables |
|---|---|
| Access management | Organise users, assign roles and grant groups permissions on platform entities. |
| Data collection | Receive submissions through push ingress or retrieve information through pull ingress. |
| Data exploration | Browse paginated records, combine filters and follow relationships between tables. |
| Processing and computation | Transform data with TypeScript processors and invoke external code through data runners. |
| Dashboards and pages | Present queried information in reusable views for selected groups. |
| Branded portals | Bring content and actions together through a portal with its own URL, branding and navigation. |
How the capabilities work together
Consider an equipment-monitoring application. This illustrative example recurs throughout the guide.
An organisation maintains equipment records and collects measurements. An external system submits readings through push ingress, or NOOSAdmin retrieves a file through pull ingress. Users inspect the stored measurements in an explorer. A processor calculates summaries, while a data runner invokes an external analysis model. Results stored in tables can then supply dashboards in a portal for the relevant user groups.
The application team chooses and configures the parts needed for its workflow. A project focused on collecting and exploring records may begin with tables, ingress and explorers. Processing and portals provide additional capabilities as the application develops.
Reading this guide
Start with Core concepts for the vocabulary used throughout the documentation. For a view of how features participate in complete scenarios, read Example workflows. If your focus is the experience provided to a particular audience, continue to Branded portals.