ckan-dcat update 11/2024 #32
Merged
Conversation
This file contains 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
- Introduced creator fields (URI, name, email, URL, type, identifier) alongside publisher fields. - Updated the RDF graph serialization to include creator details. - Extended existing tests to validate the creator functionality. - Applied similar fallback logic for creator as used for publisher.
…add-creator-support
…add-creator-support
- Ensure proper validation for access_rights as a normal text field - Close issue #308 by addressing form behavior inconsistencies
fix(form): resolve input issues for access_rights field
feat: add has_version to default schema
- Added fields to store creator details (name, email, URL, and identifier) in the DCAT profile. - Implemented functionality to serialize and deserialize creator information similar to the publisher. - Updated RDF generation logic to include creator fields in the output graph. - Enhanced unit tests to verify proper handling and serialization of creator metadata.
Feature/add creator support
Use the same files in examples used in the shacl tests, don't use separate dataset dicts on each test.
Use the same files in examples used in the shacl tests, don't use separate dataset dicts on each test.
For the parsing ones we are using the existing dataset.rdf file which has a DCAT AP flavour. We can replace it with a US centric if we can come up with a good existing example.
Use org:Organization and add a skos:prefLabel property
From landing page and documentation if there is no title defined for them. See Usage note in https://doi-do.github.io/dcat-us/#properties-for-document
As they are modeled as Data Services, the outputs fails validation because they don't contain publisher and contact point. We can revisit this if we implement first class support for Data Services
mjanez
added
bug
Consolidate all setuptools config in setup.cfg as per discussion in ckan/ckan#8456
`_add_triple_from_dict()` will check if the value is a dict and assume
it's a fluent field (i.e `{"lang1": "value_lang1", "lang2":
`value_lang2"}. `URIRefOrLiteral` also supports a lang parameter
Created multilingual versions of _object_value() and
_object_value_list() that store the different translations in the format
expected by the fluent fields, e.g.:
{
"en": "Dataset title",
"es": "Título del conjunto de datos"
}
and for tags:
{
"en": ["Oaks", "Pines"],
"es": ["Robles", "Pinos"],
}
Core fields (those ending in `_translated` are handled separately)
First iteration of pyproject.toml
Support for multiple agents when parsing
Multilingual support in DCAT profiles
New profile for DCAT US v3
…tion_to_dataset fix: Move has version from distribution to dataset
Rdflib 7.1 introduced changes in [date parsing][1] that made some base
profile tests fail. Basically the previous rdflib versions incomplete
dates like
<time:inXSDDateTimeStamp
rdf:datatype="http://www.w3.org/2001/XMLSchema#date">
1904
</time:inXSDDateTimeStamp>
were expanded to `1904-01-01`. Of course this is not a valid date and
should be expressed using `gYear`:
<time:inXSDDateTimeStamp
rdf:datatype="http://www.w3.org/2001/XMLSchema#gYear">
1904
</time:inXSDDateTimeStamp>
and we should be expecting `1904`.
This should play nice with the time properties we are generating in CKAN as
they already handle automatically `gYear`, `gYearMonth`, `date` and
`dateTime`.
Sites importing external DCAT representations that use the wrong
encoding might need to check their parsers.
[1] RDFLib/rdflib#2929
Update tests for changes in date parsing in new rdflib versions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
ckanext-schemingdcat: Feature/dcat ap 112024 ckanext-schemingdcat#123