- Koha - lists.katipo.co.nz

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

Unable to use zebra facets on OPAC in 16.11
by MAKAUTCL WB 03 Jan '17

03 Jan '17

Hi List, I'm facing a problem, I can't seem to get the facets showing in the search results. The only option I can do now is turn off zebra facets by setting <use_zebra_facets>0</use_zebra_facets>, in which case I get the facets from Koha. However, then I can't get any result in case I try to limit by availability. My system setup is as below: Debian 8.6 Koha 16.11 - deb package installation IndexData Zebra Package: libidzebra-2.0-0 Source: idzebra Version: 2.0.59-1 I read up https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11232 but that shows it as FIXED. So how do I troubleshoot this one? thanks in anticipation -Makaut

4 10

"Item-level_itypes set but no itemtype set" leads to 'Can't locate object method "ymd"'
by King, Fred 03 Jan '17

03 Jan '17

Greetings to all, System: Koha 16.11.00, Ubuntu 14.04. When I rebuild zebra, I get a series of error messages "item-level_itypes set but no itemtype set for item (itemnumber) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698." I've looked up the corresponding biblio number and barcode for the items in an inventory report, but when I try to search for them I get the error message 'Can't locate object method "ymd" via package "dateonly" (perhaps you forgot to load "dateonly"?) at /usr/share/koha/lib/Koha/DateUtils.pm line 225.' I get the same message whether I search for item number, biblio number, barcode, or title. Some of the items don't have barcodes-I don't know whether that's part of the problem. It looks as if part of the 'Can't locate object method "ymd"' problem is being fixed with Bug 17502, but I can't tell if it's just a date problem that I can fix easily since I can't call up the record to look at it. Same with item-level itemtype. Does this sound familiar to anyone? Does anyone know of a way to call up items that keep crashing Koha? Thanks, Fred King Medical Librarian, MedStar Washington Hospital Center fred.king(a)medstar.net<mailto:fred.king@medstar.net> 202-877-6670 ORCID 0000-0001-5266-0279 I have one of those metabolisms where I can eat whatever I want and my body converts it to energy and stores the excess as fat. --Randall Munroe, xkcd ---------------------------------------------------------------------- MedStar Health is a not-for-profit, integrated healthcare delivery system, the largest in Maryland and the Washington, D.C., region. Nationally recognized for clinical quality in heart, orthopaedics, cancer and GI. IMPORTANT: This e-mail (including any attachments) may contain information that is private, confidential, or protected by attorney-client or other privilege. If you received this e-mail in error, please delete it from your system without copying it and notify sender by reply e-mail, so that our records can be corrected... Thank you. Help conserve valuable resources - only print this email if necessary.

3 4

Handling of TimeZones and different Calendars (Thailand Buddhist Calendar) on a single shared Koha server
by Alex Shepherd 03 Jan '17

03 Jan '17

Hi Guys, I’m hoping to host several independent libraries on a single VM. The libraries are all in Asia spread across Sri Lanka, Myanmar and Bangkok and the server is a VM hosted on Digital Ocean in Singapore. The library in Bangkok have used the Buddhist calendar for some (not all) of their dates like DoB and some other date fields in the Bibliographic and other records. This is causing an issue with the date calculations for patron age and no doubt it will cause other issues. So this raises several issues for me: 1) Is there a tidy or supported way for me to handle the Buddhist dates? 2) Does Koha have any way to define a timezone and locale on a library by library basis where there are multiple libraries on the one server? Regards Alex Shepherd

3 2