jj0hns0n/geonode-temp — Issue #7: E&R: Saving and loading a context document from the server
Author: jj0hns0n
Created: 2011-12-12 10:01:00+00:00
State: open
Labels: Meta

Saving (and presumably loading) a context document from the server would be a kind of map export we could support.

From [wiki:JSCAPRAOverview]:

{{{
Export functionality
===============

sort of a catchall, export may be the only step in a user workflow,
and will be the endpoint for many workflows.

different forms:

* Save: persisting a context document to the server (possibly just a
json state dump)
}}}

Cholmes' comment on implementation is here:
{{{
Justin's working on it, page will be at http://geoserver.org/display/GEOS/User+Calloboration+REST+API

It will be a put/get on /users/cholmes/maps/ If a user does not have a login then a put/get on /geoserver/rest/maps/

If we don't do full toolbar configuration then we may be able to get away with having all the options in a url, and not need a rest api. Perhaps we only let logged in users do the advanced export options.
}}}

Dwins recommends this implementation strategy:
{{{
In the spirit of doing the stupidest thing that could possibly work, I
propose that we implement this in terms of the existing file upload
extension. It supports random filter extensions to impose file size
limits and other validity checks so we can just have it deny uploads of
things that are not valid JSON for round 1, with moar bettar filtering
when we're out of POC mode. Coding requirements:
* let it accept raw PUTs as well as file fields in POSTed forms
* implement a json-only filter.
}}}

We need to nail down what's going on here, and then this functionality should be broken down into actionable and estimated tickets. This ticket should be closed when those tickets have been made.