Changes between Version 1 and Version 2 of SelectionManager

Timestamp:

10/20/08 07:55:07 (16 years ago)

Author:

Fxp

Comment:

--

SelectionManager

@@ -1 @@
-= Multilingual editing =
+= Selection manager =
 
 || '''Date''' || 2008/10/20 ||
-|| '''Contact(s)''' || fxprunayre, mcoudert ||
+|| '''Contact(s)''' || mcoudert ||
 || '''Last edited''' || [[Timestamp]] ||
 || '''Status''' || draft ||
-|| '''Assigned to release''' || to be determined ||
-|| '''Resources''' || Resource available ||
+|| '''Assigned to release''' || 2.3 ? ||
+|| '''Resources''' || Resource available / patch proposed ||
 
 == Overview ==
 
-The purpose of this proposal is to improve existing massive actions on metadata (ie delete, filter search ...).
+The purpose of this proposal is to improve existing massive actions on metadata search results (ie delete, filter search ...).
 
 === Proposal Type ===
  * '''Type''': 
  * '''App''': !GeoNetwork
- * '''Module''': Search Module, Kernel
+ * '''Module''': User Interface, new SelectionManager module
 
 === Links ===
@@ -27 +27 @@
 
 == Motivations ==
-For the time being only delete action is possible on metadata, without session on this selection.
-This improvement allows user to navigate throw different tabs, keeping selected metadata in session.
+In 2.2 release, only delete action is possible on all metadata records in current search page results.
+There's no easy way to delete all metadata matching a specific search.
+This improvement allows users to navigate through search results keeping selected metadata in session. Once selected, user can't apply action to selection set.
+
+Actions available on selection:
+ * massive delete
+ * display only selected
+
+
+
 
 == Proposal == 
@@ -60 +68 @@
 
 How to deal with harvested / remote metadata : 
- * should we allow delete actions on it
+ * should we allow delete actions on it ?
 
 == Participants ==
- * List of participants and role (if necessary) in current GIP 
+ * francois