Z3950 Extensions and Fixes

Date	2010/01/26
Contact(s)	Simon Pigot
Last edited	Timestamp
Status	complete - but needs to be tied in with Timo Proescholdt's Z3950 JZKit3 proposal - see
Assigned to release	2.5
Resources	BlueNetMEST

Overview

Fixes and Enhancements to Z3950 server and client

Proposal Type

• Type: GUI Change, Core Change
• App: GeoNetwork
• Module: Harvester, Search, Z3950 server

Links

• Documents:
• Email discussions:
• Other wiki discussions:

Voting History

• Not yet voted on

---

Motivations

Enhance and fix Z3950 server, tie in with JZKit3 implementation given in proposal by Timo Proescholdt

Proposal

Z3950 server and remote search needs fixes (see bug list) and enhancements:

• Z3950 server config simplification - remove redundancy from repositories.xml.tem - redundant info is added when repositories.xml is built from the .tem file on Z3950 server startup.
• map database name used in Z3950 to GeoNetwork categories eg. searching a GeoNetwork Z3950 server specified as bluenetmest.utas.edu.au:2100/datasets would search only on records that are in the datasets category. The existing default of bluenetmest.utas.edu.au:2100/geonetwork continues to search all records
• Z3950 harvester - harvest records from a Z3950 server by specifying a Z3950 search string (extension and additional implementation based on Francois' original template in geosource)
• restore remote search interface
• add capability for GeoNetwork to provide HTML responses

All implemented in the BlueNetMEST sandbox - see version 1.2.1 on ​http://anzlicmet.bluenet.utas.edu.au

Backwards Compatibility Issues

Risks

Participants

• As above