Re: [Koha-devel] Question about Schema
You can fill a bug report, it's a bug :) 2015-08-25 14:57 GMT+01:00 Philippe Blouin philippe.blo...@inlibro.com: Simple question I'm sure, but there's this bug in circulation.tt that shows I haven't played much with the new Schema structure: (circulation.tt, line 672) [% IF ( issue ) %] div class=lastchecked pstrongChecked out: /strong[% issue.item.biblio.title %] ([% issue.item.barcode %]). Due on [% issue.date_due | $KohaDates %]/p /div [% END %] This (in bold) never shows up. The item.biblio link, well, it doesn't exists in the Result::Item per my understanding. Whatever I tried with biblioitem(s) in between didn't pan either. Suggestions would be appreciated. (If this is indeed a bug and not a code 18, I'll be happy to do the paperwork to file it in) Thanks, Blou ___ 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/ ___ 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/
[Koha-devel] Question about Schema
Simple question I'm sure, but there's this bug in circulation.tt that shows I haven't played much with the new Schema structure: (circulation.tt, line 672) [% IF ( issue ) %] div class=lastchecked pstrongChecked out: /strong[% *issue.item.biblio.title* %] ([% issue.item.barcode %]). Due on [% issue.date_due | $KohaDates %]/p /div [% END %] This (*in bold*) never shows up. The item.biblio link, well, it doesn't exists in the Result::Item per my understanding. Whatever I tried with biblioitem(s) in between didn't pan either. Suggestions would be appreciated. (If this is indeed a bug and not a code 18, I'll be happy to do the paperwork to file it in) Thanks, Blou ___ 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/
[Koha-devel] schema.k-c.org
Could we please update the schemaspy files on the site? They have lagged a lot. I'm not sure who runs it, just wanted to make him/her notice it needs updating. ___ 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/
Re: [Koha-devel] Refactoring of tools/export.pl (Hector Castro)
Excellent work, Jonathan +1 On Tue, Aug 25, 2015 at 7:30 AM, koha-devel-requ...@lists.koha-community.org wrote: Message: 2 Hi devs, I have just submitted a patch on bug 14722 to refactor the script tools/export.pl to make it more readable and robust. I have also created a new script misc/export.pl for the command line usage. If you are interested, just have a look and give me some feedbacks. Cheers, Jonathan http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14722 -- -- Atte, Héctor Eduardo Castro Avalos ___ 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/
Re: [Koha-devel] Koha Statistics
Thank you all Really an excellent information to share with all Librarians, and those who are willing to shift to Koha software. I am sure no other ILS is having such a great development.!!! Once again Thanks On Tue, Aug 25, 2015 at 4:06 PM, Tomas Cohen Arazi tomasco...@gmail.com wrote: El 25/8/2015 3:32 a. m., Chris Cormack ch...@bigballofwax.co.nz escribió: Hi I did some research, and got this http://blog.bigballofwax.co.nz/2015/08/25/some-random-statistics-about-the-last-5-years-of-koha/ Wow!! Those are really impressive numbers! Well done Chris -- Warm Regards Dr. Sandeep Bhavsar Librarian *Prin. L. N. Welingkar Institute of Management Development Research (AUTONOMOUS)* L Napoo Road | Matunga (CR) | Mumbai- 400 019. Tel: 022-2419 8377 | Mob: 9870 18 Library Portal*: http://elearn.welingkar.org/infowe http://elearn.welingkar.org/infowe* ___ 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/
Re: [Koha-devel] schema.k-c.org
On Tue, Aug 25, 2015 at 9:07 PM, Tomas Cohen Arazi tomasco...@gmail.com wrote: Thanks Chris! I saw it is already updated! I'd like to echo Tomas' thanks. --Barton ___ 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/
Re: [Koha-devel] Refactoring of tools/export.pl
Great job Jonathan! 2015-08-25 7:48 GMT-03:00 Jonathan Druart jonathan.dru...@bugs.koha-community.org: Hi devs, I have just submitted a patch on bug 14722 to refactor the script tools/export.pl to make it more readable and robust. I have also created a new script misc/export.pl for the command line usage. If you are interested, just have a look and give me some feedbacks. Cheers, Jonathan http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14722 ___ 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/ ___ 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/
[Koha-devel] Bug 14321: Koha::Upload
Hi all, This bug is a follow-up of the recently pushed new feature for uploading (bug 6874). The follow-up originates from the QA comments on that report. Although its aim was kind of architectural: merge two modules into a new one, it does more. It introduces a new tools form: tools/upload.pl for general uploads. We could later merge upload local cover images, patron images, etc. into that one too. New is the progress based on ajax code. Multiple uploads are supported and aborting an upload. This could be the base of some more extensions, but it needs your attention.. So, your signoff is very welcome ! Thanks, Marcel ___ 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/
Re: [Koha-devel] Koha Statistics
Hi Sandeep :-) Here are two links which are worth exploring: - BlackDuck Open Hub : https://www.openhub.net/p/koha - Git Stats : http://git.koha-community.org/stats/koha-master/index.html Hope this helps to answer some of your questions. All the best for your upcoming seminar. Irma CALYX On 25 August 2015 at 00:57, Dr. Sandeep Bhavsar sandeep.bhav...@gmail.com wrote: Dear All Will you be able to help me in getting the statistics of koha 1) How many bugs solved in koha in last 5 years 2) How many features add in last 5 years 3) Major developments I will share this statistics in upcoming seminar of Koha in India. Would like to show the audience that how fast koha is developing -- Warm Regards Dr. Sandeep Bhavsar Librarian *Prin. L. N. Welingkar Institute of Management Development Research (AUTONOMOUS)* L Napoo Road | Matunga (CR) | Mumbai- 400 019. Tel: 022-2419 8377 | Mob: 9870 18 Library Portal*: http://elearn.welingkar.org/infowe http://elearn.welingkar.org/infowe* ___ 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/ ___ 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/
[Koha-devel] Refactoring of tools/export.pl
Hi devs, I have just submitted a patch on bug 14722 to refactor the script tools/export.pl to make it more readable and robust. I have also created a new script misc/export.pl for the command line usage. If you are interested, just have a look and give me some feedbacks. Cheers, Jonathan http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14722 ___ 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/
Re: [Koha-devel] Koha Statistics
El 25/8/2015 3:32 a. m., Chris Cormack ch...@bigballofwax.co.nz escribió: Hi I did some research, and got this http://blog.bigballofwax.co.nz/2015/08/25/some-random-statistics-about-the-last-5-years-of-koha/ Wow!! Those are really impressive numbers! Well done Chris ___ 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/
Re: [Koha-devel] schema.k-c.org
Could this be made part of the build process? On Tue, Aug 25, 2015 at 9:59 AM, Tomas Cohen Arazi tomasco...@gmail.com wrote: Could we please update the schemaspy files on the site? They have lagged a lot. I'm not sure who runs it, just wanted to make him/her notice it needs updating. ___ 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/ ___ 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/
Re: [Koha-devel] Koha Statistics
Hi I did some research, and got this http://blog.bigballofwax.co.nz/2015/08/25/some-random-statistics-about-the-last-5-years-of-koha/ Chris ___ 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/
Re: [Koha-devel] Facilitate integration of some patches
I'd say it should be evaluated on a per-bug/patch basis. Overall I agree, but let the QAM and the RM have the final word about the bugs qualifying for this proposed fast-track treatment. I will add this to tomorrow's agenda for formally talking about this. 2015-08-20 12:44 GMT-03:00 Jonathan Druart jonathan.dru...@bugs.koha-community.org: I should have added that I can engage my own responsibility and will provide a fix as quickly as possible if the patch introduced a regression or was buggy. 2015-08-20 15:03 GMT+01:00 Marcel de Rooy m.de.r...@rijksmuseum.nl: So I suggest that for some patches, the ones with a minor severity, small or template changes could, IMO, bypass the signoff step. This idea comes up every now and then (just as we see our queues growing and slinking again..). I would suggest to make the Complexity field mandatory. Some people do not fill it. And if the Complexity== Trivial or String, test it yourself and put your own signoff below. Everything above Trivial needs another signoff. Marcel ___ 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/ ___ 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/ ___ 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/
Re: [Koha-devel] Thoughts about timing and Koha schedules
Hie, Very clever analyze. Now that you say it, November and May are usually also full of projects for us at Biblibre. Le 21/08/2015 10:56, Brendan Gallagher a écrit : Hi All - ByWater is on its 7th year, so we have a solid set of data for analyzing, and recently I've noticed a few things. Let me try and paint the picture. Major Koha releases are every six months and usually the 22nd day of the month, with the target being November and May. (Please correct me if I am wrong) Library funding cycles in the US run either fiscal year (July to June), Calendar year (January to December), or some odd fiscal year close to the July~June year. Ok that being said from the time management situation with ByWater that introduces a few complexities. (Let me describe the workflow and maybe you'll see what I am talking about) Most of the time a library will sign a migration contract with us that dictates we must have them go-live before a certain fiscal date OR the library isn't really able to sign a contract for services until a certain fiscally motivated date (which places us into a similar roll-out). That being said we find that May and November (plus and minus a month) are our busiest times of the year. I've got 3 people on the road for education/training, 3 people heavily in the fields of migrations scripts, and 3 developers that are heavily in the field of meeting development expectations for lots and lots of go-lives (*note - plus additional staff to support an influx in tickets or other support needs during a go-live period). So if we slide the releases to say February and August - I would be able to dedicate more man power (9+ people from the above paragraph) around the heavy testing/ debugging / bug writing/squashing periods for a release. I know I know - there isn't really a time that Koha doesn't need more testing, but I've noticed that the volunteer effort is usually much greater/demanding the closer we are to major release date. I am wondering if others are finding the same with their work schedules (other support providers, academic institutions, public institutions, and my favorite volunteers). Are there certain times of the years where your day job is predictably busy that you aren't able to dedicate the resources that you want towards the greatest project in the world Koha. With the data set that we're sitting on here, we are constantly seeking ways that we can contribute more. Just a thought and was curious if others analyzed a similar aspect with their environment and perhaps maybe we should bring such a discussion into the open or a general IRC meeting. Especially any of us that are support providers we should be always be thinking about how we can do more for Koha. Thanks and Cheers (another sleepless night thinking about my favorite subject - Koha), Brendan ___ 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/ -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.som...@biblibre.com ___ 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/
Re: [Koha-devel] Refactoring of tools/export.pl
Nice work, this script was indeed crazy with so much if commandline ;) Le 25/08/2015 12:48, Jonathan Druart a écrit : Hi devs, I have just submitted a patch on bug 14722 to refactor the script tools/export.pl to make it more readable and robust. I have also created a new script misc/export.pl for the command line usage. If you are interested, just have a look and give me some feedbacks. Cheers, Jonathan http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14722 ___ 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/ -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.som...@biblibre.com ___ 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/
Re: [Koha-devel] Facilitate integration of some patches
+1 On those 200, how many have a severity of trivial or lower ? Le 20/08/2015 15:51, Jonathan Druart a écrit : Hello devs, I would like to suggest a simplification of the integration workflow for some patches. Indeed the signoff queue is back to a critical threshold (200) and the signoffer's activity is very low. Being part of the QA team, I try not to test patches in the Needs Signoff queue as I loose my QA token. The active members of the QA team are very limited and when we do SO, this increase the QA queue. As a result there is less chances my patches are QAed as there are more and more patches in the QA queue. It's a bit egoistic, but we all have the same problem. So I suggest that for some patches, the ones with a minor severity, small or template changes could, IMO, bypass the signoff step. I would like to discuss this during the next dev meetings, but I am keen to get some feedbacks on this idea. Cheers, Jonathan PS: If I am correct, we already have discussed about that previously. ___ 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/ -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.som...@biblibre.com ___ 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/
Re: [Koha-devel] Thoughts about timing and Koha schedules
On the other hand, Novembre and May fit quite well with the KohaCon and the hackfest in Marseille :) 2015-08-21 9:56 GMT+01:00 Brendan Gallagher i...@bywatersolutions.com: Hi All - ByWater is on its 7th year, so we have a solid set of data for analyzing, and recently I've noticed a few things. Let me try and paint the picture. Major Koha releases are every six months and usually the 22nd day of the month, with the target being November and May. (Please correct me if I am wrong) Library funding cycles in the US run either fiscal year (July to June), Calendar year (January to December), or some odd fiscal year close to the July~June year. Ok that being said from the time management situation with ByWater that introduces a few complexities. (Let me describe the workflow and maybe you'll see what I am talking about) Most of the time a library will sign a migration contract with us that dictates we must have them go-live before a certain fiscal date OR the library isn't really able to sign a contract for services until a certain fiscally motivated date (which places us into a similar roll-out). That being said we find that May and November (plus and minus a month) are our busiest times of the year. I've got 3 people on the road for education/training, 3 people heavily in the fields of migrations scripts, and 3 developers that are heavily in the field of meeting development expectations for lots and lots of go-lives (*note - plus additional staff to support an influx in tickets or other support needs during a go-live period). So if we slide the releases to say February and August - I would be able to dedicate more man power (9+ people from the above paragraph) around the heavy testing/ debugging / bug writing/squashing periods for a release. I know I know - there isn't really a time that Koha doesn't need more testing, but I've noticed that the volunteer effort is usually much greater/demanding the closer we are to major release date. I am wondering if others are finding the same with their work schedules (other support providers, academic institutions, public institutions, and my favorite volunteers). Are there certain times of the years where your day job is predictably busy that you aren't able to dedicate the resources that you want towards the greatest project in the world Koha. With the data set that we're sitting on here, we are constantly seeking ways that we can contribute more. Just a thought and was curious if others analyzed a similar aspect with their environment and perhaps maybe we should bring such a discussion into the open or a general IRC meeting. Especially any of us that are support providers we should be always be thinking about how we can do more for Koha. Thanks and Cheers (another sleepless night thinking about my favorite subject - Koha), Brendan -- --- Brendan A. Gallagher ByWater Solutions CEO Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting and Complete Support Packages Headquarters: Portland, OR - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com i...@bywatersolutions.com ___ 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/ ___ 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/
Re: [Koha-devel] schema.k-c.org
* Barton Chittenden (bar...@bywatersolutions.com) wrote: Could this be made part of the build process? Not easily no. Chris On Tue, Aug 25, 2015 at 9:59 AM, Tomas Cohen Arazi tomasco...@gmail.com wrote: Could we please update the schemaspy files on the site? They have lagged a lot. I'm not sure who runs it, just wanted to make him/her notice it needs updating. ___ 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/ ___ 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/ -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand signature.asc Description: Digital signature ___ 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/
Re: [Koha-devel] schema.k-c.org
Thanks Chris! I saw it is already updated! El 25/8/2015 10:06 p. m., Chris Cormack chr...@catalyst.net.nz escribió: * Barton Chittenden (bar...@bywatersolutions.com) wrote: Could this be made part of the build process? Not easily no. Chris On Tue, Aug 25, 2015 at 9:59 AM, Tomas Cohen Arazi tomasco...@gmail.com wrote: Could we please update the schemaspy files on the site? They have lagged a lot. I'm not sure who runs it, just wanted to make him/her notice it needs updating. ___ 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/ ___ 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/ -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand ___ 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/