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

Bugzilla, and other sites
by Chris Cormack 19 May '16

19 May '16

Hi All Linode have discovered a hardware issue on the machine my linode is hosted on, they are working on a fix, but things will be up and down until then Chris

2 1

Call for News: May 2016 Newsletter
by kohanews 14 May '16

14 May '16

Fellow Koha users ~ 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

1 0

Reminder: Developer IRC Meeting - 11 May, 21 UTC
by Katrin Fischer 11 May '16

11 May '16

Hi all, just the usual reminder about the next Developer IRC Meeting on 11 May 2016, 21 UTC: https://wiki.koha-community.org/wiki/Development_IRC_meeting_11_May_2016 Please add any topics you want to discuss to the agenda, especially if it is about the upcoming release of 16.05. Hope to see you there, Katrin

1 0

kohadevbox: ansible => master move
by Tomas Cohen Arazi 09 May '16

09 May '16

Hi everyone, I filled an issue in the kohadevbox repo 12 days ago, requesting for feedback on merging the 'ansible' branch into 'master'. I got little feedback ,but we agreed (with Magnus) that in the scenario of no objections, we would merge it [1] It is now merged, and the original branch is kept in hte 'legacy' branch for those still using it. Sorry for any inconveniences this changes might cause. Remember kohadevbox accepts bug reports [2] and (of course!) pull requests or plain patches. I've been told there are issues running it in Jessie which I couldn't reproduce, please fill bugs if problems persist. [1] https://github.com/digibib/kohadevbox/issues/92 [2] https://github.com/digibib/kohadevbox/issues -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

Dev a app with android studio
by dave_meyer＠web.de 09 May '16

09 May '16

3 2

Why port 587 in git.koha-community.org is closed
by Hector Castro 06 May '16

06 May '16

Hi All Why the port 587 is closed. If you try to fetch with git the server timeout not response I ran nmap -sT -O git.koha-community.org Nmap scan report for git.koha-community.org (174.143.233.17) Host is up (0.090s latency). rDNS record for 174.143.233.17: 174-143-233-17.static.cloud-ips.com Not shown: 987 filtered ports PORT STATE SERVICE 21/tcp closed ftp 22/tcp open ssh 25/tcp open smtp 53/tcp closed domain 80/tcp open http 443/tcp closed https 465/tcp closed smtps *587/tcp closed submission* 6667/tcp closed irc 8080/tcp closed http-proxy 8081/tcp closed blackice-icecap 8082/tcp closed blackice-alerts 8083/tcp closed us-srv Regards -- Atte, Héctor Eduardo Castro Avalos

2 1

Time to think Plack?
by Tomas Cohen Arazi 06 May '16

06 May '16

