- Koha - lists.katipo.co.nz

-intra.mydomain
by Victor Barroso Oliveira 26 Sep '19

26 Sep '19

Good afternoon, I configured the koha admin interface to access on port 8080 but would like to access the admin interface with one from biblio-intra.mydomain How should I do this? Thanks, Victor

2 1

Email of Introduction -- Koha Support Provider
by Anthony Snell 25 Sep '19

25 Sep '19

Hello, we are requesting to be part of the Koha team as a Support Provider and be listed on your website under that area. Please let us know if there is additional information you are requiring for us to be successful in this venture. Company Name: Trident Consulting Firm, LLC Contact Person: Anthony Snell, Ph.D. Contact email: asnell(a)tridentcf.com Website: https://tridentcf.com and https://librarycare365.com Telephone: 803-447-8357

1 0

Koha 18.11.10 release
by Lucas Gass 25 Sep '19

25 Sep '19

The Koha community is proud to announce the release of Koha 19.05.04. This is a maintenance release. The full release notes are available at: https://koha-community.org/koha-18-11-10-release/ Debian packages will be up in a couple days. Cheers, -- Lucas Gass Web Developer ByWater Solutions

1 0

Integration points with Organisational ERP
by Bravismore Mumanyi 25 Sep '19

25 Sep '19

Dear Koha Community I would like to hear from university libraries using KOHA, on integration points they have achieved with the university-wide student/finance system with KOHA. e.g. When a student is registered on university ERP, a trigger creates or updates a matching record on Koha. When an order encumbers funds on koha, a trigger does the same on university's finance system. We have just been asked by our programming team what integration points we need and could only think of a few. Any integration experience outside a university system is welcome as well. Thank you Regards /Bravismore

2 1

Re: [Koha] SQL Reports on catalogue (list of books added/ entered date wise i.e today )
by Yatheesh lis 25 Sep '19

25 Sep '19

including barcode number and publisher i want can you send updated sql query On Wed, Sep 25, 2019 at 10:16 AM pandu rangaswamy <pandumlib(a)gmail.com> wrote: > > Sir, > > You can use the below SQL report, the result shows last 30 days added items. > > SELECT items.dateaccessioned,items.itemcallnumber,biblio.title,biblio.author > FROM items > LEFT JOIN biblioitems ON (items.biblioitemnumber=biblioitems.biblioitemnumber) > LEFT JOIN biblio ON (biblioitems.biblionumber=biblio.biblionumber) > WHERE items.homebranch=<<Home branch|branches>> AND DATE_SUB(CURDATE(),INTERVAL 30 DAY) <= items.dateaccessioned > ORDER BY biblio.title ASC > > On Wed, Sep 25, 2019 at 9:40 AM Yatheesh lis <yatheeshb(a)gmail.com> wrote: >> >> hi >> >> I would like generate the daily report list of books added / entered >> on particular date / (single day) >> kindly suggest sql query >> >> >> >> -- >> _______________________________________________ >> Koha mailing list http://koha-community.org >> Koha(a)lists.katipo.co.nz >> https://lists.katipo.co.nz/mailman/listinfo/koha > > > > -- > > ---------------------------------------------------------------------------- > > M. Panduranga Swamy > > +91 9664631017 > > ORCID > > ------------------------------------------------------------------------------ -- Y.Yatheesh Babu

1 0

SQL Reports on catalogue (list of books added/ entered date wise i.e today )
by Yatheesh lis 25 Sep '19

25 Sep '19

hi I would like generate the daily report list of books added / entered on particular date / (single day) kindly suggest sql query --

2 1

Re: [Koha] Help with a report query
by Kerrie Stevens 25 Sep '19

25 Sep '19

Adding to this report from Carlos below, we have multiple campuses so I'd love to be able to run the report for each campus. I've tried adding in: AND items.homebranch=<<Home branch|branches>> (copied from another report that I can select campuses) in various spots but I keep getting error messages - so I've obviously missed something important somwhere else. Where should I insert this or similar text in the search to be able to select which campus the results are from? SELECT monthname(datetime) month, type, count(datetime) as count FROM statistics WHERE YEAR(datetime) = <<year>> AND type IN ('issue', 'renew') GROUP BY month, type ORDER BY month(datetime) Thanks so much for your help! And thanks Carlos for a handy report. SQL is not my strong-point... Kerrie Stevens AALIA(CP), MAppSci(LibMgt), BBus(Info&LibMgt) Librarian – Melbourne Campus HDR Liaison Librarian ALPHACRUCIS COLLEGE ------------------------------ Message: 2 Date: Mon, 23 Sep 2019 21:17:25 -0700 From: Eric Phetteplace <ephetteplace(a)cca.edu> To: Carlos Lopez <clopez(a)dml.vic.edu.au> Cc: koha <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Help with a report query Message-ID: <CACSkZcYX_qWtUeMJ8bTcdQoaMEz8mm7Mhjni=Jg7hdnyRXhQEQ(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Hi Carlos, Your report is actually very close to doing that already. Since you're already limiting by year in your WHERE clause, you just need to change it to accept a parameter instead of using YEAR(NOW()). So this should do want you want: SELECT monthname(datetime) month, type, count(datetime) as count FROM statistics WHERE YEAR(datetime) = <<year>> AND type IN ('issue', 'renew') GROUP BY month, type ORDER BY month(datetime) That does literally what you asked—limit by a particular calendar year—but you could also limit to within a given date range by asking for two parameters and using a "BETWEEN" WHERE clause like you mentioned earlier. So that would be like: SELECT monthname(datetime) month, type, count(datetime) as count FROM statistics WHERE datetime BETWEEN <<start|date>> AND <<finish|date>> AND type IN ('issue', 'renew') GROUP BY month, type ORDER BY month(datetime) The "|date" bit there means that the reports module will expect date values for those parameters and thus provide a datepicker when people go to run the report. I will caution that I've been advised not to use the "statistics" table, though I don't entirely know why. I would've written this report using the issues and old_issues tables. Best, ERIC PHETTEPLACE Systems Librarian (he/him) ephetteplace(a)cca.edu | o 510.594.3660 5212 Broadway | Oakland, CA | 94618 :(){ :|: & };: On Mon, Sep 23, 2019 at 5:51 PM Carlos Lopez <clopez(a)dml.vic.edu.au> wrote: > Hi folks > > I have the following report query: > ---- > SELECT monthname(datetime) month, type, count(datetime) as count from > statistics where YEAR(datetime) = YEAR(NOW()) and type in ('issue', > 'renew') GROUP BY month, type ORDER BY month(datetime) > ---- > > This works well but I've been asked to provide a mechanism to select > the year to run this for (I would guess similar to the construct " > DATE > (b.dateexpiry) BETWEEN <<Between (yyyy-mm-dd)|date>> AND <<and > (yyyy-mm-dd)|date>>", except selecting only years) > > Is it possible to do this? And if so, how? > > > With kind regards from the Dalton McCaughey Library Team > > Carlos Lopez > > Dalton McCaughey Library | 29 College Crescent, Parkville, VICTORIA > 3052 > Ph: 03 9340 8888 ext.1 | library(a)dml.vic.edu.au | > library.dmlibrary.org.au > > _______________________________________________ > Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha >

2 1

Image for Koha on a Raspberry Pi now available!
by King, Fred 24 Sep '19

24 Sep '19

Esteemed Colleagues: I am delighted to say that I did indeed manage to get Koha working on a Raspberry Pi in time for my presentation at the koha-US conference last week in Pueblo, Colorado. The image is now available for download via the Avenging Chicken's web site. Go to www.avengingchicken.online<http://www.avengingchicken.online>, scroll down to the section Handbooks, Manuals, Etc. The installation has a Superlibrarian and minimal configuration, no items or bib records. Comments are welcome, either at this address or at koha(at)avengingchicken(dot)online. My slide show will be available once my eagle-eyed colleague has had a chance to proofread it. The next Adventure of Fred and the Avenging Chicken will be available once I recover from the conference and get caught up on things. Fred King, AHIP Medical Librarian, MedStar Washington Hospital Center fred.king(a)medstar.net<mailto:fred.king@medstar.net> 202-877-6670 ORCID 0000-0001-5266-0279 MedStar Authors Catalog: http://medstarauthors.org A library in the middle of a community is a cross between an emergency exit, a life-raft and a festival. They are cathedrals of the mind; hospitals of the soul; theme parks of the imagination. On a cold rainy island, they are the only sheltered public spaces where you are not a consumer, but a citizen instead. --Caitlin Moran ---------------------------------------------------------------------- MedStar Health is a not-for-profit, integrated healthcare delivery system, the largest in Maryland and the Washington, D.C., region. Nationally recognized for clinical quality in heart, orthopaedics, cancer and GI. IMPORTANT: This e-mail (including any attachments) may contain information that is private, confidential, or protected by attorney-client or other privilege. If you received this e-mail in error, please delete it from your system without copying it and notify sender by reply e-mail, so that our records can be corrected... Thank you. Help conserve valuable resources - only print this email if necessary.

1 0

