Support DCAT Catalogue CKAN natively

[hcvdwerf]

In CKAN, catalogs are typically managed as datasets (or packages), which are the core units of organization for data in the system. Each dataset can represent a collection of resources, metadata, and related information. However, when you want to represent a catalog of datasets (i.e., a collection of datasets grouped together in a higher-order structure), CKAN doesn't natively support a formal "catalog" type but instead uses dataset types and groups or organizations to create similar structures. How can we handle catalogs in CKAN? Without loosing relation with dataset and keep hierachie

Thanks in advance!

Options where we can think of to work around:

• Package relationships (package_relationships_list) - It's a way to create dataset to dataset relations
• Groups - You can leverage the n-n relationships between datasets and groups, and create a group that represents the catalog you are managing. In our instances we opted to match groups to DCAT themes, but that is not a strict guideline for anyone. In general a group is just a collection of datasets that share a membership.
• Using https://github.com/ckan/ckanext-hierarchy you can create sub-organizations. Not sure if this really matches your use case, but it gives a tiny bit more flecibility
• Custom dataset schema property - You can always expand the schema of the datasets with a new field to match which "catalog" it belongs to, and therefore manage them this way.