The 2.8.1 release is fixing two bugs introduced with the new support of cl_presentationForm to classify some datasets and documents as reuse. It's also brings small improvements on the UI, reduces ...

Comitês de Bacias Hidrográficas Estaduais classificados segundo a situação da Cobrança pelo Uso dos Recursos Hídricos.

python bindings to geonetwork API. Contribute to camptocamp/python-geonetwork development by creating an account on GitHub.

GeoCat was happy to attend FOSS4G 2024 in Belém Brazil and help support the open source community in this outreach event.

GeoNetwork catalogue for listing, searching and reviewing records.

I am attempting to set up and evaluate GeoNetwork 4.4.12 on a Windows environment as part of a metadata catalogue upgrade project. Current environment: Current environment: GeoNetwork 4.4.12 bundle installation Windows Server/Desktop environment GeoNetwork running with embedded Jetty External Elasticsearch instance being used GeoServer integration planned Issues encountered: Initial startup failures GeoNetwork would not start successfully after installation. Various connection and startup errors appeared in the logs. GeoNetwork was not appearing as a Windows service. Java processes remained running after startup attempts. Elasticsearch integration GeoNetwork reported Elasticsearch connection errors. There was uncertainty regarding the correct Elasticsearch version to use with GeoNetwork 4.4.12. Verification endpoints requested authentication credentials. Looking for confirmation of supported Elasticsearch versions and recommended configuration. Schema publication issues During startup a schemaPublication directory was automatically recreated after renaming the existing folder. Errors appear related to schema loading or publication processes. Unsure whether this indicates a corrupted schema installation, failed migration, or expected behaviour. Web application unavailable GeoNetwork startup appears to begin successfully. However, the application is not consistently accessible via: http://localhost:8085 Browser reports: "This site can't be reached" Connection refused/time-out behaviour. Upgrade/migration concerns This is effectively a fresh deployment intended to replace an older environment. Seeking guidance on: Recommended upgrade path to 4.4.12 Elasticsearch compatibility Common causes of schemaPublication errors Troubleshooting a startup sequence that completes but does not expose the web application Questions: What Elasticsearch version is recommended for GeoNetwork 4.4.12? Are there known schemaPublication issues during first startup? What log files should be reviewed first when GeoNetwork appears to start but localhost:8085 is unavailable? Is there a recommended process for validating the GeoNetwork ↔ Elasticsearch connection? Any guidance would be greatly appreciated. Thank you.

Full DCAT-AP profile support, a new name, and up to five years of long-term support