As a (geo)data portal, geoNetwork's main feature
is search through metadata
All data is stored on the database,
but it is not used for searching
Search is based on Lucene 4.9.0
Lucene folder path configurable
Configure the fields used on search on index-fields.xsl
Configure the fields exposed on index-fields.xsl
Available through the q API service
Part of the basic User Interface
Allows users to preview data layers
Read-only (view-only)
Geo-related services can be added (like geocoding)
Standard way: CSW-t
Asynchronous way: Harvesting
geoNetwork services:
Periodical jobs that copy data from other catalogs
Periodicity can be defined on simple cron format
Multiple formats on origin
Users will not be able to modify this records, but can duplicate them
geoNetwork works with four types of users:
Roles can be defined by group
The group All is a generic group for public data
Records can be batch moved to another user
GeoNetwork is compliant with the 2.0.2 version of the specification
http(s)://___/srv/$language/csw
GetCapabilities: general description of the service
DescribeRecord: information model supported by the service
GetRecordById: data of the record by identifier. Authentication optional
GetRecords: query the service using CQL or OGC Filter. Authentication optional
Harvest: Force a CSW harvesting (sync or async). Authentication required
Transaction: interface for creating, modifying and deleting catalogue records. Authentication required
Based on database settings table and xml files (config*.xml)
Latest versions rely more on Spring library
Big catalogs (+100.000 records)
Large catalogs (+300.000 records)
Huge catalogs (+1.000.000 records)