Automated Updating of Services about mrmap HOT 1 CLOSED

The current idea is to inform the owner of the service, that it should be updated, since differences have been detected. The problem in here is, that we have to make sure, that database ID have to be kept, while new layers may have been added or existing ones have been deleted by the service provider. Furthermore: What happens in the case of a renamed layer? We are not able to understand automatically if a layer or featuretype has simply been renamed. We would identify it as a new subelement of a service, remove the old persisted metadata and create this new record - each time!

If a user somewhere has added a direct link to some subelements in his/her client application (like QGIS), these links would not work anymore, since the IDs have changed.

You see, the update process isn`t as simple as we would like to have it. We need the user interaction of manual deciding whether a "new" detected subelement is in fact only a renamed "old" subelement and so on.

The logic for this has been implemented a long time ago but due to a lot of recent changes, we need to refactor this process as well. This is something we have to do.

from mrmap.