Skip to content

Releases: ckan/ckanext-dcat

v2.1.0

31 Oct 14:02
Compare
Choose a tag to compare

What's Changed

  • New base profile for the DCAT US v3 specification.
    All mandatory properties and most of the recommended and optional ones are supported. During the
    implementation of this work a few adjustments have been done to the base DCAT profile (#314) :

    • Support for temporal and spatial resolutions in distributions, which were missing on the DCAT AP profiles
    • Allow multiple values for dct:creator in DCAT AP
  • Multilingual support in DCAT profiles. Multilingual support is provided via integration
    with ckanext-fluent. Check the documentation for full details (#318)

  • At the serialization level, a new triple will be added for each of the defined languages

  • Support for multiple agents when parsing (#317)

  • Improve serialization of statements, using RDFS.label in line with the DCAT 3 spec recommendation (#313)

  • Store UIDs from contact clases (#312)

  • Fix input issues for access_rights field (#309)

  • Add has_version to the full DCAT AP schema (#306)

  • Add pyproject.toml file (#304)

  • Decouple extension from ckanext-scheming (#303)

  • Add support for dct:creator in base DCAT profiles (#302)

  • Fix DCAT date validator on empty values (#297)

  • Add support for hydra collection type PartialCollectionView (#299)

New Contributors

Full Changelog: v2.0.0...v2.1.0

v2.0.0

30 Aug 11:23
Compare
Choose a tag to compare

What's Changed

  • New profile for DCAT-AP v3, euro_dcat_ap_3, which is now the default. Existing sites willing to stick with DCAT-AP v2.x can specify the profile in the configuration if they are not doing so yet (ckan.dcat.rdf.profiles = euro_dcat_ap_2). The new euro_dcat_ap_3 profile relies on ckanext-scheming metadata schemas (see below).

  • Support for standard CKAN ckanext-scheming schemas. The DCAT profiles now seamlessly integrate with fields defined via the YAML or JSON scheming files. Sites willing to migrate to a scheming based metadata schema can do
    so by adding the euro_dcat_ap_scheming profile at the end of their profile chain (e.g. ckanext.dcat.rdf.profiles = euro_dcat_ap_2 euro_dcat_ap_scheming), which will modify the existing profile outputs to the expected format by the scheming validators. Sample schemas are provided in the ckanext/dcat/schemas folder. See the documentation for all details. Some highlights of the new scheming based profiles (#281):

    • Actual list support in the API output for list properties like dct:language
    • Multiple objects now allowed for properties like dcat:ContactPoint, dct:spatial or dct:temporal
    • Custom validators for date values that allow xsd:gYear, xsd:gYearMonth, xsd:date and xsd:dateTime
  • SHACL validation for DCAT-AP 2.1.1 profile (scheming and legacy).
    SHACL validation made surface the following issues in the existing profiles, which are now fixed (#288):

    • Cast dcat:byteSize and dcat:spatialResolutionInMeters as Decimal, not float
    • Allow only one value of dcat:spatialResolutionInMeters and dcat:temporalResolution
    • Only output the WKT version of geometries in locn:geometry, dcat:bbox and dcat:centroid. Sites that for some reason
      require GeoJSON (or both) can use the ckanext.dcat.output_spatial_format config option
      to choose which format to use
    • When using the euro_dcat_ap_2 profile, don't output temporal extent namespaced
      both with schema and dcat, just with the latter (dcat:startDate and dcat:endDate)
  • CKAN 2.11 support and requirements updates (#270)

  • New ckan dcat consume and ckan dcat produce CLI commands (#279)

  • Revamped documentation, now hosted at https://docs.ckan.org/projects/ckanext-dcat (#296)

  • Parse dcat:spatialResolutionInMeters as float (#285)

  • Split profile classes into their own separate files (#282)

  • Catch Not Authorized in View (#280)

New Contributors

Full Changelog: v1.7.0...v2.0.0

v1.7.0

04 Apr 11:38
b8ebf24
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.6.0...v1.7.0

v1.6.0

29 Feb 09:50
e2183dd
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.5.1...v1.6.0

v1.5.1

20 Jun 14:11
eb1aee0
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.5.0...v1.5.1

v1.5.0

03 May 07:21
14396e6
Compare
Choose a tag to compare

Breaking Changes

  • Support for CKAN versions prior to 2.9 has been dropped
  • Support for Python 2 has been dropped

What's Changed

New Contributors

Full Changelog: v1.4.0...v1.5.0

v1.4.0

05 Dec 14:46
618928b
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.3.0...v1.4.0

v1.3.0

01 Aug 12:12
4b06fc0
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.2.0...v1.3.0

v1.2.0

25 May 13:42
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.1.3...v1.2.0

Release v1.1.3

05 Nov 13:43
2d2c8a8
Compare
Choose a tag to compare
  • Fix behavior if publisher_uri is not available (#201)
  • Also process URIRef in rights statements (#200)