Changes between Version 25 and Version 26 of oaipmh_improvements

Timestamp:

07/17/12 17:16:19 (12 years ago)

Author:

simonp

Comment:

--

oaipmh_improvements

@@ -111 +111 @@
  - The second approach would require metadata records and the objects that are referenced from the record to be stored as a document block in Lucene (using Lucene 3.6). The OAIPMH query would search on the metadata record but the results returned would include the referenced objects from the document block. A possible advantage of this approach over the first is that the search results would not have to be processed before they are returned which means that this approach is likely to be considerably faster than the first. A disadvantage of this approach over the first is that the Lucene indexing process in !GeoNetwork would need to be substantially modified.       
 
- - As RIF-CS is a metadata object standard that supports a subset of the ISO19115/19139 objects and object relationships, we can test extraction of the ISO metadata objects using the RIF-CS schema. To implement this we will need to adapt the RIF-CS XSLTs for iso19139.mcp, eml-gbif and iso19139.anzlic to handle:
+As RIF-CS is a metadata object standard that supports a subset of the ISO19115/19139 objects and object relationships, we can test extraction of the ISO metadata objects using the RIF-CS schema. To implement this we will need to adapt the RIF-CS XSLTs for iso19139.mcp, eml-gbif and iso19139.anzlic to handle:
    * metadata objects such as person and organisation contact information as parties
    * metadata records with a project hierarchy level as activities
@@ -117 +117 @@
    * project sibling relationships as related activities
 
- - Implement the alternative oaipmh service that will use the lucene search for metadata objects + modified RIF-CS XSLTs (this should be a straightforward change to the existing oaipmh server as the code can decide whether to use the normal lucene search for metadata records or the lucene search for metadata objects based on the name of the oaipmh server service). The alternative oaipmh server could be called geonetwork/srv/eng/oaipmhMetadataObjects
+Finally, we will implement an alternative oaipmh service that will use the lucene search for metadata objects + modified RIF-CS XSLTs (this should be a straightforward change to the existing oaipmh server as the code can decide whether to use the normal lucene search for metadata records or the lucene search for metadata objects based on the name of the oaipmh server service). The alternative oaipmh server could be called geonetwork/srv/eng/oaipmhMetadataObjects
 
 The estimated time to implement this feature, including testing is 10 weeks.