search

ckan / ckan

CKAN is an open-source DMS (data management system) for powering data hubs and data portals. CKAN makes it easy to publish, share and use data. It powers catalog.data.gov, open.canada.ca/data, data.humdata.org among many other sites.
https://ckan.org/
Other
4.42k stars 1.98k forks source link

Align CKAN metadata schema to DCAT & DCAT-AP #2091

Closed groundrace closed 9 years ago

groundrace commented 9 years ago

CKAN license metadata fields are bound to to the dataset while DCAT license metadata is associated to the resource so that a dataset may have multiple file each one with a different license. I believe it could be worth to align CKAN to that model

davidread commented 9 years ago

Do you have any examples of datasets which use different licences for different parts of the data?

wardi commented 9 years ago

-1 from me too. I'm sure data users would prefer if all the datasets on a site (or all the sites) had a single license, this seems like moving in the wrong direction.

Any site is free to add an extra field to their resources that indicate a license per-resource, and change the dataset license to stay where to find that information. I was hoping to implement a complete DCAT schema on top of CKAN with the scheming extension, so thank you for pointing out this difference.

davidread commented 9 years ago

Closing issue as no response. Feel free to reopen to continue.

ondics commented 2 years ago

Our project experiences with CKAN is that quite different resources are attached to datasets in the CKAN filestore, e.g. excel-files, images, csv-files, shape-files, and so on.

Considering the creation processes of this resource files, there may apply different licenes for these files. E.g. images could have licence constraints that don't allow to change the licences to the dataset licence.

So we need per-resource licences in the CKAN core that can by managed at the user interface.