- Koha - lists.katipo.co.nz

3.18 upgrade, bug 13404 GRS1 v. DOM questions
by Amy Schuler 14 May '15

14 May '15

hi all, Just upgrading from 3.10 to 3.18.06 on Debian. That's a big leap. Everything is looking and feeling totally alien. I am testing out the upgrade and added a record using the stage marc record/import staged record tools. However, the record does not show up in catalog search. I tried reindexing: koha-rebuild-zebra -f -v instancename. That seemed to go okay up until I got these weird errors: zebraidx(5004) [warn] Couldn't open collection.abs [No such file or directory]" and "Record didn't contain match fields in (bib1,Local-number)" The reindex proceeded but skipped the biblios. I found these 2 bugs that seem relevant: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13396 and http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13404 so it sounds like there is a patch. But where is the patch? I may be an idiot but I don't see it. I just see examples of code to manually add/fix in the koha.conf.xml. If there is a patch I can use to avoid manual editing, that would be excellent. Please advise. Thanks! Amy Schuler Cary Institute

2 1

Re: [Koha] 3.18 upgrade, bug 13404 GRS1 v. DOM questions
by Amy Schuler 14 May '15

14 May '15

Update! In the reindexing attempt described below I also see: CLEANING: command not found Now when I search my catalog I get NO results for any search! In OPAC or admin interface. Please help!! Thanks On Thu, May 14, 2015 at 12:56 PM, Amy Schuler <schulera(a)caryinstitute.org> wrote: > hi all, > Just upgrading from 3.10 to 3.18.06 on Debian. That's a big leap. > Everything is looking and feeling totally alien. I am testing out the > upgrade and added a record using the stage marc record/import staged record > tools. However, the record does not show up in catalog search. I tried > reindexing: koha-rebuild-zebra -f -v instancename. That seemed to go okay > up until I got these weird errors: zebraidx(5004) [warn] Couldn't open > collection.abs [No such file or directory]" and "Record didn't contain > match fields in (bib1,Local-number)" The reindex proceeded but skipped the > biblios. > > I found these 2 bugs that seem relevant: > http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13396 and > http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13404 > > so it sounds like there is a patch. But where is the patch? I may be an > idiot but I don't see it. I just see examples of code to manually add/fix > in the koha.conf.xml. If there is a patch I can use to avoid manual > editing, that would be excellent. > > Please advise. Thanks! > > Amy Schuler > Cary Institute > > > >

1 0

Can we combine OPAC Item Status and Due Date into one column
by Iming Chan 14 May '15

14 May '15

Dear all, This maybe a strange question, but I'm wondering whether there is anyway we can combine OPAC Item Status and Due Date into one column (and remove or hide Due Date column from displaying)? The Due Date which appears when the item status is at "Checked out" will be displayed like: Checked out (Due: 13/5/2015) Just curious ... Iming ----- Iming Chan Translib Information Service Melbourne, Australia http://opac.translib.com Phone: +61 3 9801 5097 Fax: +61 3 9801 4024 E-mail: iming(a)translib.com -- View this message in context: http://koha.1045719.n5.nabble.com/Can-we-combine-OPAC-Item-Status-and-Due-D… Sent from the Koha-general mailing list archive at Nabble.com.

3 9

Koha 3.20 beta released
by Tomas Cohen Arazi 14 May '15

14 May '15

A beta release of Koha 3.20 is now available for download. We encourage all users of Koha to consider downloading and testing the beta prior to its release later this month. Debian packages for this beta will be available soon on the unstable repository. Koha 3.20 is a major release, that comes with many new features. This beta preview is released for testing purposes. Its use on production sites is discouraged. Draft release notes and download links can be found below. Share and enjoy (and test)! Download: http://koha-community.org/download-koha/ Draft release notes: http://koha-community.org/koha-3-20-beta-released/ Thanks everyone! -- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 5353750 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F

2 1

converting existing serial subscriptions from "no items" to "generate items"
by Giuseppe Angilella 14 May '15

14 May '15

Hi, whenever one creates a new subscription for a serial, Koha prompts whether you would like to "create an item record when receiving this serial", or not. Now, after some experience with my patrons, it seems that the best way of keeping track of serial loans is to have items for each serial issue. Therefore, I need to edit existing subscriptions, so that a new item record is created whenever a new serial issue is received. But how do I attach items to serial issues already recorded? (Do I need to delete them all, and start "receiving" existing issues as if they were new? I understand that unavoidably there might be some "manual" work to be done, but I would like to save as many as possible of the details already entered in the database.) Many thanks in advance and best regards, Giuseppe.

