[Koha] Migración a Koha

2019-07-10 Thread Paula Marina Gutiérrez
Estimados Colegas: Estoy trabajando en la Facultad de Ingeniería del Ejército y necesito ayuda por lo siguiente: Estamos por emprender una migración total al sistema Koha. Nuestro catálogo está en formato Cepal en el sistema Winisis, tenemos una base de Compra en el sistema Winisis también y

[Koha] Development to allow batch cancellation of selected holds

2019-07-10 Thread Johnson, Barbara
Our staff would like the option to cancel only selected items on the Holds Over tab in the Holds awaiting pickup table. Staff could select the group of holds they want to cancel and do it as a batch. The development would add a checkbox next to each item, along with a 'Cancel Selected' button

[Koha] Development idea - Create holds from patron suggestions

2019-07-10 Thread Johnson, Barbara
Our patrons who submit suggestions usually want to have a hold placed on the item for them so that they will be the first person able to check it out. This development would include the following: 1. Ordering from a suggestion method - automatically place a hold for the patron when the

Re: [Koha] Error after upgrading to 19.05

2019-07-10 Thread Jacopo
Dear Alvaro, thank you very much! You pointed me in the right direction! To summarise, the suggestion provided the 25th of March by Chris Cormack (many thanks to him too) solved the issue: https://lists.katipo.co.nz/public/koha/2019-March/052591.html I had, in /etc/koha, 2 files named in a similar

Re: [Koha] Error after upgrading to 19.05

2019-07-10 Thread Alvaro Cornejo
Hi Jacopo Look for the message title " [Koha] Problem with upgrading Koha from 17.11 to 18.11 " dated march 22nd The case is very similar. It does not provide a final solution, but it can give you ideas... Regards, Alvaro

Re: [Koha] Error after upgrading to 19.05

2019-07-10 Thread Alvaro Cornejo
Hi Jacopo I guess your migration process failed somewhere. I remember seen a post with the issue of having system calling files with extensions like "19.0501000". If I do recall well it was due to something wrong on the process. Will try to find the related post. Regards, Alvaro

Re: [Koha] Error after upgrading to 19.05

2019-07-10 Thread Jacopo
Hi, just wanted to add, as a further explanation that - the styles files (css/js) that the broswer tries to load have all the suffix 19.0501000. - the same files are present here /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap but without extension - the file including them is this one

[Koha] Report

2019-07-10 Thread Victor Barroso Oliveira
Good Morning, I need a report that shows all the loans made, refined by library and date. Would anyone have the SQL of this report to send? Thank you, Victor ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz

Re: [Koha] Error after upgrading to 19.05

2019-07-10 Thread Jacopo
Dear Mark, dearl Alvaro, thank you for your replies :) Just an update: - I moved to Debian 9 - set memcached correctly in my /etc/koha/sites//koha-conf.xml (it is now running if I check the status in the about page of the intranet) Current status: * I am able to access the intranet and to

Re: [Koha] [Koha-devel] Problems searching callnumbers with Koha and ICU

2019-07-10 Thread dcook
HI again, Mason, I just remembered a little trick that you might find useful. Try the following: echo "PZ 7 .W663 1984" | yaz-icu -x -c /path/to/phrases-icu.xml echo "PZ 7 .W663 1984" | yaz-icu -x -c /path/to/words-icu.xml That should show you how the string is normalized and tokenized for

Re: [Koha] [Koha-devel] Problems searching callnumbers with Koha and ICU

2019-07-10 Thread dcook
Hi Mason, Can you tell us what version of Zebra you're running? And what is your exact query? According to https://packages.debian.org/stretch/idzebra-2.0, you're probably running Zebra 2.0.59, unless you're pulling packages from Indexdata's APT repository. I discovered a ICU bug in Zebra

[Koha] check out one item results in multiple of those items

2019-07-10 Thread keshavonline2000
We have started experiencing a recent issue where attempting to check out one item results in multiple of those items (same barcode, checked out multiple times) being checked out to the one patron. This does not happen to every item, nor does it happen to every patron. -- Sent from: