Add missing fields#352
Merged
amercader merged 40 commits intoSep 24, 2025
Merged
Conversation
…orrectly via In_Series
…series-serialisation Support rdf dataseries serialisation
- provenance_activity - qualified_attribution - quality_annotation
- provenance_activity - qualified_attribution - quality_annotation - retention period (distribution) - homepage (catalog)
…ext-dcat into add-missing-fields
…ext-dcat into add-missing-fields
…act within Dataservice
amercader
reviewed
Jul 29, 2025
| return [] | ||
|
|
||
| try: | ||
|
|
Member
| pip install -e ckanext-scheming | ||
| git clone https://github.com/ckan/ckanext-fluent | ||
| pip install -e ckanext-fluent | ||
| pip install git+https://github.com/ckan/ckanext-fluent.git@4e9340a#egg=ckanext-fluent |
Member
There was a problem hiding this comment.
I've removed support for CKAN 2.9 in be3c8d6 so this should not be longer necessary
Contributor
Author
There was a problem hiding this comment.
I revert the test.yml
Member
|
@hcvdwerf This looks good, see some minor comments. The PR description was not very helpful though, with confusing formatting and bits that are not relevant (or just hallucinated). If you are using an AI assistant please review the description to make sure a human can understand the changes made. Thanks! |
Contributor
Author
|
@amercader I processed you comments. Any idea what is going wrong now with the croissant package? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR implements additional metadata fields across various RDF entities to enhance alignment with DCAT and provenance/quality standards. The changes improve semantic expressiveness and interoperability across datasets, catalogues, and data services.
✅ Implemented Fields
Agent
Added support for describing agents (e.g., publishers, creators, data providers).
Spatial
Included dct:spatial to indicate the geographic coverage of datasets and services.
Dataset
Enriched with:
prov:wasGeneratedBy: traces back to the activity or process that generated the dataset.
dqv:hasQualityAnnotation: links to a quality annotation to describe quality metrics or standards.
prov:qualifiedAttribution: provides detailed attribution including the responsible agent and role.
Catalog
Support added for:
foaf:homepage: to represent the catalog's homepage URL.
Distribution
Added:
dct:retentionPeriod: defines how long the distribution is retained.
dct:temporalResolution: captures the granularity of the temporal dimension.
DataService
Implemented core structure and verified alignment using the Excel specification ("Check excel").
🔧 Notes
All newly introduced fields were verified against the controlled vocabulary and shape expectations from the GDI metadata model and SHACL definitions.
The update ensures these fields are parsed, serialized, and available in the RDF export and/or API layer as appropriate.
🔗 Related Issues
Closes #337: Implement missing provenance and quality fields.
Closes #325: Add support for spatial, retention, and resolution metadata.