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


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

--

Legend:

Unmodified
Added
Removed
Modified

  • codesprint/201106-bolsena

    v22 v23  
    114114  * 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.
    115115   * 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.
    116    * 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.
     116   * 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.
    117117  * Depends on where we want GeoNetwork to fit within an organisation?
    118118