- Koha - lists.katipo.co.nz

Catalog Search Relevance Ranking
by Joel Sasse 02 Nov '17

02 Nov '17

Can anyone point me in the direction of a resource that will explain how Koha determines relevance in catalog searches? Some of my libraries have been asking about it since it's the default sort option. Thanks, Joel Sasse Network Systems Administrator Plum Creek Library System 290 S Lake St Worthington, MN 56187 Office: 507-376-5803 Mobile: 507-360-8961 Fax: 507-376-9244 O

4 3

Re: [Koha] Koha Digest, Vol 145, Issue 3
by Ghulam Mustafa Zaman 02 Nov '17

02 Nov '17

I installed the Koha latest version and after installation this isn't showing icons on desktop . On Nov 2, 2017 3:22 AM, <koha-request(a)lists.katipo.co.nz> wrote: > 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. Re: Koha enhancement request (vinod mishra) > 2. Haunted by ghost records (Charlotte Stock) > 3. Re: Catalog Search Relevance Ranking (Michael Kuhn) > 4. Re: Haunted by ghost records (Katrin Fischer) > 5. Re: Catalog Search Relevance Ranking / Dead link in manual > (Katrin Fischer) > 6. Re: Azure Active Directory (Katrin Fischer) > 7. Re: opac search (Katrin Fischer) > 8. Zebra question (Ricardo Ruiz) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 1 Nov 2017 09:48:10 +0530 > From: vinod mishra <mishravk79(a)gmail.com> > To: Manju N <manjunayak1977(a)gmail.com> > Cc: Koha <koha(a)lists.katipo.co.nz> > Subject: Re: [Koha] Koha enhancement request > Message-ID: > <CAGLUwiTVW-xK8r2wa_XzViWryGENQyuwV7YcjF9VWSwK-=Sp > Sw(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Dear Mr. Naika > > For below two points options are already given in Koha > > We want to restrict 'hold' only for checked out items. Option required at > circulation and fine rules: Allow hold only for checked out items > > > Alert message required for checked in items if there is any hold on such > items to keep those hold item separately at counter without sending for > shelving. > > For below point you may contact to Mr. Monirul (CC in this email), however > we have done this with his help. > > We want to use multiple levels late fee/fine slab. Currently, Koha supports > only one late fee slab. We would appreciate any comments or suggestions > that will help us to tweak the koha. > > > > With Regards, > > Vinod Kumar Mishra, > Assistant Librarian, > Biju Patnaik Central Library (BPCL), > NIT Rourkela, > Sundergadh-769008, > Odisha, > India. > Mob:91+9439420860 > Website: http://mishravk.com/ > ORCID ID: http://orcid.org/0000-0003-4666-7874 > > *"Spiritual relationship is far more precious than physical. Physical > relationship divorced from spiritual is body without soul" -- Mahatma > Gandhi* > > On Tue, Oct 31, 2017 at 11:38 PM, Manju N <manjunayak1977(a)gmail.com> > wrote: > > > Dear All, > > > > > > > > Anyone has customized the Koha for multiple level approvals of suggested > > titles from the patrons/faculty in Acquisition module? In our library, > we > > need multiple level approvals such as from the Head of Department and > > Chairman, Library Committee/etc. > > > > > > We want to use multiple levels late fee/fine slab. Currently, Koha > supports > > only one late fee slab. We would appreciate any comments or suggestions > > that will help us to tweak the koha. > > > > > > We want to restrict 'hold' only for checked out items. Option required at > > circulation and fine rules: Allow hold only for checked out items > > > > > > Alert message required for checked in items if there is any hold on such > > items to keep those hold item separately at counter without sending for > > shelving. > > > > > > We would appreciate any comments or suggestions to change the Koha to > meet > > the above requirements. > > > > > > > > With Regards > > > > Manju Naika,PhD > > > > Asst.Librarian,IITB > > _______________________________________________ > > Koha mailing list http://koha-community.org > > Koha(a)lists.katipo.co.nz > > https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > ------------------------------ > > Message: 2 > Date: Wed, 1 Nov 2017 08:56:14 +0000 > From: Charlotte Stock <cstock(a)halcyonschool.com> > To: koha(a)lists.katipo.co.nz > Subject: [Koha] Haunted by ghost records > Message-ID: > <CACBO8BqXeQuDTG+0a7tba8AqOyOHa19uiOo4rnQg_ > YDJWKs2WQ(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Recently I imported a large batch of records, but when I ran a search not > all of the records had loaded so I deleted the batch and reimported. > > Now, when I run a search, the results list the 'deleted' batch and then the > reimported batch, which means that users instinctively select from the > first batch of results - all of which display the message "The record you > requested does not exist" when selected. > > When I enter the record numbers of the failed entries to perform a batch > deletion, this message displays 'The biblionumber does not exist in the > database'. > > My question is how do I remove these ghost records so that they do not > appear in OPAC searches, as users will quickly give up if the first page of > results are all failed records? > > Thankyou in advance for your advice > Charlotte > > -- > Charlotte Stock - Digital Librarian > Halcyon London International School > > -- > > > > *Halcyon London International School* > > 33 Seymour Place, London W1H 5AU > > +44 (0)20 7258 1169 > <http://halcyonschool.com/?utm_source=email%20footer&utm_medium=email> > [image: http://halcyonschool.com/visit] > <http://halcyonschool.com/visit?utm_source=email%20footer&utm_medium=email > > > > <https://www.facebook.com/HalcyonLondonInternationalScho > ol?utm_source=email%20footer&utm_medium=email> > <http://www.linkedin.com/company/halcyon-london-international-school?utm_ > source=email%20footer&utm_medium=email> > <https://mydonate.bt.com/charities/halcyonlondoninternationalscho > ol?utm_source=email%20footer&utm_medium=email> > <https://twitter.com/HalcyonSchool?utm_source=email%20footer&utm_medium= > email> > > > ------------------------------ > > Message: 3 > Date: Wed, 1 Nov 2017 10:17:33 +0100 > From: Michael Kuhn <mik(a)adminkuhn.ch> > To: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] Catalog Search Relevance Ranking > Message-ID: <7022b256-d20f-4b65-f5ec-76bfaaa2e3f5(a)adminkuhn.ch> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi Joel > > > Can anyone point me in the direction of a resource that will explain > > how Koha determines relevance in catalog searches? Some of my > > libraries have been asking about it since it's the default sort > > option. > > I would suggest to start, as usual, with the Koha manual: > * https://koha-community.org/manual/17.05/html/13_searching.html > > The actual relevance ranking is done within Zebra, you will find the > "Zebra - User's Guide and Reference" here (unfortunately the link to > this guide in the Koha manual is dead): > * http://www.indexdata.com/zebra/doc/ > > For relevance ranking start here: > * http://www.indexdata.com/zebra/doc/administration-ranking.html > > Hope this helps. > > Best wishes: Michael > -- > Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis > Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz > T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch > > > ------------------------------ > > Message: 4 > Date: Wed, 1 Nov 2017 11:28:10 +0100 > From: Katrin Fischer <katrin.fischer.83(a)web.de> > To: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] Haunted by ghost records > Message-ID: <2c387021-ccb9-11a9-5b7d-c95b9d28cfed(a)web.de> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi Charlotte, > > I am not sure why it happened, but it means that your search index is > out of sync. When you imported the first batch it got indexed, but the > index didn't get cleaned up correctly when you undid it. Maybe there as > a bad record in the batch as you said they didn't all show up in search. > > A full reindex should usually fix the problem. If there are any errors > running during reindexing, this might give you another clue on what went > wrong. > > Hope this helps, > > Katrin > > > On 01.11.2017 09:56, Charlotte Stock wrote: > > Recently I imported a large batch of records, but when I ran a search not > > all of the records had loaded so I deleted the batch and reimported. > > > > Now, when I run a search, the results list the 'deleted' batch and then > the > > reimported batch, which means that users instinctively select from the > > first batch of results - all of which display the message "The record you > > requested does not exist" when selected. > > > > When I enter the record numbers of the failed entries to perform a batch > > deletion, this message displays 'The biblionumber does not exist in the > > database'. > > > > My question is how do I remove these ghost records so that they do not > > appear in OPAC searches, as users will quickly give up if the first page > of > > results are all failed records? > > > > Thankyou in advance for your advice > > Charlotte > > > > > > ------------------------------ > > Message: 5 > Date: Wed, 1 Nov 2017 11:34:51 +0100 > From: Katrin Fischer <katrin.fischer.83(a)web.de> > To: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] Catalog Search Relevance Ranking / Dead link in > manual > Message-ID: <a39c2ae5-7314-34e6-52b2-31974f021d93(a)web.de> > Content-Type: text/plain; charset=utf-8; format=flowed > > > > The actual relevance ranking is done within Zebra, you will find the > > "Zebra - User's Guide and Reference" here (unfortunately the link to > > this guide in the Koha manual is dead): > > * http://www.indexdata.com/zebra/doc/ > > > > For relevance ranking start here: > > * http://www.indexdata.com/zebra/doc/administration-ranking.html > > > Hi Michael and all, > > please report any problems with the manual that you spot or know of. We > have a pad that you can just type into, no registration required: > > https://annuel2.framapad.org/p/KohaManualTodo > > Also feel free to submit a patch directly, instructions are here: > > https://wiki.koha-community.org/wiki/Editing_the_Koha_Manual > > You can also send us text directly to format and include. I would love > if we could add more information about how the relevance ranking works! > > Katrin > > > > ------------------------------ > > Message: 6 > Date: Wed, 1 Nov 2017 13:01:05 +0100 > From: Katrin Fischer <katrin.fischer.83(a)web.de> > To: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] Azure Active Directory > Message-ID: <c9818aa2-06a7-829b-34bc-fc66ba745ff4(a)web.de> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi Bob, > > we have one library where patrons are added/updated on login, but not > using Azure Active Directory. > > There is a rather new chapter in the 17.05 manual: > > https://koha-community.org/manual/17.05/html/17_miscellaneous.html# > integrating-ldap-with-koha > > And some more notes and documentation in the module itself: > > https://perldoc.koha-community.org/C4/Auth_with_ldap.html > > Hope this helps, > > Katrin > > > > On 31.10.2017 07:02, Bob Birchall wrote: > > Has anybody integrated Koha with Azure Active Directory, using Koha's > > LDAP capability? > > We understand that the client's wish is to update users and fields in > > Koha from the AAD, not just check credentials. > > Any documentation you can point us to? > > Thanks, > > Bob Birchall > > Calyx > > _______________________________________________ > > Koha mailing list http://koha-community.org > > Koha(a)lists.katipo.co.nz > > https://lists.katipo.co.nz/mailman/listinfo/koha > > > > ------------------------------ > > Message: 7 > Date: Wed, 1 Nov 2017 13:10:11 +0100 > From: Katrin Fischer <katrin.fischer.83(a)web.de> > To: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] opac search > Message-ID: <63dd17cf-911e-5c65-8dd6-581d5e7b31f1(a)web.de> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi Erlanda, > > attachments can't be send to the list. Can you upload your photos > somewhere or provide a link to your OPAC with a sample search that shows > the problem? > > Katrin > > > On 12.10.2017 10:22, Erlanda Simonyan wrote: > > Dear list, > > We have some problems in opac search in koha 17.05. > > When we search for a keyword and from the result page and the column of > "refine your search" we clikck on any author's name that contains a > hyphen, for example > > a.. ???-???????????, ??????? , we get no result . See photos attached. > > b.. Thanks > > a.. > > _______________________________________________ > > Koha mailing list http://koha-community.org > > Koha(a)lists.katipo.co.nz > > https://lists.katipo.co.nz/mailman/listinfo/koha > > > > ------------------------------ > > Message: 8 > Date: Wed, 1 Nov 2017 17:22:20 -0500 > From: Ricardo Ruiz <rickx1(a)gmail.com> > To: koha(a)lists.katipo.co.nz > Subject: [Koha] Zebra question > Message-ID: > <CAK--UHKZ8UR18sQNnSdP8tf-s81N3vL1=952XXA_VpjhJ75qfg@ > mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hi All, > > When I try to connect using the yaz-client using the following command: > yaz-client unix:/var/run/koha/zebradb/bibliosocket > > I get the following error message: > > Connecting ... OK. > Sent initrequest. > Connection rejected by v3 target. > ID: 81 > Name: Zebra Information Server / GFS / YAZ > Version: 2.0.61 / 5.15.2 738b345708b245e67cded6d917393a80b5bd4eca > Init response contains 1 otherInfo unit: > 1: otherInfo unit contains 1 diagnostic: > 1: code = 1011 (Init / AC: Bad Userid and / or Password), > addinfo = '' > Options: search present of the Set triggerResourceCtrl scan sort > extendedServices namedResultSets > Elapsed: 0.001331 > Z> > > Where can I verify the Zebra username and password? > > > Thanks, > Ricardo > ____________________________________________________________________ > > > <http://www.avg.com/email-signature?utm_medium=email& > utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Libre > de virus. www.avg.com > <http://www.avg.com/email-signature?utm_medium=email& > utm_source=link&utm_campaign=sig-email&utm_content=webmail> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > > ------------------------------ > > 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 145, Issue 3 > ************************************ >

