[Koha] Barcode Font

[Himanshu Aggarwal]

I am able to generate the barcodes using the Bywater plugins but how to
change the barcode font size as the size of the barcode text is coming very
small. Can someone guide me please.
-- 
Assistant Librarian,
Confucius Institute Scholar 13-14,
R.D. National College,
Bandra (W.)
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Elasticsearch authority sorting giving unexpected results

[Hernandez, Heather H]

Yea!!!  Thank you, Aleisha!  I'm waiting for a sandbox to finishing 
provisioning so I can try signing off!!

--h2

~~~

Ms. Heather Hernandez (she, her, hers)
Technical Services Librarian
Library catalog:  https://keys.bywatersolutions.com/
San Francisco Maritime National Historical Park Research Center
2 Marina Blvd., Bldg. E, 3rd floor, San Francisco, CA  94123-1284
415-561-7032 (office, generally M, W, F, telecommuting Tu,Th)
heather_hernan...@nps.gov
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] One biblio record not visible in staff interface or OPAC

[Katrin Fischer]

Hi,

On 09.05.23 09:54, libr...@ssst.edu.ba wrote:

Hello,

The MARC flavor I chose in the web installer was indeed MARC21, however when I opened 
/etc/koha/koha-sites.conf to check I see that ZEBRA_MARC_FORMAT="unimarc". If I 
change this to MARC21 instead, and restart Zebra, will I stop getting errors when I add a 
record manually vs. via the Z39.50 servers?

If you take a closer look at the file, there are a lot of references to
unimarc and UNIMARC in settings and file paths. You'd need to set all
those correctly to fix your indexing problem and other issues for good.
Maybe a correct MARC21 conf file could be adapted and replace yours, but
I've never tried that.


I'm guessing that since I went through the creation/removal of a Koha instance 
more than once, with both flavors, when I created the current instance the 
Zebra indexing setting was left at UNIMARC. I thought this would be an 
automatic change during the next installation. If I absolutely must I will do 
it, but I would really like to avoid having to create yet another instance and 
to have to remake all the html customizations and CSS for the OPAC.

How did you make your changes? If you are using HTML customizations and
system preferences they are all stored in the database and you would be
able to load your existing database into a new instance and keep using it.


There's a setting in Record structure where I recently set the preference for 
autoControlNumber Value to Control Number (001) is generated as biblionumber. 
Would this be a correct setting for MARC21 then?

No, it would not be enough, you'd still be experiencing a lot of issues.
I assume every search that is not a keyword search won't work correctly.

When it comes to the two different flavors, with MARC 21 I got several MARC 
frameworks (books, serials, DVDs, etc.) in addition to the default one. With 
UNIMARC, I get the default plus fast cataloging and acquisitions.  Is this the 
same for others?

At the moment there are more sample frameworks for MARC21 than for
UNIMARC available with the sample data. You can still create your own
frameworks of course.


Hope this helps,

katrin

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Elasticsearch authority sorting giving unexpected results

[Katrin Fischer]

There is now a bug and a patch from Aleisha waiting for a sign-off:

*Bug 26472*
 -
Elasticsearch - ES - Authority record results not ordered correctly due
to punctuation marks

:)

Katrin

On 08.05.23 05:56, Aleisha Amohia wrote:

Hi all,

We have some unexpected sorting results happening when we search
authority records. We are using Elasticsearch. Wondering if anyone has
seen this before and knows a code fix or some Elasticsearch
configuration required to fix it.

I've noticed this happens in upstream Koha too so might be a real bug,
with Koha or Elasticsearch, I'm not sure which.

As an example, when we search for "political science" authorities with
the 'heading ascending' sort order, these are the results:

1. Political science Philosophy
2. Political science Poetry
3. Political science
4. Political science Problems
5. Political science Quotations

We would expect Political science (#3 in the above results list) to
show first, before the others.

Any ideas?


___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] koha-US General Meeting reminder: Wednesday, May 10, 2023

[Jennifer Marlatt]

The next koha-US General Meeting is Wednesday, May 10, 2023.



When: 8:30a PT / 11:30a ET (time converter

)

