- Koha - lists.katipo.co.nz

Wrong Username Password Koha 19.11 web installer Ubuntu 18.0.4.3 ?
by Clogher Historical Society 03 Feb '20

03 Feb '20

Hi, I'm having some trouble getting Koha up and running, I'm following the installation guide from https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages . I'm having problems with the username and password. I need to go through the final installation steps but I cannot log in - it says username and password are incorrect. I used the username and password in /etc/koha/sites/library/koha-conf.xml and used: sudo xmlstarlet sel -t -v 'yazgfs/config/pass' /etc/koha/sites/library/koha-conf.xml;echo Why is this password not accepted? Before this install I had to delete Koha and reinstall. I couldn't log in after I completed the final configuration steps where I created the new user and password. I got a Username Password incorrect when I know what I typed in. How can I log in to Koha? Do you think there is some form of corruption somewhere? I have had to delete Koha and reinstall a few times and maybe there is some mix up with the database or username password. Many thanks for the help !

2 1

koha-US meetings: February 2020
by Jason Robb 03 Feb '20

03 Feb '20

*All Zoom links have been updated to use the new koha-US organizational Zoom account. Please update any bookmarks of past meeting links.* *Upcoming meetings:* *koha-US board meeting:* Date: Wednesday, February 5th Time: 8:30am PT / 9:30am MT / 10:30am CT / 11:30am ET (time converter <https://www.timeanddate.com/worldclock/fixedtime.html?msg=koha-us+board+mee…> ) Meeting link: https://zoom.us/j/293750042 Agenda: https://docs.google.com/document/d/1ScNoxbLMwMMeEiVyLWwnr6s9916kegibwgEK01Y… *koha-US general meeting:* Date: Wednesday, February 12th Time: 8:30am PT / 9:30am MT / 10:30am CT / 11:30am ET (time converter <https://www.timeanddate.com/worldclock/fixedtime.html?msg=koha-US+general+m…>) Meeting link: https://zoom.us/j/648572897 View additional upcoming meetings and events on our Google calendar: https://calendar.google.com/calendar/embed?src=koha-us.org_dmqojds19fu8l8bd… koha-US meetings are open to any and all. Meetings are held via Zoom video conferencing. A microphone and camera are recommended but not required. Zoom is available for Windows, Mac, and Linux on desktops and Android and iOS on mobile devices. For help getting started, visit: *https://support.zoom.us/hc/en-us/categories/200101697 <https://support.zoom.us/hc/en-us/categories/200101697>* If you have topics for discussion at either meeting, please send them to secretary(a)koha-us.org. Jason Robb koha-US secretary secretary(a)koha-us.org

1 0

Wiki down?
by George 03 Feb '20

03 Feb '20

Is it just me, or is the community wiki down? George -- George Williams Next Search Catalog Coordinator Send NEXT support e-mails to nexthelp(a)nekls.org NEKLS Office: 785-838-4090 Toll Free: 888-296-6963 Fax: 785-838-3989 Next After-Hours: 785-813-1356 For specific support issues, please use: Next Catalog Support: nexthelp(a)nekls.org Courier Support: chandwork(a)nekls.org Technology Support: tech(a)nekls.org 4317 W 6th St, Lawrence, KS, 66049

3 3

Re: [Koha] Koha Digest, Vol 172, Issue 2
by adil ahmad ahmad 03 Feb '20

03 Feb '20

Please tell me that Koha stand for On Sun, Feb 2, 2020, 04:00 <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. Koha Community Newsletter: January 2020 (kohanews) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 31 Jan 2020 19:08:50 -0800 > From: kohanews <kohanews(a)gmail.com> > To: koha-devel(a)lists.koha-community.org, koha(a)lists.katipo.co.nz > Subject: [Koha] Koha Community Newsletter: January 2020 > Message-ID: <884cef58-ebbf-7614-f483-c8a17a0bdc7e(a)gmail.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > The Koha Community Newsletter for January 2020 is here: > https://koha-community.org/koha-community-newsletter-january-2020/ > > Many thanks to the folks who submitted articles and news to this month's > newsletter. > > Please feel free to email me with any corrections or suggestions. > > -- > Chad Roseburg > Editor, Koha Community Newsletter > > > > ------------------------------ > > 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 172, Issue 2 > ************************************ >

1 0

Koha Community Newsletter: January 2020
by kohanews 01 Feb '20

01 Feb '20

The Koha Community Newsletter for January 2020 is here: https://koha-community.org/koha-community-newsletter-january-2020/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Elasticsearch recent works at BibLibre
by Claire Hernandez 31 Jan '20

31 Jan '20

Hi, This week, some devs work together to move forward concretely on Elasticsearch issues encountered. You will find below a focus on some points (some are at poc state today) written by Alex and Jajm from BibLibre. We would be glad to discuss these topics at hackfest in march and having user feedbacks too :) #1 Proof of concept for language analyzers bug 21357 - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21357#c32 It's an attempt at having a default ES configuration with stemming, elision, etc. that works with multi-languages catalogs You can read the comments and patch for more information. #2 Compatibilites for tomorrow Compatibility with latest version of Search::Elasticsearch - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24552 Compatibility with Elasticsearch 7.x : Problem: Search::Elasticsearch is not yet compatible with ES 7.x, so we are stuck with ES 6.x (unless we use something else...) #3 Querying Elasticsearch in a better way POC query_string => boolean query https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24555 This POC is about replacing the use of full text queries (query_string) with Boolean queries for biblio search Advantage: => No search craches with special character ( "!", ")" etc...) => Separate query context and filter context: - Search scores are not altered by facets, - Ability to use range filter (i.e for publication date facet) Regards, Claire.

2 1

Status "in transit" after checking in
by Michael Kuhn 31 Jan '20

31 Jan '20

Hi Our library is financed by two organisations. Thus we have one Koha 18.11 instance with two separate branches, but only one circulation counter where we are checking in the items. Say we are logged in at the counter with branch A and checking in an item belonging to branch B - this will result in the following status message for the item: "In transit from branch A to branch B since 26/01/2020". To set this status to "Available" we need to log in as branch B and to check in the item once more. We would better like if the status could just go to "Available" since in fact there is no transport necessary. After some fruitless reading of the manual I came up with the idea to just delete the content of table "branchtransfers" every minute via cronjob: DELETE FROM branchtransfers; The status is then "Available", as desired. Is this possible/advisable, or do you know a better way? 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

2 1

double fines
by Margo Duncan 31 Jan '20

31 Jan '20

Good afternoon, Recently we have some patrons that are being double charged fines. It looks like when the item is turned in, the accruing fine (FU) remains and a fine (F) for the same amount is added as a second line. It doesn't appear to be happening to all patrons and I cannot determine a pattern. We are on version 18.11.02. Has anyone had this problem? Or any suggestions where to start looking? Thank you! Margo Margo Duncan, MLS Head of Library Systems Robert R. Muntz Library The University of Texas at Tyler 903.566.7174 | mduncan(a)uttyler.edu<mailto:mduncan@uttyler.edu>

8 13

Re: [Koha] Cover image not shown in opac search result but biblio detail
by Alvaro Cornejo 30 Jan '20

30 Jan '20

Hi Katrin I dissabled all cover images except for local covers and the result is the same. For some biblios the cover does only show in the detail page and not in the search results page. Any idea of what can happen? Is there maybe a size limit for the image/thumbnail? Regards Alvaaro |-----------------------------------------------------------------------------------------------------------------| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.com Le mer. 29 janv. 2020 à 16:42, Alvaro Cornejo <cornejo.alvaro(a)gmail.com> a écrit : > Hi Katrin > > Thanks for your answer. > > I'll try disabling all cover services and removing all custom css & js. > > We have Amazon and Google covers activated. > > Regards, > > Alvaro > > > |-----------------------------------------------------------------------------------------------------------------| > Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier > celular y Nextel > en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS > y GPRS online > Visitenos en www.perusms.com > > > Le mer. 29 janv. 2020 à 16:09, Katrin Fischer <katrin.fischer.83(a)web.de> > a écrit : > >> Hi Alvaro, >> >> the local cover images are stored in the database and are not >> represented in the MARC record. I'd try to remove all user specific >> JavaScript and CSS for a first test if that fixes the problem. Do you >> have other cover services activated? >> >> Katrin >> >> On 29.01.20 02:56, Alvaro Cornejo wrote: >> > Hi >> > >> > I´m running koha 19.11.002 and noticed that the opac search result does >> not >> > show biblio some cover images; however biblio detail show it. On the >> > intranet, image is shown in both, the search page and the biblio detail. >> > >> > I´ve checked all cover system preferences but found nothing that can >> help. >> > >> > In usercss I only add a line to remove ¨no cover image¨ >> > /* Hide the no image found image */ >> > .no-image { display: none !important; } >> > >> > If I remove that line, the no image icon appears for a couple of >> > seconds and then disappears >> > >> > A side question, where are the local images stored? is there a marc >> > record for that? >> > >> > Any ideas? >> > >> > Regards >> > >> > Alvaro >> > >> > >> |-----------------------------------------------------------------------------------------------------------------| >> > Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier >> > celular y Nextel >> > en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via >> SMS >> > y GPRS online >> > Visitenos en www.perusms.com >> > _______________________________________________ >> > Koha mailing list http://koha-community.org >> > Koha(a)lists.katipo.co.nz >> > https://lists.katipo.co.nz/mailman/listinfo/koha >> >

2 1

(PTFS customer) Bywater recalls plugin configured but staff side recall item symbol not showing on 18.11
by Perks, Emma (UNIVERSITY HOSPITALS BIRMINGHAM NHS FOUNDATION TRUST) 30 Jan '20

30 Jan '20

?Hello, We have the item recalls plugin version 1.0.26 installed and recall rules set up. The circulation rules are set up for item level holds and hold notices are ending with the reserves.reserve_id code. On the staff client when an item is checked out with an item level hold placed, there isn't a manual recall button anywhere on the patron record. My vendor PTFS cannot support the plugin and I cannot verify whether we have the code added to the Apache config. ? ?Does anyone know what needs to be done to display the manual recall button? Many thanks, Kind rgeards, Emma Perks Area Systems Librarian Tel: +44 (0) 121 424 9824 Email 1: baselibrary.consortium(a)nhs.net<mailto:emma.perks@heartofengland.nhs.uk> Email 2: emma.perks(a)heartofengland.nhs.uk<mailto:emma.perks@heartofengland.nhs.uk> Web: http://www.base-library.nhs.uk BASE Library Consortium ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in relation to its contents. To do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland. NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and other accredited email services. For more information and to find out how you can switch, https://portal.nhs.net/help/joiningnhsmail

2 4