2 1

opac search
by Erlanda Simonyan 01 Nov '17

01 Nov '17

Dear list, We have some problems in opac search in koha 17.05. When we search for a keyword and from the result page and the column of "refine your search" we clikck on any author's name that contains a hyphen, for example a.. ???-???????????, ??????? , we get no result . See photos attached. b.. Thanks a..

2 1

Azure Active Directory
by Bob Birchall 01 Nov '17

01 Nov '17

Has anybody integrated Koha with Azure Active Directory, using Koha's LDAP capability? We understand that the client's wish is to update users and fields in Koha from the AAD, not just check credentials. Any documentation you can point us to? Thanks, Bob Birchall Calyx

2 1

Haunted by ghost records
by Charlotte Stock 01 Nov '17

01 Nov '17

Recently I imported a large batch of records, but when I ran a search not all of the records had loaded so I deleted the batch and reimported. Now, when I run a search, the results list the 'deleted' batch and then the reimported batch, which means that users instinctively select from the first batch of results - all of which display the message "The record you requested does not exist" when selected. When I enter the record numbers of the failed entries to perform a batch deletion, this message displays 'The biblionumber does not exist in the database'. My question is how do I remove these ghost records so that they do not appear in OPAC searches, as users will quickly give up if the first page of results are all failed records? Thankyou in advance for your advice Charlotte -- Charlotte Stock - Digital Librarian Halcyon London International School -- *Halcyon London International School* 33 Seymour Place, London W1H 5AU +44 (0)20 7258 1169 <http://halcyonschool.com/?utm_source=email%20footer&utm_medium=email> [image: http://halcyonschool.com/visit] <http://halcyonschool.com/visit?utm_source=email%20footer&utm_medium=email> <https://www.facebook.com/HalcyonLondonInternationalSchool?utm_source=email%…> <http://www.linkedin.com/company/halcyon-london-international-school?utm_sou…> <https://mydonate.bt.com/charities/halcyonlondoninternationalschool?utm_sour…> <https://twitter.com/HalcyonSchool?utm_source=email%20footer&utm_medium=email>

