-
Notifications
You must be signed in to change notification settings - Fork 0
Use Case: Search
Implementation: #8
Most of the search functionality will be handled by our CKAN instance. However, CKAN lacks some features: parent-child relationships of datasets (hierarchies, collections of datasets); harvesting of observedProperty (part of our own DCAT extension relevant for scientific data); returning search results as a list of DCAT documents (currently custom JSON format). Some of these missing features could be implemented as CKAN plugins or improvements to existing plugins to improve the data we can query via the API.
TBD
- parent-child relationships
- harvesting of observedProperty
By using the ckanext-dcat extension, CKAN can already expose the full catalog as DCAT catalog under the root URL via content negotiation. No server-side filtering (except paging) is possible. However, adapting the central CKAN API to return DCAT may be more complex and shall be out-of-scope for the demo portal since we have a low number of datasets and can load the full DCAT catalog within the demo portal (followed by client-side filtering).