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
{{ message }}
Repository navigation
Point to a CKAN dataset ID to retrieve files instead of a configured storage
#19
CKAN instances and extensions often have many integrations with CKAN datasets and CKAN resources. For example identifying who modified a dataset and/or resource, DCAT support, etc. It may be beneficial to have an alternative configurable option to retrieve the catalog.json, collections.json, GeoParquet files, and any other necessary files based on the resources associated with a specific dataset. Perhaps it could initially be a configuration option to provide the ID of a public CKAN dataset. Currently an issue that might arise is identifying when and who modified the files used by ckanext-gztr along with letting CKAN instance users who have access to modifying the CKAN dataset update those files in a manner they're used to rather than primarily the CKAN sysadmin. I'd suggest supporting both approaches (files and dataset with resources) and either can be configured by a sysadmin.
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
Uh oh!
There was an error while loading. Please reload this page.
CKAN instances and extensions often have many integrations with CKAN datasets and CKAN resources. For example identifying who modified a dataset and/or resource, DCAT support, etc. It may be beneficial to have an alternative configurable option to retrieve the
catalog.json,collections.json, GeoParquet files, and any other necessary files based on the resources associated with a specific dataset. Perhaps it could initially be a configuration option to provide the ID of a public CKAN dataset. Currently an issue that might arise is identifying when and who modified the files used by ckanext-gztr along with letting CKAN instance users who have access to modifying the CKAN dataset update those files in a manner they're used to rather than primarily the CKAN sysadmin. I'd suggest supporting both approaches (files and dataset with resources) and either can be configured by a sysadmin.All reactions