Proposal of a new development for Marseille hackfest, feedback needed
Hi koha-devel, There are sometimes debates about how and who is using Koha, how it is setup, which decision is of general interest. I had 2 ideas that could be developed during the hackfest. 2 of BibLibre developers are very motivated by the idea, anyone else can join us ;-) **** 1st idea : collecting -anonymous- data on staff interface usage We sometimes are wondering whether librarians are running an old version of IE, or if they have a large screen, or if the page X is often run or not. There's a tool that could let us know: piwik (BibLibre already has an offer on Piwik for the OPAC) The idea here would be to add piwik for staff interface, and collect all datas on a single piwik instance. We made something (quick) for one of our current supported library, just to see what kind result we could get. We're quite happy with the performances, datas are interesting (which browser is used, which screen size, which pages. [ For example, the library runs an average of 40 times "reports/catalogue-stats.pl" every day (yes, that's crazy ;-) ). This page is worth being optimized !!! ] The only caveat we've seen for now is that it can be tricky to have many websites pointing to the same piwik database. We also are not completely peaceful with having 10 000 librarians calling the server. We could face a heavy load... But that's worth investigating imo. (for those who don't know what is piwik, it's like google analytics, but respect your privacy ;-) Ah, and it's a software developed by a frenchy, living in new zealand, that has office hosted by catalystNZ afaik) If the community likes the idea, we will ask him for any advice on the 2 caveats we fear. [ PS: please avoid starting a troll about piwik collecting anonymous data or not because of the IP. Anyway, the feature will be trigger-able by the library. ] **** 2nd idea : collecting nominative datas. We very often face the question "how many libraries are using Koha" So the idea is to have a form that let the library declare itself. Library name, type (academic, public,...), country,... We could also collect other data, like catalog size, systempreferences values to be able to make statistics. Example of answers we could get: * how many libraries are using Koha in Africa ? * What's the average catalog size ? Which library is the largest one ? * Is someone/how many libraries are using the "insecure" mode (syspref=insecure set to "Yes") ? [ If no, we can drop it ! ] Each library could choose to share or not the data (and maybe which level of data. One could accept to declare itself & share sysprefs, but not appear on nominative listings for example) A specific website could be made to display informations, either nominative or not. Do you like those ideas ? PS: BibLibre is of course willing to host piwik and "statistics" servers. -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper
On 12 February 2014 06:30, Paul Poulain <paul.poulain@biblibre.com> wrote:
Hi koha-devel,
There are sometimes debates about how and who is using Koha, how it is setup, which decision is of general interest. I had 2 ideas that could be developed during the hackfest. 2 of BibLibre developers are very motivated by the idea, anyone else can join us ;-)
**** 1st idea : collecting -anonymous- data on staff interface usage We sometimes are wondering whether librarians are running an old version of IE, or if they have a large screen, or if the page X is often run or not. There's a tool that could let us know: piwik (BibLibre already has an offer on Piwik for the OPAC) The idea here would be to add piwik for staff interface, and collect all datas on a single piwik instance. We made something (quick) for one of our current supported library, just to see what kind result we could get. We're quite happy with the performances, datas are interesting (which browser is used, which screen size, which pages. [ For example, the library runs an average of 40 times "reports/catalogue-stats.pl" every day (yes, that's crazy ;-) ). This page is worth being optimized !!! ]
The only caveat we've seen for now is that it can be tricky to have many websites pointing to the same piwik database. We also are not completely peaceful with having 10 000 librarians calling the server. We could face a heavy load...
But that's worth investigating imo.
(for those who don't know what is piwik, it's like google analytics, but respect your privacy ;-) Ah, and it's a software developed by a frenchy, living in new zealand, that has office hosted by catalystNZ afaik) If the community likes the idea, we will ask him for any advice on the 2 caveats we fear. [ PS: please avoid starting a troll about piwik collecting anonymous data or not because of the IP. Anyway, the feature will be trigger-able by the library. ]
Hi Paul I have cced the piwik devs who are indeed working in the Catalyst NZ offices (up on level 9, hi Matthieu and Thomas) who might have some ideas around this. Chris
Le 11/02/2014 20:09, Chris Cormack a écrit :
On 12 February 2014 06:30, Paul Poulain <paul.poulain@biblibre.com> wrote:
**** 1st idea : collecting -anonymous- data on staff interface usage We sometimes are wondering whether librarians are running an old version of IE, or if they have a large screen, or if the page X is often run or not. There's a tool that could let us know: piwik (BibLibre already has an offer on Piwik for the OPAC) The idea here would be to add piwik for staff interface, and collect all datas on a single piwik instance. We made something (quick) for one of our current supported library, just to see what kind result we could get. We're quite happy with the performances, datas are interesting (which browser is used, which screen size, which pages. [ For example, the library runs an average of 40 times "reports/catalogue-stats.pl" every day (yes, that's crazy ;-) ). This page is worth being optimized !!! ]
The only caveat we've seen for now is that it can be tricky to have many websites pointing to the same piwik database. We also are not completely peaceful with having 10 000 librarians calling the server. We could face a heavy load...
Hi Matthieu & Thomas, (From France, Marseille ;-) ) I'm not sure anymore my idea is a good one. I feel we will face 2 problems: * I wanted *any* Koha setup to be able to call a given piwik installation. It mean that piwik whould not check for the caller URL. It can be mylibrary.org or anotherfrenchlibrary.fr or kiwilibrary.nz * The volumes will be *huge*. We don't know exactly how many libraries are running Koha, but that may be 5000+, some of them being very very large (the largest french one is 50+ library branches and 200+ librarians). So I feel that 'piwiking' all libraries, all all branches and all librarians staff use will be more than huge, so a bad idea. Your opinion, any hint, welcomed ! PS for koha-devel => the other idea about collecting nominative datas is still a good one, at least I haven't found any technical problem with it yet. -- Paul Poulain - Associé-gérant Tel : (33) 4 91 81 35 08 http://www.biblibre.com Logiciels Libres pour les bibliothèques et les centres de documentation
We've used piwik on and off on a number of our sites to moderate success too. It leads to some interesting stats. I'd be happy to see it in the core along with sysprefs to opt in/out, and would be interested to see how another company has been using it too. I had issues with piwik becoming unusably slow so we abandoned it a couple of years ago, monitoring the project though it appears to have come on leaps and bounds. Count me in. On 11 Feb 2014 17:30, "Paul Poulain" <paul.poulain@biblibre.com> wrote:
Hi koha-devel,
There are sometimes debates about how and who is using Koha, how it is setup, which decision is of general interest. I had 2 ideas that could be developed during the hackfest. 2 of BibLibre developers are very motivated by the idea, anyone else can join us ;-)
**** 1st idea : collecting -anonymous- data on staff interface usage We sometimes are wondering whether librarians are running an old version of IE, or if they have a large screen, or if the page X is often run or not. There's a tool that could let us know: piwik (BibLibre already has an offer on Piwik for the OPAC) The idea here would be to add piwik for staff interface, and collect all datas on a single piwik instance. We made something (quick) for one of our current supported library, just to see what kind result we could get. We're quite happy with the performances, datas are interesting (which browser is used, which screen size, which pages. [ For example, the library runs an average of 40 times "reports/catalogue-stats.pl" every day (yes, that's crazy ;-) ). This page is worth being optimized !!! ]
The only caveat we've seen for now is that it can be tricky to have many websites pointing to the same piwik database. We also are not completely peaceful with having 10 000 librarians calling the server. We could face a heavy load...
But that's worth investigating imo.
(for those who don't know what is piwik, it's like google analytics, but respect your privacy ;-) Ah, and it's a software developed by a frenchy, living in new zealand, that has office hosted by catalystNZ afaik) If the community likes the idea, we will ask him for any advice on the 2 caveats we fear. [ PS: please avoid starting a troll about piwik collecting anonymous data or not because of the IP. Anyway, the feature will be trigger-able by the library. ]
**** 2nd idea : collecting nominative datas. We very often face the question "how many libraries are using Koha" So the idea is to have a form that let the library declare itself. Library name, type (academic, public,...), country,... We could also collect other data, like catalog size, systempreferences values to be able to make statistics.
Example of answers we could get: * how many libraries are using Koha in Africa ? * What's the average catalog size ? Which library is the largest one ? * Is someone/how many libraries are using the "insecure" mode (syspref=insecure set to "Yes") ? [ If no, we can drop it ! ]
Each library could choose to share or not the data (and maybe which level of data. One could accept to declare itself & share sysprefs, but not appear on nominative listings for example) A specific website could be made to display informations, either nominative or not.
Do you like those ideas ?
PS: BibLibre is of course willing to host piwik and "statistics" servers. -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Hi, Paul: your proposal of nominative data is very interesting, in my opinion. If possible, let users (superlibrarians only?) not only to add the library profile, but also change it to ensure that upgrades will be tracked. Stefano On 11/feb/2014, at 18.30, Paul Poulain wrote:
Hi koha-devel,
There are sometimes debates about how and who is using Koha, how it is setup, which decision is of general interest. I had 2 ideas that could be developed during the hackfest. 2 of BibLibre developers are very motivated by the idea, anyone else can join us ;-)
**** 1st idea : collecting -anonymous- data on staff interface usage We sometimes are wondering whether librarians are running an old version of IE, or if they have a large screen, or if the page X is often run or not. There's a tool that could let us know: piwik (BibLibre already has an offer on Piwik for the OPAC) The idea here would be to add piwik for staff interface, and collect all datas on a single piwik instance. We made something (quick) for one of our current supported library, just to see what kind result we could get. We're quite happy with the performances, datas are interesting (which browser is used, which screen size, which pages. [ For example, the library runs an average of 40 times "reports/catalogue-stats.pl" every day (yes, that's crazy ;-) ). This page is worth being optimized !!! ]
The only caveat we've seen for now is that it can be tricky to have many websites pointing to the same piwik database. We also are not completely peaceful with having 10 000 librarians calling the server. We could face a heavy load...
But that's worth investigating imo.
(for those who don't know what is piwik, it's like google analytics, but respect your privacy ;-) Ah, and it's a software developed by a frenchy, living in new zealand, that has office hosted by catalystNZ afaik) If the community likes the idea, we will ask him for any advice on the 2 caveats we fear. [ PS: please avoid starting a troll about piwik collecting anonymous data or not because of the IP. Anyway, the feature will be trigger-able by the library. ]
**** 2nd idea : collecting nominative datas. We very often face the question "how many libraries are using Koha" So the idea is to have a form that let the library declare itself. Library name, type (academic, public,...), country,... We could also collect other data, like catalog size, systempreferences values to be able to make statistics.
Example of answers we could get: * how many libraries are using Koha in Africa ? * What's the average catalog size ? Which library is the largest one ? * Is someone/how many libraries are using the "insecure" mode (syspref=insecure set to "Yes") ? [ If no, we can drop it ! ]
Each library could choose to share or not the data (and maybe which level of data. One could accept to declare itself & share sysprefs, but not appear on nominative listings for example) A specific website could be made to display informations, either nominative or not.
Do you like those ideas ?
PS: BibLibre is of course willing to host piwik and "statistics" servers. -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Hiya Paul et al! I think those are two very interesting ideas, well worth pursuing. A wiki page describing something similar to the second idea was created a while ago: http://wiki.koha-community.org/wiki/Add_a_button_to_the_intranet_for_registe... Au revoir! Magnus libriotech.no On 11 February 2014 18:30, Paul Poulain <paul.poulain@biblibre.com> wrote:
Hi koha-devel,
There are sometimes debates about how and who is using Koha, how it is setup, which decision is of general interest. I had 2 ideas that could be developed during the hackfest. 2 of BibLibre developers are very motivated by the idea, anyone else can join us ;-)
**** 1st idea : collecting -anonymous- data on staff interface usage We sometimes are wondering whether librarians are running an old version of IE, or if they have a large screen, or if the page X is often run or not. There's a tool that could let us know: piwik (BibLibre already has an offer on Piwik for the OPAC) The idea here would be to add piwik for staff interface, and collect all datas on a single piwik instance. We made something (quick) for one of our current supported library, just to see what kind result we could get. We're quite happy with the performances, datas are interesting (which browser is used, which screen size, which pages. [ For example, the library runs an average of 40 times "reports/catalogue-stats.pl" every day (yes, that's crazy ;-) ). This page is worth being optimized !!! ]
The only caveat we've seen for now is that it can be tricky to have many websites pointing to the same piwik database. We also are not completely peaceful with having 10 000 librarians calling the server. We could face a heavy load...
But that's worth investigating imo.
(for those who don't know what is piwik, it's like google analytics, but respect your privacy ;-) Ah, and it's a software developed by a frenchy, living in new zealand, that has office hosted by catalystNZ afaik) If the community likes the idea, we will ask him for any advice on the 2 caveats we fear. [ PS: please avoid starting a troll about piwik collecting anonymous data or not because of the IP. Anyway, the feature will be trigger-able by the library. ]
**** 2nd idea : collecting nominative datas. We very often face the question "how many libraries are using Koha" So the idea is to have a form that let the library declare itself. Library name, type (academic, public,...), country,... We could also collect other data, like catalog size, systempreferences values to be able to make statistics.
Example of answers we could get: * how many libraries are using Koha in Africa ? * What's the average catalog size ? Which library is the largest one ? * Is someone/how many libraries are using the "insecure" mode (syspref=insecure set to "Yes") ? [ If no, we can drop it ! ]
Each library could choose to share or not the data (and maybe which level of data. One could accept to declare itself & share sysprefs, but not appear on nominative listings for example) A specific website could be made to display informations, either nominative or not.
Do you like those ideas ?
PS: BibLibre is of course willing to host piwik and "statistics" servers. -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
participants (5)
-
Chris Cormack -
Magnus Enger -
Martin Renvoize -
Paul Poulain -
Stefano Bargioni