Database Properties
Database Type: PostgreSQL - 13.1 (Debian 13.1-1.pgdg100+1)
Schema public
standard public schema
Tables
| Table / View | Children | Parents | Columns | Rows | Type | Comments |
|---|---|---|---|---|---|---|
| organization_managed_location_types | 0 | 2 | 2 | 0 | Table | Per-organization information about managed location types for business analytics purposes. |
| global_roles | 1 | 0 | 2 | 4 | Table | (Enum) System-wide roles that can be assigned to users. Global roles are not tied to organizations. These are generally for system or business administration; most users have no global roles. |
| upload_types | 1 | 0 | 3 | 3 | Table | (Enum) Types of user-uploaded files whose progress can be tracked in the uploads table. |
| notification_types | 2 | 1 | 3 | 24 | Table | (Enum) Types of notifications in the application. |
| upload_statuses | 1 | 0 | 3 | 10 | Table | (Enum) Available statuses of user-uploaded files. Uploads progress through these statuses as the system processes the files. |
| managed_location_types | 1 | 0 | 2 | 3 | Table | (Enum) Type of managed location for business analytics purposes. |
| user_preferences | 0 | 2 | 3 | 0 | Table | Client-defined preferences that should persist across browser sessions. |
| notification_criticalities | 1 | 0 | 2 | 4 | Table | (Enum) Criticality information of notifications in the application. |
| organization_report_settings | 0 | 1 | 2 | 0 | Table | Organization-level settings for quarterly reports. Project-level settings are in |
| upload_problem_types | 1 | 0 | 2 | 4 | Table | (Enum) Specific types of problems encountered while processing a user-uploaded file. |
| project_report_settings | 0 | 1 | 2 | 0 | Table | Which projects require reports to be submitted each quarter. Organization-level settings are in |
| user_types | 1 | 0 | 2 | 3 | Table | (Enum) Types of users. Most users are of type 1, “Individual.” |
| project_land_use_model_types | 0 | 2 | 2 | 0 | Table | Which projects have which types of land use models. |
| reports | 2 | 6 | 14 | 0 | Table | Partner-submitted reports about their organizations and projects. |
| organizations | 13 | 5 | 14 | 0 | Table | Top-level information about organizations. |
| regions | 2 | 0 | 2 | 9 | Table | (Enum) Parts of the world where countries are located. |
| report_statuses | 1 | 0 | 2 | 4 | Table | (Enum) Describes where in the workflow each partner report is. |
| notifications | 0 | 3 | 9 | 0 | Table | Notifications for application users. |
| organization_users | 0 | 5 | 7 | 0 | Table | Organization membership and role information. |
| countries | 7 | 1 | 5 | 249 | Table | Country information per ISO-3166. |
| facility_connection_states | 1 | 0 | 2 | 3 | Table | (Enum) Progress of the configuration of a device manager for a facility. |
| land_use_model_types | 1 | 0 | 2 | 8 | Table | (Enum) Types of ways a project’s land can be used. |
| projects | 24 | 4 | 10 | 0 | Table | Distinguishes among an organization’s projects. |
| app_versions | 0 | 0 | 4 | 2 | Table | Minimum and recommended versions for Terraware mobile apps. |
| facilities | 7 | 5 | 22 | 0 | Table | Physical locations at a site. For example, each seed bank and each nursery is a facility. |
| device_managers | 0 | 2 | 13 | 0 | Table | Information about device managers. This is a combination of information from the Balena API and locally-generated values. |
| files | 8 | 2 | 12 | 0 | Table | Generic information about individual files. Files are associated with application entities using linking tables such as |
| report_files | 0 | 2 | 2 | 0 | Table | Linking table between |
| roles | 1 | 0 | 2 | 5 | Table | (Enum) Roles a user is allowed to have in an organization. |
| report_photos | 0 | 2 | 3 | 0 | Table | Linking table between |
| country_subdivisions | 1 | 1 | 3 | 57 | Table | Country subdivision (state, province, region, etc.) information per ISO-3166-2. |
| user_global_roles | 0 | 2 | 2 | 0 | Table | Which users have which global roles. |
| upload_problems | 0 | 2 | 8 | 0 | Table | Details about problems (validation failures, etc.) in user-uploaded files. |
| internal_tags | 1 | 2 | 8 | 4 | Table | Internal (non-user-facing) tags. Low-numbered tags are defined by the system; the rest may be edited by super admins. |
| uploads | 1 | 5 | 11 | 0 | Table | Information about the status of files uploaded by users. This is used to track the progress of file processing such as importing datafiles; contents of this table may expire and be deleted after a certain amount of time. |
| users | 90 | 2 | 16 | 1 | Table | User identities. A user can be associated with organizations via |
| facility_types | 1 | 0 | 2 | 4 | Table | (Enum) Types of facilities that can be represented in the data model. |
| organization_types | 1 | 0 | 2 | 6 | Table | (Enum) Type of forestry organization for business analytics purposes. |
| organization_internal_tags | 0 | 3 | 4 | 0 | Table | Which internal (non-user-facing) tags apply to which organizations. |