feat(rdf): support serialization of DatasetSeries from RDF and link c… #350
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.
@amercader I created this pull request to make serialisation of dataseries possible into ckan model
What I have done:
1. Enabling
DatasetSeries
SerializationYou extended CKAN's DCAT RDF support to correctly serialize and parse datasets of type
dcat:DatasetSeries
based on DCAT-AP 3.0:Identified where
DatasetSeries
type detection happens via RDF type triple (rdf:type dcat:DatasetSeries
).Implemented logic in
EuropeanDCATAP3Profile.parse_dataset
to:"type": "dataset_series"
if triple is present.series_order_field
andseries_order_type
with default fields2. Handling
in_series
Field Extraction and LinkingI added logic to ensure dataset membership in a series is handled cleanly:
dcat:inSeries
references in the maindatasets()
function (outsideparse_dataset()
).series_mapping
(viaguid
) to resolve URIs to internal CKANid
values.3. Scheming dataseries
I added a prorperty into the scheming dataseries YAML for:
series_order_field
,series_order_type
anddataset_series_in_series
Clarified that these require:
check ckan/ckanext-dataset-series#9
to persist properly as
extras
.