You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CKAN has functionality to enable users to do certain jobs and benefiting from them (publishing metadata, searching through metadata).
Some of the jobs rely on using extensions (harvesting, working with DCAT data standard).
Some jobs are impossible to do without necessary connectors in place.
In order to know what are de-facto capabilities of CKAN and what we can promise to customers and users, we have to manage extended functionality.
We need to define which connectors and extensions we'd define as critical to customer success with CKAN in most cases. To be able to frequently check and maintain them.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The conversation on creating visualizations led us into the following logic:
CKAN has functionality to enable users to do certain jobs and benefiting from them (publishing metadata, searching through metadata).
Some of the jobs rely on using extensions (harvesting, working with DCAT data standard).
Some jobs are impossible to do without necessary connectors in place.
In order to know what are de-facto capabilities of CKAN and what we can promise to customers and users, we have to manage extended functionality.
We need to define which connectors and extensions we'd define as critical to customer success with CKAN in most cases. To be able to frequently check and maintain them.
Beta Was this translation helpful? Give feedback.
All reactions