Yep. We've got all that in mind. Sophia is leading the uploader development; we'll let you know when things are up on a wiki for your review.
On Wed, Jun 16, 2010 at 12:19 PM, <[email protected]> wrote: > Makes sense with the sending to the geoserver, although as was discussed we > are going to have to do some things outside of GeoServer's normal usage > (i.e. metadata). Also, while it makes sense for it technically to be sending > to the geoserver instance the user will view it as the geonode instance > ontop of it that they are interacting with. Therefore, we will need to > figure out how the selecting/configuring the instance the uploader is > talking to from the UI perspective. > > > [image: Inactive hide details for Sebastian Benthall ---06/16/2010 11:11:53 > AM---Moving to the geonode mailing list, as this is getting]Sebastian > Benthall ---06/16/2010 11:11:53 AM---Moving to the geonode mailing list, as > this is getting technical. That all makes sense. > > > From: > Sebastian Benthall <[email protected]> > To: > [email protected] > Date: > 06/16/2010 11:11 AM > Subject: > [geonode] Re: Batch Uploader and Metadata > Sent by: > [email protected] > > > > ------------------------------ > > > > Moving to the geonode mailing list, as this is getting technical. > > That all makes sense. > > The metadata sounds good. It would be preferable if we could have it go > to the user account, but if that is significantly more difficult then > having > the admin account is fine. > > > To be clear, the admin account here would be _a_ user account, it would > just be an account set to have administrative privileges in the GeoNode > configuration. > > There is going to have to be able to be some configurability within the > Batch uploader no matter what as there will have to be able to be the > ability to select which GeoNode instance the user is selecting, if during > that process it is determined that also passing a specific users > credentials > is not significantly more work that would be best. > > > The issue is that the batch uploader will be configured to point at a > particular GeoServer instance, not a particular GeoNode instance, for the > purpose of decoupling the technology. > > We were talking about passing the credential through to the web app to > assign ownership, but it's a little cloudy to plan that out since we haven't > yet implemented the security sharing system and so we don't know the unknown > unknowns there. > > I agree that this is a desirable feature in the long run. > > Alternatively, if we use the first pass solution of assigning to the > admin we need to be able for the admin to select multiple files when > re-assigning metadata ownership so that the admin does not need to go > through the process for each file. > > > That's a good point about the UI on this. > > I bet there's a way to get the Django admin API to do these batch > operations. Will look into it. > > > > * From: *Sebastian Benthall [*[email protected]* <[email protected]>] > > * > Sent: *06/15/2010 05:21 PM AST* > To: *Galen Burr Evans > * Subject: *Batch Uploader and Metadata > > > Hi Galen, > > We've been hammering out the spec for the batch uploader, and I wanted > to run a couple details by you to make sure we're on the same page about > it. > > First, we want to allow users to be able to batch upload metadata. For > the format for this, we were thinking the metadata would be in XML format > in > a way that conforms to ISO19139, which is the same standard of which the > World Bank standards you sent to me earlier are a subset. > > Second, there was the question of which GeoNode users winds up owning > data that is batch uploaded. We think the most solid way to do it on a > first pass is to have anything batch uploaded to a GeoNode owned by the > site > administrative user by default. That user can then reassign ownership as > needed (once those features are in place.) We can expand this > functionality > in the future if users demand it. > > Does this work for you as the deliverables for the first round on th > batch uploader? > > -- > Sebastian Benthall > OpenGeo - *http://opengeo.org* <http://opengeo.org/> > > > > > > -- > Sebastian Benthall > OpenGeo - *http://opengeo.org* <http://opengeo.org/> > > > -- Sebastian Benthall OpenGeo - http://opengeo.org
<<graycol.gif>>
<<ecblank.gif>>
