Changes between Version 17 and Version 18 of oaipmh_improvements


Ignore:
Timestamp:
07/16/12 16:18:03 (12 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • oaipmh_improvements

    v17 v18  
    8888==== '''Deleted Records''' ====
    8989
    90 This is a feature of the OAIPMH standard that has not been implemented in the !GeoNetwork OAIPMH server but has been implemented in the OAIPMH client. To implement this capability in the !GeoNetwork OAIPMH server records (and metadata objects in general) that have been deleted from the catalog should remain searchable by date range and/or set but be marked as deleted if returned in the results to an OAIPMH client. The idea here is that the client can then determine which records have been deleted during an incremental harvest.
     90This is a feature of the OAIPMH standard that has not been implemented in the !GeoNetwork OAIPMH server but has been implemented in the OAIPMH client. To implement this capability in the !GeoNetwork OAIPMH server records (and metadata objects in general) that have been deleted from the catalog should remain searchable by date range and/or set but be marked as deleted if returned in the results to an OAIPMH client.
     91
     92The reason for this implementing this feature of the OAIPMH standard is that an OAIPMH client can determine which records have been deleted during an incremental/update harvest.
    9193
    9294== Proposal Type ==
     
    102104==== Metadata Object Harvesting ====
    103105
    104  * Implement two-stage Lucene search that retrieves metadata objects
     106Currently, !GeoNetwork will resolve all links before indexing the
     107 * Implement Lucene search that retrieves metadata objects
    105108   * 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.
    106109   * Since XLinks and parent-child + sibling relationships are or can be indexed in Lucene, a second query will be generated to collect all related metadata objects and add those to the search results.