- Koha - lists.katipo.co.nz

Making AUTO_RENEWALS a digest email. Funding issues.
by Raymund Delahunty 26 Apr '19

26 Apr '19

University of the Arts London is also interested in having AUTO_RENEWALS made (optionally?) a digest notice, and we have contacted Bywater Solutions suggesting this development proposal be added to their Crowd Sourcing page in the hope the idea will attract additional funding contributors. If this problem were to be solved the only remaining problem preventing us from using auto-renewals (without our workaround) would be the "spamming" email problem described in 19014<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19014>. We will be testing the patches held in that bug report to see their effect in the coming days. Ray Delahunty University of the Arts London r.delahunty(a)arts.ac.uk<mailto:r.delahunty@arts.ac.uk> ----- Message: 4 Date: Tue, 9 Apr 2019 20:01:12 +0000 From: "Johnson, Barbara" <Barbara.Johnson(a)bedfordtx.gov<mailto:Barbara.Johnson@bedfordtx.gov>> To: "koha(a)lists.katipo.co.nz<mailto:koha@lists.katipo.co.nz>" <koha(a)lists.katipo.co.nz<mailto:koha@lists.katipo.co.nz>> Subject: [Koha] Development idea - Create digest option for auto renewal notices Hi everyone, Bedford is considering a development that would create a digest option for auto renewal notices in order to send only one digest notice instead of a separate renewal notices for every single title. ByWater provided a quote of $5,000. The development would be based on bug #18532 (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18532) which would create auto renewal notices as a patron messaging preference that would include a digest option. We'd love to hear from other libraries that could help fund this development, even if it is only a small amount. Thanks, Barbara -- Barbara Johnson Library Technical Services Manager Bedford Public Library 2424 Forest Ridge Drive, Bedford, TX 76021-4667 Office: 817-952-2360 | Fax: 817-952-2396 | Barbara.Johnson(a)bedfordtx.gov<mailto:Barbara.Johnson@bedfordtx.gov> This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of UAL Short Courses Limited the following also applies: UAL Short Courses Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY

1 0

SQL for report on items Catalouged by each librarian per period
by Akin Adigun (Akinomatics) 26 Apr '19

26 Apr '19

Hello pls i need ur help, i want an sql query for report to generate the number of books calalogued by all librarians, but i am finding it difficult becos acquisition librarian is always the one entering the biblio in our case since all materials must pass through acquisitions.

2 1

Re: [Koha] Koha Digest, Vol 162, Issue 21
by Akin Adigun (Akinomatics) 25 Apr '19

25 Apr '19