Where:
https://us02web.zoom.us/j/293750042?pwd=SGQzS2pmU3prNFhYRHNaeTFhOHN4QT09

Agenda:
https://docs.google.com/document/d/1Gck0YOXJeZmzcTobPmmypYHlFslnfRVhKpxjrnjnciM/edit?usp=share_link



If you have additional topics for the agenda, please send them to
secret...@koha-us.org

Meetings are held via Zoom video conferencing. A microphone and webcam 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

These meetings are always free and open to any and all.



Jennifer Marlatt

koha-US Secretary

secret...@koha-us.org
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Cindy Murdock Ames]

Hi Michael,

Can you confirm your koha-conf.xml contains a message broker section, like
this?


   localhost
   61613
   guest
   guest
   
 

I had the same problem after upgrading from 22.05 to 22.11; I'm guessing
22.05 must have had some defaults set in the code that allowed the message
broker to start automatically without this section whereas 22.11 must not.
I was missing this section and added it and was able to complete imports
after restarting Koha.

I'm still having the issue with zombie background jobs (I'm afraid to test
rolling back the code on a production server) but I made a hacky bash
script to run as a cron job to check for them and kill them off so at least
our staff can do batch imports without issue, but that's another matter.

HTH!
Cindy


---
Cindy Murdock Ames
IT Services Director
Meadville Public Library | CCFLS
https://meadvillelibrary.org | https://ccfls.org

Please report tech support issues in Mantis:  https://mantis.ccfls.org


On Thu, Mar 2, 2023 at 8:51 AM Michael Brown  wrote:

