Folks, I am looking for suggestions on the best long term, architectural solution to add charting for Koha reports. Do we use: - Google visualization API - Perl module Chart - Perl module GD - something else? Also any input on adding Business Intelligence capabilities? - Perl module Business::Intelligenece::Microstrategy - Integrate with other open source BI tool like Pentaho, Jaspersoft - something else? Thanks! Savitra
savitra sirohi wrote:
Folks, I am looking for suggestions on the best long term, architectural solution to add charting for Koha reports.
Do we use: - Google visualization API - Perl module Chart - Perl module GD - something else?
I'd prefer a Perl module to a closed-source cloud service (for both ethical/privacy and practical debugging reasons), but it's been years since I really reviewed the field.
Also any input on adding Business Intelligence capabilities?
Not from me, sorry. Hope that helps, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. Past Koha Release Manager (2.0), LMS programmer, statistician, webmaster. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha
On Wed, Jan 19, 2011 at 3:15 AM, savitra sirohi <savitra.sirohi@osslabs.biz> wrote:
Folks, I am looking for suggestions on the best long term, architectural solution to add charting for Koha reports.
Do we use: - Google visualization API - Perl module Chart - Perl module GD - something else?
We used JQplot for several charts. To+
On Wed, Jan 19, 2011 at 1:15 AM, savitra sirohi <savitra.sirohi@osslabs.biz> wrote:
Folks, I am looking for suggestions on the best long term, architectural solution to add charting for Koha reports.
Do we use: - Google visualization API - Perl module Chart - Perl module GD
GD is already a Koha dependency, so going with that would avoid adding another dependency. Kind Regards, Chris
On 19/01/11 12:50, Chris Nighswonger wrote:
On Wed, Jan 19, 2011 at 1:15 AM, savitra sirohi <savitra.sirohi@osslabs.biz> wrote:
Folks, I am looking for suggestions on the best long term, architectural solution to add charting for Koha reports.
Do we use: - Google visualization API - Perl module Chart - Perl module GD
GD is already a Koha dependency, so going with that would avoid adding another dependency.
And I've seen it used to produce some nice looking reports. Definitely worth looking at. Cheers Colin -- Colin Campbell Chief Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 845 557 5634 (phone) +44 (0) 7759 633626 (mobile) colin.campbell@ptfs-europe.com skype: colin_campbell2 http://www.ptfs-europe.com
On Wed, Jan 19, 2011 at 11:34 AM, Colin Campbell <colin.campbell@ptfs-europe.com> wrote:
On 19/01/11 12:50, Chris Nighswonger wrote:
On Wed, Jan 19, 2011 at 1:15 AM, savitra sirohi <savitra.sirohi@osslabs.biz> wrote:
Folks, I am looking for suggestions on the best long term, architectural solution to add charting for Koha reports.
Do we use: - Google visualization API - Perl module Chart - Perl module GD
GD is already a Koha dependency, so going with that would avoid adding another dependency.
And I've seen it used to produce some nice looking reports. Definitely worth looking at.
I'ts server-side. I'd prefer sending the client all the data inside a json and a javacsript library to render everything ono the client side. My 2 cents To+
Le 19/01/2011 16:04, Tomas Cohen Arazi a écrit :
I'ts server-side. I'd prefer sending the client all the data inside a json and a javacsript library to render everything ono the client side. shouldn't we just wait for html5 support then (isn't this in html5. Not sure at all, if someone want to confirm...)
-- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
El 19/01/2011 16:34, Paul Poulain escribió:
Le 19/01/2011 16:04, Tomas Cohen Arazi a écrit :
I'ts server-side. I'd prefer sending the client all the data inside a json and a javacsript library to render everything ono the client side. shouldn't we just wait for html5 support then (isn't this in html5. Not sure at all, if someone want to confirm...)
The canvas element is part of HTML5 and allows for dynamic, scriptable rendering of 2D shapes and bitmap images. [SIC] http://en.wikipedia.org/wiki/Canvas_element The element is supported by the current versions of Mozilla Firefox, Google Chrome, Safari, and Opera. Current versions of Internet Explorer including IE 8 cannot natively display canvas content.[7] Google and Mozilla plugins are available[8] and support is under development for Internet Explorer 9. [SIC] http://en.wikipedia.org/wiki/Canvas_element http://en.wikipedia.org/wiki/Canvas_element http://en.wikipedia.org/wiki/Comparison_of_layout_engines_(HTML5_Canvas)
2011/1/19 Salvador Zaragoza Rubio <salvazm@masmedios.com>:
El 19/01/2011 16:34, Paul Poulain escribió:
Le 19/01/2011 16:04, Tomas Cohen Arazi a écrit :
I'ts server-side. I'd prefer sending the client all the data inside a json and a javacsript library to render everything ono the client side. shouldn't we just wait for html5 support then (isn't this in html5. Not sure at all, if someone want to confirm...)
The canvas element is part of HTML5 and allows for dynamic, scriptable rendering of 2D shapes and bitmap images. [SIC] http://en.wikipedia.org/wiki/Canvas_element
If we agree this should be done client-side, we could see several js libraries roadmaps to see if they will be porting to canvas element soon. To+
On Wed, Jan 19, 2011 at 10:04 AM, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
On Wed, Jan 19, 2011 at 11:34 AM, Colin Campbell <colin.campbell@ptfs-europe.com> wrote:
On 19/01/11 12:50, Chris Nighswonger wrote:
On Wed, Jan 19, 2011 at 1:15 AM, savitra sirohi <savitra.sirohi@osslabs.biz> wrote:
Folks, I am looking for suggestions on the best long term, architectural solution to add charting for Koha reports.
Do we use: - Google visualization API - Perl module Chart - Perl module GD
GD is already a Koha dependency, so going with that would avoid adding another dependency.
And I've seen it used to produce some nice looking reports. Definitely worth looking at.
I'ts server-side. I'd prefer sending the client all the data inside a json and a javacsript library to render everything ono the client side.
So what are the pros/cons for server-side/client-side processing of charts? Kind Regards, Chris
On Wed, Jan 19, 2011 at 1:39 PM, Chris Nighswonger <cnighswonger@foundations.edu> wrote:
So what are the pros/cons for server-side/client-side processing of charts?
If you used google chart API you will see you can enjoy several features like zooming, region selection, etc that are nice. The same for pie charts where you can choose several pieces and work with their values. I not very creative today but some interactivity might be useful. Modifying the graphs without reloading. The server-load part perhaps is not very important as this feature would be used primarly on the staff interface. To+
On 20 January 2011 05:45, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
On Wed, Jan 19, 2011 at 1:39 PM, Chris Nighswonger <cnighswonger@foundations.edu> wrote:
So what are the pros/cons for server-side/client-side processing of charts?
If you used google chart API you will see you can enjoy several features like zooming, region selection, etc that are nice. The same for pie charts where you can choose several pieces and work with their values.
I personally think we should take that out of the mix. If we were to do client side, I agree with MJ that it should be done using free software. Not a closed source cloud API. Again both for ethical (friends don't let friends use proprietary software :)) and practical reasons (depending on an Opaque API that might change makes maintenance hard). So if we were to do it clientside, what Free Software library could we use, and what benefits would that give us over a server side library and are their any downsides. Chris
On Wed, Jan 19, 2011 at 1:58 PM, Chris Cormack <chris@bigballofwax.co.nz> wrote:
On 20 January 2011 05:45, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
On Wed, Jan 19, 2011 at 1:39 PM, Chris Nighswonger <cnighswonger@foundations.edu> wrote:
So what are the pros/cons for server-side/client-side processing of charts?
If you used google chart API you will see you can enjoy several features like zooming, region selection, etc that are nice. The same for pie charts where you can choose several pieces and work with their values.
I personally think we should take that out of the mix. If we were to do client side, I agree with MJ that it should be done using free software. Not a closed source cloud API. Again both for ethical (friends don't let friends use proprietary software :)) and practical reasons (depending on an Opaque API that might change makes maintenance hard).
So if we were to do it clientside, what Free Software library could we use, and what benefits would that give us over a server side library and are their any downsides.
I fully agree that we should use a free and open source library, I proposed trying JQplot (http://www.jqplot.com/). In my email, I used the example of google's library for pointing the kind of usability that a library on the client could allow. To+
participants (8)
-
Chris Cormack -
Chris Nighswonger -
Colin Campbell -
MJ Ray -
Paul Poulain -
Salvador Zaragoza Rubio -
savitra sirohi -
Tomas Cohen Arazi