search

akvo / akvo-reporting

Akvo reporting integration
2 stars 1 forks source link

RSR integration for 'paperless reporting' #32

Open Lynngre opened 9 years ago

Lynngre commented 9 years ago

Based on the requirements outlined here https://github.com/akvo/akvo-product-design/issues/6 @adriancollier @zzgvh & @lynngre had a discussion on how the ReportServer could provide a large portion of the charts and data required for paperless reporting.

Additional documentation here: https://github.com/akvo/akvo-product-design/tree/master/RSR/Features/6-PaperlessReporting/FunctionalDesign

Two mockups here:

https://www.dropbox.com/s/ks6wcszg86ykifd/RSR_reporting_over_time.pdf?dl=0

https://www.dropbox.com/s/r5jod3jumconu7x/RSR_paperlessreporting.pdf?dl=0

We are currently working on how this could be integrated into RSR but in such a way that it could also be used for integrating into other products such as Akvo Sites/Akvo.org, etc.

adriancollier commented 9 years ago

@kardan I think it might be a good idea if we setup to connect you with @Lynngre and @zzgvh as they are looking into pieces for Paperless Reporting

Lynngre commented 9 years ago

Yes thanks @adriancollier !

Lynngre commented 9 years ago

RSR is also looking at allowing private data. Allowing organisations to stipulate which user group can access which data, for example.

This raises the question of who will have permissions to which data and how will ReportServer know what those permissions are when serving a report?

This question is, of course from the ReportServer aspect, applicable to other products such as FLOW, too.

'Single sign-on' was discussed, as Akvo are looking at implementing this so it's a good place to start. http://keycloak.jboss.org/ has been chosen.

However, it goes deeper than this.

After discussing 'single sign-on' with @iperdomo it is clear that Keycloak is pure authentication. It will know which products have which groups, for instance, but will NOT know what the permissions are for those groups on the data, for example. This takes place at the application/product level.

How will ReportServer, using a 'copy' of the data, know what the permissions on the data are for a user? This becomes an even bigger issue when looking at mashing up data at the ReportServer from FLOW & RSR, for instance.

Lynngre commented 9 years ago

On hold for now