Integrate/Associate Query Module Configuration(s) with Indicator Profile Reports

[Garth Braithwaite]

Now that we have the saved query function IP Views can have a URL to a saved query definition that a user can click on while on the IP report page. The IP editor can either run the query or take the user to the query builder interface page.

The reverse is also possible where a query module XML element can be added for any given configuration that contains URL(s) to IP reports.

Another benefit is for updating IP View Values from a query. This works well IF the IP struct is changed to a more generic dimension/measure structure to match the IBIS-Q XML struct.

Was ticket 173: Build an association between the IP view and Query Module. This would allow sharing of meta data and hitting the query module dataset from the IP page.

Build an interface in the admin app that an Indicator Editor or Owner or the Admin user can run the view app's query builder interface then save a query definition to the "system" definitions. The view app can then have a controller that serves up the system definitions to the admin app so that an IP editor can select the saved definition and assign/associate it with the IP view. A db table will be setup such that 1:n queries can be assigned to any given view.

For the reverse, the query module XML configuration section will be updated to support a series of INDICATOR_PROFILE_VIEW elements with a title and name etc.

related to tickets #104 (saved query), #33 (new storage struct).

[(none)]

Milestone Parking Lot deleted