This repository contains the custom files for the GeoNetwork implementation of the Marine Institute's Data Catalogue.
The external web portal for the MI Data Catalogue is based on GeoNetwork 3 with MI customizations: These include:
The following tools are required to be installed to setup a development environment for GeoNetwork:
For details on the latest supported versions, please refer to: GeoNetwork Software Development Guide https://github.com/geonetwork/core-geonetwork/tree/master/software_development
Ensure you have cloned the MI Data Catalogue Repository (this repo). This ensures you have the latest build scripts and MI specific file changes before starting the build.
Steps to clone MI Data Catalogue repository:
git clone --recurse-submodules https://github.com/IrishMarineInstitute/data.marine.ie.git data-catalogue
IMPORTANT: Any files included in this github repository must be included in the 'mi_geonetwork_build' maven config script, otherwise files will not be picked up by the build. Ensure your files are included in the build script before starting a build.
Run the following:
Run the commands:
git clone --recurse-submodules https://github.com/geonetwork/core-geonetwork.git geonetwork
cd geonetwork
git checkout tags/3.4.2 -b build
git status
Run a clean build by running the command:
mvn clean install -DskipTests
The build should be successful.
Note: Maven default location: C:\Users\
Pull in sub-modules for Plugins:
Run commands:
git submodule add https://github.com/metadata101/sensorML.git sensorML
git submodule add https://github.com/metadata101/iso19139.sdn-csr.git
git submodule add https://github.com/metadata101/iso19139.sdn-cdi.git
Navigate to the data-catalogue repository and run the MI script: mi_geonetwork_build.xml. This is an ant build script and will copy all required MI content into the build branch of the geonetwork repository (created earlier)
cd data-catalogue
ant -buildfile mi_geonetwork_build.xml
The build (copy files) should complete successfully.
The final step is to navigate back to the 'geonetwork' repository and re-run the Maven build. This will build a new version of the geonetwork application with MI specific changes applied.
mvn clean install -DskipTests
The build should be successful. The final build output is an output WAR file stored in: \geonetwork\web\target.
The default location of the geonetwork h2 database is: \Apache Software Foundation\Tomcat 9.0
The following files are created:
gn.h2.db
gn.lock.db
gn.trace.db
gn.trace.db.old
To deploy a fully clean version, the above files should be deleted and a new data harvest performed.
Take WAR file made from the steps described here.
Deploy in WebApps folder of an installed Tomcat instance - Stop and Start Tomcat. (Memory of 2GB needed - Java 8 and Tomcat 8 recommended by OSGeo (9 works too though).
Log-in to the GeoNetwork instance (initially default as Admin/Admin
): /geonetwork/srv/eng/catalog.signin
Under Admin Console:
/geonetwork/srv/eng/admin.console#/organization
/geonetwork/srv/eng/admin.console#/settings
Sample Group
Admin
Local file location
keep catalog record even if deleted at source
Metadata
Go to Tools and click rebuild index
.
Alternatively, use the dockerfile included in this repo.