A quick ‘hello’ from me and the team at Etch - we’re a digital customer experience consultancy and have recently started work on a new directory product for Southampton City Council. We look forward to sharing our journey with the community here, and I’ve no doubt my colleagues will be along in due course to discuss technical topics and challenges!
We recommend that a directory publishes data via an Open Referral UK compliant API. If you’re customer experience experts, you’re probably also developing one or more front ends on the directory which will read your own API. Of course, you may add extra fields/properties that are not in the standard but needed in your case.
Do stay in touch and let us have your API endpoint to take a look at when it’s ready.
Yep, we’re doing exactly that - building an ORUK compliant API, with custom properties added for our frontend (which we’re basing on the awesome Scout project BTW).
We’re really pleased to announce that our directory product has gone live today for Southampton City Council, at Directory.
We took the awesome Scout project (with a few tweaks) but used the (equally awesome and open-source) Umbraco CMS to provide an editor-friendly backoffice, with an ORUK compliant API. We’ve still got some features we’re working on for a subsequent release, but we and Southampton City Council are really pleased with what we’ve acheived.
We’ll be putting together a full case-study over the coming weeks, but any questions, just ask!
This is great news. We’ve added the Southampton/Etch Open Referral UK API feed to the Dashboard and API Query tool.
With the growth in suppliers supporting the ORUK standard, there should now be no good reason for any UK council to procure a directory that does not support the standard.