Skip to content

GeoCat Live Catalogue Services 2025.2

Updated 29 October 2025.

GeoCat Live Catalogue Services have been updated to use GeoCat Find Enterprise 2026.0 (GeoNetwork 4.4.x) technology.

Highlights

  • Quick export to DCAT-AP 3.0 formats (EU-DCAT-AP, EU-GeoDCAT-AP, Mobility, HVD).
  • Metadata editor improvements: thumbnails, clearer resource sections, resumable downloads, and support for attachments >2GB.
  • DCAT-AP NL 3.0 export and validation for Dutch metadata.
  • New harvesters (SFTP, GeoNetwork 4.x) and support for multiple DOI publication servers.
  • CSV API for custom exports and the reintroduced OAI-PMH server.

Metadata

  • Export to DCAT-AP 3.0 formats for ISO19139 / ISO19115.3-2018 metadata records: EU-DCAT-AP, EU-GeoDCAT-AP, DCAT-AP Mobility, DCAT-AP HVD.
  • Metadata editor: Improved interface for managing metadata distributions, overviews, and associated resources. These resources now have dedicated sections, making management clearer and more user-friendly.
    • Overview: Add small images (thumbnails) to visually represent the data or dataset described in the metadata record.
    • Distributions: Manage files or services that provide access to the described data, including download links and web services.
    • Associated resources: Link to related metadata records, such as datasets and services. Metadata editor resources
  • Validation report: Optional validation rule failures are now displayed as warnings instead of errors, helping users focus on critical issues. image
  • Large attachments: Metadata editor now supports attachments larger than 2GB.
  • Record page: Metadata full view now uses labels.xml configuration to display field labels, providing more meaningful and user-friendly context.
  • Resumable downloads: Metadata attachment downloads can now be resumed, improving reliability for large files.

Dutch Dataset / Services Metadata Schemas

  • DCAT-AP NL 3.0 support: GeoCat Live 2025.2 can export ISO Dutch metadata to the DCAT-AP NL 3.0 profile.
    • Export dataset and service metadata to DCAT-AP NL 3.0 RDF/XML format:
      • From the metadata view page, use the export menu to select DCAT-AP NL 3.0. image image
      • From OGC:CSW service GetRecords or GetRecordById, use output schema https://docs.geostandaarden.nl/dcat/dcat-ap-nl30 to retrieve metadata in DCAT-AP NL 3.0 format. image
    • Metadata view displays DCAT-AP NL 3.0 information mapped from ISO metadata. image
    • Metadata editor includes validation rules for dataset and service metadata, ensuring ISO required fields for DCAT-AP NL 3.0. image

Administration

  • New harvesters:
  • Multiple DOI publication servers: Configure multiple DOI servers and assign them to specific groups. image
  • Thesaurus format improvements:
    • Support for codelists in SDMX format.
    • Support for thesauri in OWL format.
    • Improved support for EU Publication Office SKOS format.
    • Create thesaurus from a shapefile.
  • Editor board search configuration: When metadata workflow is enabled, configure search results to show:
    • Approved records (default)
    • Working copies
    • Both versions
      Editing an approved record creates a working copy. The new search options make it easier to find working copies. image

API and Automation

  • CSV API: export metadata information to CSV format, selecting the fields to include in the export:
    • Define the fields to export using their XPATH expressions.
    • Extract information from contacts, online resources, and other repeatable fields.
    • Customise the column separator character and the separator for fields with multiple values.
    • See API examples at GitHub PR #7132
  • OAI-PMH server: Reintroduced after switching to Elasticsearch as the search engine.

Other Improvements

  • Audit log: Tracks changes to user information (username, email, profile updates) for improved activity tracking.
  • Analytics integration: Configure integration with Matomo or Google Analytics in config.properties. Example for Matomo: 
    # Analytics service: (empty value: no analytics),matomo,google
analytics.web.service=matomo
# Analytics javascript code to integrate with the analytics service (lines must be ended with \n\)
analytics.web.jscode=var _paq = _paq || [];_paq.push(['trackPageView']);_paq.push(['enableLinkTracking']);(function() {var u="//localhost/";_paq.push(['setTrackerUrl', u+'piwik.php']);_paq.push(['setSiteId', '1']);var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];g.type='text/javascript'; g.async=true; g.defer=true; g.src=u+'piwik.js'; s.parentNode.insertBefore(g,s);})();var currentUrl = location.href; \
window.addEventListener('hashchange', function() {_paq.push(['setReferrerUrl', currentUrl]);currentUrl = window.location.hash.substr(1);_paq.push(['setCustomUrl', currentUrl]);_paq.push(['setDocumentTitle', currentUrl]);_paq.push(['deleteCustomVariables', 'page']);_paq.push(['trackPageView']);var content = document.getElementsByTagName('body')[0];_paq.push(['MediaAnalytics::scanForMedia', content]);_paq.push(['FormAnalytics::scanForForms', content]);_paq.push(['trackContentImpressionsWithinNode', content]);_paq.push(['enableLinkTracking']);});
  • Upgrades:
    • ElasticSearch 8.14.3
    • JVM 11
    • Spring Framework 5.3.39
    • Spring Security 5.8.16
    • GeoTools 32.2