I've made some tickets about these
> Django: > * map_download is called with a map_id. It could filter out unreadable > layers from the layers it requests from the batch process [major, to avoid > bad user experience] > http://projects.opengeo.org/CAPRA/ticket/794 > * batch_layer_download gets a list of layers. I don't know whether it > would be better to return a 401 or some other error in this case, or to > proceed with the unreadable layers filtered out. [minor, can hide on the UI > layer] > > I think this comes to another question about our public HTTP interface. > I'm bringing this up primarily to raise the question of what to about it in > the short term, but also because it has implications for what will be our > API. > Didn't make a ticket about this yet because I'm not confident about which solution is best. > JavaScript, Templates > We could disable the 'select' checkbox on the Data Search page for layers > that aren't Readable. [major, to avoid bad user experience of trying to get > inaccessible batches and dealing with error handling] > http://projects.opengeo.org/CAPRA/ticket/793 > The 'download.html' template for batch downloading maps could notify the > user whether layers in the map aren't readable and tell them that they won't > be included in the batch. [minor, UI polish] > http://projects.opengeo.org/CAPRA/ticket/795 -- Sebastian Benthall OpenGeo - http://opengeo.org
