- Koha - lists.katipo.co.nz

Authority record updates fail- no matches found.
by Raymund Delahunty 14 Apr '16

14 Apr '16

University of the Arts London moved to Koha in September last year, moving away from Voyager. We subscribe to the Marcive authority update service and we receive monthly updates to existing authority records and (in theory) also new authority records derived from newly added bibliographic records added to our database and sent to Marcive for inclusion in our data file. (Not that we have submitted records yet, due in part to ongoing frustrations with authority control in Koha.). Much to my disappointment we have just suspended the monthly update service as we have been quite unable to update existing authority records as the matchpoint index simply doesn't work. If I try to update, I receive zero matches and every incoming record would be added. Has anyone, anywhere been able to update existing authority records based on the LC-Cardnumber index (010$a)? My (simplistic) take on the problem is that the normalisation rules (maybe Voyager-speak) are simply not correct and the index LC-cardnumber being built is useless. PTFS Europe who provide support to us have been assisting and they went out to this list on 22 December last year. There were lots of responses but most were too technical for me. To me the problem seems to be with the way the index is built and the matching with the data incoming is performed. The 010$a RCN structure is complex but strictly defined- some records have a space in them (Structure B), some have two (Structure A). If the LC-cardnumber index is not being built correctly to match the data standard then isn't this a bug? Included in the earlier email exchange on this list was this one (I believe it was from Joy Nelson at ByWater Solutions): "I suspect that you are correct that there is some stripping of spaces, but not to the extent you are looking for. i.e. Koha is removing 1 space, but not multiple spaces If this is the case, someone with some more expertise would need to weigh in on the behind the scenes code. [...]". If this is a bug surely lots of other Koha users will be similarly afflicted? This problem is becoming mission critical for us now as we are struggling with (ridiculous amounts of) manual authority control, and we need to resolve this ASAP. Until we resolve this we cannot make informed choices as to what settings to use in ongoing authority work (particularly the choice of settings for BiblioAddsAuthorities). There was the suggestion (again from Joy Nelson, I recall): "If you have some perl proficiency you can use perl scripts to pull out, modify the 010$a (stripping out spaces) from your authority records in Koha if that would help make them match the incoming records. But from a true cataloger's perspective you want the 010$a in your system to be the 'right value' spaces or no spaces, so using a script to modify your 010$a's may or may not be desirable." Now I won't confirm or deny that I am a true cataloger, but I am not prepared to permanently damage the sanctity of the MARC data. I do have a (ridiculously complicated MarcEdit-based) way of copying the existing 010$a (and other data) away, dealing with the spaces in the residual 010$a and doing the 7 months of overdue updates, before undoing my temporary damage to the MARC data, but the idea of doing this monthly (ripping apart the entire data in the authority file, importing the Marcive data and then undoing the damage) strikes even me as a bit extreme. So, again. Has anyone, anywhere been able to update existing authority records based on the LC-Cardnumber index (010$a)?. We don't have server access, so if there is a workaround that would be for PTFS to implement. But if the LC-cardnumber index is broken surely there will be lots of Koha sites in a similar mess to the one we are in. Any suggestions or pointers would be most appreciated Ray Delahunty Systems Support Librarian University of the Arts London https://libsearch.arts.ac.uk This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of London Artscom Limited the following also applies: London Artscom Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY

2 1

How to use Item Type ?
by satishamv 13 Apr '16

13 Apr '16

Hi, I have a basic question regarding Item Type. Item Type is required for Circulation Policy settings and Report generation, etc. For a Single Bibliographic RECORD (book) having 2 copies (ITEM), Say example, Item Type 1 = "Book" meant for Circulation and Item Type 2 ="Reference Book" meant only for reference purpose and not for loan/circulation to satisfy both conditions, either I can create both the item types (Books, Reference Book) and define a circulation policy -OR- by creating only one item type = i, e. "Books" and using 9XX, 7 - Not for loan, can I restrict loan/Circulation (reference). Which method should be used?? Am I wrong anywhere in understanding Item Type ? Should I create two "Item type" for a single bibliographic RECORD ? Kindly Clarify ? With Thanks Satish MV Librarian GEC Hassan Karnataka. -- View this message in context: http://koha.1045719.n5.nabble.com/How-to-use-Item-Type-tp5881573.html Sent from the Koha-general mailing list archive at Nabble.com.

6 6

Big Koha Migration of Turkey
by Mengu Yazicioglu 13 Apr '16

13 Apr '16

Hi all, I'm glad to share that we successfully migrated old 2.x Koha to new one, 3.20. I should also say that this a quite derived version of 3.20, we have added many new features, new modules and changed a lot of codes for the use of public libraries so we may call this Koha version as Koha -- Devinim. We've migrated 1.220.000 active users, 13.700.000 items with active 900 libraries of 1126 public libraries all cities of Turkey. We use 14 servers for all production and 4 servers for test environment. We use MariaDB and Galera Cluster with 4 nodes, 8 apache servers and 1 zebra server. We plan to cluster zebra server in the future, it cannot perform very well for this kind of huge installation. During migration, we also cleaned some dirty data, this was also a big issue for 13m items. We've done many tests before going live. OPAC page is http://koha.ekutuphane.gov.tr Thanks // /Mengü YAZICIOĞLU DEVİNİM Software Consultancy /

