-
Notifications
You must be signed in to change notification settings - Fork 38
Rfc5: startkaartbeeld per mashup
At the moment, when a mashup is made, it's layertree and startup map are exactly the same as it's motherapplication. This change will give the administrator the possibility to change the startkaartbeeld of mashups, independent of it's mother application. Note that, as foreseen now, it's not possible to change the Boomstructuur met kaarten of a mashup. That is done in the motherapplication.
This change adds very little in terms of new screens. The only new screen is that the page of startkaartbeeld of mashups is now available, instead of a message saying you can't edit a mashups startkaartbeeld.
The changes needed for the completion of this functionality are described here.
The modules which are affected by these changes are split in the viewer, viewer-admin and the database.
The viewer will need to generate a tree (SelectedContent) according to the Boomstructuur met Kaarten of the motherapplication and the Startkaartbeeld of the mashup.
- The message in the Startkaartbeeld page should be removed and the startkaartbeeld should be displayed.
- When setting SelectedContentCaches dirty, check if that is still valid for the mashups
- When creating a mashup, take the updating of the layerids into account
Adjust tables
application_layer:
remove selected_index and checked
level_:
remove selected_index
Add tables
startmap_level
level
application
selected_index
startmap_layer
application
application_layer
selected_index
checked
adjust named queries
This change has quite some impact on existing installations with mashups. When implementing, there should be taken extra care when creating database scripts for transitioning to the new database model. User should be advised to create a backup when upgrading.
- Selected Content Caches
- updating of layerids of components
- Unit tests
- Test SelectedContent generation
- Cache dirty, new selectedcontent retrieved