> Greetings:
>
> My name is Michael Brown and I am a professional cataloger and SirsiDynix
> System Admin at the Texas State Library & Archives in Austin (20+ years
> now). I have been using Koha on Arch Linux in my home library for about a
> year now. I am migrating my home server to AlmaLinux and I'm having a
> problem.
>
> I am running Koha 22.11.03.000 Rosalie on AlmaLinux 9.1. Staging a MARC
> file for import gets stuck at 0%. On screen, I am able to select the file
> for import (bib.mrc), review the profile options (but I don't change any
> defaults), and then click on "Stage for import" at the bottom. Next screen
> reads:
>
> The job has been enqueued! It will be processed as soon as possible.
> 0%
> View detail of the enqueued job
>
> After a few seconds, it changes to (and then hangs at):
>
> The job has been enqueued! It will be processed as soon as possible.
> 0% Not started
> View detail of the enqueued job
>
> Clicking on "View detail of the enqueued job" I see:
>
> Details of job #22
>
> Job ID: 22
> Status:New
> Progress:0 / 0
> Type:Staged MARC records for import
> Queued:03/02/2023 05:42
> Started:
> Ended:
>
> Report
> Detailed messages
> Return to the job list
>
> The corresponding entry in mariadb is:
>
> id 22
> status new
> progress NULL
> size 0
> borrowernumber 1
> type stage_marc_for_import
> queue Name of the queue the job is sent to long_tasks
> data {"encoding":"UTF-8","comments":"","basket_id":null...
> context JSON-serialized context information for the job
> {"flags":1,"branch":"ALMA","interface":"intranet",...
> enqueued_on 2023-03-02 05:42:33
> started_on NULL
> ended_on NULL
>
> (If you need to see the full entries for "data" and "context", please let
> me know.)
>
> tmp, koha_upload, and lock directories have been tweaked and fine tuned. I
> was getting early warnings about them not being set in koha-conf.xml so I
> created them (and set correct permissions) and I can see the uploaded file
> (for job 22 the name is 2287629673fb980ad4102f62ebeaa1b9_bib.mrc), so the
> actual upload function appears to be working.
>
> I am getting no apache errors and no other on-screen diagnostics.
>
> I have Koha 22.05.02.000 running on Arch Linux that imports this file just
> fine. Similarly, I have Koha latest running on a Debian VM that can import
> this file just fine, too.
>
> What am I missing?
>
> Details of my system:
>
> Koha version: 22.11.03.000 Rosalie
> OS version ('uname -a'): Linux alma 5.14.0-162.12.1.el9_1.x86_64 #1 SMP
> PREEMPT_DYNAMIC Mon Jan 23 14:51:52 EST 2023 x86_64
> Perl interpreter: /usr/bin/perl
> Perl version: 5.032001
> Perl @INC: /usr/share/koha/lib
> /usr/local/lib64/perl5/5.32
> /usr/local/share/perl5/5.32
> /usr/lib64/perl5/vendor_perl
> /usr/share/perl5/vendor_perl
> /usr/lib64/perl5
> /usr/share/perl5
> /var/lib/koha/plugins
> MySQL version: mysql Ver 15.1 Distrib 10.5.16-MariaDB, for Linux (x86_64)
> using EditLine wrapper
> Apache version: Server version: Apache/2.4.53 (AlmaLinux) Server built: Jul
> 20 2022 00:00:00
> Memcached: Servers: 127.0.0.1:11211 | Namespace: KOHA | Status: running. |
> Config read from: koha-conf.xml
> Zebra version: Zebra 2.2.7 (C) 1994-2023, Index Data Zebra is free
> software, covered by the GNU General Public License, and you are welcome to
> change it and/or distribute copies of it under certain conditions. SHA1 ID:
> ac40f289672405a299436d73c1532f9906774cc6 Using ICU
> Zebra status: Running
> Message broker: Using RabbitMQ
> Date and time: 03/01/2023 16:20
> Time zone: Used: America/Chicago | Config: Undefined | Environment (TZ):
> Undefined
>
> Thanks,
> Michael
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>

Re: [Koha] How To Add OCLC in Koha Z39.50 Server.

[Hernandez, Heather H]

Hello!

Michael wrote:
> Thus I assume the Z30.50 service of OCLC is not freely available
> but you will need to obtain a valid userId and password...

This is correct.  OCLC is a paid service—it is not free.  One must pay for the 
credentials necessary to get records, both bib and aut records.

Cheerio!
--h2, one of many women in the Koha community who are not "sirs" 

~~~

Ms. Heather Hernandez (she, her, hers)
Technical Services Librarian
Library catalog:  https://keys.bywatersolutions.com/
San Francisco Maritime National Historical Park Research Center
2 Marina Blvd., Bldg. E, 3rd floor, San Francisco, CA  94123-1284
415-561-7032 (office, generally M, W, F, telecommuting Tu,Th)
heather_hernan...@nps.gov
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] One biblio record not visible in staff interface or OPAC

[libr...@ssst.edu.ba]

Hello, 

The MARC flavor I chose in the web installer was indeed MARC21, however when I 
opened /etc/koha/koha-sites.conf to check I see that 
ZEBRA_MARC_FORMAT="unimarc". If I change this to MARC21 instead, and restart 
Zebra, will I stop getting errors when I add a record manually vs. via the 
Z39.50 servers? 

I'm guessing that since I went through the creation/removal of a Koha instance 
more than once, with both flavors, when I created the current instance the 
Zebra indexing setting was left at UNIMARC. I thought this would be an 
automatic change during the next installation. If I absolutely must I will do 
it, but I would really like to avoid having to create yet another instance and 
to have to remake all the html customizations and CSS for the OPAC.

There's a setting in Record structure where I recently set the preference for 
autoControlNumber Value to Control Number (001) is generated as biblionumber. 
Would this be a correct setting for MARC21 then? 

When it comes to the two different flavors, with MARC 21 I got several MARC 
frameworks (books, serials, DVDs, etc.) in addition to the default one. With 
UNIMARC, I get the default plus fast cataloging and acquisitions.  Is this the 
same for others? 

I really need to make this setup work, because the in-house system is not 
suitable for my needs, and the dev team absolutely cannot devote any time to 
adapting it for me this year. I need circulation to function properly, and 
acquisiotions so I can send out orders, and reports so I can send them to our 
management and to the federal statistics agency. 


Best regards

Aida Đikić


-Original Message-
From: Katrin Fischer  
Sent: Monday, May 8, 2023 12:30 PM
To: libr...@ssst.edu.ba; koha@lists.katipo.co.nz
Subject: Re: [Koha] One biblio record not visible in staff interface or OPAC

Hi,

that's what I've been trying to explain:

The MARC flavor you choose in the web installer will determine which sample 
data is loaded, including the MARC frameworks.

The indexing configuration is determined by how the instance was created when 
using 'sudo koha-create'. It defaults to MARC21, but can be set to UNIMARC 
using the option: --marcflavor flavor

If you have a mismatch between those settings, meaning one is MARC21 and the 
other was UNIMARC, that would explain the issues you see with indexing, search, 
links etc.

I believe the easiest solution would be to create a new instance and import 
your database there if that is the root of your problems.

Hope this helps,

Katrin


On 08.05.23 08:42, libr...@ssst.edu.ba wrote:
> Hello,
>
> "But:
> UNIMARC expects the biblionumber in 001, I think. I keep wondering if your 
> indexing configuration might be wrong."
>
> I'm pretty sure I chose MARC21 during the web installation, and I can see 
> what my indexing configuration looks like though I wouldn't be able to tell 
> if there's something wrong with it. I'd appreciate any advice on correcting 
> it as i tis.
>
> Now that I'm back at work, I can go through the same process I did with the 
> old laptop instance and see if I can replicate the solution. Any corrections 
> to the indexing configuration I would do to the work server instance.
>
> Best regards
>
> Aida Đikić
>
>
> -Original Message-
> From: Katrin Fischer 
> Sent: Thursday, May 4, 2023 8:46 PM
> To: koha@lists.katipo.co.nz
> Subject: Re: [Koha] One biblio record not visible in staff interface 
> or OPAC
>
> Hi,
>
> you should not *need* to have 001 set to biblionumber in a MARC21 
> installation to make things searchable, although it doesn't hurt if you want 
> to link records, which is one reason why you can do it. But:
> UNIMARC expects the biblionumber in 001, I think. I keep wondering if your 
> indexing configuration might be wrong.
>
> If you don't search for keyword, but select title or author as search option 
> - do you find what you are looking for?
>
> Checking the koha-conf.xml for the URLs to indexing configuration would help 
> to show if I am right or wrong.
>
> Hope this helps,
>
> Katrin
>
>
> On 04.05.23 16:01, libr...@ssst.edu.ba wrote:
>> Sucess!! I did some digging into the global settings for "controlnumber" to 
>> see if I'd missed any preferences when I reinstalled this instance, and it 
>> turned out that I needed to set the following:
>>
>> UseControlNumber to Use record control number ($w subfields) and control 
>> number (001) for linking of bibliographic records.
>>
>> under "Display", and
>>
>> autoControlNumber Control Number (001) is generated as biblionumber
>>
>> under "Record structure".
>>
>> I can now see the record by adding the appropriate biblionumber at the end 
>> of the URL, which was my workaround, but also by searching for the title, 
>> which I wanted to do.
>>
>> (But I also remember reading something about this not being a good 
>> choice if you have serials and if you are planning to catalog 
>> articles. I will need to leave this for some other time though, after 
>> I've added 

Re: [Koha] Key deprecation

[Russel G. P. Shihepo]

Thanks, I'll check it out.

On Mon, May 8, 2023 at 6:28 PM David Liddle  wrote:

> Hi Russel, are you perhaps referring to this entry in the instructions?
>
>
> https://wiki.koha-community.org/wiki/Koha_on_Debian#The_apt-key_deprecation_warning
>
> If you're seeing warnings about the older method, perhaps those very
> instructions will help you resolve the matter—not bypass it.
>
> David Liddle
> System Administrator
> david.lid...@wycliff.de (just not for this list)
>
> Wycliff e.V., https://wycliff.de
> Seminar für Sprache und Kultur, https://spracheundkultur.org
> Internationales Tagungszentrum Karimu, https://karimu.de
>
> On Mon, May 8, 2023 at 10:54 AM Russel G. P. Shihepo <
> russellge...@gmail.com> wrote:
>
>> Dear Community
>>
>> Does anyone know how to bypass key deprecation apt-key?
>>
>> Regards
>> Russel Shihepo
>> ___
>>
>> 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