Changes between Initial Version and Version 1 of TemporalExtentSearch

Timestamp:

Apr 14, 2010, 3:27:44 AM (14 years ago)

Author:

simonp

Comment:

--

TemporalExtentSearch

@@ +1 @@
+= Adding Search on Temporal Extent to Advanced Search =
+
+|| '''Date''' || 2010/04/14 ||
+|| '''Contact(s)''' || Simon Pigot ||
+|| '''Last edited''' || [[Timestamp]] ||
+|| '''Status''' || complete ||
+|| '''Assigned to release''' || 2.5.0 ||
+|| '''Resources''' || Available, patch attached ||
+
+== Overview ==
+
+!GeoNetwork can search for metadata records based on date of last change but cannot search for metadata records with a temporal extent in the resource Identification section (!DataIdentification or !ServiceIdentification).
+
+=== Proposal Type ===
+ * '''Type''': GUI Change, Core Change
+ * '''App''': !GeoNetwork
+ * '''Module''': Data Manager, Lucene Index, Search Interface, User Interface
+
+=== Links ===
+ * '''Sandbox''': BlueNetMEST 
+ * '''Other wiki discussions''': Proposed at 2008 Bolsena meeting and has been present in BlueNetMEST for some years - too long.
+
+=== Voting History ===
+ * Note voted on yet
+
+----
+
+== Motivations ==
+Add Temporal Search capability to GeoNetwork.
+
+== Proposal == 
+
+Advanced Search Interface would look like the following:
+
+
+In ISO records temporal extents can be specified in a number of different ways (GML has many different and flexible representations for time). The !GeoNetwork editor simplifies the options by using a !JavaScript calendar interface to specify an ISO DateTime or ISO Date interface. For temporal extent searching to work correctly, we need a flexible method of parsing as many of the different time formats as possible because not all records in the catalog will be created using the !GeoNetwork editor. After parsing we will need to convert to a common time format and timezone before storing in a Lucene Index field for searching. 
+
+Example temporal extents (these were not created with the !GeoNetwork editor):
+
+{{{
+
+}}}
+
+This proposal would see !GeoNetwork use parser from the JODA time library for this purpose as JODA is generally considered to be the most comprehensive time library for Java. The parsing and conversion step is done by a call to Java objects that use the JODA library when preparing the Lucene Document for indexing (index-fields.xsl).
+
+=== Backwards Compatibility Issues ===
+
+None known.
+
+== Participants ==
+ * Michael Stegherr - CSIRO CESRE - ported some of the functionality from BlueNetMEST to trunk 
+