OpenCatalogi
The public-facing software, dataset, and API catalogue. Drops into your , surfaces every register as a searchable entry, federates to data.overheid.nl out of the box.
One catalogue, every register, every public link.
Connect OpenCatalogi to your registers, configure once, and your team is publishing searchable entries the same morning. Citizens land at jouwgemeente.nl/catalogi and find what they need without writing a Woo-verzoek.
Federated search by default.
Search runs across every register on your install plus every catalogue you've federated with. Results stay sovereign, no central index.
DCAT-AP profile, NLDS-aligned.
Every entry exports as DCAT-AP and NLDS metadata. data.overheid.nl picks it up without manual upload.
Citation-stable URLs.
Every catalogue entry gets a permanent identifier. Tweede Kamer-vragen and audit trails keep working through reorganisations.
WOO publication flow.
Eleven Woo-categorieën each get a register; the catalogue surfaces them at jouwgemeente.nl/woo with audit log and retention policies built in.
Open, forever.
Every entry exportable to plain JSON. The day you uninstall is as easy as the day you installed. No vendor lock-in, ever.
Partners shipping OpenCatalogi
Implementation, hosting, and integration partners that deliver OpenCatalogi to their customers. Pick the partner you already work with, or one whose stack matches yours.
Ship Conduction to your customers.
Three tiers: Host (ship our apps), Service (SLA + third-line support), Certified (trained, joint roadmap, tender-eligible). The apps stay open source, the relationship stays direct.
Apply through Support →Four steps, one configuration pass.
The same pipeline applies to a software catalogue, a Woo-portal, or a public API directory. Configure the connector, point it at your register, the catalogue lights up.
- Spreadsheets
- Databases
- REST / SOAP
- Legacy systems
- Citizens
- Partners
- API clients
- Auditors
Federated catalogue, register-aware, dashboard-ready.
Scroll the cards. Each pins as you reach it; the next slides up to cover.
One catalogue, many publishers.
OpenCatalogi indexes registers across organisations and federates to data.overheid.nl. Search once, find every published record. No central database, no nightly import.
See the catalogueEvery entry is a typed register row.
OpenCatalogi reads OpenRegister directly. Schema changes flow through. Citation-stable IDs land in the catalogue automatically.
See OpenRegisterWhat you publish, you can chart.
MyDash reads the same registers OpenCatalogi indexes. Publish a dataset and a graph of it shows up on the dashboard the same morning.
See MyDashOn every Nextcloud dashboard.
Install OpenCatalogi and the home screen tracks what got published, what was searched, and what other gemeenten are federating from you.
Recent publications
Last items added to the public catalogue. Category hex, title, federation status.
Catalogue stats
Three KPIs at a glance: total publications, federated downstream, queries this week.
Federation status
Who is consuming your catalogue, who is publishing back. Mint = healthy, orange = retry, red = down.
One catalogue, surfaced wherever you ask.
Three integration paths that take the published catalogue beyond its own page, into the wiki, the workflow tools, and the AI assistant.
Embed a live catalogue query inside any wiki page. Procedure docs cite the canonical dataset, not a snapshot. The wiki stays explanatory; the catalogue stays authoritative.
See the wiki macroThree apps that fill the catalogue.
OpenCatalogi surfaces what's already typed. These apps fill, connect, and extend the registers OpenCatalogi reads from.