Changes between Version 31 and Version 32 of codesprint/201106-bolsena


Ignore:
Timestamp:
Jun 19, 2011, 6:17:07 AM (13 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • codesprint/201106-bolsena

    v31 v32  
    122122 * [http://hadoop.apache.org/ Hadoop], [http://nosql-database.org/ NoSQL] : useful to investigate for GN's future ?
    123123  * Some time was spent at Bolsena 2010 on investigating one nosql approach - apache couchdb (see presentation at http://geonetwork.globaldial.com/testdownloads/GeoNetworkCouchDB.pdf) - it has many interesting and attractive features for developers and does many things that GeoNetwork does. This presentation provided the opportunity to discuss the nosql direction with various interested parties in AU. The feedback depended on where and how they were trying to integrate GeoNetwork within their organisation:
    124    * 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.
     124   * 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 that would allow them to integrate GeoNetwork with the metadata they already have in their relational databases.
    125125   * Feedback on nosql direction 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.
    126126  * Depends on where we want/or where we see GeoNetwork fitting within existing organisations?