Changes between Version 8 and Version 9 of Z3950_sru_improvements


Ignore:
Timestamp:
05/03/10 19:10:17 (15 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Z3950_sru_improvements

    v8 v9  
    1818
    1919Moreover, the current Z39.50 interface hasn't been maintained: no date search support, improved geospacial indexing
    20 not applied to this part of the software, the Z3950 server in GeoNetwork does not produce HTML or other formats and harvest from Z3950 sources is not supported.
     20not applied to this part of the software, the Z3950 server in !GeoNetwork does not produce HTML or other formats and harvest from Z3950 sources is not supported.
    2121
    2222The proposal is to undertake an overhaul of the Z3950 part of the code, to update the JZKit library to version 3, implement an SRU webinterface, Z3950 harvester and make some enhancements to enable the Z3950 server to provide at least HTML (as well as the usual XML) and map Z collection names from the query to !GeoNetwork categories. Support for remote search will also be returned to !GeoNetwork but changes to the current search interface to integrate it with local search will be in a later proposal.
    … …  
    5353SRU interface implemented as jeeves service. (eg. for basic testing of 2.5.0 SRU service http://127.0.0.1:8080/geonetwork/srv/en/portal.sru?operation=searchretrieve&version=1.2&query=title%20any%20Africa ).
    5454
    55 The spring application-context had to be loosely integrated into Geonetwork, since JZKit makes extensive use of it.
    56 A ApplicationContext reference was added to the GeonetworkContext to make the Spring ApplicationContext available.
     55The spring application-context had to be loosely integrated into !GeoNetwork, since JZKit makes extensive use of it.
     56A ApplicationContext reference was added to the !GeonetworkContext to make the Spring !ApplicationContext available.
    5757Initialization in Geonetwork.java uppon Z39.50 initialization.
    5858
    … …  
    6060This is currently being done by creating a "virtual" context-set "geonet", which defines the indices that are searchable.
    6161Queries that contain unsupported indices (and relations) are rejected (this can be configured). Currently this is hard-wired
    62 in a configuration file, but this could be dynamically configured by Geonetwork if the set of searchable indices was available.
     62in a configuration file, but this could be dynamically configured by !GeoNetwork if the set of searchable indices was available.
    6363
    6464JZKit is dependent on the following libraries