Changes between Version 18 and Version 19 of oaipmh_improvements

Timestamp:

07/16/12 17:24:15 (13 years ago)

Author:

simonp

Comment:

--

oaipmh_improvements

@@ -80 +80 @@
 One of the goals of this proposal is to provide an alternative OAIPMH harvester service that:
 
- * retrieves metadata objects with '''unresolved''' references to other objects and places them in the OAIPMH harvest results
+ * retrieves metadata objects with '''unresolved''' references to other objects
  * retrieves and adds one copy of all referenced metadata objects to the OAIPMH harvest results
- * extends the current OAIPMH implementation: the default behaviour will be to return resolved metadata records. Referencing the alternative OAIPMH service will deliver all metadata objects in unresolved form.
+ * extends the current OAIPMH implementation: the default behaviour will be to return resolved metadata records (ie. the current implementation). Referencing the alternative OAIPMH service will deliver metadata objects.
 
 The reason for implementing this extension is to enable conversions to formats that support metadata objects and relationships eg. ANDS RIF-CS.
@@ -104 +104 @@
 ==== Metadata Object Harvesting ====
 
-Currently, !GeoNetwork will resolve all links before indexing the 
+Currently, !GeoNetwork will store the unresolved metadata record (ie. without linked fragments) in the database and resolve all links to fragments before returning the record as a search result. This proposal will implement a :
  * Implement Lucene search that retrieves metadata objects
    * First stage returns metadata objects with unresolved references to other external metadata objects. This is not difficult as metadata objects are stored with unresolved references in the database. Note: links to internal relationships (eg. repeated metadata in the same record) will still need to be resolved.