![hale»connect logo](https://wetransform.to/wp-content/uploads/2024/06/featured-image-Haleconnect-black-1200x534-c-default.png)
Product Update: hale»connect June 2024
Here's what's new in the June 2024 update to hale»connect, the most user-friendly way to publish datasets as services, coupled with metadata.
Features
- Official INSPIRE schemas are updated and available for selection from the preset schema dropdown menu during schema creation.
- Support for the atom feed conversion cache is added for providers other than AWS S3. Atom feed artifacts can be configured to be created on publication.
- Additional feedback to the user is added if there are limitations to the type of files that can be uploaded.
- gmx:Anchor encoding is added for service type keyword and SpatialDataServiceCategory in hale»connect generated service metadata.
- gmx:Anchor encoding is added for gmd:title in service and dataset metadata.
- gmx:Anchor encoding is added for the unique resource identifier: gmd:MD_Metadata/gmd:identificationInfo/*/gmd:citation/gmd:CI_Citation/gmd:identifier/gmd:MD_Identifier/gmd:code is added, replacing gco:CharacterString
Fixes
- Fix to create a target series correctly after deleting a target series with the same name.
- Fixed an issue where users would be prompted to log in after logging out of the platform.
- Metadata for Title and Abstract fields is now correctly filled when {{dataset.name}} is configured as an autofill rule and the source file is CSV.
- Fixed an issue where WFS GetFeature requests using a filter query would not return correct results.
- Solved a problem that led to WFS GetFeature requests for series sub-datasets to fail.
- Fixed displaying test configuration in theme validation section when a user does not have permission to edit it.
- There is no longer a limit on the number of CRSs that can be added to a theme configuration.
If you're interested in using hale»connect at your organisation, reach out to us!
You can also use our pricing slider to get an instant cost estimate.