- Koha - lists.katipo.co.nz

Koha 16.11.01 released
by Katrin 10 Jan '17

10 Jan '17

The Koha community is proud to announce the release of Koha 16.11.01 This is the first maintenance release of 16.11 and contains several bugfixes. The full release notes are available at https://koha-community.org/koha-16-11-01-released Packages will be available soon. Happy holidays!

1 1

What's on in koha-devel #9
by Jonathan Druart 09 Jan '17

09 Jan '17

Hello librarians and developers, I wish you a happy new year, 2017 will be awesome, I am sure :) At least it will be a great year for your favourite ILS - Koha is constantly improving and next releases will be even better than the last ones, as always :) = Hea = Some of us are still a bit hesitant about Hea because of the lack of communication around this project. It also seems that we would like to improve this tool and the way it displays data, to make it more attractive. To answer the first need, Chris wrote a privacy policy file [2]. You can send us feedback about it if things are not clear enough. To improve data collected by Hea, I have opened 3 bug reports (actually 1 was already opened): Bug 14608 will add an administration page for Hea, to make it more visible and understandable Bug 17802 will collect ideas (and patches?) about adding geolocation of Koha's installations Bug 17803 introduce the idea of collecting the number of libraries per installation. It will permit to know how many libraries are actually using Koha (vs the number of installations). If you are interested in these topics, get involved on the mailing list or the corresponding bug reports. = Benchmarks for 16.11 = I have compared Koha versions from 3.14.x to 16.11. The results have been posted on the wiki [3]. Everybody can replay these benchmarks easily, and some of you must do it to confirm (or not) these numbers. One important thing is that I noticed that the template caching system is not defined by default - however it brings a significant performance boost. I have opened a bug report (Bug 7533 - Add template_cache_dir to the koha-conf.xml file) to add the entry to the koha-conf file. This patch will also add a warning to the about page if the entry is not defined. If you are running a Koha install hosted by a (good) service provider, it should be correctly defined. But if you are self-hosted, you must definitely take a look at this configuration option. To play these benchmarks I needed to rebuild a database for each of these different versions of Koha. This job leads me to modify the scripts from the koha-misc4dev [4] repository. With these scripts I am now able to get a Koha installation fully testable (items, reindexation, psgi file, etc.) with any of these versions in a few minutes. That should be very useful for developers, especially to benchmark, bisect, archaeological digs or simply debug. = Important bugs waiting for love = Last month I have sent an email to koha-devel to list several important bugs waiting to be tested or QAed. It was very helpful as (almost) all of them got the expected love and have been boosted quickly. Note that we always have these kinds of important bugs, and I will try to think about a way to keep a list of them. A simple and naive approach would be to list the major, critical and blocker ones on the dashboard. Any thoughts? The one we want to see in quickly for now is Bug 17817 - Repeat this Tag (cloning) not working It is waiting for QA. Furthermore if you are confident with SIP you should take a look at the different SIP patches in the needs signoff (17758 Major, 17665, 17826, 16755, 15418, 13666) and signed off queues (16757, 16895 and 16899). = Refactoring = == Remove the biblioitems.marcxml field == This is the last call! Bug 17196 has now 4 independent signoffs, we need (at least) 1 QA guy to have a look at it. If it is not pushed quickly, I will block its integration into the next release. We do not want it to be pushed close to the release date. == Koha::Patrons == I have started to replace the C4::Member::GetMember subroutine with Koha::Patrons. You can take a look at bug 17829 to see the progress (check the remote branch on github). It's a massive change as it impacts a lot of file and it depends on lot of other patches not pushed yet to master. Using Koha::Patron will allow us to improve the REST API routes for the patron module. Moreover it will permit to manipulate patron objects and so to call the new methods recently added to our Koha::Patron module. That will make the code more readable than at the moment: only 1 patron structure will be manipulated and not 1 Koha::Patron object + the hashref returned by GetMember. Doing so the patron object will be sent to the templates and that will clean up a lot of scripts from the "members" module. = Standardize our EXPORT = Last month I talked about bug 17600. It did not get lot of attention. If nobody gets involved in the discussion I will put it aside. = Template Toolkit syntax for notices = Since Kyle's topic on the koha mailing list [1] did not receive any objections I will try and coordinate with him to move forward on this subject. The next general IRC meeting is on February 1st, 14 UTC. https://wiki.koha-community.org/wiki/General_IRC_meeting_1_February_2017 The next dev IRC meeting is on January 11th, 20 UTC. https://wiki.koha-community.org/wiki/Development_IRC_meeting_11_January_2017 In 2 days! Hope to see your there! Cheers, Jonathan [1] Template Toolkit syntax for notices - https://lists.katipo.co.nz/pipermail/koha/2016-December/046773.html [2] Hea Privacy policy - http://git.koha-community.org/gitweb/?p=hea.git;a=blob;f=Privacy_Policy.md;… [3] Benchmark for 16.11 - https://wiki.koha-community.org/wiki/Benchmark_for_16.11 [4] koha-misc4dev - http://lists.koha-community.org/pipermail/koha-devel/2016-November/043277.h…

2 1

Need help regarding data migration
by Tanzeem M.B 06 Jan '17

06 Jan '17

I am migrating to koha.I got a spreadsheet with the present data. I have found the marc21 tag info details for each column. eg. Accession Number 541##$e. I am using MarcEdit 's Delimited Text Translator. When I tried to map data and click Add argument, MarcEdit gives the following "Mapping Error." " Field / Subfield combinations must be defined at 245$a It appears that your intention is to create such a pair. If that's the case please click OK and update the mapping. If your data is not a field/subfield pair, click cancel to ignore this, as well as future messages. " But when I click ok, I get the same message, And when I click cancel cancel the data is added to the Arguments text area like : 0 541 ##$e 0 Please help me to proceed further. with thanks and regards Tanzeem

3 2

Re: [Koha] Koha Digest, Vol 135, Issue 9
by Gopalakrishna-BMSIT 06 Jan '17

06 Jan '17

Your mapping of barcode (accession) is incorrect. Map this to 952$p and try. *With Regards,* *Gopalakrishna* *Librarian, B.M.S Institute of Technology,Avalahalli, Doddaballapur Main Road,Yelahanka, Bangalore-64Ph: 080-65369469Mob.: 97418 98674* On Fri, Jan 6, 2017 at 4:30 AM, <koha-request(a)lists.katipo.co.nz> wrote: > [image: Boxbe] <https://www.boxbe.com/overview> This message is eligible > for Automatic Cleanup! (koha-request(a)lists.katipo.co.nz) Add cleanup rule > <https://www.boxbe.com/popup?url=https%3A%2F%2Fwww.boxbe.com%2Fcleanup%3Fkey…> > | More info > <http://blog.boxbe.com/general/boxbe-automatic-cleanup?tc_serial=28306993408…> > > Send Koha mailing list submissions to > koha(a)lists.katipo.co.nz > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.katipo.co.nz/mailman/listinfo/koha > or, via email, send a message with subject or body 'help' to > koha-request(a)lists.katipo.co.nz > > You can reach the person managing the list at > koha-owner(a)lists.katipo.co.nz > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Koha digest..." > > > Today's Topics: > > 1. Need help regarding data migration (Tanzeem M.B) > 2. Re: Need help regarding data migration (Joy Nelson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 5 Jan 2017 14:08:03 +0530 > From: "Tanzeem M.B" <tanzeem.mb(a)gmail.com> > To: koha(a)lists.katipo.co.nz > Subject: [Koha] Need help regarding data migration > Message-ID: > <CAFdG+--_hvLfj_ymUXvNRQaEC21ccGtbGrYAUo4dH6zP > Om0XYQ(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > I am migrating to koha.I got a spreadsheet with the present data. > I have found the marc21 tag info details for each column. > eg. Accession Number 541##$e. > I am using MarcEdit 's Delimited Text Translator. > When I tried to map data and click Add argument, MarcEdit gives the > following "Mapping Error." > " Field / Subfield combinations must be defined at 245$a > It appears that your intention is to create such a pair. > If that's the case please click OK and update the mapping. If your data > is not > a field/subfield pair, click cancel to ignore this, as well as future > messages. > " > But when I click ok, I get the same message, > And when I click cancel cancel the data is added to the Arguments text area > like : > 0 541 ##$e 0 > Please help me to proceed further. > > with thanks and regards > Tanzeem > > > ------------------------------ > > Message: 2 > Date: Thu, 5 Jan 2017 10:54:10 -0600 > From: Joy Nelson <joy(a)bywatersolutions.com> > To: "Tanzeem M.B" <tanzeem.mb(a)gmail.com> > Cc: Koha <koha(a)lists.katipo.co.nz> > Subject: Re: [Koha] Need help regarding data migration > Message-ID: > <CAFpshE_kFUObjrJk3O+c7arT+M0Ew5egS279X=reMO2E-cBcjw@ > mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hello, > There is a MarcEdit listserv I would recommend you contact. ( > https://listserv.gmu.edu/cgi-bin/wa?A0=marcedit-l) > > They are more experts in the use of MarcEdit than we are. > > Thanks! > joy > > On Thu, Jan 5, 2017 at 2:38 AM, Tanzeem M.B <tanzeem.mb(a)gmail.com> wrote: > > > I am migrating to koha.I got a spreadsheet with the present data. > > I have found the marc21 tag info details for each column. > > eg. Accession Number 541##$e. > > I am using MarcEdit 's Delimited Text Translator. > > When I tried to map data and click Add argument, MarcEdit gives the > > following "Mapping Error." > > " Field / Subfield combinations must be defined at 245$a > > It appears that your intention is to create such a pair. > > If that's the case please click OK and update the mapping. If your data > > is not > > a field/subfield pair, click cancel to ignore this, as well as future > > messages. > > " > > But when I click ok, I get the same message, > > And when I click cancel cancel the data is added to the Arguments text > area > > like : > > 0 541 ##$e 0 > > Please help me to proceed further. > > > > with thanks and regards > > Tanzeem > > _______________________________________________ > > Koha mailing list http://koha-community.org > > Koha(a)lists.katipo.co.nz > > https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > > -- > Joy Nelson > Director of Migrations > > ByWater Solutions <http://bywatersolutions.com> > Support and Consulting for Open Source Software > Office: Fort Worth, TX > Phone/Fax (888)900-8944 > What is Koha? <http://bywatersolutions.com/what-is-koha/> > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > > > ------------------------------ > > End of Koha Digest, Vol 135, Issue 9 > ************************************ > >