9 13

koha installation problem
by abdiyoo 13 Apr '16

13 Apr '16

hi,everybody i try to install koha ubuntu 14.04,but it does not work,first i make update then install the coha-common,and it's display the following error: reading Packages list ....................done building dependecy tree Reading information tree..............done E:unable to locate package Koha-common so please help me. regards. -- View this message in context: http://koha.1045719.n5.nabble.com/koha-installation-problem-tp5882926.html Sent from the Koha-general mailing list archive at Nabble.com.

3 2

Reminder: Koha-US mtg is tomorrow.
by Christopher Davis 13 Apr '16

13 Apr '16

Greetings, This message is just a courtesy reminder that Koha-US has scheduled its next monthly meeting for tomorrow, April 13th at 11:00 am Central Time. Please join this meeting by logging onto https://kslib.zoom.us/j/657929919 and then follow the directions (need help? Just contact me). Thank you, Christopher Davis Secretary, Koha-US cgdavis(a)uintah.utah.gov

1 0

NEKLS Job opportunity for NExpress Coordinator and ILS Systems Manager
by Heather Braum (NEKLS) 12 Apr '16

12 Apr '16

Last call for applicants. NEKLS will begin reviewing applications after April 15. The Northeast Kansas Library System <http://www.nekls.org/> (NEKLS) in Lawrence, KS <http://explorelawrence.com/>, has an opening and we’re looking for a diplomatic applicant with lots of energy, enthusiasm, and excellent custom service skills to come work with us! *NExpress Coordinator and ILS Systems Manager*: Opportunity for a creative librarian who will enjoy the challenge of managing a large regional shared consortia catalog, with 42 public libraries and 1 school district (public catalog <https://catalog.nexpresslibrary.org/>). The system runs on the Koha ILS <http://www.koha-community.org/>, an open source ILS used all over the world. Responsibilities include: - Providing overall management, support, and coordination of the NExpress ILS and consortia, including balancing needs of consortia with local library needs - Coordinating operations of NExpress team - Maintaining data quality of NExpress records and database - Coordinating with participating libraries and ILS support vendor regarding system features and bugs, migrations, upgrades, and software developments - Providing NExpress training to participating libraries, including planning & leading quarterly NExpress users group meetings - Participating in the international Koha community Qualified candidates will meet the following: - MLS degree preferred and 3 or more years of prior library experience is required. - Experience with integrated library automation system software is required. - Knowledge of cataloging best practices, database management (MySQL), web languages (HTML, CSS, JQuery), web CMS platforms (WordPress and LibGuides) is highly preferred. See the full job description, including qualification list <http://nekls.org/wp-content/uploads/2016/03/NExpress-Coordinator-Job-Descri…>, for more information ( http://nekls.org/wp-content/uploads/2016/03/NExpress-Coordinator-Job-Descri… ). Excellent salary ($50,000-$53,000) and benefits package, including complete health, dental, and vision coverage (single and family), short-term and long-term disability insurance, and retirement options. Position is open until filled. Evaluation of applications will begin on April 15, 2016 and will continue until position is filled. Estimated start date is on or around July 1, 2016. For questions, please contact Laura DeBaun, NEKLS Director, at ldebaun(a)nekls.org. Apply with cover letter, resume and references list by emailing Carolyn Little, Courier Coordinator, at clittle(a)nekls.org. Please use the subject line NExpress Coordinator Job Application. NEKLS is an equal opportunity employer. Heather Braum NExpress Coordinator Resource Sharing Librarian Northeast Kansas Library System hbraum(a)nekls.org "The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn, and relearn." ~Alvin Toffler, *Rethinking the Future*

1 0

Documentation link to Manual (Chinese[Taiwan]) 3.22
by Anthony Mao 11 Apr '16

11 Apr '16

Hi, The 3.22 Manual (Chinese[Taiwan]) is done few minutes ago. Is it possible add links on https://koha-community.org/documentation/? 3.22 Manual (Chinese[Taiwan]), with link as http://translate.koha-community.org/manual/3.22/zh-Hans-TW/html/ 3.20 Manual (Chinese[Taiwan]), with link as http://translate.koha-community.org/manual/3.20/zh-Hans-TW/html/ 3.18 Manual (Chinese[Taiwan])[PDF], with link as http://translate.koha-community.org/manual/3.18/zh-Hans-TW/ One more thing, Chinese[Taiwan] or Chinese[traditional] should have language code as zh-TW. zh-Hans-TW is not the right way. For your reference: Chinese (China) using the code zh-CN, Chinese (Hong Kong) coded as zh-HK in Koha. And Chinese (Singapore) would code as zh-SG. -- Wishing you all the best. . . . Anthony Mao 毛慶禎＋886 2 29052334 (voice) + 886 2 29017405 (FAX)

