Changes between Version 25 and Version 26 of ComposedMetadataRecords


Ignore:
Timestamp:
08/31/09 23:38:54 (16 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ComposedMetadataRecords

    v25 v26  
    3535The two components to be added by this proposal (in more detail):
    3636
    37  * WFS fragment harvester - this is a harvester that accepts (along with the usual harvester parameters) a WFS !GetFeature query, a template which will be for each feature and linked to metadata fragments (more than one fragment can be returned from a feature) plus permissions and categories for fragments and records created. Note: the template is only used to create records on the first run of the harvester. The WFS response to the !GetFeature request is assumed to be in the form of fragments. Current implementation uses deegree WFS where the transformation of the WFS response can be done by the server using xslt.
     37 * WFS fragment harvester - this is a harvester that accepts (along with the usual harvester parameters) a WFS !GetFeature query, a template which will be for each feature and linked to metadata fragments (more than one fragment can be returned from a feature) plus permissions and categories for fragments and records created. Note: the template is only used to create records on the first run of the harvester. The WFS response to the !GetFeature request is assumed to be in the form of fragments. Current implementation uses deegree WFS where the transformation of the WFS response can be done by the server using xslt. (See http://geonetwork.svn.sourceforge.net/viewvc/geonetwork/sandbox/BlueNetMEST/src/org/fao/geonet/kernel/harvest/harvester/metadatafragments/ - this will be renamed wfsmetadatafragmentharvester)
    3838
    39  * XLink resolver and cache - the geocat.ch sandbox uses and is developing an XLink resolver and cache mechanism. The implementation in the BlueNetMEST sandbox uses the same cache mechanism (based on Apache JCS) but the resolver has been rewritten to handle (amongst other things) relative links to fragments in the same record and to avoid caching of such fragments. See
     39 * XLink resolver and cache - the geocat.ch sandbox has developed an XLink resolver and cache mechanism. The implementation in the BlueNetMEST sandbox uses the same cache mechanism (based on Apache JCS) but parts of the resolver have been rewritten to handle (amongst other things) relative links to fragments in the same record and to avoid caching of such fragments. (See http://geonetwork.svn.sourceforge.net/viewvc/geonetwork/sandbox/BlueNetMEST/jeeves/src/jeeves/xlink)
    4040
    4141Minor changes were required to change the display of metadata fragments in the !GeoNetwork editor so that they cannot be edited.