Hi Carl,
I guess the main thing to say is that DKAN is not a distribution of CKAN. A bunch of people get confused on that point.
The main benefit of CKAN is the data specific community of developers and users surrounding it. The 200+ extensions work only for CKAN and target data management more so than web experience management.
It is relatively simple to use CKAN + Drupal in the same stack, which provides the benefit of using any Drupal distro , theme and modules while keeping the Data catalogue component purely focused on data management.
GovCMS, the Drupal distro, has some interesting modules being developed to work alongside CKAN. There is also CKAN extensions to support single sign on.
Within Drupal we simplified the user experience for uploading and viewing data but kept the power of CKAN available for ETL and post processing of data. This made it easy to provide an S3 uploader and more recently to script AWS Rekognition to markup every image asset with AI generated tagging.
Image harvesting from Twitter and Flickr is done via CKAN too :)
Although that data catalogue is only used for images and videos currently, we are building a Connector for TRIM and will soon have a PoC for public records/documents to support a proactive FOI use case. These word/PDF files will be discoverable via API in CKAN and we'll build an additional UI in Drupal to support the public discovery of FOI records.
So, my preference is using CKAN as a data catalogue and using Drupal, WordPress, SiteCore, etc to enable mashable web experiences to aid with information domain specific discovery. City employees with interest in service delivery/reporting maintain the web experience while information management specialists and data custodians maintain the CKAN data catalogue as a shared service.
Cheers,
Steven
--