- Koha-devel - lists.koha-community.org

Call for Development news - February Newsletter
by Koha Newsletter 27 Feb '14

27 Feb '14

Koha Developers ~ We'd like to improve our coverage of Koha developments in the monthly newsletter. We'll be checking the feeds, wiki and IRC minutes, however ... If you have any suggestions for us or projects/items/features/fixes you think are important [ or interesting ] for the community to know about we'd appreciate your input and knowledge. k o h a news AT gmail dot com Thank you! [ I'll send this email out sooner next month ...sorry for the late notice! CR ] -- Chad Roseburg Joanne Dillon Editors, Koha Newsletter

1 0

DataTables - using class names in aTargets
by Galen Charlton 27 Feb '14

27 Feb '14

Hi, There have been a fair number of bugs filed for fixing table sorting as columns get added to or removed from tables. At root, they stem from our current habit of referring to columns by numeric position in aoColumns and aoColumnDefs/aTargets, e.g., { "aTargets": [ 1, 2 ], "sType": "natural" } and "aoColumns": [ { "sType": "title-string" },{ "sType": "html" },null,{ "sType": "title-string" },null,null,null,null,null,null[% IF ( exports_enabled ) %],null[% END %] ], However, the documentation for DataTables says that aTargets doesn't have to be just an array of integers; it can also be "a string - class name will be matched on the TH for the column". To reduce the risk of silly columns-sorting bugs, I suggest that we adopt a practice of using descriptive CSS class names for table headers and using the class names in aoColumnsDefs/aTarget specifications, and dropping the use of aoColumns. Thoughts? Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc(a)esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org

3 3

Re: [Koha-devel] DataTables - using class names in aTargets
by David Cook 27 Feb '14

27 Feb '14

+1 -----Original Message----- Date: Tue, 25 Feb 2014 09:34:55 -0800 From: Galen Charlton <gmc(a)esilibrary.com> To: "koha-devel(a)lists.koha-community.org" <koha-devel(a)lists.koha-community.org> Subject: [Koha-devel] DataTables - using class names in aTargets Message-ID: <CAPLnt64r5EfNogfH2Q=_RWux=f3E9BuALOS5Ggnft_FkrqQH_g(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hi, There have been a fair number of bugs filed for fixing table sorting as columns get added to or removed from tables. At root, they stem from our current habit of referring to columns by numeric position in aoColumns and aoColumnDefs/aTargets, e.g., { "aTargets": [ 1, 2 ], "sType": "natural" } and "aoColumns": [ { "sType": "title-string" },{ "sType": "html" },null,{ "sType": "title-string" },null,null,null,null,null,null[% IF ( exports_enabled ) %],null[% END %] ], However, the documentation for DataTables says that aTargets doesn't have to be just an array of integers; it can also be "a string - class name will be matched on the TH for the column". To reduce the risk of silly columns-sorting bugs, I suggest that we adopt a practice of using descriptive CSS class names for table headers and using the class names in aoColumnsDefs/aTarget specifications, and dropping the use of aoColumns. Thoughts? Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc(a)esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org

3 2

Feedback requested
by Mark Tompsett 26 Feb '14

26 Feb '14

Greetings, I was wondering if other developers would care to comment on recommended disk space sizes for a git install on Bug 11830. Thank you! GPML, Mark Tompsett

3 2

[QA] QA break between tonight and the beginning of the hackfest in Marseille
by Fischer, Katrin 26 Feb '14

26 Feb '14

Hi QA team, as a result of yesterday’s developer meetings we are going to take a short break from QAing in order to give Galen the opportunity to clean out the Passed QA queue before the hackfest in Marseille. Please focus on sign offs and kitten rescue (looking at bugs in Failed QA, Doesn’t apply) during this and next week instead. Thank you! Katrin

1 0

Database in specific directory & backup
by Andrea Furin 26 Feb '14

26 Feb '14

hi to all. two questions: 1. is it possible to save the koha database in a specific directory, like in home directory in a second hard drive? 2. for making regular backups is it better to have only one partition in an hard drive (system + data) and create an image file of the hard disk and save it in other storage devices instead of having an hard disk for system and another for data? (i noticed that config files are in different places in system partition) tia andrea furin --

1 0

FW: [Koha] 3.14 Koha (Pie)
by Marcel de Rooy 26 Feb '14

26 Feb '14

"Cherry picked" from Koha ML. Compliments for Brendan and Galen. As well as for the March 14 option from Heather :) ________________________________________ Van: koha-bounces(a)lists.katipo.co.nz [koha-bounces(a)lists.katipo.co.nz] namens Hernandez, Heather [heather_hernandez(a)nps.gov] Verzonden: dinsdag 25 februari 2014 23:10 Aan: Brendan Gallagher CC: koha(a)lists.katipo.co.nz Onderwerp: Re: [Koha] 3.14 Koha (Pie) Hey, Brendan-- You didn't wait until Mar. 14?:) I hope he enjoys his Pi Pie! Cheerio! --heather ~~~~~~~~~~~~~~ Heather Hernandez Technical Services Librarian Cultural Resources and Museum Management Division San Francisco Maritime National Historical Park heather_hernandez(a)nps.gov 415-561-7032 (voice) 415-556-3540 (fax) http://www.nps.gov/safr/historyculture/library-collections.htm "The sailor does not pray for wind, he learns to sail."--Gustaf Lindborg _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Proposal of a new development for Marseille hackfest, feedback needed
by Paul Poulain 24 Feb '14

24 Feb '14

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

5 5

foss4lib webinars about OpenSource in libraries
by Paul Poulain 24 Feb '14

24 Feb '14

Not really a developer thing, but I see that foss4lib organise some webinars about "OpenSource". Does anyone from this mailing list plan to attend one of them or know what they'll talk about ? ( https://foss4lib.org/content/free-webinars-introducing-foss4lib ) -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper

1 0

Install Koha 3.14.03 with Single Command in Ubuntu 12.04 LTS
by DP Tripathi 22 Feb '14

22 Feb '14

Dear Library Professionals! Install Koha 3.14 with single command in Ubuntu 12.04 LTS. Download and keep the file wherever you wish to keep in the server. (For ex: someone keeps the file at Desktop) then run the following command. This script assumes that you have Apache and MySQL pre-installed in your system. Login as root: sudo su (Enter) Enter the password: Run the following command: *root@localhost:/home/library/Desktop# *chmod +x install_koha.sh *root@localhost:/home/libraryDesktop# *./install_koha.sh Ensure that your system is connected with Internet. Follow the Instruction. Add the port 8080 (Listen 8080) when it asks to add and save & close the file. It will install Koha 3.14 in your system. To open the Interface, use the following user id and password. User ID : koha_library Password: (please note down the password from terminal, it appears like 10ImCcKq3QHpfdx7) Enjoy! Feel free to contact at dptkvs(a)gmail.com, if you face any problem. Download the File at http://librarianguide.in/install_koha.sh Thanks! -- ********************* D. P. Tripathi Assistant Librarian Biju Patnaik Central Library NIT Rourkela Odisha - 769008 India www.librarianguide.in **********************

1 0