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

exact purpose of items.paidfor column
by Indranil Das Gupta 19 Feb '17

19 Feb '17

Hi all, What is the exact purpose of the items.paidfor MEDIUMTEXT field? I do see a bug filed - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12817 regards, Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 WWW : http://www.l2c2.co.in Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg

2 1

marc_tag_structure: Some clean up is needed?
by Mark Tompsett 18 Feb '17

18 Feb '17

Greetings, I was looking to sign off bug 18111, which looks good by the way, and then I noticed that ods and xml exports were floody. So, I was pondering how to fix them, because the code is reminiscent of MARC indicators and not authorised_value or framework code. So, I put in a condition to catch things and make it not floody, but then my exports were strange. Some had ‘#’ and some had ‘’ in the authorised_values. This, of course, didn’t match the CSV patch in bug 17389. And regardless of format, I would expect the same values in the columns. So I thought, “Why are some #’s and some blank?” Turns out marc_tag_structure has both NULL and empty strings in the authorised_value field. I thought to myself, “Where did this get set?” I had recently dropped and recreated my database, so it had to be an installer file. Well, it turns out that installer/data/mysql/en/marcflavour/marc21/mandatory/marc21_framework_DEFAULT.sql has some NULL and some empty strings. So, first question: is that right? So, then I thought, “Okay, so where is this # being processed?” I found it around line 1128 in C4/ImportExportFramework.pm which reads: $data = '' if ($data eq '#'); So, second question: shouldn’t an empty string have been put out in the first place? To which I thought, “Bah! It works. It’s ugly and gross and should be refactored somehow, but I don’t know which way, so I’ll just leave it.” So, last question: if you were going to refactor, what would your plan of attack be? This includes choosing not to refactor as an option. GPML, Mark Tompsett

1 0

Re: [Koha-devel] Hackfest in Marseille, book your flight ! (Brendan Gallagher)
by BOUIS Sonia 17 Feb '17

17 Feb '17

Hello Brendan, I'm happy to see you all next month :) The french association KohaLa is going to organise a workshop to work on updating marc framework with the last IFLA recommandation. I'm sure that there will be cataloging and authority specialists that will be enthousiat to see what's is going on with RDF and linked data. Cheers, Sonia Message: 3 Date: Thu, 16 Feb 2017 17:46:32 -0800 From: Brendan Gallagher <info(a)bywatersolutions.com> To: Paul Poulain <paul.poulain(a)biblibre.com> Cc: "koha-devel(a)lists.koha-community.org" <koha-devel(a)lists.koha-community.org> Subject: Re: [Koha-devel] Hackfest in Marseille, book your flight ! Message-ID: <CANGWTFQv=Kxn-XKAa40K-MXe7WWsuHKZGr6QK5dnBunhstkemg(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Excellent! We have five people attending from ByWater (Me, Joy, Nick, JesseM and Michael). We are hoping to dedicate a full day to RDF (linked data) work - maybe more! I am hoping to see as many of you as we can there. We always look forward to this hackfest - such a great experience if you can afford to attend. Cheers, Brendan On Tue, Feb 14, 2017 at 9:25 AM, Paul Poulain <paul.poulain(a)biblibre.com> wrote: > Hi, > > A reminder : the Hackfest in Marseille will take place next month, march > 20 - 24. > > Book your flights & drop me an email (I'm hoping to officially open > registrations this week) > > See you next month ! > > -- > 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(a)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(a)bywatersolutions.com

1 0

schema.koha-community.org regenerate?
by Mark Tompsett 16 Feb '17

16 Feb '17

Greetings, There is a new table biblio_metadata and marcxml is gone from biblioitems. This is what caught my attention, and why I am asking if someone could regenerate the online schema. Any assistance is appreciated. [Smile] GPML, Mark Tompsett

1 0

Sending email on behalf of customers
by Magnus Enger 16 Feb '17

16 Feb '17

Hi! I run Koha for several customers, and a number of them have email enabled. The sender of these emails is set to be the email of the library in question, e.g. library(a)example.org. Now, the problem is that services like GMail and Hotmail are not accepting these emails, because they see them as non-legitimate, in the sense that they are sent from some random server somewhere on the internet, that is not in any way associated with example.org. And they are right, of course! I *am* sending email on behalf of libraries from some random server on the internet. So, the question is: how to get around this? I see two possibilities: 1. Work with the sysadmins of the organizations of each library and have them include my servers in their "published lists of trusted servers" (I am thinking of stuff like SPF, PTR, OpenDKIM etc - I have not gotten my head around all of the details.) This would entail talking to lots of different sysadmins (if there is one) at lots of different organizations = lots of work... 2. So I was thinking about a second optoin - paying my way out, through some service like the ones listed here: https://zapier.com/learn/email-marketing/best-transactional-email-sending-s… My thinking is that GMail and Hotmail would "think" like "hm, this email says it comes from example.org, but it originated from some random server. BUT it was sent through ServiceX, which you have to pay to use, so it is probably legit". But I have no idea if GMail and Hotmail works like that at all. Does anyone else have a clue about this? Or some other way to solve the problem? Best regards, Magnus Enger Libriotech

6 9

Edit button in circulation rule
by Baptiste Wojtkowski 15 Feb '17

15 Feb '17

Hello all, Is that normal that, by editing a circulation rule : 1) You can change the patron category and the Item type 2) If you do it, this will create a new rule instead of editing the old one. Kind regards Baptiste Wojtkowski

2 1

Call for news: February 2017 Newsletter
by kohanews 14 Feb '17

14 Feb '17

I'm collecting news for the February 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

What's on in koha-devel #10
by Jonathan Druart 08 Feb '17

08 Feb '17

Hello librarians and developers, Several interesting initiatives emerged in this beginning of year 2017. Lot of things need to ready for the next stable release in March. If you have some spare time, do not hesitate to get involve and make things you love moving forward :) = Catalyst academy = Let's start with the yearly Catalyst academy week. The Open Source Academy is a Catalyst initiative designed to provide training & work experience in open source development for young New Zealand technologists. We got signoffs and patches from 6 students (Zoe, Luke, Grace, Karen, Caitlin and Emma) and they all got at least 1 patch pushed into master this week [1]. Congrats to all of them! Looking forward the next one :) = Move marcxml out of the biblioitems table (bug 17196) = Well, that's it, it's in and will be in 17.05! I'd like to specially thanks Mason, Josef, Zeno, Nick and Marcel to have been involved in the testing and QA process of this important change. It will offer us more flexibility in the future for new developments as well as bring us performance boost in few areas. Since that change will break lot of reports, I have worked on a way to automatically detect the problematic reports and automagically convert it using the new columns. I think we really need it for the next major release, take a look at bug 17898 (Add a way to automatically convert SQL reports). = Dashboard = I have submitted a pull request which has been quickly merged (thanks Chris!). The dashboard (http://dashboard.koha-community.org) now displays a "Overall bug tracker health status" with the number of blocker, critical and major bug reports opened over the last 60 days. If you want to quickly know which are the hot patches waiting for you, just click on the link and you will get the bug list. =Bootstrap 3= The bootstrap library used for the staff interface has been upgraded to the version 3.3.7. Lot of work has been done by Josef and Owen to make the staff interface looking awesome. Elements like buttons, links, icons, modal windows have been homogenised. Some work are still in progress but the big step has been done. You can take a look at the depend patches of bug 17873 (Make all buttons Bootstrap styled) if you want easy signoffs. = Hea - Share your statistics with the community = Few days ago I have submitted patches for a proposition of what could be Hea version 2. If you want more informations, take a look at bug 18066 and especially the comment 2 about screenshots. Developers are very welcome to test, and librarians to give their opinion on what could be missing to make Hea better. I would also like to get help from a native English speaker to add more informations on the administration page to explain better what happens (and what will not happen!) when an option or another is set. = Refactoring = Lot of refactoring bug reports are waiting for testers and QAers. Everything has been stuck for the last month. I really would like to see more attention on these bugs, to continue the work in progress. To know how you can help, take a look at this graph: https://bugs.koha-community.org/bugzilla3/showdependencygraph.cgi?id=15449 Zoom out, zoom out, once again. If you are a signoffer, pick the orange boxes, if you are a QAer, look at the yellow ones. = Template Toolkit syntax for notices = This is certainly one of the most important area if you want to help us getting this in for the next release. These are quite lot of things to do to get something ready. First we want to make sure we will not get regression using the TT syntax. To prove that, I have opened an omnibus (see bug 17961 and related bugs - TT syntax for notices - Prove we have an equivalent for our historical custom syntax). A huge amount of tests are provided to prepare the ground and safe our backs for later. It is, in my opinion, the important part of the work. All of these patches are easy to test. To ease the migration for libraries, I have developed an interface to automagically convert the notices from the historical syntax to the TT syntax. You can take a look at bug 17981 and bug 18007 for this interface change. To test *all* of this stack change, you just need to checkout the remote branch from my github repository [2] Screenshot of the convert interface: https://pageshot.net/pVRqSxln4A9cqjtM/pro.kohadev.vm = Authority merge bugs = Marcel is reworking the authority merge feature. It is quite buggy and the code is hard to maintain currently. You can take a look at bug 17908 (Authority merge omnibus) and all related bug reports to help and/or follow the progress. The next general IRC meeting is on March 1st, 20 UTC. https://wiki.koha-community.org/wiki/General_IRC_meeting_1_March_2017 The next dev IRC meeting is today (!) at 20 UTC https://wiki.koha-community.org/wiki/Development_IRC_meeting_8_February_2017 Hope to see your there! Cheers, Jonathan [1] https://wiki.koha-community.org/wiki/Catalyst_Academy [2] https://github.com/joubu/Koha/tree/bug_17981

1 1

Koha development meeting reminder
by Nick Clemens 07 Feb '17

07 Feb '17

Hi All, The next Koha development meeting is on IRC tomorrow 08 February 2017 at 20:00 UTC You can see what that is in your local time here: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+I… Agenda is here: https://wiki.koha-community.org/wiki/Development_IRC_meeting_8_February_2017 Please make sure to add any topics you wish to discuss. See you all soon!

1 0

Github
by David Cook 06 Feb '17

06 Feb '17

Looking at Moodle's Github, I notice a line that says "mirrored from git://git.moodle.org/moodle.git" (https://github.com/moodle/moodle) I know https://github.com/Koha-Community/Koha is supposed to be a mirror of "git://git.koha-community.org/koha.git", so I was thinking that might be nice. although it seems like adding/updating that "mirrored from" is easier said than done: https://issues.apache.org/jira/browse/INFRA-9978. But I've been looking around and it seems that you might be able to turn off pull requests? Is that something folk would want to do? I've noticed other Githubs add their own little subtitle saying that it's just a mirror of another Git. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

1 0