Implementation of the Gemini 2.2 metadata profile to work with Geonetwork 3.0.x, 3.2.x and later releases
Switch branches/tags
Clone or download
Pull request Compare This branch is 10 commits behind AstunTechnology:3.2.x.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

GEMINI 2.2 schema plugin

This is the GEMINI 2.2 schema plugin for GeoNetwork 3.2.x. Do not use it with either Geonetwork 3.0 or 3.4- switch to the appropriate branch in this repository for the correct version of Geonetwork

Installing the plugin

GeoNetwork version to use with this plugin

Use GeoNetwork 3.2.x only.

Adding the plugin to the source code

Add the plugin as a submodule into GeoNetwork schema module:

cd schemas
git submodule add -b 3.2.x iso19139.gemini22

Add the new module to the schema/pom.xml:


Add the dependency in the web module in web/pom.xml:


Add the module to the webapp in web/pom.xml:


Build the application

Once the application is built, the war file contains the schema plugin:

$ mvn clean install -Penv-prod

Deploy the profile in an existing installation

After building the application, it's possible to deploy the schema plugin manually in an existing GeoNetwork installation:

  • Copy the content of the folder schemas/iso19139.gemini22/src/main/plugin to INSTALL_DIR/geonetwork/WEB-INF/data/config/schema_plugins/iso19139.gemini22

  • Copy the jar file schemas/iso19139.gemini22/target/schema-iso19139.gemini22-3.2.1-SNAPSHOT.jar to INSTALL_DIR/geonetwork/WEB-INF/lib.

If there's no changes to the profile Java code or the configuration (config-spring-geonetwork.xml), the jar file is not required to be deployed each time.

Adding editor configuration

Once the application started, check the plugin is loaded in the admin > standard page. Then in admin > Settings, add to metadata/editor/schemaConfig the editor configuration for the schema: