Hi Katrin, We are pleased to convey our sincere appreciation for adding focuzinfotech to the esteemed roster of Koha Support Providers. Being acknowledged as a reliable contributor to the Koha community is a great privilege, and we are excited about the chance to provide our expertise and services to libraries and institutions around the globe who rely on Koha.
Regards Dixson On Sun, 2023-09-10 at 12:00 +1200, koha-requ...@lists.katipo.co.nz wrote: > Send Koha mailing list submissions to > koha@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-requ...@lists.katipo.co.nz > > You can reach the person managing the list at > koha-ow...@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: Request for Listing a Paid Service Provider, Texas, USA > based. (Katrin Fischer) > 2. Re: Request for Listing a Paid Support Service Provider > (Katrin Fischer) > 3. Re: check out problem in koha v23.05 (Katrin Fischer) > 4. Re: Format of Barcode (Katrin Fischer) > 5. Re: Has NFC vs. NFD encoding changed for Unicode in koha? > (Katrin Fischer) > 6. check out problem in koha v23.05 (Rudy Hinojosa) > > > ------------------------------------------------------------------- > --- > > Message: 1 > Date: Sat, 9 Sep 2023 14:46:43 +0200 > From: Katrin Fischer <katrin.fischer...@web.de> > To: koha@lists.katipo.co.nz > Subject: Re: [Koha] Request for Listing a Paid Service Provider, > Texas, USA based. > Message-ID: <17af4aa6-d58b-a1e9-564e-45ab35685...@web.de> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi Rudy, > > thx for taking on the feedback. I see that the spelling has been > fixed > and also found the link in your footer. Please consider linking the > words 'Koha community' - it's better for accessibility too :) > > I have added an entry for your company to the Koha support providers > list: > > https://koha-community.org/support/paid-support/country/#usa > > Katrin > > On 08.09.23 14:52, Rudy Hinojosa wrote: > > Company Name: Lightwave Library > > Contact Person: Rudy Hinojosa > > Contact Email: rudy.hinoj...@lightwavelibrary.com > > Website: https://LightwaveLibrary.com > <https://lightwavelibrary.com> > > Telephone: +1 737-372-7779 > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha@lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > ------------------------------ > > Message: 2 > Date: Sat, 9 Sep 2023 15:19:56 +0200 > From: Katrin Fischer <katrin.fischer...@web.de> > To: koha@lists.katipo.co.nz > Subject: Re: [Koha] Request for Listing a Paid Support Service > Provider > Message-ID: <9504b010-b0ef-9108-cc2d-f25c084f0...@web.de> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi Dixson, > > I have added your company to the Koha support providers list: > > https://koha-community.org/support/paid-support/country/#ind > > I found the link to Koha community behind "Learn More" at the top of > your page. Maybe consider to make it a little bit more obvious. > > Katrin > > On 07.09.23 09:26, support wrote: > > Dear Koha Community, > > > > > > > > Company Name: focuzinfotechI kindly request the addition of > focuzinfotech.com to the list of paid > > service providers on the Koha Community website. We are a company > based > > in Kerala, India, and specialize in offering a wide range of > services > > for Koha, including installation, customization, data migration, > > support, training, and cloud hosting, catering to clients across > all > > regions. We are proud to have successfully implemented and provided > > support to more than 300 + satisfied customers throughout India. > > > > > > Contact Person: Mr.Dixson Rodriges > > > > Contact email: supp...@focuzinfotech.com > > > > Website: https://www.kohaforyou.com > > https://www.focuzinfotech.com > > Telephone: +91 9249500540 , 0484-2805303 > > > > > > Thank you for considering our request. > > > > > > -- > > > > Thank you & Regards, > > > > > > Dixson Rodrigues > > Manager - IT Support & Service > > Focuz Infotech > > 41/161, N H Bye Pass > > Edappally, Kochi - 682024 > > Cell: +91-9249500540 > > Phone: +91 484 2805303 > > WhatsApp: +91-9249500540 > > > > > > > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha@lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > ------------------------------ > > Message: 3 > Date: Sat, 9 Sep 2023 15:21:57 +0200 > From: Katrin Fischer <katrin.fischer...@web.de> > To: zen zenitram <quickfir...@gmail.com> > Cc: koha@lists.katipo.co.nz > Subject: Re: [Koha] check out problem in koha v23.05 > Message-ID: <68277d4d-8d14-9124-64a6-921d1030d...@web.de> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi, > > other things you could check here: > > * Calendar: do you have holiday entries that could explain the > behaviour? > > * Circulation rules: do you have a hard due date set that could > explain? > > Hope this helps, > > Katrin > > On 07.09.23 05:44, zen zenitram wrote: > > The is expiry date is set to expire on December 17, 2023. Sometimes > > our server is slow,s to load and the same day due date shows. It > only > > happens after we update to KOHA v23.05 > > > > On Wed, Sep 6, 2023 at 7:11 PM Katrin Fischer > > <katrin.fischer...@web.de> wrote: > > > > Hi, > > > > could you check if the patrons are expired or expiring soon? > You'd > > also > > see this if the expiration date is empty. > > > > Hope this helps, > > > > Katrin > > > > On 03.09.23 07:21, zen zenitram wrote: > > > Good day! > > > > > > We encountered error while checking out books in our library > > using koha > > > v23.05. the circulation and fine rules is set to due in 6 > days, > > but when > > > someone borrowed the book the due becomes on the same date it > is > > borrowed. > > > It didnt happen before we upgraded our koha tp latest > version. > > > > > > Thank you! > > > _______________________________________________ > > > > > > Koha mailing list http://koha-community.org > > > Koha@lists.katipo.co.nz > > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha@lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > ------------------------------ > > Message: 4 > Date: Sat, 9 Sep 2023 15:24:44 +0200 > From: Katrin Fischer <katrin.fischer...@web.de> > To: koha@lists.katipo.co.nz > Subject: Re: [Koha] Format of Barcode > Message-ID: <10822405-0b7a-bea6-4928-6a4ebd1c0...@web.de> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi Kevin, > > the AutoBarcode feature looks at all barcodes in your system to > determines which is the next one to generate. If an unexpected number > is > generated and you feel it should be smaller still, check for any > 'unusual' existing barcodes that could explain the jump in numbers. > > Something like "select max(barcode) from items;" might reveal > something, > or also looking at the full list like "select barcode from items > order > by barcode". > > Hope this helps, > > Katrin > > On 06.09.23 17:37, Furst, Kevin wrote: > > Hello, > > > > I have an issue with how the next barcode displays when autofilled > when > > added a new item to a record. In my autobarode setting, I have > > EAN-Incremental 13 Barcode selected. When creating a new item for a > record, > > the system does autofill the barcode field however the formatting > however > > it shows up in scientific number format rather than just integers > or plain > > text. > > > > For example, A barcode we use should look like this: > > > > 345171000448832 > > > > However, in the form, it fills something like this: > > > > 3.45171000471993e+19 > > > > Converting that to a real number, I get 34517100047199300000 which > is too > > large/too many digits. I cannot just lop off the extra zeros. I > would like > > to understand how that service works and what to try to get it > working > > correctly. > > > > Thank you, > > *Kevin Furst* > > Technology Director > > Pine River-Backus Schools > > o | 218.587.8030 > > @ | kfu...@prbschools.org > > > > Technology Office/Help Desk: 218-587-8510 > > > > *Confidentiality Notice: This E-mail message, including any > attachments, is > > for the sole use of the intended recipient(s) and may contain > confidential > > and privileged information. Any unauthorized review, use, > disclosure or > > distribution is prohibited. If you are not the intended recipient, > please > > contact the sender by reply E-mail and destroy all copies of the > original > > message.* > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha@lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > ------------------------------ > > Message: 5 > Date: Sat, 9 Sep 2023 15:34:09 +0200 > From: Katrin Fischer <katrin.fischer...@web.de> > To: koha@lists.katipo.co.nz > Subject: Re: [Koha] Has NFC vs. NFD encoding changed for Unicode in > koha? > Message-ID: <6d8cc9b2-64bf-1e7d-4c5c-f9e67383c...@web.de> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi Jesse, > > first: of course you can join koha-devel and you are welcome there :) > > I am not aware of any conscious/intentional change in Koha and I know > that we've always been importing and exporting records with combined > diacritics (NFC) into Koha to avoid display and editing issues > (German > umlauts etc.) > > When you edit the records in Koha, do they present with NFC or NFD? > (you > can tell by removing a diacritic, does it require one or two steps?) > > How were the records added to Koha? > > Can you replicate the behaviour on another installation for example > on a > sandbox? > > Hope this helps, > > Katrin > > On 03.09.23 05:11, Jesse Savage wrote: > > This is probably a question for a developer, but I'm not one, so > don't > > really want to join the koha-devel list (and they probably wouldn't > want me > > to), and I know a lot of developers frequent this list. My > apologies to > > anyone who might not be interested in this question. > > > > I recently got a new Windows laptop on which I installed (I think) > a newer > > version of WSL/Ubuntu, and I see that records exported with the > "MARC > > (Unicode/UTF-8)" option (as *utf8 files, which look to be basically > *mrc) > > apparently use NFD (or "decomposed") encodings for Unicode > characters (in > > my case, mainly Spanish and French titles) and thus don't display > properly > > in *less*, *grep*, or *cat* (the diacritic follows the standard- > Latin > > character, rather than integrated with it) as do files encoded with > NFC > > characters, and the characters also can't be *grep*'d with searches > like > > "grep $'\u16A0'." The program I use to update records for uploading > also > > outputs NFD, even if the records it takes for input contain NFC. > (I'm > > waiting on the answer to the present questions to see whether that > program > > has an option hidden somewhere to output NFC instead, which I'd > prefer.) > > > > So, is this a systematic change in koha? *Should I ensure that > *.mrc files > > for batch uploading ALWAYS include only NFD characters, or do the > > underlying processes standardize NFC vs. NFD?* The system on which > the > > catalog lives (but which I don't administer) currently has koha > > 23.05.00.000 and runs on "SMP Debian 5.10.179-1 (2023-05-12) > x86_64". > > Please feel free to respond directly if you feel the answer won't > interest > > anybody else. > > > > Thanks very much in advance! > > Jesse > > --------------------- > > Jesse Savage > > (pronouns he, him, his) > > jess...@gmail.com > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha@lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > ------------------------------ > > Message: 6 > Date: Sat, 9 Sep 2023 09:11:58 -0500 > From: Rudy Hinojosa <rudy.hinoj...@lightwavelibrary.com> > To: koha@lists.katipo.co.nz > Subject: [Koha] check out problem in koha v23.05 > Message-ID: > <609d2ca0-33cd-b705-8860-8277c0f4e...@lightwavelibrary.com> > Content-Type: text/plain; charset=UTF-8; format=flowed > > > On 9/3/23 19:00, koha-requ...@lists.katipo.co.nz wrote: > > [Koha] check out problem in koha v23.05 > > In response to those seeing anomalies of circulated items getting > checked out with the same day or next day due date. This is caused > by > items in your items table not having an item type associated against > it. > There are many factors that would allow this, but mostly settings. > You > can have Koha base circulation rules against the biblio item type > specification or the specific items item type specification. The > default > is items I believe. Create a custom report to display biblio and > items > item types and check for null. Fix the nulls with batch modification > tools if you can. This won't automatically fix the due dates for > items > already circulated. To fix items already circulatied, you will need > to > go to Tools->Batch Extend Due Dates and run this tool. > > Please keep in mind that renewals will be looking for the loan > period > column under "renewal loan period", not "loan period". You'll want > to > double check your circulation rules for correctness. > > Cheers! > > Rudy Hinojosa > > > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Koha mailing list > Koha@lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > > > ------------------------------ > > End of Koha Digest, Vol 215, Issue 9 > ************************************ > _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha