Sophia, David, and I met to talk about GeoNode requirements for the Batch Uploader today and I wanted to get those notes out.
For background, OpenGeo's working on a Batch Uploader client application that users will be able to use to point at a directory of data and metadata and upload it to a GeoServer instance. From there, we are integrate with the GeoNode web application so that GeoNode users can browse that data through the web UI. What features does this entail for GeoNode (on top of the features being built as more generic community modules for GeoServer)? (David, correct me if I've gotten any of this wrong) First, as part of the extra plugins that GeoNode adds to GeoServer, we will need to add a listener to GeoServer that responds to new data being loaded into GeoServer's FTP server and ping the GeoNode web app. When the Django app gets the ping from the listener, it will import the new layer and the metadata from GeoServer's data directory. What's slightly hairy about this is that the uploader will have uploaded a metadata document which GeoServer normally wouldn't know what to do with, for the benefit of the web application grabbing it later. The web app will read the metadata from the uploaded XML and put it into the web app's model of the layer. It will then assign ownership of the layer to the site administrative user (this is pending approval by the World Bank). -- Sebastian Benthall OpenGeo - http://opengeo.org
