Changes between Version 22 and Version 23 of ComposedMetadataRecords
- 08/31/09 23:27:40 (4 years ago)
v22 v23 35 35 The two components to be added by this proposal (in more detail): 36 36 37 * WFS fragment harvester - this is a harvester that accepts (along with the usual harvester parameters) a WFS GetFeature query, a template 37 * WFS fragment harvester - this is a harvester that accepts (along with the usual harvester parameters) a WFS GetFeature query, a template 38 38 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 has modified the resolver links 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 . See 40 41 Minor changes were required to change the display of metadata fragments in the !GeoNetwork editor so that they cannot be edited. 40 42 41 43 Future work would add: … … 44 46 * URN resolver to provide a level of indirection that can be used to cope with changing URLs and ensure referential integrity. Metadata fragments are linked into records using XLinks. XLinks can use URLs or URNs in the link attribute (xlink:href). URNs are intended to provide a permanent A service that provides the ability to register a urn and associated URL, and lookup a URL given a URN, would allow the implementation to use URNs in place of URLs, thus providing a measure of control over broken links/missing content which can occur if we were to use URLs. 45 47 * Support for updating a fragment in !GeoNetwork- sometimes it makes sense for a fragment to be edited and saved back into the external database from which it was harvested. WFS-T support would be used to provide this facility. 48 46 49 * Support in the editor for fragments: the original intention of subtemplates was that they be accessible from the editor ie. a user could select a fragment (eg. contact info) to use when editing that portion of a metadata record. Some work appears to have already been done in the geocat.ch sandbox on this function. 47 50 * Access to fragments by other editor tools: Other editing tools (eg. the wizard based ANZMETLite tool) can use fragments in their interface to ease the metadata entry and editing process. Fragments harvested into !GeoNetwork should be accessible to these tools.