Database Schema¶

Kamerplanter uses ArangoDB as its primary database — a multi-model system combining document and graph database capabilities. All entities are organized as document collections; relationships are modeled as edge collections in the named graph kamerplanter_graph.

Overview¶

Document Collections¶

Master Data (REQ-001)¶

Species — field propagation_methods¶

The propagation_methods field is an array of PropagationMethod enum values documenting which propagation techniques are typical for the species. Allowed values:

seed · cutting · division · rhizome_division · bulb · tuber · offset · grafting · layering · spore · runner · leaf_cutting · self_seeding

The array is optional (default: empty list) in the SpeciesCreate schema and a required field in SpeciesResponse (returned as an empty list when not populated). All pre-loaded crop species seed data (143 species) is fully populated.

Species — field propagation_months¶

The propagation_months field is an array of integers (list[int], range 1–12) indicating in which months vegetative propagation (division, cuttings, offsets, runners, etc.) is most suitable for the species. Month numbers are deduplicated and sorted ascending on the server side.

Distinction: propagation_months covers vegetative propagation timing only. Sowing windows (generative propagation from seed) are represented by the separate fields direct_sow_months, indoor_start_months, and transplant_months.

Example: Anemone hupehensis (Japanese anemone) — propagation_months: [3, 4] (division in early spring, before new growth begins).

Species — field propagation_notes¶

The propagation_notes field is an expert free-text field capturing practical propagation knowledge that cannot be expressed in structured fields like propagation_methods or propagation_months — typical failure points, species-specific substrate or temperature requirements, acclimatisation steps, and similar success factors.

Distinction: propagation_notes is plain free text for qualitative expert knowledge. Structured timing belongs in propagation_months; technique classification belongs in propagation_methods.

Population: All 183 species with populated propagation methods in the seed data include a notes text.

Locations and Infrastructure (REQ-002, REQ-019)¶

Plant Instances and Runs (REQ-013)¶

Planting run states:

planned → active → harvesting → completed
                             → cancelled

Irrigation and Fertilization (REQ-004, REQ-014)¶

Pest Management — IPM (REQ-010)¶

Harvest (REQ-007)¶

Tasks and Workflows (REQ-006)¶

Authentication and Users (REQ-023)¶

Tenants and Memberships (REQ-024)¶

Roles per tenant: admin, grower, viewer

Care Reminders (REQ-022)¶

Onboarding (REQ-020)¶

Miscellaneous¶

Edge Collections (Graph Relationships)¶

Master Data Graph¶

Location Graph¶

Plant Instance Graph¶

Planting Run Graph¶

Tank and Fertilization Graph¶

IPM Graph¶

Harvest Graph¶

Task Graph¶

Tenant Graph¶

Indexes¶

Kamerplanter automatically creates the following indexes on startup:

Tenant Data Isolation¶

All tenant-bound resources carry a tenant_key field. The FastAPI dependency require_permission() automatically checks on each request whether the requesting user is a member of the corresponding tenant.

Global resources (no tenant binding): species, cultivars, botanical_families, pests, diseases, treatments, starter_kits

Tenant-bound resources: sites, locations, plant_instances, planting_runs, tanks, fertilizers, nutrient_plans, tasks

Technical Notes for Developers¶

• Collections and the named graph are automatically created and migrated by ensure_collections() at backend startup.
• Add new collections or edge definitions to collections.py — they are created on the next startup.
• AQL queries use FOR ... IN GRAPH kamerplanter_graph exclusively for graph traversals.
• _key and _id are ArangoDB-internal identifiers. Application keys (e.g. instance_id) are separate fields with hash indexes.

See Also¶

• API Reference
• Environment Variables
• Backend Architecture