1 0

Migrating 6 eLM System to Koha
by Alex Shepherd 10 Apr '16

10 Apr '16

Hi, This is my first post on this list and I have the unenviable task of migrating 6 Theological Libraries (in Asia) from the ConTec eLM system over to Koha. These eLM system are the UNICODE variant to support the various local language holdings (Thai, Sinhala, Tamil, Burmese & English) in those libraries, which I converted from various bespoke systems over to eLM and did all the mapping/hacking/converting from the local language special fronts to UNICODE and did quite a lot of data cleansing during that process. So I’m hoping that this subsequent migration to Koha will be a lot simpler - once I know how. I have had ConTec perform a trial export of one of the libraries and as an experiment I imported the biblio records file and it loaded the 30k items in about 30 seconds and I was able to search for records and find them so that was very encouraging. However now I am needing to work out what to do with the rest of the data and hopefully figure out a path that will allow me to batch convert each library from the ConTec eLM Export files. I’ve been educating myself about Koha but as I’m not a librarian (I’m an experienced and resourceful IT Software Developer / Architect in Hamilton NZ) my library skills consist only of what I have needed to know and figured out to make eLM “work” and not necessarily be “awesome”. While googling "koha ELM migration” I came across a thread discussing some migration scripts from an eLM export here: http://koha.1045719.n5.nabble.com/Instruction-document-on-items-holdings-mi… After some more googling I found what I believe this the migration tool here: https://gitlab.com/catalyst-koha-migration-toolbox/koha-migration-toolbox/t… Is this the best place to start with eLM migration or are there better resources? Who are the best people who may be able to help or advise me on this process? I’m doing this on a voluntary basis but I may be able to get some $$$ to pay for some migration support assistance. TIA Regards Alex Shepherd p: +64-7-829 4441 m: +64-21-777764 e: kiwi64ajs(a)gmail.com

2 1

Re: [Koha] Suggestion Challenge
by Kerrie Stevens 09 Apr '16

09 Apr '16

Hi Bruce, Do you have multiple locations in your catalogue? I am shown there are # suggestions but if they are from another location then I can't see them until I change my library to that same location. Then I can see them and deal with the suggestions before changing back to my normal library location. Hope this helps, Kerrie Stevens Harvest Bible College Message: 6 Date: Thu, 7 Apr 2016 19:01:32 -0400 From: "Bruce A. Metcalf" <bruce.metcalf(a)augustansociety.net> To: Koha <koha(a)lists.katipo.co.nz> Subject: [Koha] Suggestion Challenge Message-ID: <5706E6CC.5020801(a)augustansociety.net> Content-Type: text/plain; charset=utf-8; format=flowed Greetings, The Acquisition Page tells me my system has over 9000 suggestions, but when I go to the Suggestions management page to look a them, it says "No data available in table". I'm thinking this is some sort of glitch, but I have no idea where to go to reset the suggestion number to zero. Any suggestions (no pun intended)? Koha 3.22.5from packages under Debian 7.10, both current on updates. Regards, / Bruce / Bruce A. Metcalf Library Director The Augustan Society,Inc. ------------------------------ 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 126, Issue 12 *************************************

3 2

Re: [Koha] v3.22 - Import Patrons
by Jonathan Druart 08 Apr '16

08 Apr '16

Sergio, which version of the 3.22 branch are you using? What you describe make me think about bug 15840, a fix has been pushed to 3.22.05 2016-04-07 16:35 GMT+01:00 Sergio Scotto <sscotto(a)psi.uba.ar>: > Hi Tomas, thx for the reply! > > This is what i do: > > First i import the file test.csv (its only one patron) in koha, and the import is succesfull. > Then, i try to re-import the same file (chaning or not chaning some field) to rewrite the patron (maintaing cardumber), and the the site crash. > > (I got 2 codes in the file, psi for library and ND for user category) > > > Sergio. > > > _____ > > De: Tomas Cohen Arazi [mailto:tomascohen@gmail.com] > Enviado el: jueves, 07 de abril de 2016 12:24 p.m. > Para: Sergio Scotto > CC: Koha list > Asunto: Re: [Koha] v3.22 - Import Patrons > > > You should fill a bug, specifying the steps to reproduce. It would help if you provided some sample data that is known to fail (maybe a portion of your import) so we can reproduce it in our test environments. > > 2016-04-07 12:07 GMT-03:00 Sergio Scotto <sscotto(a)psi.uba.ar>: > > > Hi guys, i am trying to import patrons in koha, the import works fine, but > when i select the update option in case that a cardnumber is matched the web > site crash and nothing is update. > Any suggest? > > Thx! > Sergio > > > > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > > -- > > Tomás Cohen Arazi > Theke Solutions (http://theke.io <http://theke.io/> ) > ✆ +54 9351 3513384 > GPG: B2F3C15F > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha

1 0