1 0

SQL report: Digests in message preferences
by Chad Roseburg 13 May '15

13 May '15

Does anyone have a report showing barcodes of patrons who do not have the "Digests only?" option enabled. I see the transport types but am not sure how the digest option is stored. Thank you! -- Chad Roseburg Automation Dept. North Central Regional Library

7 11

MARC modification templates
by Katelyn Browne 13 May '15

13 May '15

Hi all, I've just about got our MARC modification template set up, but I have one major issue I can't solve: moving and modifying item prices. Here's what I do with MARCedit: --move all of 852 (where our vendor puts items) to 952 --(do other stuff on other subfields) --move 952$9 to 952$g --remove "P" and "usd" from the price (which come as, for example, *P10.99usd* instead of *10.99*) --copy 952$g into 952$v I've attempted to reproduce these steps in our modification template, but 952$g and 952$v come up blank when I import the records. I suspect the problem is with the P/usd issue and requires some regular expressions (which are not my expertise). If you are good at RegEx, or you have addressed a similar problem, can you make some suggestions? Thanks! --Katelyn. Katelyn Browne High School Librarian & Technology Teacher Capital City Public Charter School 100 Peabody Street NW Washington, DC 20011 (202) 387-0309 x1745 kbrowne(a)ccpcs.org http://www.ccpcs.org/library/

1 0

strange behavior with a public report
by Arturo Longoria 13 May '15

13 May '15

Hi all, I've come across strange behavior with a public report in Koha since our library was upgraded to 3.18. I'm not sure if it is a bug or if I am doing something incorrectly, and so I thought I'd ask for some input. I've created a custom SQL report that will output basic bibliographic data for titles that are included in a list ("virtual shelf"), and I have marked this report as public so that I can access its JSON output via /cgi-bin/koha/svc/report?id={report id}&sql_params={virtual shelf number} on the public side. The issue I'm having is that if I run this report within the staff client, it works perfectly. If I edit the list by adding/removing titles to it and then re-run the report in the staff client, everything is displayed as expected. But if I run the report on the public side to get the JSON output, the report will only show me bib. info for the titles that were originally saved in the list! That is, when I first create a list and access its JSON output, it works fine. But if I then edit the list by removing a title or adding a new title, the JSON output is not updated – it continues to show me the old contents of the list. If I run the report through the staff client, though, it does show me the updated contents of the list! The two outputs are different. Any ideas on what could be causing this? The report's settings have a cache expiry of 0 seconds (the default). I've tried setting different cache expiry periods to see if that is the issue, but that seems to do nothing. The SQL is a very simple select statement: SELECT biblionumber, author, title, seriestitle, copyrightdate, notes, abstract FROM virtualshelfcontents vsc LEFT JOIN biblio using (biblionumber) WHERE vsc.shelfnumber = <<Enter shelf number>> Arturo Longoria Texas State Law Library www.sll.texas.gov<http://www.sll.texas.gov/>

2 2

searching error after upgrading from 3.14.05 to 3.18.05.1
by Arayik Manukyan 13 May '15

13 May '15

Hi List, Our Koha 3.14.05 tarball installed on linux Ubuntu We have some problem, after upgrading to 3.18.05.1 When searching the catalogue we get Error: Can't call method "raw" on an undefined value at /usr/share/koha/lib/C4/Search.pm line 800. Please help as soon as possible. Thanks, Araik

1 0

Question about author sorting
by Robin Sheat 13 May '15

13 May '15

As some of you know, I'm in the process of implementing Elasticsearch support into Koha. Katrin pointed out that there's a bit of an irregularity with the author sorting, but I'm not sure if it's wrong as such. So I'm after a bit of input into what actual people would expect or would like. Imagine you have a book, with multiple authors: Title of Book Andrews, A ; Matthews, M ; Zimmermann, Z You do a search for "title", sorted by author A->Z, and get results, with "Title of Book" at the top due to "Andrews, A." You then sort it by author Z->A, and get "Title of Book" at the top again, due to "Zimmerman, Z." There is clearly logic behind it doing this, but is it the right thing to do? If not, what do you think an appropriate alternative would be? -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF

2 1