I installed the Koha latest version and after installation this isn't showing icons on desktop . On Nov 2, 2017 3:22 AM, <[email protected]> wrote:
> Send Koha mailing list submissions to > [email protected] > > 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 > [email protected] > > You can reach the person managing the list at > [email protected] > > 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 <[email protected]> > To: Manju N <[email protected]> > Cc: Koha <[email protected]> > Subject: Re: [Koha] Koha enhancement request > Message-ID: > <CAGLUwiTVW-xK8r2wa_XzViWryGENQyuwV7YcjF9VWSwK-=Sp > [email protected]> > 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 <[email protected]> > 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 > > [email protected] > > https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > ------------------------------ > > Message: 2 > Date: Wed, 1 Nov 2017 08:56:14 +0000 > From: Charlotte Stock <[email protected]> > To: [email protected] > Subject: [Koha] Haunted by ghost records > Message-ID: > <CACBO8BqXeQuDTG+0a7tba8AqOyOHa19uiOo4rnQg_ > [email protected]> > 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 <[email protected]> > To: [email protected] > Subject: Re: [Koha] Catalog Search Relevance Ranking > Message-ID: <[email protected]> > 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 [email protected] · W www.adminkuhn.ch > > > ------------------------------ > > Message: 4 > Date: Wed, 1 Nov 2017 11:28:10 +0100 > From: Katrin Fischer <[email protected]> > To: [email protected] > Subject: Re: [Koha] Haunted by ghost records > Message-ID: <[email protected]> > 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 <[email protected]> > To: [email protected] > Subject: Re: [Koha] Catalog Search Relevance Ranking / Dead link in > manual > Message-ID: <[email protected]> > 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 <[email protected]> > To: [email protected] > Subject: Re: [Koha] Azure Active Directory > Message-ID: <[email protected]> > 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 > > [email protected] > > https://lists.katipo.co.nz/mailman/listinfo/koha > > > > ------------------------------ > > Message: 7 > Date: Wed, 1 Nov 2017 13:10:11 +0100 > From: Katrin Fischer <[email protected]> > To: [email protected] > Subject: Re: [Koha] opac search > Message-ID: <[email protected]> > 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 > > [email protected] > > https://lists.katipo.co.nz/mailman/listinfo/koha > > > > ------------------------------ > > Message: 8 > Date: Wed, 1 Nov 2017 17:22:20 -0500 > From: Ricardo Ruiz <[email protected]> > To: [email protected] > 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 > [email protected] > https://lists.katipo.co.nz/mailman/listinfo/koha > > > ------------------------------ > > End of Koha Digest, Vol 145, Issue 3 > ************************************ > _______________________________________________ Koha mailing list http://koha-community.org [email protected] https://lists.katipo.co.nz/mailman/listinfo/koha
