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

Timestamp:

Jun 19, 2011, 3:05:52 AM (13 years ago)

Author:

simonp

Comment:

--

codesprint/201106-bolsena

@@ -101 +101 @@
  
  * 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. 
+ * Tracking changes to metadata - need to know who, what and when changes are made to metadata. How to do this as GeoNetwork? Perhaps a database driven approach which uses a metadata history table that is 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. 
 
  * ...
@@ -112 +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. 
+  * Some time was spent at Bolsena 2010 on investigating apache couchdb (see presentation at http://geonetwork.globaldial.com/testdownloads/GeoNetworkCouchDB.pdf) and it has many interesting and attractive features for developers and does many things that GeoNetwork does.
+   * Feedback on nosql direction from those that want to use GeoNetwork to manage their metadata in relational databases is not so good: almost all of these potential users of GeoNetwork (at least those I've spoken to in AU anyway!) want GeoNetwork to evolve toward using an object-relational mapping as they believe they have the skills to integrate GeoNetwork with the metadata they already have in their relational databases.
+   * Feedback from those that are happy to continue managing metadata using their existing tools and databases but want to publish metadata to GeoNetwork because of its interoperability and standards support: they probably don't care as they are happy to use components like the WFS GetFeature harvester to build metadata records from the metadata in their relational databases.
+  * Depends on where we want GeoNetwork to fit within an organisation? 
 
 === Presentations ===