Changes between Version 15 and Version 16 of ExtendedRegions

Timestamp:

01/29/13 01:18:35 (12 years ago)

Author:

jesseeichar

Comment:

--

ExtendedRegions

@@ -166 +166 @@
 '''Implementation Notes'''
 
-The actual implementation will consist of the services and a strategy object that can be configured the geonetwork configuration files.  The intention is that for a particular application the strategy object can be implemented and configured for use.  The default implementation will be the current implementation factored out into the strategy object.
+The actual implementation will consist of the services and a strategy object that can be configured the geonetwork configuration files (config-spring.xml).  The intention is that for a particular application the strategy object can be implemented and configured for use.  The default implementation will be the current implementation factored out into the strategy object.
 
 The main strategy object is called:
 
 RegionsDAO which is the entry point into searching and querying regions.  See the javadocs of this class for information on how to use the class and implement new custom regions strategies.
+
+'''Default implementations'''
+Two strategies will be shipped with Geonetwork by default:
+
+ * Thesaurus Regions - The regions and region categories are derived from the regions listed in the regions thesaurus that is shipped with geonetwork by default
+* Metadata Regions - Each region is an extent in one of the metadata elements.  Because of the cost to search the metadata the first version will no allow list searching all regions in this strategy.  The search options are limited to category (the fileid of the MD), this will list the ids of the "regions/extents" within that metadata.  The other option is to get a region by id.  This is the form:  metadata:<fileIdentifier>:<edit ref of geometry>.  In the first version only iso19139 can be obtained and only polygons (not bbox) 
+
 
 '''Example URLS'''