Changes between Version 20 and Version 21 of codesprint/201106-bolsena

Timestamp:

Jun 19, 2011, 2:54:39 AM (13 years ago)

Author:

simonp

Comment:

--

codesprint/201106-bolsena

@@ -84 +84 @@
   * What type of communication between components ? [http://activemq.apache.org/ JMS]
   * ESB, Routine engine ([http://camel.apache.org/ Camel])
+ 
 
 ==== Agreement on new or existing dependencies ====
@@ -98 +99 @@
   * file upload : where we have file upload functions, it would be nice if we provide a drag & drop function instead of the old, old, filechooser -- something like Gmail has it. Of course with perfect degrading for users of certain browsers. A very good one is [http://aquantum-demo.appspot.com/file-upload jQuery File Upload]
  * i18n : it's a little hell to add a new translation of GeoNetwork. It's not in 1 place where you put some translated strings to i18n keys -- no, all sorts of files including js and sql and xslt files need to be updated. There's no documentation on all the places you need to touch. We shouldn't write that documentation either, now: instead we should make it very much more easy to add a new translation for GeoNetwork.
+ 
+ * Schema plugins - currently support plugging in metadata schema/profile composed of xslts, XSDs etc (ie. whatever is in a GeoNetwork schema directory) - also needs to support adding jeeves services eg. services to search and retrieve taxonomic metadata from the Australian Plant and Fauna databases for Marine Community Profile or to retrieve keywords from an online Oceanographic thesaurus (neither of these databases use standard interfaces but the searches are important to Marine Community Profile members) - suggestions/thoughts on how to add services to jeeves dynamically? 
+ * Tracking changes to metadata - need to know who, what and when changes are made to metadata. How to do this as GeoNetwork? Perhaps a metadata history table triggered from the metadata table? Some comparison of metadata records from different versions would still be necessary to determine changes because in it's simplest form the history table would have a complete copy of the metadata record in it. 
 
  * ...
@@ -108 +112 @@
  * CSW 3.0
  * [http://hadoop.apache.org/ Hadoop], [http://nosql-database.org/ NoSQL] : useful to investigate for GN's future ?
+  * Feedback on the nosql approach has not been good from some quarters - some time was spent at Bolsena 2010 on investigating apache couchdb (see presentation at http://geonetwork.globaldial.com/testdownloads/GeoNetworkCouchDB.pdf) and although it has many interesting and attractive features for developers and does many things that GeoNetwork does, almost all potential users of GeoNetwork at least those I've spoken to in AU want it to evolve toward an object-relational mapping so that they integrate it with metadata in their relational databases. 
 
 === Presentations ===