Restore CKAN standard-variable autocomplete: label_contains + enable_ckan

[mosoriob]

Problem

The CKAN dataset form autocompletes MINT standard variables against this API. It is broken in production.

The widget was built against the v1.8.0 FastAPI catalog. Two behaviours it depends on were not ported to this service:

• label filters with _eq. A partial term matches nothing, so a suggestion only appears once the user types the entire variable name.
• enable_ckan does not exist. The response is the plain JSON-LD array. CKAN's parseCompletions reads item.name || item.Name || item.Format; our rows carry none of those, so every suggestion collapses to an empty string.

Measured against production before the fix:

label=a                        -> 0
label=land_surface_wind        -> 0
label=land_surface_wind__spee  -> 0
label=land_surface_wind__speed -> 1

Change

Two new query params on the generic list handler, both opt-in.

label_contains=<term> builds label: { _ilike: "%term%" }. % and _ in the term are escaped so they match literally. This matters: standard variable labels are underscore-heavy (land_surface_wind__speed), and an unescaped _ is a single-character wildcard in Postgres, which would make the search quietly wrong rather than obviously broken.

enable_ckan=true projects the result into {"ResultSet": {"Result": [{"Name": "..."}]}}.

label keeps its exact-match behaviour, so existing callers are unaffected.

Note on the API-design choice

I added a separate param rather than widening label to a substring match. label is live on a deployed API with consumers I cannot enumerate, and there was a test pinning _eq. Turning every resource's exact filter into a substring match seemed like the wrong trade for a fix aimed at one widget. Happy to collapse the two if you would rather label just do substring.

Why the openapi.yaml change is required

Both params are declared on /standardvariables. This is not only for docs: fastify-openapi-glue validates the querystring and AJV strips undeclared params before the handler runs. Implementing them without declaring them would compile, pass every service-level test, and still do nothing in production.

Tests

npm test — 134 passed, 38 skipped (was 130). npm run build clean.

15 new tests across two levels:

• src/__tests__/integration.test.ts — filter construction, wildcard escaping, label + label_contains combined, response shaping, enable_ckan=false not treated as truthy.
• src/__tests__/standardvariables-ckan-route.test.ts (new) — goes through the real Fastify router with Hasura mocked, covering the AJV stripping and the boolean coercion that a direct service call bypasses.

Deploying this

The CKAN side needs a matching one-line change, pointing its autocomplete at label_contains=? instead of label=? (ckanext-dso_scheming/mint_presets.json, in the ckan-docker repo). That change is prepared but not yet merged. The CKAN form stays broken until this is deployed.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Vh9z6U8JosPJnGqPNQf3fk