KYE Protocol™ CKAN Connector™
Govern CKAN datasets, resources, harvests, metadata changes and publication workflows with KYE Protocol™ authority, purpose, evidence and replay. V1 read-only + advisory; V2 write-back; V3 ckanext-kye plugin.
What the V1 connector does
- Portal inventory — organisations / datasets / resources / harvests / DataStore tables / users — all mapped into KYE Protocol™ entities.
- Authority gap detection — when a publish / update / delete action has no documented authority chain, KYE Protocol™ flags it.
- Evidence Pack™ emission — every governed action produces a signed kye.evidence.pack.v1 entry.
- Publication receipts — embeddable evidence badges that CKAN portals can show on dataset pages (the public sees the authority + evidence behind every publication).
V1 is read-only. No write-back, no enforcement, no package_update interception. Trust accrues from observation; V2 adds governed write-back. V3 ships ckanext-kye for in-CKAN UI integration.
The seven canonical CKAN schemas
Every CKAN object KYE Protocol™ governs lives under one of seven canonical schemas:
kye.connector.ckan.v1— connector profile contractkye.ckan_connection.v1— one connection per (tenant, portal) pairkye.ckan_portal.v1— portal metadata + risk tier + jurisdictionskye.ckan_dataset_binding.v1— CKAN dataset ↔ KYE Protocol™ dataset entitykye.ckan_resource_binding.v1— resource binding + data classificationkye.ckan_harvest_source.v1— trust + authority + schedule per harvestkye.ckan_action_event.v1— every CKAN Action API call with KYE Protocol™ authority + decision + evidence refkye.ckan_consultant_profile.v1— CKAN specialist marketplace listing
Get started
The CKAN connector is available as part of the KYE Protocol™ CKAN Connector™ SKU (£25k/yr add-on) or via the KYE Open Data Portal Audit Pilot™ (4-week pilot, £35k). Both ship with the canonical demo seed pack so you can see the connector at work against a representative public-sector CKAN portal before binding it to yours.
Apply for a CKAN Audit Pilot →
Positioning
KYE Protocol™ does not replace CKAN. It does not fork CKAN. It does not certify CKAN itself. KYE Protocol™ integrates with CKAN to add authority, evidence, consultant support and AI-era governance around data-portal operations.