Hello pls i need ur help, can anyone help me out, i want an sql query for report to generate the number of books calalogued by all librarians, but i am finding it difficult becos acquisition librarian is always the one entering the biblio in our case since all materials must pass through acquisitions. I am using Koha 18.11 on Debian 9 thanks On Thursday, April 25, 2019, 1:14:24 AM GMT+1, koha-request(a)lists.katipo.co.nz <koha-request(a)lists.katipo.co.nz> wrote: This message is eligible for Automatic Cleanup! (koha-request(a)lists.katipo.co.nz) Add cleanup rule | More info 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. Clear Holiday Calendar (Charles Kelley) 2. Re: Clear Holiday Calendar (Owen Leonard) 3. Re: Clear Holiday Calendar (Alvaro Cornejo) 4. Re: Koha 17.05 randomly repeating an earlier transaction. (Jonathan Druart) ---------------------------------------------------------------------- Message: 1 Date: Wed, 24 Apr 2019 22:27:53 +0900 From: Charles Kelley <cmkelleymls(a)gmail.com> To: Discussion Group Koha <koha(a)lists.katipo.co.nz> Subject: [Koha] Clear Holiday Calendar Message-ID: <CAM8F7wrYBRiSk=gVLCpjLgGUOPhEQt0o_-vKcEqZNTdJ5ahjcA(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Hello, all I made an irrecoverable error when I made a holiday for U.S. Memorial Day: I made the holiday perpetual on everyday. Now I cannot delete the holiday. How do I clear this? It's a demo, so no great harm has been done. But I don't want to reload the demo from scratch. If there is no way to clear the holiday calendar, then I have a feature request into Koha developers. Thank you for your help in this matter. -- -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 1-301-741-7122 [US cell] 011-80-81-4714-5490 [JPN cell] mnogojazyk(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually. ------------------------------ Message: 2 Date: Wed, 24 Apr 2019 09:46:16 -0400 From: Owen Leonard <oleonard(a)myacpl.org> To: Discussion Group Koha <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Clear Holiday Calendar Message-ID: <CAO4qe2N71Uc49WrE9-fQuOZWnHfLhWrGRO44qj-R_vuwdZ8F=w(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" > Now I cannot delete the holiday. Do you not see how to delete the holiday or are you trying to delete and it isn't working? If it is the latter, is there some error message associated with the failure? -- Owen -- Web Developer Athens County Public Libraries https://www.myacpl.org ------------------------------ Message: 3 Date: Wed, 24 Apr 2019 08:55:11 -0500 From: Alvaro Cornejo <cornejo.alvaro(a)gmail.com> To: Charles Kelley <cmkelleymls(a)gmail.com> Cc: Discussion Group Koha <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Clear Holiday Calendar Message-ID: <CAO55aG8jotaYqteLaXQb31-uagD1g1-v3R4DT4Oi3woXSB==DA(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Hi Charles If the holiiday editor does not work you can manually edit the database. There are two holliday related tables: special_holidays <http://schema.koha-community.org/18_11/tables/special_holidays.html> and repeatable_holidays <http://schema.koha-community.org/18_11/tables/repeatable_holidays.html> you can access them an delete the faulty record manually. 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. 24 avr. 2019 à 08:29, Charles Kelley <cmkelleymls(a)gmail.com> a écrit : > Hello, all > > I made an irrecoverable error when I made a holiday for U.S. Memorial > Day: I made the holiday perpetual on everyday. Now I cannot delete the > holiday. How do I clear this? It's a demo, so no great harm has been done. > But I don't want to reload the demo from scratch. > > If there is no way to clear the holiday calendar, then I have a feature > request into Koha developers. > > Thank you for your help in this matter. > > -- > -- Charles. > > Charles Kelley, MLS > PSC 704 Box 1029 > APO AP 96338 > > 1-301-741-7122 [US cell] > 011-80-81-4714-5490 [JPN cell] > > mnogojazyk(a)aol.com [h] > cmkelleymls(a)gmail.com [p] > > linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> > Meeting Your Information Needs. Virtually. > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > ------------------------------ Message: 4 Date: Wed, 24 Apr 2019 19:04:39 -0400 From: Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> To: Raymund Delahunty <r.delahunty(a)arts.ac.uk> Cc: koha <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Koha 17.05 randomly repeating an earlier transaction. Message-ID: <CAJzKNY4G4EbipzBHX=D-joHfjh6_YuVCwS4zE1fR0eAyu-W++w(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Hi Raymund, I would also check the access logs around this timestamp. Regards, Jonathan Le ven. 12 avr. 2019 à 03:29, Raymund Delahunty <r.delahunty(a)arts.ac.uk> a écrit : > > We have recently had two examples of what appears to be Koha issuing an item to a reader “by itself” without any staff member doing the operation. Both took place at the same library site, and same issue desk, but different staff users logged on. We are multi-site, multi-issue desk, with heavy use of self-issue, but the problem is only reported (so far) using Circulation (so no SIP2 traffic), and at the one location. Yesterday we received this: > “This morning Koha decided to randomly issue an item to a student. The student wasn't present- she only emailed us once she had automatic notification of her borrowing the item. The item was issued at 10:13 today. This never happened. We still have the item in our cupboard. It looks like Koha duplicated the student's previous transaction that had taken place a couple of days earlier. Neither of us on the desk issued the item, or remember anything unusual. Could it be that when we logged into Koha, it had that transaction still in its memory somehow????”) > Our support company have advised: “We have investigated this transaction in the logs but there isn't anything to indicate what might have happened. It is recorded as a checkout in the standard way. > | 29319123 | 2019-04-09 10:13:04 | 341304 | CIRCULATION | ISSUE | 370312 | 1407873 > I'm afraid there isn't very much more we can do regarding this […]” > The previous example was sort-of similar- a laptop was returned by a user and it was *immediately* issued to a staff member who had borrowed (and returned) the item *the previous day*. She immediately complained that she was at her office, and away from the library, and had NOT borrowed the laptop. > Has anyone experience this? Any ideas what we should look for? Thanks for any suggestions. > Ray Delahunty > University of the Arts London > This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of UAL Short Courses Limited the following also applies: UAL Short Courses Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha ------------------------------ 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 162, Issue 21 *************************************

1 0

List of Item By Item Category
by ikbar 25 Apr '19

25 Apr '19

Hi all need some help Can you help me to get List of Item By Item Category in koha use saved SQL query. im asking this because im zero in IT but my boss gives me this task. Sorry for disturbing you but im really need help Tq for advance -- Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html

2 2

List of Item By Item Category
by ikbar 25 Apr '19

25 Apr '19

Hi all Need some help Can you help me to get List of Item By Item Category in koha use saved SQL query. im asking this because im zero in IT but my boss gives me this task. Sorry for disturbing you but im really need help Tq foa advance -- Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html

1 0

Koha 17.05 randomly repeating an earlier transaction.
by Raymund Delahunty 25 Apr '19

25 Apr '19

We have recently had two examples of what appears to be Koha issuing an item to a reader “by itself” without any staff member doing the operation. Both took place at the same library site, and same issue desk, but different staff users logged on. We are multi-site, multi-issue desk, with heavy use of self-issue, but the problem is only reported (so far) using Circulation (so no SIP2 traffic), and at the one location. Yesterday we received this: “This morning Koha decided to randomly issue an item to a student. The student wasn't present- she only emailed us once she had automatic notification of her borrowing the item. The item was issued at 10:13 today. This never happened. We still have the item in our cupboard. It looks like Koha duplicated the student's previous transaction that had taken place a couple of days earlier. Neither of us on the desk issued the item, or remember anything unusual. Could it be that when we logged into Koha, it had that transaction still in its memory somehow????”) Our support company have advised: “We have investigated this transaction in the logs but there isn't anything to indicate what might have happened. It is recorded as a checkout in the standard way. | 29319123 | 2019-04-09 10:13:04 | 341304 | CIRCULATION | ISSUE | 370312 | 1407873 I'm afraid there isn't very much more we can do regarding this […]” The previous example was sort-of similar- a laptop was returned by a user and it was *immediately* issued to a staff member who had borrowed (and returned) the item *the previous day*. She immediately complained that she was at her office, and away from the library, and had NOT borrowed the laptop. Has anyone experience this? Any ideas what we should look for? Thanks for any suggestions. Ray Delahunty University of the Arts London This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of UAL Short Courses Limited the following also applies: UAL Short Courses Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY

3 2

(no subject)
by vijay kumar 23 Apr '19

23 Apr '19

Dear members, My library is transition to migrate from a proprietary softawre to Koha... Actually backup of prior ILS has been developed accordingly to support Koha-17.05.06 But any how, we have tried to import the sql file in koha-18.05.11. After some modification, we are able to import in koha-latest 1. I am sharing the errors during zebra indexing I need your valuable suggestion to modify and rectify the errors Thaks, With regards, Vijay Kumar koha@virtualBox:/home/vijay$ /usr/share/koha/bin/migration_tools/ rebuild_zebra.pl -b -a -r -v .item-level_itypes set but no itemtype set for item (13525) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 710. .item-level_itypes set but no itemtype set for item (13526) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 710. .item-level_itypes set but no itemtype set for item (13527) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 710. .item-level_itypes set but no itemtype set for item (13528) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 710. .item-level_itypes set but no itemtype set for item (13529) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 710. 12801................................................................................................. 12901................................................................................................. 13001................................................................................................. 13101................................................................................................. 13201................................................................................................. 13301................................................................................................. 13401................................................................................................. 13501......................................................................................... Records exported: 13590 ==================== REINDEXING zebra ==================== ==================== CLEANING ==================== ---------------------------------------------------------------------------------------------------------------------- This is the MARC field of a record ---------------------------------------------------------------------------------------------------------------------- LDR 00953 a2200421 4500 000 B3 001 023974 005 20190307155428.0 008 001 23974 010 _a 020 _a9788184242576 _cRS.1200.00 082 _a025 _bKOG 100 1 _aKoganuramath MM 245 1 _aLibrary and information science profession in the knowledge society _b _cM M Koganuramath, B D Kumber and B S Kedamani, ed. 246 1 _a 250 _a 260 _aNew Delhi _bAllied publishers _c2008 300 _axviii, 398p. _bill. 490 _a 500 _a 508 _a 600 _a 610 _a 611 _a 630 _a 650 _a 651 _a 653 _aLibrary science 653 _aDocumentation 654 _a 700 _aKumber, B D, ed. 700 _aKedamani, B S, ed. 856 _d _f _u 904 _a 951 _a 964 _a _b _c _d _e _f _g 965 _a 999 _c8553 _d8553

3 3

How to get statistic for borrowed item by borrower with department
by ikbar 23 Apr '19

23 Apr '19

Hi all master I need help with this matter where I need koha GUI sql script for:- A statistic for the borrowed item by a borrower with the department (if can do in the date range) tq for advance -- Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html

2 6

Koha cron job - Elasticsearch index updates
by C P Hong 22 Apr '19

22 Apr '19

Hello I am testing Elasticsearch in Koha 18.11. Is there a configuration in Koha to run cron job for Elasticsearch? I ask this question because I cannot find records of books by searching the catalog that I had cataloged recently into Koha. Similar to the above question. >From wiki -https://wiki.koha-community.org/wiki/Elasticsearch#Configuration do I need to run this command regularly for records that I entered into Koha? misc/search_tools/rebuild_elastic_search.pl -v -d Please let me know. Best Regards Chee

1 0

Adding Literary Form (008/33) to Advanced Search
by Craig Butosi 19 Apr '19

19 Apr '19

Hi all, Running 18.11.04 on Ubuntu 16.04.6 LTS. Has anyone added the 008/33 Literary Form index to their advanced search as a drop down menu (in the same manner as the Audience, Content, Format, Additional content types for books/printed materials indexes? If so, may I ask what the basic steps would be involved to do this? Many thanks, Craig Butosi, MA, MLIS, B Mus (Hons) Library: library.craigbutosi.ca

1 0