1 0

COPPA and self registration
by Chad Roseburg 06 Jan '17

06 Jan '17

We are planning to use the self-registration feature. How do you deal with patrons under 13 and COPPA? Thanks! -- Chad Roseburg Asst. Director / IT Automation Dept. North Central Regional Library

4 4

Re: [Koha] Template Toolkit Syntax for Slips & Notices
by Katrin 04 Jan '17

04 Jan '17

Hi Radek, sorry, missed to send my question to the list earlier today. I am not sure if <<count>> ever worked for those, we have only used it for DUEDGST and PREDUEDGST so far. Could you file a bug? I think the count needs to be updated every time a checkout/return is recorded. Katrin On 04.01.2017 13:25, Radek Šiman wrote: > Hi Katrin, > > we tried it in CHECKIN/CHECKOUT/RENEWAL as I remember (a month or two > ago). > > Radek > > Dne 04.01.17 v 12:44 Katrin Fischer napsal(a): >> Hi Radek, >> do you mean the due/predue digests or the checkout and checkin notices? >> Katrin >> *Gesendet:* Mittwoch, 04. Januar 2017 um 11:53 Uhr >> *Von:* "Radek Šiman" <radek.siman(a)centrum.cz> >> *An:* koha(a)lists.katipo.co.nz >> *Betreff:* Re: [Koha] Template Toolkit Syntax for Slips & Notices >> Hi, >> >> we also really appreciate the TT option to have in notices. We tried it >> and faced a problem especially with those digest letters. If you use >> digests only, most of the letter is prepared for the first round and >> then its updated with iterated data items as they come. This means that >> placeholders like <<count>> are not updated anymore so we can see >> letters saying eg. "you returned 3 items", but in the fact there is much >> more of them listed in: >> ---- >> <<biblio.title>> >> ---- >> Maybe it's a bug and not a TT issue...? >> >> Regards >> Radek >> >> Dne 04.01.17 v 8:24 Katrin napsal(a): >> > +1 to what Bob said. I think we need the old syntax to be fully >> > working at least for a longer transition time. >> > >> > I can see that TT will allow us to have even nicer notices than we >> > have now, so looking forward to having the option. >> > >> > I think documentation will be really important in order to have >> > libraries use the feature. We have some special constructs with the >> > current syntax now. It would be nice to have mapping on how to achieve >> > the same output or similar with the new TT syntax. I am thinking of >> > things like: >> > >> > <<date_due|dateonly>> >> > <<today>> >> > <item><<items.fine>></item> >> > <<items.content>> >> > ... >> > >> > Katrin >> > >> > On 03.01.2017 12:40, Bob Birchall wrote: >> >> Its good to see the commitment to keeping the existing syntax as an >> >> alternative to the new syntax - thank you!. There are a massive >> >> number of existing notice templates in Koha libraries and libraries >> >> could face a significant cost to switch to the new syntax. So as >> >> long as the path involves introducing the new but retaining the old >> >> as an alternative, we're in favour. >> >> Thanks for the initiative. >> >> Bob Birchall >> >> Calyx >> >> >> >> On 02/01/17 22:01, Jonathan Druart wrote: >> >>> Silence will be considered as an agreement. >> >>> If you have any questions, please do not hesitate to ask. >> >>> >> >>> Regards, >> >>> Jonathan >> >>> >> >>> On Tue, 6 Dec 2016 at 16:03 Kyle Hall <kyle.m.hall(a)gmail.com> wrote: >> >>> >> >>>> Hey All! >> >>>> >> >>>> As you may know, Koha 16.11 supports the use of Template Toolkit >> >>>> markup in >> >>>> Koha's slips and notices. This provides huge benefits over our >> current >> >>>> bespoke syntax, such as >> >>>> A) Consistency, we have odd tags like <<itemscontent>> >> >>>> B) Flow control, for example, we can hide labels for fields that >> >>>> are empty >> >>>> C) Flexible, for example, maybe you want to mask part of a patrons >> >>>> name on >> >>>> a print slip, with TT it's easy! >> >>>> >> >>>> Jonathan and I would really like to get moving on making Template >> >>>> Toolkit >> >>>> the defacto way to deal with slips and notices in Koha. This is >> not a >> >>>> trivial undertaking, and we'd like to get it done in time for the >> >>>> 17.05 >> >>>> release. >> >>>> >> >>>> To do this we will: >> >>>> A) Port all slips and notices to TT syntax >> >>>> B) Enable TT syntax in the slips and notices editor >> >>>> C) Document the new TT syntax of slips and notices >> >>>> >> >>>> These tasks will be accomplished on bugs 15278, 15277, and 15276 >> >>>> respectively. >> >>>> >> >>>> I would like to stress that the existing Slips and Notices >> syntax will >> >>>> continue to work in 17.05, and you will *not* need to update your >> >>>> existing >> >>>> templates during the 17.05 upgrade process. >> >>>> >> >>>> We are looking for community input on this project before we >> >>>> proceed. Let >> >>>> us know what you think! >> >>>> >> >>>> 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 mailing list http://koha-community.org >> >>>> Koha(a)lists.katipo.co.nz >> >>>> https://lists.katipo.co.nz/mailman/listinfo/koha >> >>>> >> >>> _______________________________________________ >> >>> Koha mailing list http://koha-community.org >> >>> Koha(a)lists.katipo.co.nz >> >>> https://lists.katipo.co.nz/mailman/listinfo/koha >> >> >> >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> >> Koha(a)lists.katipo.co.nz >> >> https://lists.katipo.co.nz/mailman/listinfo/koha >> > >> > _______________________________________________ >> > Koha mailing list http://koha-community.org >> > Koha(a)lists.katipo.co.nz >> > https://lists.katipo.co.nz/mailman/listinfo/koha >> >> >> _______________________________________________ >> Koha mailing list http://koha-community.org >> Koha(a)lists.katipo.co.nz >> https://lists.katipo.co.nz/mailman/listinfo/koha > >

1 0

Koha Meeting Reminder
by Nick Clemens 04 Jan '17

04 Jan '17

Hi All, Just a reminder that the next Koha General Meeting is today! The meeting is scheduled for 20 UTC - you can convert to local times here: http://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+IRC+General+M… The agenda is on the wiki, please add any topics you wish to discuss: https://wiki.koha-community.org/wiki/General_IRC_meeting_4_January_2016 See you all soon! -Nick

2 2

Announcement for next week's meeting
by Christopher Davis 04 Jan '17

04 Jan '17

Dear Colleagues, I would like to announce next Wednesday's Koha-US monthly meeting scheduled for January 11th, 2017 at 10:30 am Central Time. The location of the meeting will be <https://kslib.zoom.us/j/450230564>. For details of this meeting (including an agenda), please visit <http://koha-us.net/index.php/Minutes2017-01-11>. We would love to include your thoughts as well, so If you would like to add an item to the agenda of this meeting, then I invite you to email me with your ideas. Regards, Christopher Davis Secretary, Koha-US cgdavis(a)uintah.utah.gov

1 0

Template Toolkit Syntax for Slips & Notices
by Kyle Hall 04 Jan '17

04 Jan '17

Hey All! As you may know, Koha 16.11 supports the use of Template Toolkit markup in Koha's slips and notices. This provides huge benefits over our current bespoke syntax, such as A) Consistency, we have odd tags like <<itemscontent>> B) Flow control, for example, we can hide labels for fields that are empty C) Flexible, for example, maybe you want to mask part of a patrons name on a print slip, with TT it's easy! Jonathan and I would really like to get moving on making Template Toolkit the defacto way to deal with slips and notices in Koha. This is not a trivial undertaking, and we'd like to get it done in time for the 17.05 release. To do this we will: A) Port all slips and notices to TT syntax B) Enable TT syntax in the slips and notices editor C) Document the new TT syntax of slips and notices These tasks will be accomplished on bugs 15278, 15277, and 15276 respectively. I would like to stress that the existing Slips and Notices syntax will continue to work in 17.05, and you will *not* need to update your existing templates during the 17.05 upgrade process. We are looking for community input on this project before we proceed. Let us know what you think! 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 )

5 4

does anyone has a Koha 2.2.x era DB schema around?
by Indranil Das Gupta 04 Jan '17

04 Jan '17

Hi List echo $SUBJECT. tia -- 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