feat(catalogue): add attributes for valid dcat

[BrendaHijmans]

Keep in branch for testing, not ready for merge

What are the main changes you did

• add attributes for valid dcat output

see https://github.com/molgenis/GCC/issues/1029

How to test

• explain here what to do to test this (or point to unit tests)

Checklist

• check Version number and bump
• dcat:theme = Health (Health / http://publications.europa.eu/resource/authority/data-theme/HEAL) > add in 'header rdf' > add in catalogue-reformat of model or rdf
• dcat:license in header rdf as placeholder
• would be nice to have some kind of conversion that takes all Resources that have an 'inSeries' pointing to them from CollectionEvents as DatasetSeries and all other as just Dataset.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[mswertz]

this looks good to me

[mswertz]

I think it is nice to make our data model closer to DCAT in areas where that makes sense such as these ones.

[YpeZ]

I have my doubts about the validity of creator being a ref_array in these tables. In Dublin Core this attribute is described as

An entity responsible for making the [resource].

They seem to be pretty strict about it, but having multiple creators is reasonable for larger resources such as Resources and Collection Events

[BrendaHijmans]

I healthdcat-ap the cardinality is 1…n. So I took that as our source of truth Op 12 feb 2025 om 16:45 heeft Ype Zijlstra ***@***.***> het volgende geschreven: I have my doubts about the validity of creator being a ref_array in these tables. In Dublin Core this attribute is described as An entity responsible for making the [resource]. They seem to be pretty strict about it, but having multiple creators is reasonable for larger resources such as Resources and Collection Events —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>