New Features

The new GeoNetwork opensource comes with substantial upgrades of different components.

2.10 release


  • Metadata on maps: Add template for making metadata on static or interactive maps. Add a search criteria for easily found maps. Web Map Context could be loaded into the map viewer.
  • Metadata linked data: Easier metadata relation configuration and new support for source dataset and siblings. See metadata_link)
  • Hide part of metadata: Provide a method to hide portions of metadata using withHeld ISO attribute
  • Wiki markup in metadata: Allow users to enter markup text in metadata elements and have results shown with rendered html
  • WFS data downloader: Simple component to download WFS data


  • User profile: Setup user belonging to multiple groups with different profiles
  • Virtual CSW configuration interface to add new end points


  • Security layer: New security layer based on Spring Security adding support for CAS and much more flexible LDAP configuration
  • Xlink: Add local:// as a protocal for xlink links
  • Provide basic functionnalities (ie. search and view) when database is in readonly

2.8 release

User interface

  • Javascript widget user interface: A new user interface using one of the latest Javascript widget libraries (extJS) has been added to support searching, editing and viewing metadata records. The user interface is now much easier for Javascript developers to reorganize and customize. GeoNetwork comes with two flavours of home page: one has the sidebar search similar to the old interface and the other uses a tabbed search layout. The 2.6.x user interface is still available as the default and has been updated.

New home page of GeoNetwork opensource using JavaScript Widgets - tab layout


New home page of GeoNetwork opensource using JavaScript Widgets- sidebar layout


  • Search Statistics: Captures and displays statistics on searches carried out in GeoNetwork. The statistics can be summarized in tables or in charts using JFreeChart. There is an extensible interface that you can use to display your own statistics. See Search Statistics.
  • New Harvesters: OGC Harvesting: Sensor Observation Service, Z3950 harvesting, Web Accessible Folder (WAF), GeoPortal 9.3.x via REST API See Harvesting.
  • Harvest History and Scheduling: Harvesting events are now recorded in the database for review at any time. See Harvest History. Harvester scheduling is now much more flexible, you can start a harvest at any time of the day and at almost any interval (weekly etc).
  • Extended Metadata Exchange Format (MEF): More than one metadata file can be present in a MEF Zip archive. This is MEF version 2. See Export facilities.
  • System Monitoring: Automatically monitoring the health of a Geonetwork web application. See System Monitoring.


  • Metadata Status: Allows finer control of the metadata workflow. Records can be assigned a status that reflects where they are in the metadata workflow: draft, approved, retired, submitted, rejected. When the status changes the relevant user is informed via email. eg. when an editor changes the status to ‘submitted’, the content reviewer receives an email requesting review. See Status.
  • Metadata Versioning: Captures changes to metadata records and metadata properties (status, privileges, categories) and records them as versions in a subversion respository. See Versioning.
  • Publishing data to GeoServer from GeoNetwork: You can now publish geospatial information in the form of GeoTIFF, shapefile or spatial table in a database to GeoServer from GeoNetwork. See GeoPublisher.
  • Custom Metadata Formatters: You can now create your own XSLT to format metadata to suit your needs, zip it up and plug it in to GeoNetwork. See Formatter.
  • Assembling Metadata Records from Reusable Components: Metadata records can now be assembled from reusable components (eg. contact information). The components can be present in the local catalog or brought in from a remote catalog (with caching to speed up access). A component directory interface is available for editing and viewing the components. See Fragments.
  • Editor Improvements: Picking terms from a thesaurus using a search widget, selecting reusable metadata components for inclusion in the record, user defined suggestions or picklists to control content, context sensitive help, creating relationships between records.
  • Plug in metadata schemas: You can define your own metadata schema and plug it into GeoNetwork on demand. Documentation to help you do this and example plug in schemas can be found in the Developers Manual. Some of the most common community plug in schemas can be downloaded from the GeoNetwork source code repository. See Schemas.
  • Multilingual Indexing: If you have to cope with metadata in different languages, GeoNetwork can now index each language and search all across language indexes by translating your search terms. See Multilingual search.
  • Enhanced Thesaurus support: Thesauri can be loaded from ISO19135 register records and SKOS files. Keywords in ISO records are anchored to the definition of the concept in the thesaurus. See Thesaurus.

CSW service

  • Virtual CSW Endpoints: Now you can define a custom CSW service that works with a set of metadata records that you define. See Virtual CSW server entry points.

INSPIRE Directive

  • Support for the INSPIRE Directive: Indexing and user interface extensions to support those who need to implement the INSPIRE metadata directive (EU).
  • Installer package to enable INSPIRE options: An optional new package in the installer enables GeoNetwork INSPIRE features if selected, avoiding manual steps to enable INSPIRE support.


  • Improved Database Connection Handling and Pooling: Replacement of the Jeeves based database connection pool with the widely used and more robust Apache Database Connection Pool (DBCP). Addition of JNDI or container based database connection support. See Database configuration.
  • Configuration Overrides: Now you can add your own configuration options to GeoNetwork, keep them in one file and maintain them independently from GeoNetwork. See Configuration override.
  • Many other improvements: charset detection and conversion on import, batch application of an XSLT to a selected set of metadata records (see Processing), remote notification of metadata changes, automatic integration tests to improve development and reduce regression and, of course, many bug fixes.