2 1

Koha enhancement request
by Manju N 01 Nov '17

01 Nov '17

Dear All, Anyone has customized the Koha for multiple level approvals of suggested titles from the patrons/faculty in Acquisition module? In our library, we need multiple level approvals such as from the Head of Department and Chairman, Library Committee/etc. We want to use multiple levels late fee/fine slab. Currently, Koha supports only one late fee slab. We would appreciate any comments or suggestions that will help us to tweak the koha. We want to restrict 'hold' only for checked out items. Option required at circulation and fine rules: Allow hold only for checked out items Alert message required for checked in items if there is any hold on such items to keep those hold item separately at counter without sending for shelving. We would appreciate any comments or suggestions to change the Koha to meet the above requirements. With Regards Manju Naika,PhD Asst.Librarian,IITB

2 1

Koha hosting through Port forwarding VPS
by Ashok Francis 31 Oct '17

31 Oct '17

Dear Library Professionals, I would like to share a happy news that I have successfully hosted library opac and staff client in internet through "port forwarding" VPS network. Port forwarding is a important tool in every broadband network like Binatone 300 mbps VDSL router, Dlink router., etc., I have set Library LAN's IP address and koha staff client and opac's port number in port forwarding. After that I have checked my public IP address in google. After getting the public IP address, I typed public IP address with koha opac port number in the browser. Now it is working in worldwide. We can access our library from anywhere in the world. It is completely free of cost. You can use this tool for VPS. Here is my library opac and staff client. https://good-samaritan-school.com/library/ <https://good-samaritan-school.com/library/> I would like to give credits to Sunitha Barve madam who had encouraged me very well. She is very good library professional. Thank you Madam. Sincerely, Ashok Francis

