This documentation explains how an RDMO catalog and sensorsearch.toml work
together. It is intended for editors who want to reuse the Earth Sensor
catalog, adapt it to another catalog, or change which sensor registries and
metadata fields are synchronized.
The plugin supports four connected workflows:
- searching remote devices and configurations or missions;
- copying backend metadata into RDMO answers;
- deriving project-local device choices from selected configurations;
- refreshing metadata and synchronizing data-collection variables.
- Catalog editor guide explains the building blocks and gives a safe sequence for adapting a catalog.
- Configuration reference describes the TOML sections and how each setting relates to catalog elements.
- Earth Sensor catalog map lists the concrete page,
question, attribute, option-set, provider, and condition URIs from
testing/catalogs/earth-sensor+original.xml. - Operations and limitations describes runtime behavior, authentication, performance, and current backend limitations.
- Developer architecture describes module responsibilities and the service boundary used for synchronization logic.
- Development history tells the curated story of the plugin's evolution, major releases, and the design decisions behind its current architecture.
- SMS location and configuration-period remediation plan records the reviewer findings and the planned resolver, diagnostics, configuration, testing, feedback, and catalog-period changes.
- Configuration-period baseline and optional membership filtering supersedes the earlier period recommendation and treats the current Earth Sensor catalog as the compatibility baseline.
The repository-level sensorsearch.toml is the
authoritative deployment configuration and is packaged into the plugin wheel.
The Earth Sensor catalog used by this guide is
testing/catalogs/earth-sensor+original.xml.
The independently namespaced development mirror is
testing/catalogs/example_catalog_sensorsearch.xml;
its test-only profile is
testing/fixtures/sensorsearch-plugin-dev.toml.
Catalog and TOML configuration are joined by exact URIs. A question's visible text is not used for synchronization. When a question or attribute URI changes, update every corresponding TOML reference and optionset or condition reference.
The following identities must also remain distinct:
- device option IDs use prefixes such as
kitsms,gfzsms,ufzsms, ando2aregistry; - configuration option IDs use
kitcfg,gfzcfg,ufzcfg, ando2amission; - each configuration backend points to the matching device prefix so mounted devices can be materialized correctly.
For a new catalog, first import and test the Earth Sensor example unchanged. Then duplicate one complete workflow at a time. Start with search and a small metadata mapping, add configuration membership next, and add refresh or data-collection automation only after the collection attributes and indexes are correct.