Hi everyone, I just wanted to raise some questions, that might be worth thinking about at the KohaCon16 hackfest, or just here. Koha has been a CGI app for ages. And we slowly made it work under Plack to gain performance. We did so, by running it inside a CGI emulation context (i.e. CGI::Emulate::PSGI [1]). We even wired all stuff so packages can take advantage of Plack out of the box (just not enabled by default, that'd be a next future step). We then introduced a Mojolicious implementation of (a beggining of) a REST API. Is it time to start thinking of Koha as a Plack app and focus on that? [1] Through Plack::App::CGIBin actually. -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

4 4

Fuzzy searching in ICU
by David Cook 06 May '16

06 May '16

Hi all, I thought I was going crazy(er) last night when search wasn't working for me in my Koha dev install... I kept seeing this message in yaz-client: [120] Unsupported Truncation attribute -- v2 addinfo '103' I started going through my configuration files with a fine-tooth comb, when suddenly I realized that I was using the ICU tokenizer rather than the CHR tokenizer. Sure enough, when I changed that over and re-built Koha, it was working again. I'm sure everyone who uses ICU knows that you can't use QueryFuzzy searching, but this was a painful reminder. Perhaps we should add a warning to the text for QueryFuzzy in the system preferences, or maybe tie use of QueryFuzzy to the "UseICU" system preference, although I don't know if anyone actually uses that preference. I don't know if mine was turned on or off. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595

3 5

Re: [Koha-devel] Invalid local time for date in time zone: America/Santiago
by David Cook 05 May '16

05 May '16

Hey Barton, Yes, the year 2038 for timestamps is a problem even on 64 bit machines. Here’s a test you can do on a 64 bit MySQL install on a 64 bit OS: select unix_timestamp('2038-01-20'); select from_unixtime(2548990800); Both will return null. You can also try storing a value of ‘2039-01-01’ into a timestamp column, and you’ll get the following message : Out of range value for column 'timestamp' at row 1 Here’s some good explanations: <http://askubuntu.com/questions/675116/timestamp-year-2038-problem-for-64-bi…> http://askubuntu.com/questions/675116/timestamp-year-2038-problem-for-64-bi… <https://bugs.mysql.com/bug.php?id=12654> https://bugs.mysql.com/bug.php?id=12654 Also, I’d never heard of date_t before your email, and the only references I can see to it are for specific projects which have implemented it as a new data structure themselves. I think time_t is the standard and that depends on your system architecture, although as you can see in those above links – it’s more complicated than that in MySQL. -- issues.date_due is already a DATETIME data type, so we don’t need to worry about 2038. As for time zones, why would it be tricky storing it in UTC? At the moment, you can only have due dates in one time zone. That means you can’t have library systems spanning more than one timezone. Maybe that’s a rare or uncommon scenario, but here in the state of New South Wales, we actually do have 2 different timezones. In that case, when you’re doing a check out, you choose a local time, convert it to UTC for storage, and then render it in local time for the library user and library staff. I imagine the trickiest part would be the Reports module, as users wouldn’t know to use something like the CONVERT_TZ() function. Calculating overdues against holidays might be tricky… although that’s a case of just getting your timezone right as well. I reckon your timezone should be set per library, so you just fetch your UTC datetime, convert it to your local library timezone, probably convert it to floating to do math, and then convert it back to local timezone, and then whatever else you need. It sounds complex, but it’s really not that bad when you have it structured well. -- Barton, I’m not sure I understand your reaction :p. I also field support tickets for a living, and I think it would be a lot easier to field tickets for a re-architected system that is created off years of experience rather than years of technical debt. Of course, I know re-architecting a system is also a lot easier said than done. But I think that’s why you see folks like EBSCO thinking about creating a microservice based system which can integrate with Koha. Incremental change. I suppose dates are most important when it comes to circulation and patrons… and I think that’s what people probably think about when they think of core Koha. I suppose acquisitions and serials require a lot of careful date handling as well… I was actually thinking about Koha and “asset tracking” in general this morning on the way to the office. I don’t know. Maybe Koha is fine just being a 1 timezone system. I imagine library systems spanning over multiple timezones are probably the exception rather than the rule. We need to re-think some of our DateTime logic though. Whether we use ‘floating’ timezones more consistently, or are careful with creating local times that don’t exist… David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595 From: Barton Chittenden [mailto:barton@bywatersolutions.com] Sent: Thursday, 5 May 2016 12:04 AM To: David Cook <dcook(a)prosentient.com.au> Subject: Re: [Koha-devel] Invalid local time for date in time zone: America/Santiago On Thu, Apr 28, 2016 at 7:27 PM, David Cook <dcook(a)prosentient.com.au <mailto:dcook@prosentient.com.au> > wrote: I don’t think using “timestamp” would be preferable to “datetime”. First, MySQL’s timestamp seems to suffer from the Year 2038 problem ( <https://en.wikipedia.org/wiki/Year_2038_problem> https://en.wikipedia.org/wiki/Year_2038_problem)(http://bugs.mysql.com/bug.…) while datetime does not. Even on 64 bit machines? Oh MySQL, MySQL, knowest thou not of date_t? Second, you’d be handling timezones at the data level rather than at the application level. I’d rather have a convention of storing DATETIME as UTC, having Koha fetch that DATETIME as UTC, and then doing timezone conversions from there. I think that could be handled *relatively* transparently in DateUtils.pm, but there are a lot of corner cases like due dates that get ... tricky. As for the same server running different time zones, you can change the timezone on a per connection setting I think, but that could be a hassle. I think it would be easier just to store things clearly as UTC. This is done on a different project I work on, and it works well. Oh, I think it’ll be a nightmare changing timezone/timestamp/datetime handling in Koha. I don’t even know if it’s possible, to be honest. Well, it would be possible, but it would likely be an error-prone process. It’s things like this which make me think that we need to start thinking about a version of Koha that doesn’t have a clear upgrade path. A Koha with some major architectural changes which will need a skilled hand to migrate to. It won’t be nice for a lot of people… but I don’t know how else we’re going to make some major changes without dramas. >From a design standpoint, I agree. >From the point of view of someone who fields support tickets for a living: NOOOOOOOOOOOOOOOOOOOOO!!!! ... but that's just an emotional response. Cheers, --Barton

3 4

Re: [Koha-devel] Searching with the question mark wildcard (Part two)
by David Cook 05 May '16

05 May '16

My last email may have been a bit over the top, although I still stand by the fact that Search.pm butchers queries before they get to Zebra. Hopefully, the integration of ElasticSearch will make a re-write of the Zebra-related code to be unnecessary. While we’re still planning to hold on to Zebra, I think it’s mostly as a Z39.50/SRU server? I actually quite like Zebra as a search engine, but the way the search code in Koha was implemented makes it impossible to use Zebra as it should be used. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-bounces(a)lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] On Behalf Of Francois Charbonnier Sent: Wednesday, 4 May 2016 11:00 PM To: koha-devel(a)lists.koha-community.org >> koha-devel <koha-devel(a)lists.koha-community.org> Subject: [Koha-devel] Searching with the question mark wildcard Hello, Has anyone tried to implement the question mark (?) wildcard ? The documentation says "Two of the wildcard characters that can be used in Koha searches are the asterisk ('*') and the percent sign ('%'). However, these two characters act differently when used in searching." (http://manual.koha-community.org/3.22/en/searchfaq.html) But, CQL also supports the question mark wildcard "? : Matches any single character, so that c?t will match any of the words cat, cot or cut, but not coat or indeed ct." (http://zing.z3950.org/cql/intro.html#6) We are currently evaluating this implementation. If you already tried, your feebacks will be appreciated. And, any advice on how you'll do it will be welcome as well! Thanks! -- François Charbonnier, Bibl. prof. / Chef de produits Tél. : (888) 604-2627 <mailto:francois.charbonnier@inLibro.com> francois.charbonnier(a)inLibro.com inLibro | pour esprit libre | <http://www.inLibro.com> www.inLibro.com

1 0