ckanext-actor-registry
Keeps a shared registry of publishers (organizations, people) and contact points for CKAN metadata. Datasets refer to stable registry IDs, so a publisher’s or contact point’s details are corrected once instead of in every dataset. CKAN organizations stay separate from the metadata roles. It installs from PyPI with pip install ckanext-actor-registry.
Features
- Management pages for publishers and contact points (editors create and edit; merging and deletion for sysadmins).
- Inline creation while editing a dataset, with pickers for publisher and contact points, and per-user recent choices.
- A migration page that turns CKAN’s free-text Author and Maintainer fields into shared contact points, in rounds, and never changes the originals.
- A cleanup page for inactive or missing references.
- Optional DCAT-AP 3 export through ckanext-dcat (publishers as foaf:Agent, contact points as vcard:Kind), so the export says what the dataset page says.
- Scheming field types and example schemas; English by default with a Swedish translation.
Use Cases:
Catalogues where the same publisher or contact appears on many datasets and the copies drift apart: municipalities, agencies and other data portals that need consistent, exportable DCAT-AP metadata. It also helps portals that want to move away from free-text contact fields without losing existing data.
Dataset URL: View on CKAN