How To Get Listed as Koha Support Provider
by Dileepa Rathnayake 24 Sep '19

24 Sep '19

Dear Team, We have been providing Koha support services including hosting, DB migration, various hardware integration including NFC technology. Would like to get listed as a Koha support service provider at below page. https://koha-community.org/support/paid-support/random/ Just wondering if this is the correct mailing list to send introduction information as instructed below. https://koha-community.org/support/paid-support/how-to-get-listed/ Aplogies if I have missed something. Kindly guide us to correct path if this is not the correct list. Best Regards, Dileepa On Thu, 19 Sep 2019 12:00:02 +1200 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. Auto increment/ Checkout & Checkin (Arshad Iqbal) > 2. Use of indicators in field 245 (Giacomo Visini) > 3. Re: Use of indicators in field 245 (Philippe Blouin) > 4. Re: Use of indicators in field 245 (Giacomo Visini) > 5. Re: Use of indicators in field 245 (Eric Phetteplace) > 6. How to make the Koha/Zebra search ignore hyphens? (Michael Kuhn) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 18 Sep 2019 12:00:02 +0500 > From: Arshad Iqbal <arshadsanwal(a)gmail.com> > To: Koha list <koha(a)lists.katipo.co.nz> > Subject: [Koha] Auto increment/ Checkout & Checkin > Message-ID: > <CABSgbwY81yrgvjT8WtuUwMHc-8AeckDv1Dr8+65hKBHt1R53_w(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hi to all > I am facing problem in circulation, an item checking out first time and > checking in , If I repeat this activity again, in repeating case auto > increment DBMS error clicking, login koha database via PHPMYADMIN, clean 0 > number from issue and old issue table. I have configured Auto increment > from koha wiki, but error is still coming. How to cope with this error? > > -- > > Best Regards > *Muhammad Arshad Iqbal* > *Assistant Librarian* > *NUST Central Library * > *National University of Science and Technology (NUST)* > *Sector H-12, Islamabad, Pakistan* > *Tel. Office:051-90851087* > *Cell no.+923444900809* > * +923004900159* > > > ------------------------------ > > Message: 2 > Date: Wed, 18 Sep 2019 07:06:50 +0000 > From: Giacomo Visini <Giacomo.VISINI(a)divaantwerp.be> > To: koha <koha(a)lists.katipo.co.nz> > Subject: [Koha] Use of indicators in field 245 > Message-ID: > <AM4P190MB00506315326CEC987E7A2D55EF8E0(a)AM4P190MB0050.EURP190.PROD.OUTLOOK.COM> > > Content-Type: text/plain; charset="us-ascii" > > Hi fellow Koha users, > > Just a quick question. Can someone shed a light on the use of the indicators in field 245? Since our conversion to Koha we stopped using them, but data from previous systems has these indicators filled in. Upon inspection, in most cases the given value is even wrong somehow (0's are 1's etc.). But it doesn't seem to affect indexation. > > So my question is, is there no need to fill in the indicators of field 245? Do you guys use them? For what purpose? > > For the sake of exhaustivity: we are currently using version 18.11.06.000 > > Thanks in advance for any replies. > > Kind regards, > > Giacomo Visini I Bibliotheekmedewerker > DIVA, Antwerp Home of Diamonds > Gildekamersstraat 9, B-2000 Antwerpen > T + 32 3 360 52 42 > giacomo.visini(a)divaantwerp.be<mailto:giacomo.visini@divaantwerp.be> > > > > ------------------------------ > > Message: 3 > Date: Wed, 18 Sep 2019 08:35:40 -0400 > From: Philippe Blouin <philippe.blouin(a)inlibro.com> > To: Giacomo Visini <Giacomo.VISINI(a)divaantwerp.be>, koha > <koha(a)lists.katipo.co.nz> > Subject: Re: [Koha] Use of indicators in field 245 > Message-ID: <531f8cd7-a133-0cef-f2e7-4d0f1de5dbec(a)inlibro.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > I'd need to check the index file, but normally ind2's use is to skip the > first X characters when ordering. Ex to skip "The" at the beginning of > a title. > > Philippe Blouin, > Directeur de la technologie > > Tél. : (833) 465-4276, poste 230 > philippe.blouin(a)inLibro.com <mailto:philippe.blouin@inLibro.com> > > inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com> > On 2019-09-18 3:06 a.m., Giacomo Visini wrote: > > Hi fellow Koha users, > > > > Just a quick question. Can someone shed a light on the use of the indicators in field 245? Since our conversion to Koha we stopped using them, but data from previous systems has these indicators filled in. Upon inspection, in most cases the given value is even wrong somehow (0's are 1's etc.). But it doesn't seem to affect indexation. > > > > So my question is, is there no need to fill in the indicators of field 245? Do you guys use them? For what purpose? > > > > For the sake of exhaustivity: we are currently using version 18.11.06.000 > > > > Thanks in advance for any replies. > > > > Kind regards, > > > > Giacomo Visini I Bibliotheekmedewerker > > DIVA, Antwerp Home of Diamonds > > Gildekamersstraat 9, B-2000 Antwerpen > > T + 32 3 360 52 42 > > giacomo.visini(a)divaantwerp.be<mailto:giacomo.visini@divaantwerp.be> > > > > _______________________________________________ > > 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, 18 Sep 2019 14:58:16 +0000 > From: Giacomo Visini <Giacomo.VISINI(a)divaantwerp.be> > To: Philippe Blouin <philippe.blouin(a)inlibro.com>, koha > <koha(a)lists.katipo.co.nz> > Subject: Re: [Koha] Use of indicators in field 245 > Message-ID: > <AM4P190MB005050E448B345E086F08AD7EF8E0(a)AM4P190MB0050.EURP190.PROD.OUTLOOK.COM> > > Content-Type: text/plain; charset="utf-8" > > Hi Philippe, > > Thanks for the reply! > > The second indicator in field 245, according to the MARC 21 rules, should indeed be used to skip possible articles (i.e. The, Le, La, Les, De, Het, etc.) when indexing. But in Koha, or in our case anyway, these indicators don’t seem to be working. Most of our records have the indicators filled in, but it doesn’t affect indexation. No characters are skipped, even if the second indicator is filled in. > > So my question is: what’s the point of filling in these indicators, if they don’t do what they are supposed to do? > > Are there any libraries in the Koha community who use the indicators of 245? And do the indicators do what they’re supposed to do? > > Again, thank you for any reply. > > Kind regards, > > Giacomo Visini I Bibliotheekmedewerker > DIVA, Antwerp Home of Diamonds > Gildekamersstraat 9, B-2000 Antwerpen > T + 32 3 360 52 42 > giacomo.visini(a)divaantwerp.be<mailto:giacomo.visini@divaantwerp.be> > > > Van: Philippe Blouin <philippe.blouin(a)inlibro.com> > Verzonden: woensdag 18 september 2019 14:36 > Aan: Giacomo Visini <Giacomo.VISINI(a)divaantwerp.be>; koha <koha(a)lists.katipo.co.nz> > Onderwerp: Re: [Koha] Use of indicators in field 245 > > > I'd need to check the index file, but normally ind2's use is to skip the first X characters when ordering. Ex to skip "The" at the beginning of a title. > Philippe Blouin, > Directeur de la technologie > > Tél. : (833) 465-4276, poste 230 > philippe.blouin(a)inLibro.com<mailto:philippe.blouin@inLibro.com> > inLibro | pour esprit libre | www.inLibro.com<http://www.inLibro.com> > On 2019-09-18 3:06 a.m., Giacomo Visini wrote: > > Hi fellow Koha users, > > > > Just a quick question. Can someone shed a light on the use of the indicators in field 245? Since our conversion to Koha we stopped using them, but data from previous systems has these indicators filled in. Upon inspection, in most cases the given value is even wrong somehow (0's are 1's etc.). But it doesn't seem to affect indexation. > > > > So my question is, is there no need to fill in the indicators of field 245? Do you guys use them? For what purpose? > > > > For the sake of exhaustivity: we are currently using version 18.11.06.000 > > > > Thanks in advance for any replies. > > > > Kind regards, > > > > Giacomo Visini I Bibliotheekmedewerker > > DIVA, Antwerp Home of Diamonds > > Gildekamersstraat 9, B-2000 Antwerpen > > T + 32 3 360 52 42 > > giacomo.visini(a)divaantwerp.be<mailto:giacomo.visini@divaantwerp.be><mailto:giacomo.visini@divaantwerp.be><mailto:giacomo.visini@divaantwerp.be> > > > > _______________________________________________ > > Koha mailing list http://koha-community.org > > Koha(a)lists.katipo.co.nz<mailto:Koha@lists.katipo.co.nz> > > https://lists.katipo.co.nz/mailman/listinfo/koha > > ------------------------------ > > Message: 5 > Date: Wed, 18 Sep 2019 09:55:10 -0700 > From: Eric Phetteplace <ephetteplace(a)cca.edu> > To: Giacomo Visini <Giacomo.VISINI(a)divaantwerp.be> > Cc: koha <koha(a)lists.katipo.co.nz> > Subject: Re: [Koha] Use of indicators in field 245 > Message-ID: > <CACSkZcYEn99kWAFCMnFuk_pjWQk_neG2rEdkWwy6+bbjH97p2Q(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hi Giacomo, > > You're right that the second indicator, nonfiling characters, doesn't > really seem to do anything. It's an archaic holdover and probably not > needed with the complicated indexing mechanisms that are available to us > now. It's pretty trivial for machines to skip leading stopwords like "the" > etc. without instruction. > > The first indicator is still meaningful, I believe. Having a main entry > under one of the 1XX fields and then a title added entry is enabled by this > indicator. So following this example documentation > <https://www.itsmarc.com/crs/mergedprojects/conser/conser/module_7_4__ccm.htm> > I found: > > 111 2# $a Federal Management Improvement Conference. > 245 10 $a Proceedings of the Federal Management Improvement Conference. > > The "title" of the serial is the name of the conference and the 245 is used > as an added entry. I'm not a cataloger so the function of a title added > entry isn't entirely clear to me but a lot (about half) of our records > have this indicator set to 1. > > So our records still use both indicators, however we mainly copy catalog. > It makes sense to keep using the fields especially when it's free like > this. Just because they don't have a lot of importance in Koha doesn't mean > another system won't care about them and it makes the data more consistent > with other MARC repositories. > > Best, > > ERIC PHETTEPLACE Systems Librarian (he/him) > > ephetteplace(a)cca.edu | o 510.594.3660 > > 5212 Broadway | Oakland, CA | 94618 > > :(){ :|: & };: > > > On Wed, Sep 18, 2019 at 12:07 AM Giacomo Visini < > Giacomo.VISINI(a)divaantwerp.be> wrote: > > > Hi fellow Koha users, > > > > Just a quick question. Can someone shed a light on the use of the > > indicators in field 245? Since our conversion to Koha we stopped using > > them, but data from previous systems has these indicators filled in. Upon > > inspection, in most cases the given value is even wrong somehow (0's are > > 1's etc.). But it doesn't seem to affect indexation. > > > > So my question is, is there no need to fill in the indicators of field > > 245? Do you guys use them? For what purpose? > > > > For the sake of exhaustivity: we are currently using version 18.11.06.000 > > > > Thanks in advance for any replies. > > > > Kind regards, > > > > Giacomo Visini I Bibliotheekmedewerker > > DIVA, Antwerp Home of Diamonds > > Gildekamersstraat 9, B-2000 Antwerpen > > T + 32 3 360 52 42 > > giacomo.visini(a)divaantwerp.be<mailto:giacomo.visini@divaantwerp.be> > > > > _______________________________________________ > > Koha mailing list http://koha-community.org > > Koha(a)lists.katipo.co.nz > > https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > ------------------------------ > > Message: 6 > Date: Wed, 18 Sep 2019 22:46:15 +0200 > From: Michael Kuhn <mik(a)adminkuhn.ch> > To: "Koha : access" <koha(a)lists.katipo.co.nz> > Subject: [Koha] How to make the Koha/Zebra search ignore hyphens? > Message-ID: <5b63f3b4-76c1-c1f8-f35a-6a33e3b0afa5(a)adminkuhn.ch> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi > > We have found that, at least in German, there are words or combinations > of words that can be written in different ways, and both are correct and > are meaning the same, e. g. > > * Ultraschallmessgerät = Ultraschall-Messgerät > * Sintiswing = Sinti-Swing > * Teeei = Tee-Ei > * Haftpflichtversicherungsgesellschaft = > Haftpflicht-Versicherungsgesellschaft > > This is a general concept in German, so it makes no sense to add a "used > for/see from:" in the authority data. Anyway, such words can exist > everywhere in the bibliographic record, not only in fields linked to > authority fields. > > Now the question: is there a way how to teach Koha (or Zebra) to look > for the second term also when the first term is searched, and vice > versa? Or shorter: Just to ignore the hyphens? Using the standard > configuration Koha will not find the second term if the first one is > searched, and vice bversa. > > We would appreciate any hint or tip! > > 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 > > > ------------------------------ > > 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 167, Issue 15 > *************************************

2 4

Koha 19.05.01 release
by Fridolin SOMERS 24 Sep '19

24 Sep '19

The Koha community is proud to announce the release of Koha 19.05.01. This is a maintenance release with 1 security bugfix. The full release notes are available at https://koha-community.org/koha-19-05-01-release/ Debian packages are available. After maintaining 17.11.x I'm proud to continue with actual stable version. I'm then looking forward to see "Koha 20". Regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre, France - software and system maintainer

3 5