1 0

Fwd: Inventory "problem" column definitions
by Caroline Cyr-La-Rose 31 Oct '17

31 Oct '17

Hello all, I'm trying to figure out what the "problems" in my inventory output mean. I'm using the barcode file input and the CSV output with Koha 16.05. I extrapolated some definitions, but I can't figure out "item not scanned" and "change item status". Please don't hesitate to correct my definitions if they are wrong! * missing item: item is in the database, but not in the barcode file * barcode not found: barcode is not in the database * wrong place: item should be in another location * item not scanned: item is in the database, but not in the barcode file (what is the difference between this and "missing item"?) * change item status: ?? Are there other "problems" other than these five? I will make sure to add the definitions to the wiki, since they are not there nor in the manual. Thanks everybody! Caroline Cyr La Rose, MLIS Head of training and support, inLibro

2 3

DBMS_auto_increment : cannot check-in items checked out before a certain upgrade
by Giuseppe Angilella 31 Oct '17

31 Oct '17

Hi, I am running Koha 17.05.05.000 on Ubuntu 14.04.1 with mysql Ver 14.14 Distrib 5.5.58. I regularly upgrade Koha via apt-get, and I've suddenly realized I cannot check-in items which had been checked-out (presumably before a certain upgrade). I can check-in items which have been checked-out with the presently installed release of Koha. Following the error message, I came across the wiki page: https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix I followed the instructions given there, and added the additional init file as described there. No error reported by /var/log/mysql/error.log upon restarting or running the mysql service. However, I cannot yet check-in back items which were checked-out in the past. (I can still do that with new check-outs.) Since it seems that the problem is solved with new check-outs, would you recommend that I manually remove old check-outs from the database, and issue them again (with a new date - doesn't matter, as long as it works)? Many thanks and best regards, Giuseppe.

3 2

Just a test
by Jonathan Druart 31 Oct '17

31 Oct '17

Is this mailing-list working? Koha is not working, what can I do?

2 1