> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/products/registry/farmer-registry/deployment/data-seeding.md). # Data seeding Turning on the Farmer Registry's sample, bulk and sanity data, the reporting views and the dashboards, and the install Jobs in the order they run. This page lists the steps and choices. What each kind of data is: [Data the registry can create](/products/registry/farmer-registry.md#data-the-registry-can-create) and, for all registries, [Country data & seeding](/products/registry/registry/deployment-and-extension/country-data-and-seeding.md). What the reporting views and dashboards are: [Reporting and dashboards](/products/registry/farmer-registry.md#reporting-and-dashboards). The registry's own configuration (registers, screens, DCI templates, approval policies) is always seeded by the db-seed Job. Everything below is optional. ## Before you install On the **commons-services** form: * **Dataset Themes** includes `agriculture` (the default) and **Load Datasets** is on. Without them the coded dropdowns are empty. * **Load Sample People** is on, if you want sample data. The Farmer Registry's Jobs read Master Data through its API, with the `-staff-portal` Keycloak client. That client needs read access to Master Data's `/catalogue` and `/samples`. ## Sample data 1. On the Farmer Registry form, turn on **Load Sample Data**. Turn on **Load Sample Images** too for profile photos. 2. Install or upgrade. 3. Check: the staff portal lists farmers numbered like the sample people, e.g. `FR-0007`, with lands `LAND-0007-1`. {% hint style="warning" %} If Master Data holds no sample people, the loader falls back to a CSV baked into the image and says so in its log. Those people's addresses do not match your country pack. Turn on **Load Sample People** on commons-services and upgrade both. {% endhint %} ## Bulk data 1. On the form, under **Analytics**, turn on **Generate bulk demo data**. 2. Set **Bulk demo farmers** if 100,000 is not the size you want. 3. Optional, in YAML: set `analytics.bulkSample.expectedCountry` (e.g. `ETH`) so the Job fails if Master Data holds another country. 4. Install or upgrade. Check the `-fr-bulk-sample` Job completed. Bulk generation needs Master Data's geography; the Job fails if it is not there. ## Sanity data Sanity data is created only with **Sanity - Run Full E2E** on. Its fixtures are never deleted, so use it only on a test environment. Steps: [Sanity testing](/products/registry/farmer-registry/deployment/sanity-testing.md). ## Reporting views On by default (**Build reporting views**). Choose the refresh interval in **Reporting data refresh** (cron, hourly by default; empty means never). Between refreshes, new farmers are not in reports. Check the `-fr-reporting-views` Job completed, and the CronJob `-fr-reporting-views-refresh` exists. ## Dashboards The dashboards are imported into the environment's Superset at install. To load them: 1. Install Superset with commons-services (**Install Superset?**). 2. Install or upgrade the Farmer Registry. 3. Check the `-fr-dashboards` Job's log says the dashboards were imported. If Superset was not reachable, the Job skips the import and says so. Upgrade the registry once Superset is up. To fail the install instead, set `analytics.dashboards.superset.required: true` in YAML. Bringing reporting up for a country: [Setting up reporting](/platform/platform-services/reporting-and-analytics/setting-up-reporting.md). ## Install sequence The install Jobs run as Helm post-install and post-upgrade hooks, in hook-weight order. Helm waits for each to succeed before the next, so **a failure blocks every Job after it**. | Weight | Job | Does | Runs when | | ------ | ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | | — | the `iam-register` Job | Registers the registry's roles and permissions in IAM. A regular Job, started with the pods; a failure does not fail the release | always | | 10 | `-db-seed` | Registry configuration, sample data, images, templates. Waits for AWE and for Master Data's geography | **Enable DB Seed** (on) | | 11 | `-sanity-pm-seed` | Registers the test partner in Partner Management, with its key and its scope policy for this registry (allowing the consents it signs itself) | **Sanity - Run Full E2E** | | 13 | `-sanity-data-seed` | The sanity farmer, Keycloak user and approver rule | **Sanity - Run Full E2E** | | 15 | `-registrant-auth-bootstrap` | Sets up the eSignet login farmers use before a credential is issued | credentials on | | 16 | `-agent-vc-register` | Registers the Farmer Credential with Inji Certify | credentials on | | 25 | `-sanity` | Runs the sanity suite | **Run Sanity Tests** (on) | | 40 | `-fr-bulk-sample` | Generates the bulk farmers | **Generate bulk demo data** | | 45 | `-fr-reporting-views` | Builds the reporting views | **Build reporting views** (on) | | 50 | `-fr-dashboards` | Imports the dashboards into Superset | `analytics.dashboards.enabled` (on) | Two dependencies are on other releases, which Helm cannot order: * **Master Data** must be seeded before db-seed (weight 10) and bulk generation (weight 40). Both wait for it, then fail with a clear message. * **Superset** must be reachable for the dashboard import (weight 50). The Job waits, then skips. {% hint style="warning" %} If Superset has no dashboards after an install, check the **earlier** Jobs first. A failed bulk Job (weight 40) stops the reporting views and the dashboard import from running. {% endhint %} ## For production Keep sample data, sample images, bulk data and the full e2e off. Keep **Enable DB Seed** and **Load Templates to Object Store** on. Details: [An empty install](/products/registry/registry/deployment-and-extension/country-data-and-seeding.md#an-empty-install-for-production). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.openg2p.org/products/registry/farmer-registry/deployment/data-seeding.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.