From kohanews at gmail.com Mon May 1 05:17:26 2017 From: kohanews at gmail.com (kohanews) Date: Sun, 30 Apr 2017 20:17:26 -0700 Subject: [Koha-devel] Koha Community Newsletter: April 2017 Message-ID: Fellow Koha users: The Koha Community Newsletter for April 2017 is here: Koha Community Newsletter: April 2017 Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. Thanks! -- Chad Roseburg Editor, Koha Community Newsletter -------------- next part -------------- An HTML attachment was scrubbed... URL: From veron at veron.ch Mon May 1 18:33:42 2017 From: veron at veron.ch (=?UTF-8?Q?Marc_V=c3=a9ron?=) Date: Mon, 1 May 2017 18:33:42 +0200 Subject: [Koha-devel] The interface "winks" when I check out a book after upgrading firefox In-Reply-To: <1fd3e1eb-46df-f5ef-9cba-8ca7697f7828@inlibro.com> References: <19b5bdc1-9dd0-022f-6d72-6136f0e13d15@inlibro.com> <1fd3e1eb-46df-f5ef-9cba-8ca7697f7828@inlibro.com> Message-ID: <7361ca3d-3a5e-70dc-cc10-5cf2859e3a52@veron.ch> Thanks, Fran?ois, for filing Bug 18518 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18518 I could reproduce with Firefox ESR 45.3.0 (Debian) as well by slowing it down. See comment on Bug. Marc Am 30.04.2017 um 23:08 schrieb Francois Charbonnier: > > Thanks Marc! That's exactly what I mean. Do you think it's something > that can be fixed ? > > > Fran?ois Charbonnier, > Bibl. prof. / Chef de produits > > T?l. : (888) 604-2627 > francois.charbonnier at inLibro.com > > > inLibro | Sp?cialistes en technologies documentaires | www.inLibro.com > > Le 2017-04-28 ? 15:35, Marc V?ron a ?crit : >> >> Hi Fran?ois >> >> I have a strange 'blinking' or 'winking' on current master as well - >> not sure if we speak about the same thing: >> >> - On the staff client main page, click on 'Patrons' >> - While loading the page, I see very shortly a yellow message "Add >> patrons to" (I took a video and stepped through it to be able to read >> the text). >> - Then the page refreshes and displays as expected. >> - I get the same when I am on the page Home > Patrons and click 'Search'. >> >> I get it with Firefox 53.0 (Windows) >> I do not get it with Firefox ESR 45.3.0 (Debian) >> >> Is it that what you mean? >> >> Marc >> >> Am 27.04.2017 um 20:58 schrieb Francois Charbonnier: >>> >>> Hi, >>> >>> I use Koha 16.05 and firefox 53. When I check out an item, the >>> interface "winks". >>> >>> I tried this with firefox 52, the interface stays still. >>> >>> Have you noticed it as well ? Any advice to fix it ? >>> >>> Thanks! >>> >>> -- >>> Fran?ois Charbonnier, >>> Bibl. prof. / Chef de produits >>> >>> T?l. : (888) 604-2627 >>> francois.charbonnier at inLibro.com >>> >>> >>> inLibro | Sp?cialistes en technologies documentaires | >>> www.inLibro.com >>> >>> >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at 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 at 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 at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick at bywatersolutions.com Tue May 2 22:26:18 2017 From: nick at bywatersolutions.com (Nick Clemens) Date: Tue, 02 May 2017 20:26:18 +0000 Subject: [Koha-devel] Koha General IRC Meeting Reminder - May 3, 2017 - 20 UTC Message-ID: Hi All, Just a reminder that our next general meeting is tomorrow May 3rd in IRC at 20 UTC Link to local date and time conversion: http://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+IRC+General+Meeting&iso=20170503T20 The agenda is here: https://wiki.koha-community.org/wiki/General_IRC_meeting_03_May_2017 This meeting will be elections for 17.11 - you can see candidates for roles here: https://wiki.koha-community.org/wiki/Roles_for_17.11 Feature slush is on Friday, so make some noise tomorrow for anything you want to see moving along. Don't forget, next Wednesday will be a special Bugs Only! Global Bug Squashing Day to get things moving for outstanding bugs before the next release. If you want to get involved meetings and GBSD are good points of entry so hope to see you all there! -Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From mtj at kohaaloha.com Wed May 3 09:13:06 2017 From: mtj at kohaaloha.com (Mason James) Date: Wed, 3 May 2017 19:13:06 +1200 Subject: [Koha-devel] Jenkins is down Message-ID: hi Folks would someone please fix jenkins specifically the debian_8 node https://jenkins.koha-community.org/computer/Debian_8/ thanks, Mason From dcook at prosentient.com.au Thu May 4 01:42:16 2017 From: dcook at prosentient.com.au (David Cook) Date: Thu, 4 May 2017 09:42:16 +1000 Subject: [Koha-devel] Task schedulers and message queues for Koha In-Reply-To: References: <0ad301d28b14$e55deb30$b019c190$@prosentient.com.au> <42a983a1-d2c7-b857-384d-a0fcf630ef6d@cineca.it> <0c2d01d28c91$f4b9f5a0$de2de0e0$@prosentient.com.au> <0e689b11-ebe7-107e-151e-0f7edfbeb981@cineca.it> <0cd801d28d6f$abc22780$03467680$@prosentient.com.au> <0ce901d28d88$2470b300$6d521900$@prosentient.com.au> Message-ID: <076101d2c466$e5d81e60$b1885b20$@prosentient.com.au> Hi Jonathan, I have scrapped the work that I was doing on a generic task scheduler. Instead, I?ve developed a daemon which just works for OAI-PMH harvesting. Feel free to go ahead with whatever you?re planning, and I?m happy to contribute ideas. I was concerned that I was being overly ambitious, and that the project would never be accepted into Koha. A third-party message queue like RabbitMQ would add another dependency to Koha, which would further complicate installations and maintainance, although I think it might still be the best way forward. Or using something like ZeroMQ to set up our own using some established work. I had written my own message queue in Perl, which was fairly easy to do, so that?s always an alternative. For the task scheduler, I used POE for the event framework and used timers to schedule tasks. Initially I didn?t use a message queue, but I think using one would be more optimal. You fire up some workers, register them with the message queue, and then they consume messages as the message queue assigns them. The task scheduler would then just be used for initially queuing the messages into the queue for the workers to consume. With the OAI-PMH daemon, which I?d like to post ASAP to 10662, I?m still using POE for the event framework, but I?m using POE::Component::JobQueue to handle the queue. I have a queue for downloading and a queue for importing. Each queue has X workers which run in parallel. At the moment, I?m forking the workers, since it was the easiest thing to do, but it is a little bit heavy. Not in terms of the overhead of forking, which is fairly non-existent really, but since you?re getting a copy of the harvester for each forked worker, the resources seem to add up a bit. At the moment, my design is for a single Koha system, or one with a lot of resources. Anyway, so the Koha web interface connects to the OAI-PMH harvester daemon using a UNIX socket. In koha-conf.xml, I have a line pointing to a configuration file, and in there is a socket address. It uses a super simple protocol serialised in JSON with null terminated lines to submit/list/start/stop/delete jobs in the harvester. The harvester downloads records to the file system and adds a pointer to the database, and then the importer job queue assigns a database entry to each of its workers and imports the records into Koha. I was thinking that even with a task scheduler and message queue, I?d probably still implement the OAI-PMH harvester as I have. Maybe I could replace the UNIX socket connection with the message queue, so the harvester consumes messages from the queue rather than the client, but it?s a bit academic. The harvester needs to have direct control over its workers rather than the queue sending messages to the workers, so that it can control the jobs directly. I?m not a huge fan of how the Python-based Celery scheduler manages cancelled jobs, although I found Celery to be a neat piece of work. Anyway, long story short, no real news. I?ve abandoned making a generic task scheduler and message queue, and just made my to-purpose daemon which implements its own internal queue management for the sake of simplicity and efficacy. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Jonathan Druart Sent: Wednesday, 26 April 2017 2:21 AM To: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] Task schedulers and message queues for Koha On Thu, 23 Feb 2017 at 00:51 David Cook > wrote: I?m planning to post the code for what I have already in early March. Any news here? We really need to remove the way our background jobs are implemented to make them work under Plack. I'd like to avoid duplication of work... David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Tomas Cohen Arazi [mailto:tomascohen at gmail.com ] Sent: Thursday, 23 February 2017 2:16 PM To: David Cook >; Tajoli Zeno >; koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] Task schedulers and message queues for Koha Share it :-) El mi?., 22 de feb. de 2017 9:57 PM, David Cook > escribi?: Hi Zeno, I have a number of concerns about Celery. One of those is that it would add numerous external dependencies and complexity to Koha implementations. Your suggestion of Celery + RabbitMQ + AnyEvent::RabbitMQ sounds ok, although it would involve work too. While Celery clients exist for PHP and Node.js, we'd need to create a Perl implementation of the Celery protocol using AnyEvent::RabbitMQ (or Net::RabbitFoot). Not that I'm necessarily opposed to that. We'd also still need to write the tasks in Python (or use web hooks which would have the overhead of HTTP plus you'd have to worry about your web server being up). I'm not sure how keen the community at large is to support more server-side languages. I like writing Python, so I don't mind porting over my OAI-PMH code from Perl to Python. I've abandoned the HTTP::OAI module anyway for a few reasons. RabbitMQ is a pretty heavy duty product as well which comes with its own requirements: https://www.rabbitmq.com/production-checklist.html. While we currently help people with Apache, MySQL, Zebra, and ElasticSearch, we'd also all need to become experts with RabbitMQ. I've already put together a Perl-based scheduler using POE which forks its own workers. And I've already put together a basic Perl-based message queue which sends events to pre-existing workers (like Celery). Celery with RabbitMQ is more mature and complex, but my Perl programs do the trick. Looking at DSpace's OAI-PMH harvester, it works very much like my first design. It's a Java scheduler which uses threads rather than child processes to do its work. Due to the lack of engagement overall, I think I'll probably just keep my existing design, since it works and works quite well. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 > -----Original Message----- > From: Tajoli Zeno [mailto:z.tajoli at cineca.it ] > Sent: Wednesday, 22 February 2017 7:49 PM > To: David Cook >; koha-devel at lists.koha- > community.org > Subject: Re: [Koha-devel] Task schedulers and message queues for Koha > > Hi David and all, > > Il 21/02/2017 23:29, David Cook ha scritto: > >. Two, they wanted to > > execute OAI-PMH requests every 2-3 seconds and cron has 1 minute as > >its finest granularity. Three, even if you setup a cronjob to run > >every minute, long running tasks could get duplicated (although you > >could mitigate that with locks which would be a pain). Plus, you want > >to run tasks in parallel, so you're going to want to use multiple > >processes, which cron isn't really set up to achieve. > > Ok, if you need those features cron isn't enough. > But why do you drop the option Celery + RabbitMQ + AnyEvent::RabbitMQ > > They have official debiano packages: > https://packages.debian.org/jessie/python-celery > https://packages.debian.org/jessie/rabbitmq-server > https://packages.debian.org/jessie/libanyevent-rabbitmq-perl > > We still use one of their dpendencies for similar tasks (libanyevent-perl "event > loop framework with multiple implementations"). > > Python is already present in our Debian/Ubuntu system, it is a prereq of the > distributions. > > Redone a so complex stack in perl i think is very complex. > > Bye > Zeno Tajoli > > > > -- > Zeno Tajoli > /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche > Email: z.tajoli at cineca.it Fax: 051/6132198 > *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) _______________________________________________ Koha-devel mailing list Koha-devel at 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/ -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F _______________________________________________ Koha-devel mailing list Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Thu May 4 12:24:16 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Thu, 04 May 2017 10:24:16 +0000 Subject: [Koha-devel] Jenkins is down In-Reply-To: References: Message-ID: I'll take care as soon as I get to the office. Thanks for reporting! El mi?., 3 de may. de 2017 4:13 AM, Mason James escribi?: > hi Folks > would someone please fix jenkins > > specifically the debian_8 node > https://jenkins.koha-community.org/computer/Debian_8/ > > thanks, Mason > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick at bywatersolutions.com Thu May 4 15:15:37 2017 From: nick at bywatersolutions.com (Nick Clemens) Date: Thu, 04 May 2017 13:15:37 +0000 Subject: [Koha-devel] Global Bug Squashing Day - Bugs Only Edition! Wednesday, May 10th, 2017 Message-ID: Hi All, A reminder / update - next week will be a GBSD dedicated to squashing bugs for the upcoming 17.05 release. I added a wiki page here: https://wiki.koha-community.org/wiki/2017-05-10_Global_bug_squashing_day_-_Bugs_only_edition ! I will be adding some bugs there and trying to keep status up to date as I can but please help out, list bugs you want to work on/are working on, add comments/sections or make the page more attractive :-) We want community involvement so if you have been thinking of getting involved this is a great time. I will be available in IRC as long as I can that day, feel free to ping me. If you are a seasoned community member and can help please add your name to the 'hand holders' list on the wiki I hope to see you all around, hear lots of questions, and see lots of squashing :-) -Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From barton at bywatersolutions.com Fri May 5 01:05:30 2017 From: barton at bywatersolutions.com (Barton Chittenden) Date: Thu, 4 May 2017 19:05:30 -0400 Subject: [Koha-devel] [ByWater Partners] Global Bug Squashing Day - Bugs Only Edition! Wednesday, May 10th, 2017 In-Reply-To: References: Message-ID: I'd like to add that if anybody would like help in the next few days with a testing environment, whether it's a guided tour of the koha-sandboxes, or help setting up kohadevbox (see https://github.com/digibib/kohadevbox ), feel free to ask me (barton) in IRC. Just mention my name in #koha, and I'll come-a-running. Feeling comfortable in the testing environment, and with the testing process itself is the name of the game. That's why we do the GBSD -- so that testers know that there will be people around to answer questions. One of the ways go get comfortable is to take a nice easy walk through the process a couple of times before doing it in earnest... and I'll be happy to do that with you. :-) --Barton On Thu, May 4, 2017 at 9:15 AM, Nick Clemens wrote: > Hi All, > > A reminder / update - next week will be a GBSD dedicated to squashing bugs > for the upcoming 17.05 release. > > I added a wiki page here: > https://wiki.koha-community.org/wiki/2017-05-10_Global_ > bug_squashing_day_-_Bugs_only_edition! > > I will be adding some bugs there and trying to keep status up to date as I > can but please help out, list bugs you want to work on/are working on, add > comments/sections or make the page more attractive :-) > > We want community involvement so if you have been thinking of getting > involved this is a great time. > > I will be available in IRC as long as I can that day, feel free to ping > me. If you are a seasoned community member and can help please add your > name to the 'hand holders' list on the wiki > > I hope to see you all around, hear lots of questions, and see lots of > squashing :-) > > -Nick > > > _______________________________________________ > Partners mailing list > Partners at lists.bywatersolutions.com > http://lists.bywatersolutions.com/mailman/listinfo/partners > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From oleonard at myacpl.org Fri May 5 15:46:03 2017 From: oleonard at myacpl.org (Owen Leonard) Date: Fri, 5 May 2017 09:46:03 -0400 Subject: [Koha-devel] [ByWater Partners] Global Bug Squashing Day - Bugs Only Edition! Wednesday, May 10th, 2017 In-Reply-To: References: Message-ID: > I'd like to add that if anybody would like help in the next few days with a > testing environment, whether it's a guided tour of the koha-sandboxes, or > help setting up kohadevbox (see https://github.com/digibib/kohadevbox ), > feel free to ask me (barton) in IRC. Just mention my name in #koha, and I'll > come-a-running. Same here, between 8AM and 1PM EDT. Feel free to '/msg oleonard' if you'd feel more comfortable asking in private. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org From nick at bywatersolutions.com Fri May 5 15:58:39 2017 From: nick at bywatersolutions.com (Nick Clemens) Date: Fri, 05 May 2017 13:58:39 +0000 Subject: [Koha-devel] [ByWater Partners] Global Bug Squashing Day - Bugs Only Edition! Wednesday, May 10th, 2017 In-Reply-To: References: Message-ID: Note the link may not work as expected: Bug list for GBSD GBSD Main page My enthusiasm for exclamation point was not aprreciated by google On Thu, May 4, 2017 at 7:05 PM Barton Chittenden < barton at bywatersolutions.com> wrote: > I'd like to add that if anybody would like help in the next few days with > a testing environment, whether it's a guided tour of the koha-sandboxes, or > help setting up kohadevbox (see https://github.com/digibib/kohadevbox ), > feel free to ask me (barton) in IRC. Just mention my name in #koha, and > I'll come-a-running. > > Feeling comfortable in the testing environment, and with the testing > process itself is the name of the game. That's why we do the GBSD -- so > that testers know that there will be people around to answer questions. One > of the ways go get comfortable is to take a nice easy walk through the > process a couple of times before doing it in earnest... and I'll be happy > to do that with you. :-) > > --Barton > > On Thu, May 4, 2017 at 9:15 AM, Nick Clemens > wrote: > >> Hi All, >> >> A reminder / update - next week will be a GBSD dedicated to squashing >> bugs for the upcoming 17.05 release. >> >> I added a wiki page here: >> >> https://wiki.koha-community.org/wiki/2017-05-10_Global_bug_squashing_day_-_Bugs_only_edition >> ! >> >> I will be adding some bugs there and trying to keep status up to date as >> I can but please help out, list bugs you want to work on/are working on, >> add comments/sections or make the page more attractive :-) >> >> We want community involvement so if you have been thinking of getting >> involved this is a great time. >> >> I will be available in IRC as long as I can that day, feel free to ping >> me. If you are a seasoned community member and can help please add your >> name to the 'hand holders' list on the wiki >> >> I hope to see you all around, hear lots of questions, and see lots of >> squashing :-) >> >> -Nick >> >> >> _______________________________________________ >> Partners mailing list >> Partners at lists.bywatersolutions.com >> http://lists.bywatersolutions.com/mailman/listinfo/partners >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolin.somers at biblibre.com Fri May 5 17:53:49 2017 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Fri, 5 May 2017 17:53:49 +0200 Subject: [Koha-devel] Koha and xhtml2pdf In-Reply-To: <03b301d2bcd1$f8231080$e8693180$@prosentient.com.au> References: <87ad6dc9-9c1e-2e9c-aed6-302eb54596e3@biblibre.com> <1492728474-sup-6582@t60p> <03b301d2bcd1$f8231080$e8693180$@prosentient.com.au> Message-ID: Hie devels, Finally we solved by downgrading the lib Pillow to 2.7 using Python PIP. Note that is this in Ubuntu Xenial. Le 24/04/2017 ? 10:08, David Cook a ?crit : > Yeah, no one uses easy_install anymore. It's all about pip. > > However, the community likes to have everything packaged, and using pip is > like using cpan... so this seems like an issue to me. Does Koha have anyone > of notifying that there's a dependency missing if it's not installed in this > case? > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St > Ultimo, NSW 2007 > Australia > > Office: 02 9212 0899 > Direct: 02 8005 0595 > > >> -----Original Message----- >> From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel- >> bounces at lists.koha-community.org] On Behalf Of Mark Alexander >> Sent: Friday, 21 April 2017 8:57 AM >> To: Fridolin SOMERS >> Cc: koha-devel >> Subject: Re: [Koha-devel] Koha and xhtml2pdf >> >> This may not be relevant to Ubuntu, but I was able to get a working > xhtml2pdf >> on Debian Jessie using this: >> >> apt-get install python-pip python-dev >> pip install xhtml2pdf >> >> Before figuring this out, I tried using 'easy_install pisa', but xhtml2pdf >> complained about missing dependencies and I was too lazy to figure out how > to >> install them. One thing I discovered during this head-scratching phase > was that >> easy_install has been deprecated, and pip is used nowadays, which led me > to >> the above solution. >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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.somers at biblibre.com From fridolin.somers at biblibre.com Fri May 5 18:01:06 2017 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Fri, 5 May 2017 18:01:06 +0200 Subject: [Koha-devel] The interface "winks" when I check out a book after upgrading firefox In-Reply-To: <7361ca3d-3a5e-70dc-cc10-5cf2859e3a52@veron.ch> References: <19b5bdc1-9dd0-022f-6d72-6136f0e13d15@inlibro.com> <1fd3e1eb-46df-f5ef-9cba-8ca7697f7828@inlibro.com> <7361ca3d-3a5e-70dc-cc10-5cf2859e3a52@veron.ch> Message-ID: Oh I've proposed also a patch on Bug 18551. I've looked in http://splitter.koha-community.org before but I dont see bug 18518. Should I rebase my bug on this one or provide a followup in this one ? Regards, Le 01/05/2017 ? 18:33, Marc V?ron a ?crit : > Thanks, Fran?ois, for filing Bug 18518 > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18518 > > I could reproduce with Firefox ESR 45.3.0 (Debian) as well by slowing it > down. See comment on Bug. > > Marc > > > Am 30.04.2017 um 23:08 schrieb Francois Charbonnier: >> >> Thanks Marc! That's exactly what I mean. Do you think it's something >> that can be fixed ? >> >> >> Fran?ois Charbonnier, >> Bibl. prof. / Chef de produits >> >> T?l. : (888) 604-2627 >> francois.charbonnier at inLibro.com >> >> >> inLibro | Sp?cialistes en technologies documentaires | www.inLibro.com >> >> Le 2017-04-28 ? 15:35, Marc V?ron a ?crit : >>> >>> Hi Fran?ois >>> >>> I have a strange 'blinking' or 'winking' on current master as well - >>> not sure if we speak about the same thing: >>> >>> - On the staff client main page, click on 'Patrons' >>> - While loading the page, I see very shortly a yellow message "Add >>> patrons to" (I took a video and stepped through it to be able to read >>> the text). >>> - Then the page refreshes and displays as expected. >>> - I get the same when I am on the page Home > Patrons and click >>> 'Search'. >>> >>> I get it with Firefox 53.0 (Windows) >>> I do not get it with Firefox ESR 45.3.0 (Debian) >>> >>> Is it that what you mean? >>> >>> Marc >>> >>> Am 27.04.2017 um 20:58 schrieb Francois Charbonnier: >>>> >>>> Hi, >>>> >>>> I use Koha 16.05 and firefox 53. When I check out an item, the >>>> interface "winks". >>>> >>>> I tried this with firefox 52, the interface stays still. >>>> >>>> Have you noticed it as well ? Any advice to fix it ? >>>> >>>> Thanks! >>>> >>>> -- >>>> Fran?ois Charbonnier, >>>> Bibl. prof. / Chef de produits >>>> >>>> T?l. : (888) 604-2627 >>>> francois.charbonnier at inLibro.com >>>> >>>> >>>> inLibro | Sp?cialistes en technologies documentaires | >>>> www.inLibro.com >>>> >>>> >>>> _______________________________________________ >>>> Koha-devel mailing list >>>> Koha-devel at 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 at 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 at 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 at 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.somers at biblibre.com From mtj at kohaaloha.com Mon May 8 07:16:28 2017 From: mtj at kohaaloha.com (Mason James) Date: Mon, 8 May 2017 17:16:28 +1200 Subject: [Koha-devel] Koha 16.05.12 released Message-ID: The Koha community is proud to announce the release of Koha 16.05.12. This is a maintenance release of 16.05 and includes 49 bugfixes. The full release notes are available at https://koha-community.org/koha-16-05-12-release/ Packages will be available soon. From fridolin.somers at biblibre.com Tue May 9 11:49:04 2017 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Tue, 9 May 2017 11:49:04 +0200 Subject: [Koha-devel] Single character searches are slow when queryfuzzy and/or querystemming are enabled. In-Reply-To: References: Message-ID: <0b885712-62c8-cd18-6f4c-ba0c20c3743d@biblibre.com> Yep, We had this issue with QueryStemming. We solved it by setting in zebra-biblios-dom.cfg a lower value 10000 for truncmax, 1000000000 by default. Of course results are not very good when there is more than 10k results but it works realy faster. Regards, Le 06/03/2017 ? 20:43, Barton Chittenden a ?crit : > I've got an issue that we've seen periodically at ByWater; I want to file a > bug, but I don't have a clear idea of how to replicate the issue, so I'm > trying to solicit information from the community on how to narrow the scope > of the problem and/or measure the performance problems that I'm seeing. > > The problem is that keyword searches (as you'd see from an un-modified > masthead search on the opac, or the "search the catalog" search on the > staff client) are markedly slow on some sites when > > a) The search term contains single letter words like "a" in "Once Upon A > Time" and > b) One or both of the QueryFuzzy or QueryStemming system preferences is > enabled. > > We first ran across this issue when we moved a number our Koha instances to > slower drives, and found that some (but not all) would time out when > searching for "Once upon a time", "A swiftly tilting planet", "Hitchiker's > Guide to the Galaxy" (where the 's' after the apostrophe is counted as a > single word). > > I turned on 'request' logging in zebra, here's the query that timed out: > > find @attrset Bib-1 @or @or @or @or @or @or @attr 1=36 @attr 4=1 @attr 6=3 > @attr 9=32 @attr 2=102 "once upon a time" @attr 1=4 @attr 4=1 @attr 6=3 > @attr 9=28 @attr 2=102 "once upon a time" @attr 1=36 @attr 4=1 @attr 9=26 > @attr 2=102 "once upon a time" @attr 1=4 @attr 4=6 @attr 9=24 @attr 2=102 > "once upon a time" @attr 4=6 @attr 5=103 @attr 9=16 @attr 2=102 "once upon > a time" @attr 4=6 @attr 5=1 @attr 9=14 @attr 2=102 "onc? upon? a time? " > @attr 4=6 @attr 9=14 @attr 2=102 "once upon a time" > Sent searchRequest. > > > I ran the PQF in zebra: > > Z> base biblios > Z> find @attrset Bib-1 @or @or @or @or @or @or @attr 1=36 @attr 4=1 @attr > 6=3 @attr 9=32 @attr 2=102 "once upon a time" @attr 1=4 @attr 4=1 @attr 6=3 > @attr 9=28 @attr 2=102 "once upon a time" @attr 1=36 @attr 4=1 @attr 9=26 > @attr 2=102 "once upon a time" @attr 1=4 @attr 4=6 @attr 9=24 @attr 2=102 > "once upon a time" @attr 4=6 @attr 5=103 @attr 9=16 @attr 2=102 "once upon > a time" @attr 4=6 @attr 5=1 @attr 9=14 @attr 2=102 "onc? upon? a time? " > @attr 4=6 @attr 9=14 @attr 2=102 "once upon a time" > Sent searchRequest. > Received SearchResponse. > Search was a success. > Number of hits: 119, setno 1 > SearchResult-1: term=once upon a time cnt=3, term=once upon a time cnt=5, > term=once cnt=94, term=upon cnt=63, term=a cnt=4876, term=time cnt=515, > term=once cnt=168, term=upon cnt=125, term=a cnt=19801, term=time cnt=1507, > term=once cnt=9830, term=upon cnt=960, term=a cnt=82237, term=time > cnt=8524, term=onc cnt=1915, term=upon cnt=914, term=a cnt=82237, term=time > cnt=7709, term=once cnt=1302, term=upon cnt=914, term=a cnt=68283, > term=time cnt=5442 > records returned: 0 > Elapsed: 98.163583 > > > The elapsed time is just under 100 seconds; I think Koha times out after 60. > > We looked at the disk I/O and found that the disk where the searches were > occurring was getting hammered, so we migrated the sites that were having > issues onto a server that had a much faster drive, and this did, at least > solve the time-out issue. > > The issue keeps on popping up, however -- if not in actual timeouts, then > at least in complaints of slowness in search. > > My hypothesis is that either QueryFuzzy or QueryStemming is expanding the > one letter words, i.e. a search for "a" is returning results for either all > words that start with "a" or all words contaning "a", and that all of these > results are written to disk before any further filtering is done. > > When we were seeing timeout issues, I'm not clear on which sites were > likely to have issues -- sites with a very small number of bibs didn't have > issues, but the problem wasn't solely by collection size. So here's what > I'd like to know, for the purposes of further testing, and/or to be able to > replicate the issue: > > 1) Is there anyone who knows all about PQF who can tell me why the query > above would run so slowly? > 2) Is there part of the PQF that seems to be behaving particularly badly? > Which parts of the query are returning "term=a cnt=82237", and can we avoid > having that called twice? > 3) How do I go about constructing a data set that illustrates this problem? > 4) What's the best way to measure the performance problems and/or define > what the problem is when I file a bug? > 5) Are there any work-arounds, given that certain sites really want query > stemming and queryfuzzy enabled? > > Thanks, > > --Barton > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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.somers at biblibre.com From mirko at abunchofthings.net Tue May 9 13:07:02 2017 From: mirko at abunchofthings.net (Mirko Tietgen) Date: Tue, 9 May 2017 13:07:02 +0200 Subject: [Koha-devel] [Koha] Koha 16.05.12 released In-Reply-To: References: Message-ID: <906cfc83-371b-9270-2a4b-18e1a5d33dda@abunchofthings.net> The Debian package for Koha 16.05.12 is now available from the Koha community repository. -- Mirko -- Mirko Tietgen mirko at abunchofthings.net http://koha.abunchofthings.net http://meinkoha.de Mason James schrieb am 08.05.2017 > The Koha community is proud to announce the release of Koha 16.05.12. > > This is a maintenance release of 16.05 and includes 49 bugfixes. > > The full release notes are available at > https://koha-community.org/koha-16-05-12-release/ > > Packages will be available soon. > _______________________________________________ > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > From jonathan.druart at bugs.koha-community.org Tue May 9 18:37:01 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Tue, 09 May 2017 16:37:01 +0000 Subject: [Koha-devel] Communication - Extra meeting on May 10th, 13UTC Message-ID: Hello, I'd like you to take a look at the following pad: https://mensuel.framapad.org/p/build_task_force_Koha_1711 Following what I announced in the RM proposal I will send an email to the different actors of the community. I'd like to get your opinion on the content. I propose to discuss it (quickly because we have patches to test!) for agreement tomorrow May 10th 13UTC https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+IRC+Meeting&iso=20170510T13 If we need more time to reach a consensus or if there are strong objections we could rethink the whole thing and vote later. Cheers, Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick at bywatersolutions.com Tue May 9 22:44:02 2017 From: nick at bywatersolutions.com (Nick Clemens) Date: Tue, 09 May 2017 20:44:02 +0000 Subject: [Koha-devel] Acquisitions change in Koha 16.11 and forward Message-ID: Hello All, With the current versions of Koha there have been some changes in acquisitions and how prices are calculated and there seems to be some confusion in terms and how things are currently being used. We wanted to clarify what is happening, propose a change and get feedback on what needs to happen. When placing an order there are several price fields: Vendor price (listprice in db) -This is used to populate the Replacement cost and budgeted cost on the order page. It is not used against the budget Replacement cost (rrp in db) -This is used to calculate the 'budgeted cost/ecost' in the budget - it also populates the replacement price in the item created by the aqc process once received Budgeted cost (ecost in db) -This is the replacement/rpp minus any discount on the order - this is the value that will be encumbered when the order is placed Actual cost (unitprice) -This is the eventual 'price' of the item and is the encumbered amount once the item has been received. With the changes that were made one can no longer adjust the 'Replacement/RRP' once an order is placed - this is because this value is adjusted for tax in the db (rrp_tax_excluded, rrp_tax_included) and used for calculating the ecost tax adjusted (ecost_tax_excluded, ecost_tax_included) Some libraries have been having issues as they use 'Replacement' cost mostly for populating items and are not used to it being unable to be edited and/or affecting budgets. We are proposing to rename the current 'Replacement cost' field to match the db value - 'Recommended retail price' (RRP) and add a new 'Replacement cost' field, editable at any point, that is only used for populating the item field. We think this will clear up how the other values are being used and restore functionality that changed. Please let us know if this works or what other suggestions you have here. Thank you, Nick, Kyle, Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL: From veron at veron.ch Wed May 10 05:16:05 2017 From: veron at veron.ch (=?UTF-8?Q?Marc_V=c3=a9ron?=) Date: Wed, 10 May 2017 05:16:05 +0200 Subject: [Koha-devel] Acquisitions change in Koha 16.11 and forward In-Reply-To: References: Message-ID: +1 Marc Am 09.05.2017 um 22:44 schrieb Nick Clemens: > Hello All, > > With the current versions of Koha there have been some changes in > acquisitions and how prices are calculated and there seems to be some > confusion in terms and how things are currently being used. > > We wanted to clarify what is happening, propose a change and get > feedback on what needs to happen. > > When placing an order there are several price fields: > Vendor price (listprice in db) > -This is used to populate the Replacement cost and budgeted cost on > the order page. It is not used against the budget > > Replacement cost (rrp in db) > -This is used to calculate the 'budgeted cost/ecost' in the budget - > it also populates the replacement price in the item created by the aqc > process once received > > Budgeted cost (ecost in db) > -This is the replacement/rpp minus any discount on the order - this is > the value that will be encumbered when the order is placed > > Actual cost (unitprice) > -This is the eventual 'price' of the item and is the encumbered amount > once the item has been received. > > With the changes that were made one can no longer adjust the > 'Replacement/RRP' once an order is placed - this is because this value > is adjusted for tax in the db (rrp_tax_excluded, rrp_tax_included) and > used for calculating the ecost tax adjusted (ecost_tax_excluded, > ecost_tax_included) > > Some libraries have been having issues as they use 'Replacement' cost > mostly for populating items and are not used to it being unable to be > edited and/or affecting budgets. > > We are proposing to rename the current 'Replacement cost' field to > match the db value - 'Recommended retail price' (RRP) and add a new > 'Replacement cost' field, editable at any point, that is only used for > populating the item field. > > We think this will clear up how the other values are being used and > restore functionality that changed. > > Please let us know if this works or what other suggestions you have here. > > Thank you, > Nick, Kyle, Jonathan > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From josef.moravec at gmail.com Wed May 10 07:45:50 2017 From: josef.moravec at gmail.com (Josef Moravec) Date: Wed, 10 May 2017 05:45:50 +0000 Subject: [Koha-devel] Acquisitions change in Koha 16.11 and forward In-Reply-To: References: Message-ID: Does make sense to me. Josef st 10. 5. 2017 v 5:16 odes?latel Marc V?ron napsal: > +1 > Marc > > Am 09.05.2017 um 22:44 schrieb Nick Clemens: > > Hello All, > > With the current versions of Koha there have been some changes in > acquisitions and how prices are calculated and there seems to be some > confusion in terms and how things are currently being used. > > We wanted to clarify what is happening, propose a change and get feedback > on what needs to happen. > > When placing an order there are several price fields: > Vendor price (listprice in db) > -This is used to populate the Replacement cost and budgeted cost on the > order page. It is not used against the budget > > Replacement cost (rrp in db) > -This is used to calculate the 'budgeted cost/ecost' in the budget - it > also populates the replacement price in the item created by the aqc process > once received > > Budgeted cost (ecost in db) > -This is the replacement/rpp minus any discount on the order - this is the > value that will be encumbered when the order is placed > > Actual cost (unitprice) > -This is the eventual 'price' of the item and is the encumbered amount > once the item has been received. > > With the changes that were made one can no longer adjust the > 'Replacement/RRP' once an order is placed - this is because this value is > adjusted for tax in the db (rrp_tax_excluded, rrp_tax_included) and used > for calculating the ecost tax adjusted (ecost_tax_excluded, > ecost_tax_included) > > Some libraries have been having issues as they use 'Replacement' cost > mostly for populating items and are not used to it being unable to be > edited and/or affecting budgets. > > We are proposing to rename the current 'Replacement cost' field to match > the db value - 'Recommended retail price' (RRP) and add a new 'Replacement > cost' field, editable at any point, that is only used for populating the > item field. > > We think this will clear up how the other values are being used and > restore functionality that changed. > > Please let us know if this works or what other suggestions you have here. > > Thank you, > Nick, Kyle, Jonathan > > > _______________________________________________ > Koha-devel mailing listKoha-devel at lists.koha-community.orghttp://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 at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From katrin.fischer.83 at web.de Wed May 10 22:14:09 2017 From: katrin.fischer.83 at web.de (Katrin) Date: Wed, 10 May 2017 22:14:09 +0200 Subject: [Koha-devel] Acquisitions change in Koha 16.11 and forward In-Reply-To: References: Message-ID: <4cb343d1-5b53-9e4d-5c34-999c72892c9b@web.de> +1 On 10.05.2017 07:45, Josef Moravec wrote: > Does make sense to me. > > Josef > > st 10. 5. 2017 v 5:16 odes?latel Marc V?ron > napsal: > > +1 > Marc > > > Am 09.05.2017 um 22:44 schrieb Nick Clemens: >> Hello All, >> >> With the current versions of Koha there have been some changes in >> acquisitions and how prices are calculated and there seems to be >> some confusion in terms and how things are currently being used. >> >> We wanted to clarify what is happening, propose a change and get >> feedback on what needs to happen. >> >> When placing an order there are several price fields: >> Vendor price (listprice in db) >> -This is used to populate the Replacement cost and budgeted cost >> on the order page. It is not used against the budget >> >> Replacement cost (rrp in db) >> -This is used to calculate the 'budgeted cost/ecost' in the >> budget - it also populates the replacement price in the item >> created by the aqc process once received >> >> Budgeted cost (ecost in db) >> -This is the replacement/rpp minus any discount on the order - >> this is the value that will be encumbered when the order is placed >> >> Actual cost (unitprice) >> -This is the eventual 'price' of the item and is the encumbered >> amount once the item has been received. >> >> With the changes that were made one can no longer adjust the >> 'Replacement/RRP' once an order is placed - this is because this >> value is adjusted for tax in the db (rrp_tax_excluded, >> rrp_tax_included) and used for calculating the ecost tax adjusted >> (ecost_tax_excluded, ecost_tax_included) >> >> Some libraries have been having issues as they use 'Replacement' >> cost mostly for populating items and are not used to it being >> unable to be edited and/or affecting budgets. >> >> We are proposing to rename the current 'Replacement cost' field >> to match the db value - 'Recommended retail price' (RRP) and add >> a new 'Replacement cost' field, editable at any point, that is >> only used for populating the item field. >> >> We think this will clear up how the other values are being used >> and restore functionality that changed. >> >> Please let us know if this works or what other suggestions you >> have here. >> >> Thank you, >> Nick, Kyle, Jonathan >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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 at 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 at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Thu May 11 08:08:06 2017 From: dcook at prosentient.com.au (David Cook) Date: Thu, 11 May 2017 16:08:06 +1000 Subject: [Koha-devel] Packaging RDF::Trine Message-ID: <025c01d2ca1c$f4da7be0$de8f73a0$@prosentient.com.au> Hi all, Magnus and I have been working on a RDF project for Stockholm University Library, and I've been using RDF::Trine for our prototype. It works great overall, although I found a bug with RDF::Trine::Store::SPARQL version 1.016 (most current version on CPAN*). I sent in a pull request yesterday (https://github.com/kasei/perlrdf/pull/147) and the author of the module said that he's hoping to review it and merge it into master in the next few days. But what this means is that we'll be wanting to use the latest version of RDF::Trine, and that's going to be much newer than what is in the Debian repositories for Jessie and Wheezy. I've taken a peek at the code in those repos, and it's buggy too. I seem to recall on https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13642 that there were some issues packaging RDF libraries, but I think it may have mostly related to RDF::Helper, of which we have no need. But Mirko if I could get your input, that would be great. *Actually it seems the latest version in CPAN is newer than master in Github. I'll have to talk to the maintainer about that too. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mirko at abunchofthings.net Thu May 11 15:05:16 2017 From: mirko at abunchofthings.net (Mirko Tietgen) Date: Thu, 11 May 2017 15:05:16 +0200 Subject: [Koha-devel] Packaging RDF::Trine In-Reply-To: <025c01d2ca1c$f4da7be0$de8f73a0$@prosentient.com.au> References: <025c01d2ca1c$f4da7be0$de8f73a0$@prosentient.com.au> Message-ID: <222bf064-0b86-8823-b5ce-46a7a9dad618@abunchofthings.net> Hi David, I tried a quick build of librdf-trine-perl 1.016 in Jessie and it works. It will require some backports/packaging of dependencies. libdbd-sqlite-perl (n/a) libcache-lru-perl (sid: 0.04-1) librdf-trine-perl (sid: 1.015-1) Cheers, Mirko David Cook schrieb am 11.05.2017 > Hi all, > > > > Magnus and I have been working on a RDF project for Stockholm University > Library, and I've been using RDF::Trine for our prototype. It works great > overall, although I found a bug with RDF::Trine::Store::SPARQL version 1.016 > (most current version on CPAN*). I sent in a pull request yesterday > (https://github.com/kasei/perlrdf/pull/147) and the author of the module > said that he's hoping to review it and merge it into master in the next few > days. But what this means is that we'll be wanting to use the latest version > of RDF::Trine, and that's going to be much newer than what is in the Debian > repositories for Jessie and Wheezy. I've taken a peek at the code in those > repos, and it's buggy too. > > > > I seem to recall on > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13642 that there > were some issues packaging RDF libraries, but I think it may have mostly > related to RDF::Helper, of which we have no need. But Mirko if I could get > your input, that would be great. > > > > *Actually it seems the latest version in CPAN is newer than master in > Github. I'll have to talk to the maintainer about that too. > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > From paul.poulain at biblibre.com Thu May 11 15:49:01 2017 From: paul.poulain at biblibre.com (Paul Poulain) Date: Thu, 11 May 2017 15:49:01 +0200 Subject: [Koha-devel] Authenticate to use Webservices/ Koha API Message-ID: <765d6ef9-65be-caa2-8bd5-cb4ecad5adba@biblibre.com> Hi all, Matthias is working on connecting Koha and Coral, and he's facing some problems with authentication. We need to authenticate and use a session cookie, that's not easy. Could we find another solution ? Should we revive bz 13920 ? (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13920) Suggestions/ideas welcomed ! -- Paul Poulain, Associ?-g?rant / co-owner BibLibre, Services en logiciels libres pour les biblioth?ques BibLibre, Open Source software and services for libraries From tomascohen at gmail.com Thu May 11 16:00:21 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Thu, 11 May 2017 14:00:21 +0000 Subject: [Koha-devel] Authenticate to use Webservices/ Koha API In-Reply-To: <765d6ef9-65be-caa2-8bd5-cb4ecad5adba@biblibre.com> References: <765d6ef9-65be-caa2-8bd5-cb4ecad5adba@biblibre.com> Message-ID: We need to resurrect it, yes. We need to keep the idea of allowing API/key management (add/delete/revoke) and provide basic authentication (though headers) using those. I mean the first patches from Julian, not the whole patchset that requires a full Auth.pm rewrite/refactoring. Martin was wroking on an Oauth2 implementation, but for trusted consumers, it would be ok to use basic authentication through an SSL connexion. Regards El jue., 11 may. 2017 a las 10:49, Paul Poulain () escribi?: > Hi all, > > Matthias is working on connecting Koha and Coral, and he's facing some > problems with authentication. We need to authenticate and use a session > cookie, that's not easy. Could we find another solution ? Should we > revive bz 13920 ? > (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13920) > > Suggestions/ideas welcomed ! > > > -- > Paul Poulain, Associ?-g?rant / co-owner > BibLibre, Services en logiciels libres pour les biblioth?ques > BibLibre, Open Source software and services for libraries > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 <+54%209%20351%20351-3384> GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From hector.hecaxmmx at gmail.com Thu May 11 16:39:03 2017 From: hector.hecaxmmx at gmail.com (Hector Castro) Date: Thu, 11 May 2017 08:39:03 -0600 Subject: [Koha-devel] Packaging RDF::Trine (Hector Castro) Message-ID: Hi David I remember that the issue found in RDF::Trine at that moment was the dependencies used by module especially because use Moose. The policy was not to use Moose about some problems with Koha. I don't know if this policy has been change since the introduction of Plack. Regards. > Message: 2 > Date: Thu, 11 May 2017 16:08:06 +1000 > From: "David Cook" > To: > Subject: [Koha-devel] Packaging RDF::Trine > Message-ID: <025c01d2ca1c$f4da7be0$de8f73a0$@prosentient.com.au> > Content-Type: text/plain; charset="us-ascii" > > Hi all, > > > > Magnus and I have been working on a RDF project for Stockholm University > Library, and I've been using RDF::Trine for our prototype. It works great > overall, although I found a bug with RDF::Trine::Store::SPARQL version > 1.016 > (most current version on CPAN*). I sent in a pull request yesterday > (https://github.com/kasei/perlrdf/pull/147) and the author of the module > said that he's hoping to review it and merge it into master in the next few > days. But what this means is that we'll be wanting to use the latest > version > of RDF::Trine, and that's going to be much newer than what is in the Debian > repositories for Jessie and Wheezy. I've taken a peek at the code in those > repos, and it's buggy too. > > > > I seem to recall on > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13642 that there > were some issues packaging RDF libraries, but I think it may have mostly > related to RDF::Helper, of which we have no need. But Mirko if I could get > your input, that would be great. > > > > *Actually it seems the latest version in CPAN is newer than master in > Github. I'll have to talk to the maintainer about that too. > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: attachments/20170511/90fe5c84/attachment-0001.html> > > ------------------------------ > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > > End of Koha-devel Digest, Vol 138, Issue 10 > ******************************************* > -- Atte, H?ctor Eduardo Castro Avalos -------------- next part -------------- An HTML attachment was scrubbed... URL: From mirko at abunchofthings.net Thu May 11 17:11:08 2017 From: mirko at abunchofthings.net (Mirko Tietgen) Date: Thu, 11 May 2017 17:11:08 +0200 Subject: [Koha-devel] Packaging RDF::Trine In-Reply-To: <222bf064-0b86-8823-b5ce-46a7a9dad618@abunchofthings.net> References: <025c01d2ca1c$f4da7be0$de8f73a0$@prosentient.com.au> <222bf064-0b86-8823-b5ce-46a7a9dad618@abunchofthings.net> Message-ID: <4c6a45c3-7624-5660-7b99-194631b05cfb@abunchofthings.net> Mirko Tietgen schrieb am 11.05.2017 > libdbd-sqlite-perl (n/a) That is actually libdbd-sqlite3-perl these days and available. -- Mirko From oha at oha.it Thu May 11 19:14:08 2017 From: oha at oha.it (Francesco Rivetti) Date: Thu, 11 May 2017 19:14:08 +0200 Subject: [Koha-devel] Authenticate to use Webservices/ Koha API In-Reply-To: <765d6ef9-65be-caa2-8bd5-cb4ecad5adba@biblibre.com> References: <765d6ef9-65be-caa2-8bd5-cb4ecad5adba@biblibre.com> Message-ID: Hi, maybe worth mentioning i've started working on this https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18315 Oha On 2017-05-11 3:49 PM, Paul Poulain wrote: > Hi all, > > Matthias is working on connecting Koha and Coral, and he's facing some > problems with authentication. We need to authenticate and use a session > cookie, that's not easy. Could we find another solution ? Should we > revive bz 13920 ? > (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13920) > > Suggestions/ideas welcomed ! > > From dcook at prosentient.com.au Fri May 12 03:51:41 2017 From: dcook at prosentient.com.au (David Cook) Date: Fri, 12 May 2017 11:51:41 +1000 Subject: [Koha-devel] Packaging RDF::Trine In-Reply-To: <222bf064-0b86-8823-b5ce-46a7a9dad618@abunchofthings.net> References: <025c01d2ca1c$f4da7be0$de8f73a0$@prosentient.com.au> <222bf064-0b86-8823-b5ce-46a7a9dad618@abunchofthings.net> Message-ID: <02ac01d2cac2$4d8abd90$e8a038b0$@prosentient.com.au> I'm not sure that I understand the details of your message, but hurray for getting a recent build working in Jessie! My pull request has about 2 lines of code changed, so it should build the same as 1.016. The author of RDF::Trine suggested I try out Attean as well, but the documentation isn't very good and it looks like it won't work with a SPARQL endpoint, so no good to us. Plus it has a ton of dependencies it seems. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 > -----Original Message----- > From: Mirko Tietgen [mailto:mirko at abunchofthings.net] > Sent: Thursday, 11 May 2017 11:05 PM > To: David Cook ; koha-devel at lists.koha- > community.org > Subject: Re: Packaging RDF::Trine > > Hi David, > > I tried a quick build of librdf-trine-perl 1.016 in Jessie and it works. It will > require some backports/packaging of dependencies. > > libdbd-sqlite-perl (n/a) > libcache-lru-perl (sid: 0.04-1) > > librdf-trine-perl (sid: 1.015-1) > > Cheers, > > Mirko > > > David Cook schrieb am 11.05.2017 > > Hi all, > > > > > > > > Magnus and I have been working on a RDF project for Stockholm > > University Library, and I've been using RDF::Trine for our prototype. > > It works great overall, although I found a bug with > > RDF::Trine::Store::SPARQL version 1.016 (most current version on > > CPAN*). I sent in a pull request yesterday > > (https://github.com/kasei/perlrdf/pull/147) and the author of the > > module said that he's hoping to review it and merge it into master in > > the next few days. But what this means is that we'll be wanting to use > > the latest version of RDF::Trine, and that's going to be much newer > > than what is in the Debian repositories for Jessie and Wheezy. I've > > taken a peek at the code in those repos, and it's buggy too. > > > > > > > > I seem to recall on > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13642 that > > there were some issues packaging RDF libraries, but I think it may > > have mostly related to RDF::Helper, of which we have no need. But > > Mirko if I could get your input, that would be great. > > > > > > > > *Actually it seems the latest version in CPAN is newer than master in > > Github. I'll have to talk to the maintainer about that too. > > > > > > > > David Cook > > > > Systems Librarian > > > > Prosentient Systems > > > > 72/330 Wattle St > > > > Ultimo, NSW 2007 > > > > Australia > > > > > > > > Office: 02 9212 0899 > > > > Direct: 02 8005 0595 > > > > > > > > From dcook at prosentient.com.au Fri May 12 03:59:05 2017 From: dcook at prosentient.com.au (David Cook) Date: Fri, 12 May 2017 11:59:05 +1000 Subject: [Koha-devel] Packaging RDF::Trine (Hector Castro) In-Reply-To: References: Message-ID: <02ad01d2cac3$559f6a70$00de3f50$@prosentient.com.au> Hi Hector, Ahh, I did see something about that. Well, after looking through the source code, it looks like Moose and MooseX::ArrayRef are only used in RDF/Trine/Parser/Turtle/Token.pm and RDF/Trine/Parser/Turtle/Lexer.pm, so if we don?t load those modules, then we won?t need to actually ?use? Moose. In the past, I think the fear has been that using Moose with CGI would slow down Koha too much, but Plack would solve that since it would load it at startup and keep it in memory for all the requests without having to reload for each page request. My work with RDF::Trine is in a daemon which doesn?t interact directly with end users, and the performance seems fine to me, although I?m using RDF/Trine/Parser/RDFXML.pm which doesn?t use Moose it seems. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Hector Castro [mailto:hector.hecaxmmx at gmail.com] Sent: Friday, 12 May 2017 12:39 AM To: koha-devel at lists.koha-community.org Cc: dcook at prosentient.com.au Subject: Packaging RDF::Trine (Hector Castro) Hi David I remember that the issue found in RDF::Trine at that moment was the dependencies used by module especially because use Moose. The policy was not to use Moose about some problems with Koha. I don't know if this policy has been change since the introduction of Plack. Regards. Message: 2 Date: Thu, 11 May 2017 16:08:06 +1000 From: "David Cook" > To: > Subject: [Koha-devel] Packaging RDF::Trine Message-ID: <025c01d2ca1c$f4da7be0$de8f73a0$@prosentient.com.au > Content-Type: text/plain; charset="us-ascii" Hi all, Magnus and I have been working on a RDF project for Stockholm University Library, and I've been using RDF::Trine for our prototype. It works great overall, although I found a bug with RDF::Trine::Store::SPARQL version 1.016 (most current version on CPAN*). I sent in a pull request yesterday (https://github.com/kasei/perlrdf/pull/147) and the author of the module said that he's hoping to review it and merge it into master in the next few days. But what this means is that we'll be wanting to use the latest version of RDF::Trine, and that's going to be much newer than what is in the Debian repositories for Jessie and Wheezy. I've taken a peek at the code in those repos, and it's buggy too. I seem to recall on https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13642 that there were some issues packaging RDF libraries, but I think it may have mostly related to RDF::Helper, of which we have no need. But Mirko if I could get your input, that would be great. *Actually it seems the latest version in CPAN is newer than master in Github. I'll have to talk to the maintainer about that too. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ _______________________________________________ Koha-devel mailing list Koha-devel at 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/ End of Koha-devel Digest, Vol 138, Issue 10 ******************************************* -- Atte, H?ctor Eduardo Castro Avalos -------------- next part -------------- An HTML attachment was scrubbed... URL: From wilfredoqi at gmail.com Sat May 13 01:38:47 2017 From: wilfredoqi at gmail.com (Wilfredo Felix Quispe Infantes) Date: Fri, 12 May 2017 18:38:47 -0500 Subject: [Koha-devel] INSTALL KOHA 16 with database Postgresql9.4 Message-ID: Hello, Some experience with Koha and postgresql, some steps for this to work correctly? Thank You -------------- next part -------------- An HTML attachment was scrubbed... URL: From mik at adminkuhn.ch Sat May 13 11:31:37 2017 From: mik at adminkuhn.ch (Michael Kuhn) Date: Sat, 13 May 2017 11:31:37 +0200 Subject: [Koha-devel] INSTALL KOHA 16 with database Postgresql9.4 In-Reply-To: References: Message-ID: <98e0dfd9-6b59-faaa-b529-0cc587d817ce@adminkuhn.ch> Hi Wilfredo > Some experience with Koha and postgresql, some steps for this to work > correctly? Koha only supports MySQL or MariaDB. Postgresql is NOT supported. See https://koha-community.org/download-koha/ for the official Koha requirements (while I guess they are not even up-to-date - unfortunately Koha is not very outspoken about its actual requirements, the manual speaks rather vaguely about "recommendations" and "developer documentation"). From time to time some people seem to make efforts to also support Postgresql, but nothing has ever come out of it, so far. See : * https://wiki.koha-community.org/wiki/PostgreSQL * https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11389 (2014) * https://lists.katipo.co.nz/public/koha/2015-October/043851.html Best wishes: Michael -- Gesch?ftsf?hrer ? Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH ? Pappelstrasse 20 ? 4123 Allschwil ? Schweiz T 0041 (0)61 261 55 61 ? E mik at adminkuhn.ch ? W www.adminkuhn.ch From jonathan.druart at bugs.koha-community.org Mon May 15 16:54:04 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Mon, 15 May 2017 14:54:04 +0000 Subject: [Koha-devel] INSTALL KOHA 16 with database Postgresql9.4 In-Reply-To: References: Message-ID: Hello Wilfredo, Unfortunately we only support MySQL (no strict mode) or MariaDB. We are working hard to use DBIx::Class (ORM) to abstract our SQL queries and to become DB agnostic. Do you have a list of issues you faced? Regards, Jonathan On Fri, 12 May 2017 at 20:38 Wilfredo Felix Quispe Infantes < wilfredoqi at gmail.com> wrote: > Hello, > Some experience with Koha and postgresql, some steps for this to work > correctly? > > Thank You > > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From kohanews at gmail.com Mon May 15 19:27:14 2017 From: kohanews at gmail.com (kohanews) Date: Mon, 15 May 2017 10:27:14 -0700 Subject: [Koha-devel] Call for News: May 2017 Newsletter Message-ID: I'm collecting news for the May newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events , **** one month back is the cut-off ****. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. -- Chad Roseburg Editor, Koha Community Newsletter -- Chad Roseburg Editor, Koha Community Newsletter From z.tajoli at cineca.it Tue May 16 19:02:05 2017 From: z.tajoli at cineca.it (Tajoli Zeno) Date: Tue, 16 May 2017 19:02:05 +0200 Subject: [Koha-devel] Koha 17.05 Dates In-Reply-To: References: Message-ID: <5b5cfa49-e774-8918-1588-050677f58483@cineca.it> Hi to all, >May 12 - Feature Freeze, String Freeze, 1st Draft of Release Notes I don't find the 1st Draft of Release Note for 17.05. Where can I find it ? Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.tajoli at cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) From kyle.m.hall at gmail.com Wed May 17 13:24:34 2017 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Wed, 17 May 2017 07:24:34 -0400 Subject: [Koha-devel] Koha 17.05 Dates In-Reply-To: <5b5cfa49-e774-8918-1588-050677f58483@cineca.it> References: <5b5cfa49-e774-8918-1588-050677f58483@cineca.it> Message-ID: Zeno, you should have gotten a devel email titled "Koha 17.05 Release Notes - Draft 1". Please let me know if you didn't get it so I can resend it! Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) 2017-05-16 13:02 GMT-04:00 Tajoli Zeno : > Hi to all, > > >May 12 - Feature Freeze, String Freeze, 1st Draft of Release Notes > > I don't find the 1st Draft of Release Note for 17.05. > Where can I find it ? > > Bye > Zeno Tajoli > > -- > Zeno Tajoli > /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche > Email: z.tajoli at cineca.it Fax: 051/6132198 > *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kyle.m.hall at gmail.com Wed May 17 13:29:59 2017 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Wed, 17 May 2017 07:29:59 -0400 Subject: [Koha-devel] Koha 17.05 Release Notes - Draft One ( 2nd attempt ; ) Message-ID: I think my first attempt may be caught in mailing list moderation, so here is a link to the markdown version available on GitHub: https://github.com/kylemhall/Koha/blob/bc497cd58a874c4c10f214e7c2a8d5b35aa47a78/misc/release_notes/release_notes_17_05_00.md Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) -------------- next part -------------- An HTML attachment was scrubbed... URL: From kyle.m.hall at gmail.com Wed May 17 13:30:44 2017 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Wed, 17 May 2017 07:30:44 -0400 Subject: [Koha-devel] Koha 17.05 Dates In-Reply-To: References: <5b5cfa49-e774-8918-1588-050677f58483@cineca.it> Message-ID: I've sent a new email with a link to the markdown version of the release notes, but I figured I'd put it here as well: https://github.com/kylemhall/Koha/blob/bc497cd58a874c4c10f214e7c2a8d5b35aa47a78/misc/release_notes/release_notes_17_05_00.md Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Wed, May 17, 2017 at 7:24 AM, Kyle Hall wrote: > Zeno, you should have gotten a devel email titled "Koha 17.05 Release > Notes - Draft 1". Please let me know if you didn't get it so I can resend > it! > > Kyle > > > > > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > 2017-05-16 13:02 GMT-04:00 Tajoli Zeno : > >> Hi to all, >> >> >May 12 - Feature Freeze, String Freeze, 1st Draft of Release Notes >> >> I don't find the 1st Draft of Release Note for 17.05. >> Where can I find it ? >> >> Bye >> Zeno Tajoli >> >> -- >> Zeno Tajoli >> /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche >> Email: z.tajoli at cineca.it Fax: 051/6132198 >> *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/ >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.poulain at biblibre.com Wed May 17 18:17:11 2017 From: paul.poulain at biblibre.com (Paul Poulain) Date: Wed, 17 May 2017 18:17:11 +0200 Subject: [Koha-devel] Koha 17.05 Release Notes - Draft One ( 2nd attempt ; ) In-Reply-To: References: Message-ID: <76ad5e3f-e0ec-8017-99f8-b4726687dd61@biblibre.com> Hi Kyle & al, Some comments : * About [17196] Move marcxml out of the biblioitems table = o shouldn't it be also at the header, to be clearly visible (the warning about SQL report not working anymore) ? o are you sure of "SQL queries on the marcxml data will get a performance boost" ? I think it's "SQL queries that use biblioitems bot not marcxml data will get a bit performance boost" * there are a lot of enhancements related to internal/plumbing. That's great. But as they are, in the Release Notes, my feeling is that they are so many that other enhancements are "lost". * i'd like to see HEA v2 ([18066] ) promoted in the header, as well as ElasticSearch progress (various patches) * [17855] New onboarding tool feature to guide users through setting up Koha, and minor web installer UI improvements => it's in "new feature". Shouldn't it be in "enhancements" instead ? Same feeling for [14224] patron notes about item shown at check in * [12461] Add patron clubs feature => deserve some details ! * shouldn't * [17486] Remove 'Mozilla Persona' as an authentication method be in the header of the RNotes ? * shouldn't [17762] Ability to translate notices be considered as a new feature ? * [17960] Rename opac_news.new with opac_news.content NOTICE - If you are using opac_news.new in your notice templates, you should update it to opac_news.content o => it should be in the header (easy to miss it) * at the end = The branch for this version of Koha and future bugfixes in this release line is *bug17618-qa*. => just to double check: it's auto-generated and will be correct in the final release, isn't it ? Additional comment : contributors list : * Marcel de Rooy (160) [Rijksmuseum (160) ] ==> WOW !! great job Marcel !!! -- Paul Poulain, Associ?-g?rant / co-owner BibLibre, Services en logiciels libres pour les biblioth?ques BibLibre, Open Source software and services for libraries -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: From chrisc at catalyst.net.nz Wed May 17 19:44:53 2017 From: chrisc at catalyst.net.nz (Chris Cormack) Date: Thu, 18 May 2017 05:44:53 +1200 Subject: [Koha-devel] Koha 17.05 Release Notes - Draft One ( 2nd attempt ; ) In-Reply-To: <76ad5e3f-e0ec-8017-99f8-b4726687dd61@biblibre.com> References: <76ad5e3f-e0ec-8017-99f8-b4726687dd61@biblibre.com> Message-ID: <5BFBC4DD-A9A7-4A65-973D-268774A34928@catalyst.net.nz> Id say the on boarding tool is definitely a new feature. I agree with the plumbing ones though, no one except devs care about them I would put them last or even leave them out. If the release notes are long people don't read them Chris On 18 May 2017 4:17:11 AM NZST, Paul Poulain wrote: >Hi Kyle & al, > >Some comments : > > * About [17196] > > Move marcxml out of the biblioitems table = > o shouldn't it be also at the header, to be clearly visible (the > warning about SQL report not working anymore) ? > o are you sure of "SQL queries on the marcxml data will get a > performance boost" ? I think it's "SQL queries that use > biblioitems bot not marcxml data will get a bit performance boost" > * there are a lot of enhancements related to internal/plumbing. That's > great. But as they are, in the Release Notes, my feeling is that > they are so many that other enhancements are "lost". > * i'd like to see HEA v2 ([18066] > ) > promoted in the header, as well as ElasticSearch progress (various > patches) > * [17855] > New > onboarding tool feature to guide users through setting up Koha, and > minor web installer UI improvements => it's in "new feature". > Shouldn't it be in "enhancements" instead ? Same feeling for [14224] > > patron notes about item shown at check in > * [12461] > Add > patron clubs feature => deserve some details ! > * shouldn't > * [17486] > > Remove 'Mozilla Persona' as an authentication method be in the > header of the RNotes ? > * shouldn't [17762] > > Ability to translate notices be considered as a new feature ? > * [17960] > > Rename opac_news.new with opac_news.content NOTICE - If you are > using opac_news.new in your notice templates, you should update it > to opac_news.content > o => it should be in the header (easy to miss it) > * > > at the end = The branch for this version of Koha and future bugfixes > in this release line is *bug17618-qa*. => just to double check: it's > auto-generated and will be correct in the final release, isn't it ? > >Additional comment : > >contributors list : > > * Marcel de Rooy (160) [Rijksmuseum (160) ] ==> WOW !! great job > Marcel !!! > >-- >Paul Poulain, Associ?-g?rant / co-owner >BibLibre, Services en logiciels libres pour les biblioth?ques >BibLibre, Open Source software and services for libraries -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kyle.m.hall at gmail.com Wed May 17 20:04:04 2017 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Wed, 17 May 2017 14:04:04 -0400 Subject: [Koha-devel] Koha 17.05 Release Notes - Draft One ( 2nd attempt ; ) In-Reply-To: <76ad5e3f-e0ec-8017-99f8-b4726687dd61@biblibre.com> References: <76ad5e3f-e0ec-8017-99f8-b4726687dd61@biblibre.com> Message-ID: Thanks Paul! I'll definitely take those suggestions into account for the final release notes. Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Wed, May 17, 2017 at 12:17 PM, Paul Poulain wrote: > Hi Kyle & al, > > Some comments : > > - About [17196] > Move > marcxml out of the biblioitems table = > - shouldn't it be also at the header, to be clearly visible (the > warning about SQL report not working anymore) ? > - are you sure of "SQL queries on the marcxml data will get a > performance boost" ? I think it's "SQL queries that use biblioitems bot not > marcxml data will get a bit performance boost" > - there are a lot of enhancements related to internal/plumbing. That's > great. But as they are, in the Release Notes, my feeling is that they are > so many that other enhancements are "lost". > - i'd like to see HEA v2 ([18066] > ) > promoted in the header, as well as ElasticSearch progress (various patches) > - [17855] > New > onboarding tool feature to guide users through setting up Koha, and minor > web installer UI improvements => it's in "new feature". Shouldn't it be in > "enhancements" instead ? Same feeling for [14224] > > patron notes about item shown at check in > - [12461] > Add > patron clubs feature => deserve some details ! > - shouldn't > - [17486] > > Remove 'Mozilla Persona' as an authentication method be in the header of > the RNotes ? > - shouldn't [17762] > > Ability to translate notices be considered as a new feature ? > - [17960] > > Rename opac_news.new with opac_news.content NOTICE - If you are using > opac_news.new in your notice templates, you should update it to > opac_news.content > - => it should be in the header (easy to miss it) > - > > at the end = The branch for this version of Koha and future bugfixes > in this release line is *bug17618-qa*. => just to double check: it's > auto-generated and will be correct in the final release, isn't it ? > > Additional comment : > > contributors list : > > - Marcel de Rooy (160) [Rijksmuseum (160) ] ==> WOW !! great job > Marcel !!! > > -- > Paul Poulain, Associ?-g?rant / co-owner > BibLibre, Services en logiciels libres pour les biblioth?ques > BibLibre, Open Source software and services for libraries > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kyle.m.hall at gmail.com Wed May 17 20:06:43 2017 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Wed, 17 May 2017 14:06:43 -0400 Subject: [Koha-devel] Koha 17.05 Release Notes - Draft One ( 2nd attempt ; ) In-Reply-To: <5BFBC4DD-A9A7-4A65-973D-268774A34928@catalyst.net.nz> References: <76ad5e3f-e0ec-8017-99f8-b4726687dd61@biblibre.com> <5BFBC4DD-A9A7-4A65-973D-268774A34928@catalyst.net.nz> Message-ID: I don't know if I want to remove the 'plumbing' bugs altogether. Simply having them there shows the healthy development Koha goes thought. That being said I think the idea of moving those to the bottom in favor of highlighting the types of bugs that librarians can visually see and experience is a pretty good idea. Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Wed, May 17, 2017 at 1:44 PM, Chris Cormack wrote: > Id say the on boarding tool is definitely a new feature. > > I agree with the plumbing ones though, no one except devs care about them > I would put them last or even leave them out. If the release notes are long > people don't read them > > Chris > > On 18 May 2017 4:17:11 AM NZST, Paul Poulain > wrote: >> >> Hi Kyle & al, >> >> Some comments : >> >> - About [17196] >> Move >> marcxml out of the biblioitems table = >> - shouldn't it be also at the header, to be clearly visible (the >> warning about SQL report not working anymore) ? >> - are you sure of "SQL queries on the marcxml data will get a >> performance boost" ? I think it's "SQL queries that use biblioitems bot not >> marcxml data will get a bit performance boost" >> - there are a lot of enhancements related to internal/plumbing. >> That's great. But as they are, in the Release Notes, my feeling is that >> they are so many that other enhancements are "lost". >> - i'd like to see HEA v2 ([18066] >> ) >> promoted in the header, as well as ElasticSearch progress (various patches) >> - [17855] >> New >> onboarding tool feature to guide users through setting up Koha, and minor >> web installer UI improvements => it's in "new feature". Shouldn't it be in >> "enhancements" instead ? Same feeling for [14224] >> >> patron notes about item shown at check in >> - [12461] >> Add >> patron clubs feature => deserve some details ! >> - shouldn't >> - [17486] >> >> Remove 'Mozilla Persona' as an authentication method be in the header of >> the RNotes ? >> - shouldn't [17762] >> >> Ability to translate notices be considered as a new feature ? >> - [17960] >> >> Rename opac_news.new with opac_news.content NOTICE - If you are using >> opac_news.new in your notice templates, you should update it to >> opac_news.content >> - => it should be in the header (easy to miss it) >> - >> >> at the end = The branch for this version of Koha and future bugfixes >> in this release line is *bug17618-qa*. => just to double check: it's >> auto-generated and will be correct in the final release, isn't it ? >> >> Additional comment : >> >> contributors list : >> >> - Marcel de Rooy (160) [Rijksmuseum (160) ] ==> WOW !! great job >> Marcel !!! >> >> -- >> Paul Poulain, Associ?-g?rant / co-owner >> BibLibre, Services en logiciels libres pour les biblioth?ques >> BibLibre, Open Source software and services for libraries >> >> > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Wed May 17 20:10:23 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Wed, 17 May 2017 18:10:23 +0000 Subject: [Koha-devel] Koha 17.05 Release Notes - Draft One ( 2nd attempt ; ) In-Reply-To: References: <76ad5e3f-e0ec-8017-99f8-b4726687dd61@biblibre.com> <5BFBC4DD-A9A7-4A65-973D-268774A34928@catalyst.net.nz> Message-ID: +1! El mi?., 17 may. 2017 a las 15:06, Kyle Hall () escribi?: > I don't know if I want to remove the 'plumbing' bugs altogether. Simply > having them there shows the healthy development Koha goes thought. That > being said I think the idea of moving those to the bottom in favor of > highlighting the types of bugs that librarians can visually see and > experience is a pretty good idea. > > Kyle > > > > > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > On Wed, May 17, 2017 at 1:44 PM, Chris Cormack > wrote: > >> Id say the on boarding tool is definitely a new feature. >> >> I agree with the plumbing ones though, no one except devs care about them >> I would put them last or even leave them out. If the release notes are long >> people don't read them >> >> Chris >> >> On 18 May 2017 4:17:11 AM NZST, Paul Poulain >> wrote: >>> >>> Hi Kyle & al, >>> >>> Some comments : >>> >>> - About [17196] >>> >>> Move marcxml out of the biblioitems table = >>> - shouldn't it be also at the header, to be clearly visible (the >>> warning about SQL report not working anymore) ? >>> - are you sure of "SQL queries on the marcxml data will get a >>> performance boost" ? I think it's "SQL queries that use biblioitems bot not >>> marcxml data will get a bit performance boost" >>> - there are a lot of enhancements related to internal/plumbing. >>> That's great. But as they are, in the Release Notes, my feeling is that >>> they are so many that other enhancements are "lost". >>> - i'd like to see HEA v2 ([18066] >>> ) >>> promoted in the header, as well as ElasticSearch progress (various patches) >>> - [17855] >>> New >>> onboarding tool feature to guide users through setting up Koha, and minor >>> web installer UI improvements => it's in "new feature". Shouldn't it be in >>> "enhancements" instead ? Same feeling for [14224] >>> >>> patron notes about item shown at check in >>> - [12461] >>> Add >>> patron clubs feature => deserve some details ! >>> - shouldn't >>> - [17486] >>> >>> Remove 'Mozilla Persona' as an authentication method be in the header of >>> the RNotes ? >>> - shouldn't [17762] >>> >>> Ability to translate notices be considered as a new feature ? >>> - [17960] >>> >>> Rename opac_news.new with opac_news.content NOTICE - If you are using >>> opac_news.new in your notice templates, you should update it to >>> opac_news.content >>> - => it should be in the header (easy to miss it) >>> - >>> >>> at the end = The branch for this version of Koha and future bugfixes >>> in this release line is *bug17618-qa*. => just to double check: it's >>> auto-generated and will be correct in the final release, isn't it ? >>> >>> Additional comment : >>> >>> contributors list : >>> >>> - Marcel de Rooy (160) [Rijksmuseum (160) ] ==> WOW !! great job >>> Marcel !!! >>> >>> -- >>> Paul Poulain, Associ?-g?rant / co-owner >>> BibLibre, Services en logiciels libres pour les biblioth?ques >>> BibLibre, Open Source software and services for libraries >>> >>> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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 at 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/ -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From z.tajoli at cineca.it Thu May 18 07:19:36 2017 From: z.tajoli at cineca.it (Zeno Tajoli) Date: Thu, 18 May 2017 07:19:36 +0200 (CEST) Subject: [Koha-devel] Koha 17.05 Release Notes - Draft One ( 2nd attempt ; ) In-Reply-To: <76ad5e3f-e0ec-8017-99f8-b4726687dd61@biblibre.com> Message-ID: <1600202827.99487799.1495084776870.JavaMail.root@cineca.it> Hi Paul and all, In fact I'm cut & paste comments in bugzilla to insert them into 'Text for release note'. In fact Release Notes are done by a script but if we change bugzilla, it change also it !! Bye Zeno Tajoli From tomascohen at gmail.com Thu May 18 14:08:11 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Thu, 18 May 2017 12:08:11 +0000 Subject: [Koha-devel] Adding new authority types Message-ID: Hi, bug 17805 proposes to add a new authority type, and I was wondering what has been the normal handling for this, specially regarding the upgrade process. Should it be added automatically? Regards -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick at bywatersolutions.com Fri May 19 14:51:37 2017 From: nick at bywatersolutions.com (Nick Clemens) Date: Fri, 19 May 2017 12:51:37 +0000 Subject: [Koha-devel] [ByWater Partners] Acquisitions change in Koha 16.11 and forward In-Reply-To: References: Message-ID: Hi Sandre, The current replacement/rrp field is used for two things: 1 - passing through from the orders as the items.replacementprice field 2 - the basis for calculating prices (minus discount, plus tax, etc) Splitting the replacement cost out will allow proper discount/tax calculation while allowing manual edit to the replacement cost to add fees etc. I believe our proposal works for your workflow. -Nick On Tue, May 16, 2017 at 5:40 PM Sandre Cunha wrote: > Before you add yet another price field to acquisitions, I would like to > understand the intended function of the "replacement/rrp" field. > > I realize that not all libraries operate the same and that they have a > variety of needs and restraints. For Monterey Public Library, the only > reason to even have replacement cost in the order screen is to streamline > processing when the item gets to cataloging, i.e., so they don't have to > enter it. > For us, the replacement cost is the price we charge the customer if they > lose or damage the item. Is this the intended purpose of this field? > > Our replacement cost used to be the list price plus $10 for processing, > but never included tax. > > Example 1: > Retail price: $27.99 Actual cost: $15.34 Sales tax:$1.34 In this > scenario, the replacement price = $37.99 [27.99 + $10.00 processing] > > Now, we use our actual cost [the price discounted from retail]; the only > time it is different is when the cost is less than our maximum fine, in > which case the maximum fine fee becomes the replacement price. > > Example 2: > Retail price: $27.99 Actual cost: $15.34 Sales tax: $1.34 > Replacement price = $15.34 > > Example 3: > > Retail price: $18.00 Actual cost: $9.86 Sales tax: $0.83 Replacement > price: $10.00 [our maximum late fine for this collection is $10.00, which > is more than 9.86] > > Other drawbacks to the new way "replacement/rrp" is handled: when you need > to create an order for which the cost is $0 (gift, credit allocation, or > pre-order for next fiscal year) but you want to have a replacement cost > recorded. > > Additionally, please note that we do not enter discounts in our vendor > records, as even with our largest two vendors the discount varies depending > on the type of material and source. With one vendor our contract specifies > a 42% discount for many items, but for some we get less, some no discount, > and every once in a while we pay more than retail due to a surcharge. > > I would be interested to know the methods acquisitions staff at other > libraries use. It would be useful to have a better understanding of usage > and needs before adding yet another field to the order details. > > ________________________ > Sandre Cunha > Technical Services Supervisor > Monterey Public Library > 625 Pacific Street > Monterey, CA 93940 > Tel. 831-646-3740 <(831)%20646-3740> > > ?If you want to build a ship, don?t drum up your men to collect wood and > give orders and distribute the work. Instead, teach them to yearn for the > vast and endless sea." -- Antoine de Saint-Exup?ry > > On Tue, May 9, 2017 at 1:44 PM, Nick Clemens > wrote: > >> Hello All, >> >> With the current versions of Koha there have been some changes in >> acquisitions and how prices are calculated and there seems to be some >> confusion in terms and how things are currently being used. >> >> We wanted to clarify what is happening, propose a change and get feedback >> on what needs to happen. >> >> When placing an order there are several price fields: >> Vendor price (listprice in db) >> -This is used to populate the Replacement cost and budgeted cost on the >> order page. It is not used against the budget >> >> Replacement cost (rrp in db) >> -This is used to calculate the 'budgeted cost/ecost' in the budget - it >> also populates the replacement price in the item created by the aqc process >> once received >> >> Budgeted cost (ecost in db) >> -This is the replacement/rpp minus any discount on the order - this is >> the value that will be encumbered when the order is placed >> >> Actual cost (unitprice) >> -This is the eventual 'price' of the item and is the encumbered amount >> once the item has been received. >> >> With the changes that were made one can no longer adjust the >> 'Replacement/RRP' once an order is placed - this is because this value is >> adjusted for tax in the db (rrp_tax_excluded, rrp_tax_included) and used >> for calculating the ecost tax adjusted (ecost_tax_excluded, >> ecost_tax_included) >> >> Some libraries have been having issues as they use 'Replacement' cost >> mostly for populating items and are not used to it being unable to be >> edited and/or affecting budgets. >> >> We are proposing to rename the current 'Replacement cost' field to match >> the db value - 'Recommended retail price' (RRP) and add a new 'Replacement >> cost' field, editable at any point, that is only used for populating the >> item field. >> >> We think this will clear up how the other values are being used and >> restore functionality that changed. >> >> Please let us know if this works or what other suggestions you have here. >> >> Thank you, >> Nick, Kyle, Jonathan >> >> _______________________________________________ >> Partners mailing list >> Partners at lists.bywatersolutions.com >> http://lists.bywatersolutions.com/mailman/listinfo/partners >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Fri May 19 18:15:22 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Fri, 19 May 2017 16:15:22 +0000 Subject: [Koha-devel] marcxml > biblio_metadata - Automatically convert reports Message-ID: Hi guys, It seems like my calls did not get the expected attention, so I am trying once again. Bug 17196 (Move marcxml out of the biblioitems table) has been pushed to master a while ago and 17.05 will be the first release with this change. I wrote bug 17898 (Add a way to automatically convert SQL reports) 4 months ago asking for a special attention: librarians will need it to update easily their reports. Since 17.05 is going to be released in a week and we are in string freeze, I guess there is no way to get it in. But I personally think that we should make an exception for this one. Please do not let this request without answer once again. Cheers, Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL: From kyle.m.hall at gmail.com Fri May 19 18:57:19 2017 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Fri, 19 May 2017 12:57:19 -0400 Subject: [Koha-devel] Koha 17.05 Release Notes - Draft 2 + Beta Message-ID: Hey all, Here is the second version of the Release Notes and the beta! The release notes have the same issues as before. I'll fix the character encodings by hand in the final release. https://github.com/kylemhall/Koha/blob/v17.05.00_RC1/misc/release_notes/release_notes_17_05_00.md I've included the tarball in the repo rather than muck up the ftp server with it: https://github.com/kylemhall/Koha/tree/v17.05.00_RC1/releases Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) -------------- next part -------------- An HTML attachment was scrubbed... URL: From veron at veron.ch Fri May 19 20:41:49 2017 From: veron at veron.ch (=?UTF-8?Q?Marc_V=c3=a9ron?=) Date: Fri, 19 May 2017 20:41:49 +0200 Subject: [Koha-devel] marcxml > biblio_metadata - Automatically convert reports In-Reply-To: References: Message-ID: +1 for this, even if we are in string freeze We will have a mix between translations and English anyway in the more exposed install tool (see Bug 18629), so some more English strings are OK. Marc Am 19.05.2017 um 18:15 schrieb Jonathan Druart: > Hi guys, > > It seems like my calls did not get the expected attention, so I am > trying once again. > Bug 17196(Move marcxml out of the biblioitems table) has been pushed > to master a while ago and 17.05 will be the first release with this > change. > I wrote bug 17898 (Add a way to automatically convert SQL reports) 4 > months ago asking for a special attention: librarians will need it to > update easily their reports. > Since 17.05 is going to be released in a week and we are in string > freeze, I guess there is no way to get it in. But I personally think > that we should make an exception for this one. > > Please do not let this request without answer once again. > > Cheers, > Jonathan > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From katrin.fischer.83 at web.de Mon May 22 08:06:45 2017 From: katrin.fischer.83 at web.de (Katrin) Date: Mon, 22 May 2017 08:06:45 +0200 Subject: [Koha-devel] Koha 16.11.08 released Message-ID: <840c2bc4-2675-3871-ce14-eaabae5761e1@web.de> The Koha community is proud to announce the release of Koha 16.11.08. This is a maintenance release of 16.11 and includes 5 enhancements and 50 bugfixes. The full release notes are available at https://koha-community.org/koha-16-11-08-release/ Packages will be available soon. From mirko at abunchofthings.net Mon May 22 10:44:09 2017 From: mirko at abunchofthings.net (Mirko Tietgen) Date: Mon, 22 May 2017 10:44:09 +0200 Subject: [Koha-devel] [Koha] Koha 16.11.08 released In-Reply-To: <840c2bc4-2675-3871-ce14-eaabae5761e1@web.de> References: <840c2bc4-2675-3871-ce14-eaabae5761e1@web.de> Message-ID: Katrin Fischer schrieb am 22.05.2017 > The Koha community is proud to announce the release of Koha 16.11.08. > > This is a maintenance release of 16.11 and includes 5 enhancements > and 50 bugfixes. > > The full release notes are available at > https://koha-community.org/koha-16-11-08-release/ > > Packages will be available soon. The Debian package is now available from the Koha community repository. -- Mirko -- Mirko Tietgen mirko at abunchofthings.net http://koha.abunchofthings.net http://meinkoha.de From M.de.Rooy at rijksmuseum.nl Mon May 22 11:16:04 2017 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Mon, 22 May 2017 09:16:04 +0000 Subject: [Koha-devel] Adding new authority types In-Reply-To: References: Message-ID: Tomas, Only talking about MARC21 here: I did not come across any inserts into auth_types in updatedatabase. But since authorities_normal_marc21.sql is in marc21/mandatory, I would expect a new official authority type to be inserted both at install and upgrade time. Marcel Van: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] Namens Tomas Cohen Arazi Verzonden: donderdag 18 mei 2017 14:08 Aan: koha-devel Onderwerp: [Koha-devel] Adding new authority types Hi, bug 17805 proposes to add a new authority type, and I was wondering what has been the normal handling for this, specially regarding the upgrade process. Should it be added automatically? Regards -- Tom?s Cohen Arazi Theke Solutions (https://theke.io) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From barton at bywatersolutions.com Mon May 22 16:21:07 2017 From: barton at bywatersolutions.com (Barton Chittenden) Date: Mon, 22 May 2017 10:21:07 -0400 Subject: [Koha-devel] marcxml > biblio_metadata - Automatically convert reports In-Reply-To: References: Message-ID: Just in case anyone is late catching up on email, bug 17898 was pushed to master on 2017-05-22... so we're all set here. On Fri, May 19, 2017 at 2:41 PM, Marc V?ron wrote: > +1 for this, even if we are in string freeze > > We will have a mix between translations and English anyway in the more > exposed install tool (see Bug 18629), so some more English strings are OK. > > Marc > > Am 19.05.2017 um 18:15 schrieb Jonathan Druart: > > Hi guys, > > It seems like my calls did not get the expected attention, so I am trying > once again. > Bug 17196 (Move marcxml out of the biblioitems table) has been pushed to > master a while ago and 17.05 will be the first release with this change. > I wrote bug 17898 (Add a way to automatically convert SQL reports) 4 > months ago asking for a special attention: librarians will need it to > update easily their reports. > Since 17.05 is going to be released in a week and we are in string freeze, > I guess there is no way to get it in. But I personally think that we should > make an exception for this one. > > Please do not let this request without answer once again. > > Cheers, > Jonathan > > > _______________________________________________ > Koha-devel mailing listKoha-devel at lists.koha-community.orghttp://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 at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From julian.maurice at biblibre.com Mon May 22 18:17:30 2017 From: julian.maurice at biblibre.com (Julian Maurice) Date: Mon, 22 May 2017 18:17:30 +0200 Subject: [Koha-devel] Koha 3.22.21 release Message-ID: The Koha community is proud to announce the release of Koha 3.22.21. This is a maintenance release and contains several bugfixes. The full release notes are available at https://koha-community.org/koha-3-22-21-release/ Please note that Koha version 3.22 won't be maintained anymore and this is the last 3.22 release. If you are still using it, you should consider upgrading to a more recent version. From tomascohen at gmail.com Mon May 22 19:04:48 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Mon, 22 May 2017 17:04:48 +0000 Subject: [Koha-devel] Koha 3.22.21 release In-Reply-To: References: Message-ID: Julian, 3.22 was pretty good :-D Well done! El lun., 22 may. 2017 a las 13:17, Julian Maurice (< julian.maurice at biblibre.com>) escribi?: > The Koha community is proud to announce the release of Koha 3.22.21. > > This is a maintenance release and contains several bugfixes. > > The full release notes are available at > https://koha-community.org/koha-3-22-21-release/ > > Please note that Koha version 3.22 won't be maintained anymore and this > is the last 3.22 release. If you are still using it, you should consider > upgrading to a more recent version. > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From julian.maurice at biblibre.com Mon May 22 19:52:10 2017 From: julian.maurice at biblibre.com (Julian Maurice) Date: Mon, 22 May 2017 19:52:10 +0200 Subject: [Koha-devel] Koha 3.22.21 release In-Reply-To: References: Message-ID: Glad to read that :-) Thanks Le 22/05/2017 ? 19:04, Tomas Cohen Arazi a ?crit : > Julian, 3.22 was pretty good :-D > Well done! > > El lun., 22 may. 2017 a las 13:17, Julian Maurice > (>) > escribi?: > > The Koha community is proud to announce the release of Koha 3.22.21. > > This is a maintenance release and contains several bugfixes. > > The full release notes are available at > https://koha-community.org/koha-3-22-21-release/ > > Please note that Koha version 3.22 won't be maintained anymore and this > is the last 3.22 release. If you are still using it, you should consider > upgrading to a more recent version. > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > > -- > Tom?s Cohen Arazi > Theke Solutions (https://theke.io ) > ? +54 9351 3513384 > GPG: B2F3C15F -- Julian Maurice BibLibre From katrin.fischer.83 at web.de Mon May 22 22:32:55 2017 From: katrin.fischer.83 at web.de (Katrin) Date: Mon, 22 May 2017 22:32:55 +0200 Subject: [Koha-devel] Adding new authority types In-Reply-To: References: Message-ID: Hi Tomas, I think it should be added when updating, if it does not already exist. It's easy to delete an extra authority type if you don't want it, harder to add it. We probably need a new framework for this, the datbase entries for the authority type and amend the mappings in some of the scripts so they know 147 is the main heading for named events. Hope this helps, Katrin On 18.05.2017 14:08, Tomas Cohen Arazi wrote: > Hi, bug 17805 > proposes > to add a new authority type, and I was wondering what has been the > normal handling for this, specially regarding the upgrade process. > > Should it be added automatically? > > Regards > -- > Tom?s Cohen Arazi > Theke Solutions (https://theke.io ) > ? +54 9351 3513384 > GPG: B2F3C15F > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick at bywatersolutions.com Tue May 23 20:51:27 2017 From: nick at bywatersolutions.com (Nick Clemens) Date: Tue, 23 May 2017 18:51:27 +0000 Subject: [Koha-devel] REMINDER: Koha IRC Developers Meeting - Tomorrow, May 24th, 14 UTC Message-ID: Hello Koha community! Just a reminder that tomorrow is our next devel meeting in IRC. https://koha-community.org/get-involved/irc/ Time & Date: 24 May 2017, 14:00 UTC Time and Date.com converter for various local times Agenda: https://wiki.koha-community.org/wiki/Development_IRC_meeting_24_May_2017 Please add anything you wish to discuss. Look forward to seeing you all there. -Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Tue May 23 21:25:57 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Tue, 23 May 2017 19:25:57 +0000 Subject: [Koha-devel] UUIDs? Message-ID: Has anyone considered the option to use UUIDs for our PK? I'm pretty sure DBIx::Class supports them. I'm not sure how SQL::Abstract handles them, but I know MySQL provides the uuid() function. This way we could get rid of this auto increment problem... and get new ones of course :-P I'm just wondering if there's been any discussion about that. Regards -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From barton at bywatersolutions.com Tue May 23 23:45:36 2017 From: barton at bywatersolutions.com (Barton Chittenden) Date: Tue, 23 May 2017 17:45:36 -0400 Subject: [Koha-devel] UUIDs? In-Reply-To: References: Message-ID: Oooh. Very nice idea, Tomas! On Tue, May 23, 2017 at 3:25 PM, Tomas Cohen Arazi wrote: > Has anyone considered the option to use UUIDs for our PK? I'm pretty sure > DBIx::Class supports them. I'm not sure how SQL::Abstract handles them, but > I know MySQL provides the uuid() function. > > This way we could get rid of this auto increment problem... and get new > ones of course :-P > > I'm just wondering if there's been any discussion about that. > > Regards > -- > Tom?s Cohen Arazi > Theke Solutions (https://theke.io ) > ? +54 9351 3513384 <+54%209%20351%20351-3384> > GPG: B2F3C15F > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From magnus at enger.priv.no Wed May 24 09:23:43 2017 From: magnus at enger.priv.no (Magnus Enger) Date: Wed, 24 May 2017 09:23:43 +0200 Subject: [Koha-devel] [Koha] NCIP project In-Reply-To: References: Message-ID: On 19 May 2017 at 09:07, vikram zadgaonkar wrote: > We are working on NCIP server integration with koha.We are looking for > support for the same. > > Currently, ncip framework (server and responses etc) appears to be working. > However, data from koha db is not being picked up. There appears to be some > communication error between the koha library (C4) and ncip server's modules. Are you using the NCIPServer created by Chris Cormack/Catalyst and later forked/developed by several people, including ByWater and myself? If so: How are you running it? I run it something like this: $ sudo KOHA_CONF=/etc/koha/sites/koha/koha-conf.xml perl -I/home/magnus/kohaclone/ bin/ncip_dancing.pl --port 80 KOHA_CONF=/etc/koha/sites/koha/koha-conf.xml is the path to the koha-conf.xml of the Koha instance that NCIPServer should be talking to. -I/home/magnus/kohaclone/ is the path to where the C4 and Koha folders are. This is how NCIPServer knows where to find the C4:: and Koha:: modules it needs. Hope that helps, Magnus Libriotech From mtj at kohaaloha.com Wed May 24 21:17:58 2017 From: mtj at kohaaloha.com (Mason James) Date: Thu, 25 May 2017 07:17:58 +1200 Subject: [Koha-devel] Koha 16.05.13 release Message-ID: <40f33ef7-0e0d-aa69-130d-729849d5ba1b@kohaaloha.com> The Koha community is proud to announce the release of Koha 16.05.13 This is a maintenance release and includes 36 bugfixes, and Hea2 :0) https://hea.koha-community.org/ The full release notes are available at https://koha-community.org/koha-16.05.13-release/ Packages will be available soon. Mason From josef.moravec at gmail.com Thu May 25 12:29:58 2017 From: josef.moravec at gmail.com (Josef Moravec) Date: Thu, 25 May 2017 10:29:58 +0000 Subject: [Koha-devel] Expected behaviod when printing serials - add reserve? In-Reply-To: References: Message-ID: Hello Jonathan, I would say we should add holds only when the new issue is and syspref RoutingListAddReserves is on. Print list is bad action/time for that. The hold should be item level - as biblio level hold on serial is not really useful... Regards Josef po 13. 3. 2017 v 17:26 odes?latel Jonathan Druart < jonathan.druart at bugs.koha-community.org> napsal: > Hi devs, > > I found an obvious bug in serials/routing-preview.pl. > If the script is called with ok=1 (hum... yes...), the script will add or > modify a hold placed on the bibliographic records existing in the routing > list. > So from /serials/serials-collection.pl?subscriptionid=1, click on "Print > list" you get a pop-up with a print and close button. > When the pop-up is generated, we already have the ok=1 and the go through: > 66: my ($count2, at bibitems) = GetBiblioItemByBiblioNumber($biblio); > Then later: > 96 > AddReserve($branch,$routing->{borrowernumber},$biblio,\@bibitems,$routing->{ranking}, > undef, undef, $notes,$title); > > The problem is that GetBiblioItemByBiblioNumber will always return only 1 > value (for obvious reasons) and @bibitems will always be empty => reserve > is placed at bib level > > The thing is that this bug exists for ages (at least 2006, maybe always). > What is the expected behaviour? > > No need to tell you that I was going to kick GetBiblioItemByBiblioNumber > when I found that bug. > > Cheers, > Jonathan > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mirko at abunchofthings.net Thu May 25 19:07:53 2017 From: mirko at abunchofthings.net (Mirko Tietgen) Date: Thu, 25 May 2017 19:07:53 +0200 Subject: [Koha-devel] [Koha] Koha 16.05.13 release In-Reply-To: <40f33ef7-0e0d-aa69-130d-729849d5ba1b@kohaaloha.com> References: <40f33ef7-0e0d-aa69-130d-729849d5ba1b@kohaaloha.com> Message-ID: Mason James schrieb am 24.05.2017 > The Koha community is proud to announce the release of Koha 16.05.13 > > This is a maintenance release and includes 36 bugfixes, and Hea2 :0) > https://hea.koha-community.org/ > > The full release notes are available at > https://koha-community.org/koha-16.05.13-release/ > > Packages will be available soon. The Debian package for Koha 16.05.13 is now available from the Koha community repository. Please note that this will be the last official Debian package for the Koha 16.05.x branch. With the release of Koha 17.05, Debian packages will be available for Koha 17.05.x ('stable') Koha 16.11.x ('oldstable') Koha 16.05.x will continue to be maintained during the coming release cycle and receive maintenance and security updates, but there won't be official Debian packages available from the Koha community repository any longer. Cheers, Mirko -- Mirko Tietgen mirko at abunchofthings.net http://koha.abunchofthings.net http://meinkoha.de From kyle.m.hall at gmail.com Sun May 28 17:53:14 2017 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Sun, 28 May 2017 11:53:14 -0400 Subject: [Koha-devel] Koha 17.05 Release Delay Message-ID: Hello All, As some of you may have heard at the last IRC meeting, I'm in the middle of moving into a new home. This has delayed the release of 17.05 a bit. I hope to have it out the door sometime tonight or tomorrow ( as soon as I've got internet access again ). Sorry for the delay! Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) -------------- next part -------------- An HTML attachment was scrubbed... URL: From mirko at abunchofthings.net Tue May 30 12:14:54 2017 From: mirko at abunchofthings.net (Mirko Tietgen) Date: Tue, 30 May 2017 12:14:54 +0200 Subject: [Koha-devel] [Koha] Koha 16.05.13 release In-Reply-To: <40f33ef7-0e0d-aa69-130d-729849d5ba1b@kohaaloha.com> References: <40f33ef7-0e0d-aa69-130d-729849d5ba1b@kohaaloha.com> Message-ID: <7202f83e-65b6-8b31-252c-32419bd872d2@abunchofthings.net> The first package for Koha 16.05.13 accidentally contained a wrong branch and was removed from the repository after discovery last week. I have uploaded 16.05.13-2 to the Koha community repository. Apologies for any inconvenience! -- Mirko Mason James schrieb am 24.05.2017 > The Koha community is proud to announce the release of Koha 16.05.13 > > This is a maintenance release and includes 36 bugfixes, and Hea2 :0) > https://hea.koha-community.org/ > > The full release notes are available at > https://koha-community.org/koha-16.05.13-release/ > > Packages will be available soon. > > Mason > > _______________________________________________ > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > From kyle.m.hall at gmail.com Wed May 31 04:13:44 2017 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Tue, 30 May 2017 22:13:44 -0400 Subject: [Koha-devel] Koha 17.05.00 released! Message-ID: Hello all! It is my honor to announce the release of Koha 17.05.00! Thanks you to everyone who contributed time and effort making this the best version of Koha yet! The release notes can be found on the Koha Community website: https://koha-community.org/koha-17-05-released/ Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.de.Rooy at rijksmuseum.nl Wed May 31 08:26:12 2017 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Wed, 31 May 2017 06:26:12 +0000 Subject: [Koha-devel] Koha 17.05.00 released! In-Reply-To: References: Message-ID: Great! Thanks Kyle. ________________________________ Van: koha-devel-bounces at lists.koha-community.org namens Kyle Hall Verzonden: woensdag 31 mei 2017 04:13 Aan: Koha Devel; Koha Onderwerp: [Koha-devel] Koha 17.05.00 released! Hello all! It is my honor to announce the release of Koha 17.05.00! Thanks you to everyone who contributed time and effort making this the best version of Koha yet! The release notes can be found on the Koha Community website: https://koha-community.org/koha-17-05-released/ Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Meadville Public Library | what's happening @ your library www.meadvillelibrary.org Location, hours and circulation policy. Crawford County Federated Library System ( http://www.ccfls.org ) ccfls.org - the libraries of Crawford County, PA www.ccfls.org The Crawford County Federated Library System (CCFLS) is pleased to announces the installation of Koha Zoom Intergrated Library System (ILS) catalog and circulation ... -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Wed May 31 15:09:36 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Wed, 31 May 2017 13:09:36 +0000 Subject: [Koha-devel] Koha 17.05.00 released! In-Reply-To: References: Message-ID: That's awesome! Thanks! El mar., 30 may. 2017 a las 23:13, Kyle Hall () escribi?: > Hello all! > > It is my honor to announce the release of Koha 17.05.00! > > Thanks you to everyone who contributed time and effort making this the > best version of Koha yet! > > The release notes can be found on the Koha Community website: > https://koha-community.org/koha-17-05-released/ > > Kyle > > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Wed May 31 18:18:08 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 31 May 2017 16:18:08 +0000 Subject: [Koha-devel] What's on in koha-devel #13 Message-ID: Hello librarians and developers, I have a lot of things to tell you :) First, Koha 17.05 is out! I would like to congratulate Kyle and all the release team! It includes 7 new features and many enhancements and bug fixes. You can find the release notes on the website : https://koha-community.org/koha-17-05-released/ I would like to highlight a feature that I am talking about for months now, Hea version 2 = Hea v2 = The development is now in the last version of 3.22.x and has been backported to all supported releases. So if you are using 3.22, 16.05 or 16.11 you should upgrade to (at least) 3.22.21, 16.05.13 or 16.11.08 and share with us information about your libraries! See the global map to see all libraries https://hea.koha-community.org/libraries-on-a-map (just a few at the moment, we are waiting for you!) See an example of the detail of a Koha installation with several libraries: https://hea.koha-community.org/libraries/425 You can tune and choose the information to share with the community on a new administration page. You can find it under "Administration ? Usage statistics". I really hope to see a whole map full of libraries in the next weeks :) = 17.11 development has started = 17.05 is out, that means the next development cycle has just started. I have been elected to take the lead as Release Manager for this one. I announced in my RM proposal ( https://wiki.koha-community.org/wiki/Proposal_for_RM_17.11_joubu) that I wanted to integrate more people in the team. To this end, I needed to know 1) who is willing to dedicate time for the next 6 months, 2) what are the needs of everybody and 3) coordinate and assign tasks to ease and speed the integration of patches. As I am not a politician I will try and do what I said. You may have noticed that I already started, here are the different actions that have already been triggered: == Contact people == I have sent an email to 1) the support companies, 2) the contributors and 3) the general list ( https://lists.katipo.co.nz/pipermail/koha/2017-May/048066.html) to ask them/you filling a form ( https://framaforms.org/ready-to-help-the-koha-community-1493918217), to collect ideas/needs on what we could work on the next release and who is going to help. I have received 40 answers so far, for a total of 62 persons and 852h per months. 29 support companies, 6 libraries and 5 volunteers. That's a good start, but quite a lot of (active) support companies did not answer yet. If you are not an employee of a support company, you can still fill the form! == A new tool - kanban == To coordinate and assign tasks I suggest a new tool that is quite easy to use: a kanban. You can find it at https://tree.taiga.io/project/joubu-koha-rm-1711/kanban There is a wiki page to explain a bit how it works: https://tree.taiga.io/project/joubu-koha-rm-1711/wiki/home It will be a very important tool for the next release, so if you are involved directly or indirectly in the Koha community (translation, documentation, write or test patches, etc.) you should join us if it is not done yet. For instance we are currently reworking our entry points on the wiki to welcome new contributors, there is a task on the kanban subdivided in several tasks: https://tree.taiga.io/project/joubu-koha-rm-1711/us/21 == Welcoming new contributors, a priority == As I just said previously we are focussing on welcoming new contributors, if you are new and willing to help us it's certainly the best moment to do it. You should just wait a bit to let us rebuilt our wiki and give you the desire to help! If you always wanted to dive into the Koha code, we are writing a tutorial to help and guide you throughout the different steps of a patch: write a patch, attach it to the bug tracker, sign it off, etc. It is called koha-howto and you can find more information about it on the kanban. The official announcement should arrive soon. = Collaborative what's on = Heh yeah, I am sure some of you are sick of my English grammar and my obsession for the wiki syntax in my emails :) Since I guess other developers would like to share what they did over the previous month I have created a pad ( https://annuel2.framapad.org/p/What_s_on_in_koha-devel) where everybody can contribute to the next "what's on in koha-devel" email. Feel free to add stuffs to this page when you want to highlight something. = Push refactoring patches soon = I have a lot of refactoring patches that are in the queue for too long. I really would like to see a collective effort done on them. They will lead to cleaner and more flexible and maintainable code. We have seen lot of bug recently that would have been avoided with them. See the kanban and filter on the "Refactoring" Epic to see what must be done quickly. Do not forget the IRC meetings! If you want to tell us something or highlight a problem, start a discussion, it is the place to do it (do not forget to add the topic on the agenda!) The next general IRC meeting is on June 7th at 13 UTC. https://wiki.koha-community.org/wiki/General_IRC_meeting_7_June_2017 The next dev IRC meeting is on June 14 at 21 UTC https://wiki.koha-community.org/wiki/Development_IRC_meeting_14_June_2017 Cheers, Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at bywatersolutions.com Wed May 31 21:26:49 2017 From: info at bywatersolutions.com (Brendan Gallagher) Date: Wed, 31 May 2017 12:26:49 -0700 Subject: [Koha-devel] Koha 17.05.00 released! In-Reply-To: References: Message-ID: YAY! I love releases! Great job Kyle! On Wed, May 31, 2017 at 6:09 AM, Tomas Cohen Arazi wrote: > That's awesome! Thanks! > > El mar., 30 may. 2017 a las 23:13, Kyle Hall () > escribi?: > >> Hello all! >> >> It is my honor to announce the release of Koha 17.05.00! >> >> Thanks you to everyone who contributed time and effort making this the >> best version of Koha yet! >> >> The release notes can be found on the Koha Community website: >> https://koha-community.org/koha-17-05-released/ >> >> Kyle >> >> http://www.kylehall.info >> ByWater Solutions ( http://bywatersolutions.com ) >> Meadville Public Library ( http://www.meadvillelibrary.org ) >> Crawford County Federated Library System ( http://www.ccfls.org ) >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/ > > -- > Tom?s Cohen Arazi > Theke Solutions (https://theke.io ) > ? +54 9351 3513384 <+54%209%20351%20351-3384> > GPG: B2F3C15F > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting and Complete Support Packages Office: Portland, OR - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com info at bywatersolutions.com -------------- next part -------------- An HTML attachment was scrubbed... URL: