Re: [Koha] User instance-koha already exists

2024-05-12 Thread Katrin Fischer

Hi,

there are some open bugs concerning the koha-remove that might explain
part of the issue you see:

 * *Bug 31124*
   <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31124> -
   koha-remove fails to remove long_tasks queue daemon, so koha-create
   for same  user fails
 * *Bug 16291*
   <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16291> -
   koha-remove --purge should also delete '/etc/koha/sites/$instance' dir
 * *Bug 6416*
   <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6416> -
   koha-remove fails when dropping user

Hope this helps,

Katrin

On 03.05.24 02:06, Victor Barroso Oliveira wrote:

Good afternoon,

Koha v. 22.05.16

Removed an instance
$koha-remove instance

Then I tried to create an instance with the same name

$koha-create --create-db instance

It displayed the following message "User instance-koha already exists"

How can I resolve this?
___

Koha mailing listhttp://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


Re: [Koha] Question about inventory

2024-05-12 Thread Katrin Fischer

Hi Ramona,

I am no expert of LOC classification, but maybe something you could check:

 * Have you set the classification source in your items? (952$2)
 * When you run a report on your items, are itemcallnumber, cn_source
   and cn_sort all set?

An example SQL report would be:

SELECT itemcallnumber, cn_source and cn_sort FROM items WHERE
itemcallnumber LIKE "JUVE D%";

That would tell you if Koha has been configured correctly to create the
right sortable form of your LOC callnumbers.

Hope that helps,

Katrin


On 03.05.24 17:10, Ratliff, Ramona wrote:

Hello everyone,

We are starting to do inventory, and the two of us working with it haven't
done it before in Koha, so we have one question.
When we ran a shelf list, some of the call numbers were out of order. We
use Library of Congress classification. The problem looked like this:
JUVE D 767..92 .M42 2002
JUVE DS 793 .G67 M33 1997
JUVE DT 63 .M35 1997
JUVE D 141 .V37 1991

All of the call numbers with only D instead of DS or DT should have come
before anything with two letters for this line in the call numbers.
Instead, there were Ds, then DFs, DGs, DKs, DSs and DTs and then 5 books
with only D showed up after the DTs.

*Ramona Ratliff *

Information Specialist

*York University*

Office: (402) 363-5708 |rjratl...@york.edu| *york.edu
<http://www.york.edu/>*
___

Koha mailing listhttp://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


Re: [Koha] Issue with updated_on in borrowers table and LDAP auth

2024-05-12 Thread Katrin Fischer

Hi,

I see that you have raised a bug now, which is good:

*Bug 36822*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36822> - When
creating a new patron via C4::Auth_with_ldap inserts -00-00 for
invalid updated_on

Katrin

On 04.05.24 00:29, Betka, Corey A wrote:

Hello,
I've inherited a really old install of koha (3.18.11) and I'm trying to 
get it migrated to current stable. I've figured out most of the database 
upgrade issues along the way thanks to the mailing list archives and old bug 
entries, but now I've run into something I can't find a solution for.

Relevant versions:
OS: Ubuntu 22.04
Koha: 23.11.04-4
MySQL: 8.0.36-0ubuntu0.22.04.1

Issue:
When a user is created via LDAP auth to the OPAC, the updated_on field in the borrowers 
table is set to "-00-00 00:00:00" and this makes it fail to display in the 
Intranet interface, showing a 500 error for that page of Patrons or if you search 
directly for the patron. If I have the new patron request a change in their record via 
OPAC and approve it in the Intranet, the updated_on field changes to a current value and 
then things work as expected. That's obviously not scalable.

We have LDAP auth configured to connect to our campus active directory with the 
following settings:
1
1
1

  
  
  
  
  
  Champaign, IL
  1
  TCC
  ST


I've done some slight modification to the logging in Patron.pm and the values 
that are being logged for updated_on don't make much sense to me:
"updated_on" : { "after" : "SCALAR(0x55fff641bca0)", "before" : "2024-05-03 
21:59:40" } }

Any suggestions? Is this a side effect of explicit_defaults_for_timestamp 
changing in MySQL? Does mariadb handle this differently? I had to use mysql to 
get past some foreign key issues early in the database upgrade scripts, but am 
open to migrating to mariadb now that the data can be brought forward.


Thanks,

Corey Betka
Infrastructure Architect

University of Illinois at Urbana-Champaign │ Student Affairs │ Student Affairs 
Technology
330 Clark Hall │ 1203 S 4th St │ M/C 548 │ Champaign, IL 61820


___

Koha mailing listhttp://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


Re: [Koha] Set a new id to validate duplicate record

2024-05-03 Thread Katrin Fischer

Hi Guillermo,

do you mean how to configure the duplicate check in cataloguing?

At the moment this is not possible, but ISBN is one of the fields
included by default.

*Bug 15248*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15248> - Make
it possible to configure duplicate check on bibliographic records

Hope this helps,

Katrin

On 24.04.24 16:14, Guillermo wrote:

Hi everyone,

How do I configure an ID to validate the duplicity of a new record when it
is added for the first time in the cataloging module, for example isbn
082a$, only when making the entry, but not in the database.

Guillermo Gonzalez

Biblioteca Universidad Simón Bolívar

Venezuela
___

Koha mailing listhttp://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


Re: [Koha] Koha Error 500

2024-05-03 Thread Katrin Fischer

Hi Igor,

this points to a translation issue - you should not see this problem
when working with the English templates.

The problem is that something got translated that should not have been,
like a piece of code. I am not seeing an obvious issue in the
translations right now, it might already be fixed with the next bugfix
release.

If you look at the translated template file and compare it to the
English one, you might be able to spot and correct the issue locally.

Hope that helps,

Katrin

On 25.04.24 15:05, Сычев Игорь Алексеевич wrote:

Hello!

After updating 23.05 to 23.11.04, when 
switchinghttp://192.168.1.243:8080/cgi-bin/koha/changelanguage.pl?language=ru-RU  I get 
an error "Error 500".

[Thu Apr 25 19:44:01.249628 2024] [cgi:error] [pid 171913] [client 
192.168.1.77:60121] AH01215: Template process failed: file error - parse error 
- member-display-address-style.inc line 1: unexpected token (line_break): 
/usr/share/koha/intranet/cgi-bin/members/moremember.pl, 
referer:http://192.168.1.243:8080/cgi-bin/koha/members/moremember.pl?borrowernumber=1
[Thu Apr 25 19:44:01.249970 2024] [cgi:error] [pid 171913] [client 192.168.1.77:60121] AH01215: 
  [% \xd0\x9a\xd0\x9e\xd0\x9c\xd0\x9f\xd0\x9b\xd0\x95\xd0\x9a\xd0\xa2 line_break = 
"" %] at /usr/share/koha/lib/C4/Templates.pm line 134.: 
/usr/share/koha/intranet/cgi-bin/members/moremember.pl, 
referer:http://192.168.1.243:8080/cgi-bin/koha/members/moremember.pl?borrowernumber=1
[Thu Apr 25 19:44:01.279866 2024] [cgi:error] [pid 171913] [client 
192.168.1.77:60121] End of script output before headers: moremember.pl, 
referer:http://192.168.1.243:8080/cgi-bin/koha/members/moremember.pl?borrowernumber=1

There is no such problem 
withhttp://192.168.1.243:8080/cgi-bin/koha/changelanguage.pl?language=de-DE

What needs to be fixed?

Good Luck!

Igor A. Sychev
Tomsk Polytechnic University
https://lib.tpu.ru

___

Koha mailing listhttp://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


Re: [Koha] How user be a member of three libraries?

2024-04-20 Thread Katrin Fischer

Hi,

a patron account can only be linked to one home library. Depending on
what you need to do, the library group feature could be helpful. It
allows you to limit what a staff user can do (view patrons, edit items)
to a group of libraries.

Hope this helps,

Katrin

On 20.04.24 07:14, Sami M. Rasheed wrote:

Hello,
  We created a user (a librarian user), and it is necessary for this person to 
be a member of three libraries. Our consortium consists of ten libraries.

We use Koha 23.11.04
Thanks.
Sami
___

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


Re: [Koha] Problem with email notices

2024-04-18 Thread Katrin Fischer

Hi Fred,

did you set them up in the overdue notice triggers or is this the
PREDUE* one?

What does your template look like?

Katrin


On 18.04.24 20:46, King, Fred wrote:

Esteemed Koha colleagues,

I recently set up overdue notices via Gmail. Everything seems to be going well 
except for one thing. I have Koha set up to send a friendly reminder on the day 
the item is due. For example, Schooner got this message (condensed to save 
space):

Dear  Schooner,
This is a friendly reminder that the following item(s) you borrowed from the 
library is/are now due:

"Bellevue"
by Oshinsky, David M.
WX 28 .O82 2017
Barcode: 32975000764287

(If the title, author, etc. are blank, please disregard this notice. We're 
trying to figure out why this keeps happening.)
Please return as soon as possible, or contact the library at 202-877-6221, or at 
whclibr...@medstar.net<mailto:whclibr...@medstar.net> if you would like to 
renew it. (Note that reserve books cannot be renewed except under special 
circumstances.)
For after hours returns: There is a book drop in the hallway outside of the 
library (2A43)
Thank you very much for your prompt attention to this matter.

Note: Schooner is my dog, who has no reasonable expectation of privacy 
regarding her book borrowing, so I can identify her by name.

The following day, she got another message:

Dear  Schooner,
This is a friendly reminder that the following item(s) you borrowed from the 
library is/are now due:

""
by

Barcode:

(If the title, author, etc. are blank, please disregard this notice. We're 
trying to figure out why this keeps happening.)
Please return as soon as possible, or contact the library at 202-877-6221, or at 
whclibr...@medstar.net<mailto:whclibr...@medstar.net> if you would like to 
renew it. (Note that reserve books cannot be renewed except under special 
circumstances.)
For after hours returns: There is a book drop in the hallway outside of the 
library (2A43)
Thank you very much for your prompt attention to this matter.

This is happening with every friendly reminder that goes out. It's not 
happening with any other notices, and it's using the same template for the 
reminder and the blank one.

Is this happening to anybody else? Does anyone have suggestions on how to fix 
it? I'm stumped.

--Fred

Fred King, MSLS, AHIP
Medical Librarian, MedStar Washington Hospital Center
fred.k...@medstar.net
202-877-6670
ORCID -0001-5266-0279
MedStar Authors Catalog: http://medstarauthors.org

I usually don't brag about owning expensive things, but I just left the grocery 
store.
--Anon

___

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


Re: [Koha] Patron not searchable after initial login with LDAP

2024-04-15 Thread Katrin Fischer

Hi,

patron search relies on the API now, but you should be able to see an
error in the logs. We recently had problems with invalid dates
preventing patron search. The problem turned out to be -00-00 in
borrowers.date_renewed.

Maybe an account created through LDAP mappings could also create some
invalid data.

You can also check the development tools in the browser for errors, but
usually the logs should have some useful hint. tail -f
/var/log/koha/instancename/*.log is usually the recommended way to see
what's going on while recreating the error.

Hope this helps,

Katrin


On 15.04.24 09:22, Andreas Tomiak wrote:

Hello,

a new user has successfully created a new patron record. If we try to
search him, the administrative interface returns empty pages.

We don´t find any hint in the log files. A database error?

The user was created automatically after his first login with LDAP data.

Any hints to fix this?

We are using the actual Koha version, restart of koha-common or
MariaDB and a full system restart does not change the weird behaviour.


Thanks

Andreas Tomiak



___

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


Re: [Koha] Content of tags and in OAI-PMH

2024-04-14 Thread Katrin Fischer

It looks like this old bug could possibly be related:

*Bug 21104*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21104> -
oai.pl returns wrong baseURL

Hope this helps,

Katrin

On 08.04.24 08:48, Magnus Enger wrote:

Hi!

I had a quick look at this, but couldn't figure out anything. But it
looks like a bug, so please report it in Bugzilla, so we don't loose it.

Best regards,
Magnus

Den 04.04.2024 21:20, skrev Michael Kuhn:

Hi

In our library we are using Koha 21.11.10

We are trying to use OAI-PMH but when calling
https://bibliothek.iunworld.com/cgi-bin/koha/oai.pl?verb=Identify the
output is as follows:

  
  
  
2024-04-03T16:39:53Z
    https://bibliothek.iunworld.com/opac/oai.pl
    
  IUN World
https://bibliothek.iunworld.com/opac/oai.pl
  2.0
  root@localhost
2020-01-21T13:25:14Z
  persistent
-MM-DDThh:mm:ssZ
  gzip
    
  

As you see in both the tags  and  there is an
incorrect URL ( https://bibliothek.iunworld.com/opac/oai.pl ) which
only leads to a 404 error page. The correct URL would be
https://bibliothek.iunworld.com/cgi-bin/koha/oai.pl

I have changed the following line in file
"/usr/share/koha/lib/Koha/OAI/Server/Identify.pm" to get the correct
URL at least in tag :

  #baseURL => $baseURL,
  baseURL =>
'https://bibliothek.iunworld.com/cgi-bin/koha/oai.pl',

But I couldn't find out how to get the correct URL also in tag
. In fact I doubt what I'm doing is the correct way but I
couldn't find any information in the manual on how to configure
OAI-PMH except via the system preferences. Why is Koha showing the
incorrect URL https://bibliothek.iunworld.com/opac/oai.pl at all and
how can I change this?

Best wishes: Michael

___

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


Re: [Koha] record does not exist when clicking title in search results

2024-03-25 Thread Katrin Fischer

Hi Andrew,

you could compare your settings to the ones in one of the demo
installations. A first thing to check would be if the link in the OPAC
is missing the biblionumber parameter and if you have checked the OPAC
in the visibility settings of the framework.

Hope this helps,

Katrin

On 25.03.24 15:42, Andrew Hartung wrote:

Looking at the koha to marc mapping, 999c and d are ignored.
How should I set them up in edit subfield constraints? I've tried but keep 
getting framework errors.


Date: Wed, 20 Mar 2024 09:40:39 +0100
From: Fridolin SOMERS 
Hi,

By default link will use MARC 999c (for MARC21).
Do you have the biblionumber linked to this field ?

Le 20/03/2024 à 01:44, Andrew Hartung a écrit :

I'm still having problems with this.
In the catalog search results clicking on the title gives me a page:

"The record you requested does not exist()."
However, if I click on the pic of the book cover, if it has one, the record
displays fine.
I've ran koha-rebuild-zebra, batchRebuildBiblioTables.pl and
batchRebuildItemsTables.pl.

All three give errors with some problem biblio records, which I have
deleted, but they still show in the errors. Only rebuild-zebra actually
completes, the other two crash.


___

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


Re: [Koha] Request to be listed as paid support provider: imCode Partner AB

2024-03-07 Thread Katrin Fischer

Hi Magnus,

I have added imCode to the Koha support providers list:

https://koha-community.org/support/paid-support/country/#swe

Please check and let me know if any changes are needed.

Katrin

On 07.03.24 14:36, Magnus Enger wrote:

Kia ora, dear Community!

imCode is a Swedish company that has worked with Open Source software
for 20+ years and with Koha for the last 7 years. We have, together
with our daughter company Libriotech, installed Koha in over 40
municipalities, 100+ schools and 40+ special libraries. We are the
largest Koha supplier in Sweden and Norway with 15 employees making
sure we have redundancy in all aspects of our operations.

imCode would kindly ask to be listed as a provider of paid support for
Koha:

Company Name: imCode Partner AB

Contact Person: Tomas Holasek

Contact email: i...@imcode.com

Website: https://imcode.com/koha

Telephone: +46 498 200 301

Best regaqrds,
Magnus
Libriotech/imCode

___

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


Re: [Koha] Cyrillic alphabet when saving to a file

2024-02-26 Thread Katrin Fischer

Hi,

can you verify that it's different in Koha itself? It might be visible
when you edit the record and try to delete the character.

It sounds like your character might be in a decomposed Unicode
normalization form (NFD vs. NFC).

Hope this helps,

Katrin

On 26.02.24 11:23, Сычев Игорь Алексеевич wrote:

Hello!
What needs to be corrected so that when saving to MAC (Unicode/UTF-8) there is a Cyrillic character 
"й", and not two characters "и" and " ̆"?

Good Luck!

Igor A. Sychev
Tomsk Polytechnic University
https://lib.tpu.ru


___

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


Re: [Koha] Email delivery pending

2024-02-08 Thread Katrin Fischer

Hi,

the welcome email is sent immediately, but the checkin and checkout
notices are usually only sent out every 15 minutes or to the interval
you have set your process_message_queue.pl cron job. Until the job is
run, the notices remain pending.

It's recommended to not set the interval too low, as the checkin and
checkout notices 'collect' transactions until run and if you set it low
you might end up with multiple emails for the same session.

Hope this helps,

Katrin


On 08.02.24 10:41, Shankar Reddy Kolle wrote:

Dear Sir/madam
Greetings.
I have migrated Koha version 19.05 to Koha 22.05.08 in Ubuntu 22.04.
An in-built SMTP server is enabled to send emails to the patron.
The system sends the welcome email after new patron registration
but it does not send the chekins and checkout email.
it is showing the notice is pending.
Please help me to figure it out.

Thank you in advance.


___

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 hide port number when accessing koha staff client in the browser.

2024-02-08 Thread Katrin Fischer

Hi zen,

you need to use different URLs for the staff interface and the OPAC.

They can be either different by using different ports or by using
different subdomains.

You cannot hide a port number if you are using ports outside of 443/80
in the browser.

You might want to change your configuration to use something like
opac.com.ph and staff.com.ph instead.

Hope this helps,

Katrin

On 08.02.24 09:41, zen zenitram wrote:

Good day!

Can someone help me on how we hide port number when our user access KOHA
staff client in the internet. for security purposes.
sample
OPAC: opac.com.ph
staff client: opac.com.ph:10001

I want to hide the 1001


i just saw someone answer to use 2 different IP addresses,

https://lists.katipo.co.nz/public/koha/2014-April/039152.html

how can i do that?
___

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


Re: [Koha] While searching patron getting the error (koha upgraded from 19.05 to

2024-02-06 Thread Katrin Fischer

Hi,

we recently saw a similar issue. It turned out that we had invalid dates
in borrowers.date_renewed. To verify you could create a report:

select * from borrowers where date_renewed = '-00-00';

If that returns results, you have the same problem we had. I think these
can only be fixed from server side with an update statement:

update borrowers set date_renewed = NULL where date_renewed = '-00-00';

Hope this helps,

Katrin


On 06.02.24 11:43, Shankar Reddy Kolle wrote:

Dear Sir/madam

Please help to resolve this issue :

I have a system with Ubuntu 16.04 and Koha version 19.05.
Yesterday I installed koha 22.05.08 in Ubuntu 22.04.
and migrated the old data (Koha 19.05)  to (Koha 22.05.08.
When I search any patron by name I am getting this error

Something went wrong when loading the table.
500: Internal Server Error.
Month out of range.
Month out of range.
Month out of range.
Month out of range.
Month out of range.
Month out of range.
Month out of range.

Hoping for the solution

Thank you

___

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


Re: [Koha] Call number display in holdings table and

2024-02-06 Thread Katrin Fischer

Hi Andrew,

there is no way to display bibliographic information in the holdings
table. What you can do is set the itemcallnumber system preference to
082a. Then if you add an item, it will copy the value from 082$a to
952$o as a suggestion for your callnumber.

You could also consider changing the XSLT files to display 082$a in the
bibliographic information above the table. But if you want to use the
inventory module etc. effectively, I think you need to make sure to set
the callnumbers within the items properly.

The error you see when clicking on the detail page could be an indexing
issue. Did you make any other changes to the frameworks and mappings?
I'd first try to reindex.

Hope this helps,

Katrin

On 05.02.24 20:36, Andrew Hartung wrote:


Sorry, I should have added that I'm running koha 23.11. I don't have
access to the server now, so I'm not sure of the minor version but not
the most recent release, probably, 23.11.01

On Monday 05 February 2024 01:28:16 PM (-06:00), Andrew Hartung wrote:

> I need the call number field from Marc21 082a displayed in the
holdings table in the bibliographic detail of the record in the OPAC.
> > > I tried using the value builder cn_browser.pl, but it did
nothing. I removed it from the marc framework and now when clicking on
the title of a book from the catalog search screen gives this error:
> > > "The record you requested does not exist()."
> > > However, if I click on the pic of the book cover, the record
displays fine. What can I do to fix this and display the call number
in that table?
> > Thank you,
> Andrew Hartung
___

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


Re: [Koha] KOHA OPAC customize page

2024-02-02 Thread Katrin Fischer

Hi,

how did you implement your customizations?

If you changed the template files, they will be overwritten with each
update. If you use HTML customizations, news and system preferences like
OpacUserCSS and OpacUserJs the changes will be kept.

Hope this helps,

Katrin

On 02.02.24 03:46, zen zenitram wrote:

Good day!

Everytime we update of upgrade the Operating system (Ubuntu 22.04), the
customize opac page return to default page, It disable some of the html
codes that we use. we need to customize it again and again everytime we
update the operating system.

Any fix for that?

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


Re: [Koha] Koha January release with security fixes

2024-02-02 Thread Katrin Fischer

All links now work as expected.

On 02.02.24 11:06, Michael Kuhn wrote:

Hi Fridolin

You wrote:

> The full release notes are available here:
> https://koha-community.org/koha-23-11-02-released/

This link works.

> https://koha-community.org/koha-23-05-08-released/
> https://koha-community.org/koha-22-11-14-released/
> https://koha-community.org/koha-22-05-18-released/

These three links do not work.

Best wishes: Michael

___

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


Re: [Koha] Koha - item - Restricted access

2024-01-29 Thread Katrin Fischer

Hi,

I believe you set the usage restrictions to restricted in the item?

The pull down is using the values from the RESTRICTED authorised value
category. The value corresponding to 1 in that list will not allow for
checkout. If you set up other positive or negative number values, you
will be able to check them out.

Hope this helps,

Katrin

On 29.01.24 10:28, Сычев Игорь Алексеевич wrote:

Hello!

A bibliographic record has been made.
The item (donated from a private collection, has marks) is access to a limited 
circle of users (university employees). The item has a restricted access. The 
librarian herself decides who to lend and who to refuse.

When trying to checkout this item, we receive the message "Item is restricted".
What needs to be configured or corrected so that this item be able to checkout 
when it is necessary?

Good Luck!

Igor A. Sychev
Tomsk Polytechnic University
https://lib.tpu.ru

___

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


Re: [Koha] Zebra Index not working

2024-01-16 Thread Katrin Fischer

Hi Anke,

have you checked if your Zebraserver is running?

Maybe try: koha-zebra --restart instance or koha-zebra --stop / --start
instance.

Does the about page show anything about your Zebra's status? (front page)

Hope this helps,

Katrin

On 16.01.24 14:49, Bruns, Anke wrote:

Hi,

we are facing a similar problem to
https://stackoverflow.com/questions/26925152/reindexing-zebra-because-there-
are-no-results-found-in-opac-and-intranet-search.
I tried rebuilding the Zebra index, also checked the directories'
permissions according to
https://koha.katipo.co.narkive.com/cc099Nwf/reindexing-zebra-because-there-a
re-no-results-found-in-opac-and-intranet-search
and tried to reset the Zebra Index, as proposed in
https://koha-community.org/manual/16.11/html/apis02.html .

None of this shows any effect. According to screen output, the 6 biblios
(it's a very new testing instance) are exported and the index is rebuilt as
expected. Yet, there are no search results at all.

Curiously, the Koha instance where this problem occurs is one of six
instances on one and the same server, all other five having fully functional
Zebra indexes, and a rebuild on another instance on that server works
without any problems.

Does anybody have an idea what might be the reason for this?

Cheers in advance,
Anke



___

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


[Koha] Reminder: General IRC meeting 17 January 2024

2024-01-16 Thread Fischer, Katrin
Hi all,

 

just a quick reminder that we have scheduled a General IRC meeting for
tomorrow:

 

https://wiki.koha-community.org/wiki/General_IRC_meeting_17_January_2024

 

Time:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+General+IRC+M
eeting
<https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+General+IRC+
Meeting=20240117T1400> =20240117T1400 

 

 

Katrin

___

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


Re: [Koha] Prevent specific MARC field from being duplicated?

2024-01-13 Thread Katrin Fischer

Hi Tasha,

at the moment it's not possible to specify which fields not to copy. But
there is a bug report requesting this functionality that you could
comment on:

*Bug 26071*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26071> -
Allow to configure fields not to be copied when using "Edit as new
(duplicate)" in cataloging

Hope this helps,

Katrin

On 03.01.24 16:06, Bales (US), Tasha R wrote:

Hello, I have not yet found the answer to this question.  We are still running 
21.05, but plan to upgrade soon (unsure to what release).

When duplicating a bibliographic record, is it possible to NOT duplicate a 
specific MARC field from the source record?

In particular, I'd like to avoid duplicating action notes that are in the 583 
field.  We use dated action notes, and we duplicate lots of records, and 
information in source records that is not applicable to target records is being 
saved to them by mistake.

Our use of the field is as follows:  583$a has a default value.  583$c uses the 
dateaccessioned.pl plugin to enable a date picker/calendar.

Is there a way to "block" certain fields from being duplicated?  Although we 
could train staff to delete that field with every duplication, I'd prefer to avoid human 
error and the additional keystrokes.

Thanks in advance for all ideas.  If a JavaScript/jQuery solution is possible, 
maybe that would work, but I'm not sure how to make it happen.

Tasha Bales


___

Koha mailing listhttp://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


Re: [Koha] Department Name in Item Information

2024-01-13 Thread Katrin Fischer

Hi,

you can define custom/additional item fields by adding capital letter
subfields to the 952 in your bibliographic frameworks. If you don't map
them to a database column in items, the information will be
automatically stored in items.more_subfields.xml.  You can also link
these new subfields to an authorised value category you created for your
departments.

The additional item fields won't show in the normal detail view, but in
the MARC view and item editor.

Hope this helps,

Katrin

On 05.01.24 12:17, Rupinder Singh wrote:

Hi,
We have been using Koha at our university for the last year. We get
allocated a consolidated budget at the beginning of the financial year. And
we'd like to spend that budget as per the purchase requests sent by
different departments of the university. However we haven't used the
acquisition module yet and are not planning to do so.
But of all the books we catalog in koha, I also want to save information
about the department that requested that book. So that it can be exported
via catalog report, so I can see how much of the budget we have spent on
each department. And each book item shall have this information for the
requesting department in the Items section.
Please suggest what the best approach to achieve this could be.
Is there any existing field to specify that, or is there any existing field
I can make use of to put this information?
I have also found certain subfields in 952 item information that are not in
use. Can I map a new authorized value to this newly created field?
Please, guys, Guide me.

Rupinder Singh
___

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


Re: [Koha] Argument "0, 00" isn't numeric in numeric gt (>) at /usr/share/koha/lib/C4/Overdues.pm line 292.

2024-01-08 Thread Katrin Fischer

Hi Michael,

if you have set the CurrencyFormat system preference to 'FR' the display 
format will be 0,00, but if the wrong format is in the database it will 
also display as 0,00. So it can hide the problem. If you set it to a 
CurrencyFormat with decimal ., the problem could become easier to spot.


Hope this helps,

Katrin

On 08.01.24 10:53, Michael Kuhn wrote:

Hi Katrin and Magnus

Many thanks for your answers!

It is not possible to change the value to "0.00" via Koha menu 
"Administration > Defining circulation and fine rules for all 
libraries" - even wehn savin "0.00" it will still show "0,00".


We have eight rules there - all of them show value "0,00" in column 
"Overdue fines cap (amount)". But in table "circulation_rules" I found 
the following:


MariaDB [koha_bibliothek]> SELECT * FROM circulation_rules WHERE 
rule_name="overduefinescap";
+-++--+--+-++ 


| id  | branchcode | categorycode | itemtype | rule_name    | rule_value
+-++--+--+-++ 


|   4 | NULL   | NULL | NULL | overduefinescap |   |
|  34 | NULL   | NULL | BUCH | overduefinescap | 0.00  |
|  67 | NULL   | NULL | CD   | overduefinescap | 0.00  |
|  94 | NULL   | NULL | ZSS  | overduefinescap | 0.00  |
| 136 | NULL   | PT   | BUCH | overduefinescap |   |
| 170 | NULL   | HB   | BUCH | overduefinescap | 0.00  |
| 182 | NULL   | NULL | KONV | overduefinescap |   |
| 214 | NULL   | NULL | DVD  | overduefinescap |   |
+-++--+--+-++ 


8 rows in set (0,000 sec)

So I changed just the values actually containing "0,00" as follows:

MariaDB [koha_bibliothek]> UPDATE circulation_rules SET rule_value = 
'0.00' WHERE rule_value = '0,00';


Thus table "circulation_rules" now shows:

MariaDB [koha_bibliothek]> SELECT * FROM circulation_rules WHERE 
rule_name="overduefinescap";
+-++--+--+-++ 

| id  | branchcode | categorycode | itemtype | rule_name    | 
rule_value |
+-++--+--+-++ 


|   4 | NULL   | NULL | NULL | overduefinescap |   |
|  34 | NULL   | NULL | BUCH | overduefinescap | 0.00  |
|  67 | NULL   | NULL | CD   | overduefinescap | 0.00  |
|  94 | NULL   | NULL | ZSS  | overduefinescap | 0.00  |
| 136 | NULL   | PT   | BUCH | overduefinescap |   |
| 170 | NULL   | HB   | BUCH | overduefinescap | 0.00  |
| 182 | NULL   | NULL | KONV | overduefinescap |   |
| 214 | NULL   | NULL | DVD  | overduefinescap |   |
+-++--+--+-++ 


8 rows in set (0,000 sec)

However, even after restarting Koha ( memcached apache2 koha-common ) 
Koha menu "Administration > Defining circulation and fine rules for 
all libraries" still shows the value "0,00" in column "Overdue fines 
cap (amount)" for all eight rules as before.


I will now wait and see what happens after the next run of 
"/etc/cron.daily/koha-common".


Best wishes: Michael

___

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


Re: [Koha] Argument "0, 00" isn't numeric in numeric gt (>) at /usr/share/koha/lib/C4/Overdues.pm line 292.

2024-01-06 Thread Katrin Fischer

Hi Michael,

this was fixed with:

*Bug 33028*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33028> -
Wrongly formatted monetary amounts in circulation rules break scripts
and calculation

But the fix still requires you to fix the values stored in the database.

You could try to edit the rule and save 0.00 (with the .). It might
work.Or you could use SQL to make sure all the monetary values in
circulation_rules are correctly formatted.

Hope this helps,

Katrin


On 06.01.24 11:33, Michael Kuhn wrote:

Hi

Our library is working with Koha 22.05.17.

Since some days the anacron job "cron.daily" sends us an e-mail with
hundreds of lines like the following every day:

 Argument "0,00" isn't numeric in numeric gt (>) at
/usr/share/koha/lib/C4/Overdues.pm line 292.

I see in the circulation and fine rules the "Overdue fines cap
(amount)" shows as "0,00" instead of "0.00" as usual. However, this
can't be changed at this place.

Changing lines in script "Overdues.pm" according to
https://gomezcardozo.com/error-en-fines-koha/ didn't help.

How can this output be prevented?

Best wishes: Michael

___

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


Re: [Koha] koha-plugin-room-reservations

2023-12-26 Thread Katrin Fischer

Hi,

please report the issue on the issue tracker for the plugin project on
gitlab/github where you downloaded it.

When you report this, you might want to include more information, like
if the plugin has worked before etc. to help finding the problem.

Katrin

On 24.12.23 11:53, Sami M. Rasheed wrote:

Dear all,
Hi,
koha-plugin-room-reservations (V. 4.02) not working under Koha 23.11.00, the 
OPAC display this error:


Sorry, the requested page is not available

Error 500

This message can have the following reason(s):

- An error occurred while processing your request.

What's next?

- You can use the menu and links at the top of the page
- You can search our catalog using the search form at the top of this page.
- Return to the catalog home page.

Report issues and broken links

- To report this error, please contact the Koha Administrator. Send email.


Thanks
___

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


Re: [Koha] Generating fine in every renewal

2023-12-18 Thread Katrin Fischer

Hi,

could it be that you have set up a rental fee for the item type? Rental
fees are calculated for the initial checkout, but also for renewals.

If you look at the details of the fines, what are they exactly called?
(Fine accruing? renewed?)

Hope this helps,

Katrin

On 14.12.23 11:39, JITHIN N wrote:

Dear community
We are using Koha 22.11.07. In our Koha circulation rule patron category
have maximum 5 time renewal allowed (Renewal Count) with time period of 10
days (Renewal period). In administration menu  *Renewal Period Base* is
calculated based on old due date  of book and for late return every day 1
rupee is calculated as fine. A patron have overdue of a book which is not
returned till date with 30 days late,  his account shows accruing fine of
30 rupees. when the staff renew the book,  along with 30 rupees an amount
of 20 rupees creating with a total of 50 rupees. If again renew the book it
again generating an amount 10 rupees along with 50 rupees with total of 60.
Since the account have already fine till the date why Koha generating  fine
again  based on new due date of renewal. is it a bug or any configuration
need to change?
___

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


Re: [Koha] Setting up an SRU target

2023-12-18 Thread Katrin Fischer

Hi,

I couldn't test, but I thnk you might be missing schema=marcxml in your
list of additional SRU options. Maybe worth a try!

Hope this helps,

Katrin

On 16.12.23 23:08, Rubeno wrote:

Hello all,

I'm trying to set up an SRU target and can't seem to find the way.

The SRU server is the Austrian National Library. Here's the info for
their SRU server:

https://obv-at-oenb.alma.exlibrisgroup.com/view/sru/43ACC_ONB?version=1.2=explain

They provide some more info here:

   https://labs.onb.ac.at/en/datasets/catalogue/

So I'm trying to look for a book that I know exists, because I can
retrieve it in XML like this:

https://obv-at-oenb.alma.exlibrisgroup.com/view/sru/43ACC_ONB?version=1.2=alma.title=terminaro%20and%20alma.creator=Portmann=searchRetrieve

However I don't know what to set up in the 'Additional SRU options'
field. I've tried several combinations of
"sru=get,sru_version=1.2,operation=searchRetrieve", but I never get
any hit.

As for the SRU field mapping, I'm trying this:
title=title,isbn=isbn,author=creator,issn=issn,subject=subjects

The manual https://software.indexdata.com/yaz/doc/zoom.html that is
linked to in the Koha interface is complete gibberish to me.

I have no installation of my own yet (still deciding whether Koha is
manageable for my association), so I'm using this demo server:

   https://intra1.orex.es/

Can anybody help, at least describing a working setup for other SRU
targets? Thanks!

Rubeno

___

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


Re: [Koha] View SQL generated by Average Loan Time report?

2023-12-05 Thread Katrin Fischer

Hi Cindy,

at the moment it's not possible to see the created SQL query in the GUI,
maybe this would be a good idea for an enhancement.

But I believe the matrix style reports, like Average loan time, might
not be easy to rebuilt in reports as they probably require multiple SQL
queries.

Katrin

On 29.11.23 18:01, Cindy Murdock Ames wrote:

Hi all,

Is there a way to view the query that the Average Loan Time report is using
(issues_avg_stats.pl)?  I'd like to put it in a SQL report and add further
limits to it, it would be handy to be able to dump the query to the screen
or log it somewhere.

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

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


Re: [Koha] Rabbitmq

2023-12-05 Thread Katrin Fischer

Hi Andrew,

I cannot tell if it's possible to downgrade or make Koha work on the
newer OS, but in case it isn't:

If you haven't changed any configuration files or used the upload
feature, it should be enough to dump your database and re-import it into
an empty instance database.

Something like this:
http://kohageek.blogspot.com/2015/08/move-old-koha-database-to-new.html

If you have files in your file system or changed configuration files you
will have to move them as well.

A full backup is as always recommended.

Hope this helps,

Katrin


On 02.12.23 00:53, Andrew R Hartung wrote:

So is there any advice on what I should do? Do I need to reinstall the
OS to a LTS version and reinstall koha? I really hope to avoid this,
but if that is necessary, so be it.
If so, what is recommended procedure to save and then import all of my
koha catalog, preferences, etc.. into the new system?



So in a moment of stupidity I updated my server to Ubuntu 23.10 and
rabbitMQ will not build. I thought I was on the LTS, but wasn't. Koha
states that it is using SQL messaging. What are the ramifications from
this? I don't actually understand how rabbitMQ is used by koha.
___

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


Re: [Koha] Help! This title cannot be requested

2023-11-30 Thread Katrin Fischer

Hi,

some more ideas on what to check in the circulation rules:

* Can the item be checked out by this patron? (number of allowed
checkouts > 0)

* Are there 1 ore more holds allowed? (check all hold relevant settings)

For system preferences you could also check MaxReserves.

In the item type configuration: is the record marked as for reference?

Hope this helps,

Katrin

On 29.11.23 14:32, Alipio Luiz de Souza Silva wrote:

Hello..When a patron tries to reserve an item in the OPAC, they receive the
message: "This title cannot be requested".

Under Preference:
OPACHoldRequests: Allow

Under Circulation and fines rules (for all item type, for all patron
category):
On shelf holds allowed: Yes
OPAC item level holds: Allow/Force

I really don't know what I miss.
Can you help me?


[image: Mailtrack]
<https://mailtrack.io?utm_source=gmail_medium=signature_campaign=signaturevirality11;>
Sender
notified by
Mailtrack
<https://mailtrack.io?utm_source=gmail_medium=signature_campaign=signaturevirality11;>
29/11/23,
09:31:52
___

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


Re: [Koha] Location fields

2023-11-30 Thread Katrin Fischer

Hi Charles,

I would advise against changing the item field (952) mappings. It will
affect your searching and could also break functionality in Koha.

Changing the mapping will only change how things are stored when you
edit a new item/record. Unless you also run the job mentioned on that
page. But before doing that, you should be sure on what you are doing to
not risk losing data.

Can you explain a bit more on what you are trying to do?

Katrin

On 29.11.23 04:25, Charles Athey wrote:

I am new to this list and am a retired software developer with 40+ years of 
experience.

I am a volunteer at the Sacramento FamilySearch Center. We have recently 
implemented Koha for our Center. We wanted a way to keep track of the PDF scans 
of the books we have that are not available online. Most are copy protected and 
we have scanned them for two reasons: 1) For preservation so that we can look 
at the PDF instead of having the book be handled by patrons as many are really 
old and 2) So we can easily search in the book as we have run OCR software on 
the PDFs, this greatly increases their usefulness for doing family history 
research. There is no access to our Koha or the PDFs outside of our physical 
center at this point. We are hoping to someday allow this but want to be very 
sure we do not violate any copyrights. We have all the books we have PDFs for.

I am hoping someone can explain to me how we the location fields are handled. 
Specifically, I have tried using the Koha->Marc mapping to map (c) to 952$c and 
also to 999$c but the location or permanent_location fields don’t get changed. 
Rather, the more_subfields_xml field gets written. I thought changing this field 
would modify the items.location field or permanent_location field. The Koha wiki, 
https://wiki.koha-community.org/wiki/Holdings_data_fields_(9xx), says the 
items.location field should be written.

We are running Koha 23.05.05 <https://koha-community.org/> on Ubuntu 22.05LTS 
Server virtual machine. We have MariaDB and Apache2 also running on this same Ubuntu 
server.

Thanks

Charles L. Athey III
Sacramento FamilySearch Center






___

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


Re: [Koha] Koha 23.05.05 advanced editor interface hanging on editing existing catalogue record

2023-11-30 Thread Katrin Fischer

Please try updating to 23.05.06, it could be:

*Bug 35181*
 - Can
no longer edit sample records with advanced cataloguing editor

On 29.11.23 14:53, Michael Kuhn wrote:

Hi Iming Chan

You wrote

> I am running Koha 23.05.05 and using Google Chrome as the browser.
>
> Does anyone else have trouble editing an existing catalogue record
> using the advanced editor?
>
> After we switched to the Advanced Editor from the basic editor, the
> screen just showed "Loading, please wait ...".  Pressed F12 and I
> noticed there are two page errors of "Incorrect use of
> .

In May 2022 I reported a similar problem which is (to my knowledge)
still unsolved (the library meanwhile uses Koha 21.11.09):

https://lists.katipo.co.nz/public/koha/2022-May/057752.html

There were no answers to this post.

Best wishes: Michael

___

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


Re: [Koha] Koha integration with other systems

2023-11-28 Thread Katrin Fischer

Hi Joel,

you can add additional match points for patron import by configuring
patron attributes marked as unique. As soon as it's configued it will
show up in the pull down on the patron import tool. It works quite well,
but you might need to adjust your CSV file a bit for the special syntax
required to import patron attributes.

Hope this helps,

Katrin

On 28.11.23 21:29, Coehoorn, Joel wrote:

We configured our Koha installation to use our university AD FS
(SAML-based) SSO service. Note I've setup over a dozen different apps
for this service, and Koha was definitely the most difficult to get
working... but it DOES work.

We also have a "manual integration" to populate users in Koha based on
our Jenzabar J1 SIS, which amounts to a report our librarians can run
on demand and then manually import the generated CSV file via Koha's
Patron Import tool. When done right this is idempotent, which is a
fancy way of saying the librarians can run it as often as they want
without duplicating users. However, we built and configured things so
Koha student accounts expire at the end of each term, meaning someone
MUST run it each term to reactivate our students. This process has
been in place since long before Koha had its own API, so I'm hoping to
use that to make this run automatically in the background in the near
future.

We do NOT have an integration with our student billing for things like
late fees or lost item charges. Those are still handled completely by
hand.

One feature I would like to see Koha add is the ability to match new
users based on an external immutable ID. The existing patron import
tool allows us to match existing patrons based on card number or
username (email). However, BOTH of those might need to change. We
don't want to leave an old card active if it's lost or stolen and we
need to replace it. A random person shouldn't be able to pick it up
and use the old card, and so the new card will have a newly-generated
barcode number. Our student emails/usernames track with their real
names, and these do also change on occasion (most common reasons are a
parent divorce or student marriage). But we have an immutable student
ID for each person, and it would be really nice for Koha to have a way
to ingest that and use it for patron updates, because we know for
certain it really won't change. There may also be some support around
borrowernumber, but our SIS has no knowledge of the borrowernumber
when creating the student exports.

*Joel Coehoorn*
Director of Information Technology
*York University*
Office: 402-363-5603 | jcoeho...@york.edu | york.edu <https://york.edu>



On Mon, Nov 27, 2023 at 12:47 PM Katrin Fischer
 wrote:

Hi Russel,

Koha provides a lot of different APIs and protocols for
integrating with
other systems. This might be a starting point:
https://wiki.koha-community.org/wiki/APIs_and_protocols_supported_by_Koha

Hope this helps,

Katrin

On 27.11.23 16:05, Russel G. P. Shihepo wrote:
> Dear Community
>
> Does Koha support integrations such as:
>
> - Centralized Single-Sign-On Integration.
> - ERP Integration (Student and HRMs).
> - Payment gateway integration.
>
> I have been tasked by our school to make an attempt to integrate
Koha with
> other systems at the institution. Thank you in advance.
>
>
> Regards,
> Russel
> ___
>
> 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


___

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


Re: [Koha] Koha integration with other systems

2023-11-27 Thread Katrin Fischer

Hi Russel,

Koha provides a lot of different APIs and protocols for integrating with
other systems. This might be a starting point:
https://wiki.koha-community.org/wiki/APIs_and_protocols_supported_by_Koha

Hope this helps,

Katrin

On 27.11.23 16:05, Russel G. P. Shihepo wrote:

Dear Community

Does Koha support integrations such as:

- Centralized Single-Sign-On Integration.
- ERP Integration (Student and HRMs).
- Payment gateway integration.

I have been tasked by our school to make an attempt to integrate Koha with
other systems at the institution. Thank you in advance.


Regards,
Russel
___

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


Re: [Koha] RabbitMQ

2023-11-23 Thread Katrin Fischer

Hi Andrew,

can you give us your exact version? There is no released 23.10 and the
developer version should be 23.06. As Fridolin said, I believe RabbitMQ
is not mandatory right now and there is a SQL fallback.

Hope that helps,

Katrin

On 22.11.23 00:43, Andrew Hartung wrote:

So in a moment of stupidity I updated my server to 23.10 and rabbitMQ
will not build. I thought I was on the LTS, but wasn't. Koha states
that it is using SQL messaging. What are the ramifications from this?
I don't actually understand how rabbitMQ is used by koha.


___

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


Re: [Koha] koha installation error

2023-11-14 Thread Katrin Fischer

Hi Tom,

I tested the command in my Ubuntu 22 LTS installation and it worked OK.

Does the problem persist for you?

Could it be something is blocking access to debian.koha-community.org?

Hope this helps,

Katrin

On 13.11.23 03:14, Tom Obrien wrote:

Greetings,
I upgraded ubuntu server 16 LTS to 22 LTS.
I am trying to install koha but I get the following error:
wget -O- https://debian.koha-community.org/koha/gpg.asc | sudo apt-key add -
--2023-11-13 06:30:33--  https://debian.koha-community.org/koha/gpg.asc
Resolving debian.koha-community.org (debian.koha-community.org)... failed:
Temporary failure in name resolution.
wget: unable to resolve host address ‘debian.koha-community.org’
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d
instead (see apt-key(8)).
gpg: no valid OpenPGP data found.


Kindly assist me on how to overcome this problem.
Thank in advance.
Tom
___

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


Re: [Koha] How to display framework code

2023-11-11 Thread Katrin Fischer

Hi Dave,

in older versions this is not possible, but it displays by default from
23.05:

*Bug 33607*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33607> - Show
framework on record details page

Hope this helps,

Katrin

On 11.11.23 11:19, da...@penkler.net wrote:

Hi,
I would like to display the framework code associated with a record in
the staff interface detail page.
Thanks,
-Dave Penkler
Bibliothèque ABCeR - Centre Théologique de Meylan-Grenoble
___

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


Re: [Koha] Issue logging into staff interface [Plack log complains about missing encryption key]

2023-11-10 Thread Katrin Fischer

Hi Martin,

I believe that should have worked especially after your reboot. I would
add the key back, as you should not leave it with the placeholder string.

Maybe someone else has an idea?

Katrin


On 10.11.23 20:11, Martin Morris wrote:

Hello Katrin,



Thanks for your help.  I edited koha-conf.xml in 
/etc/koha/sites//koha-conf.xml, so I think that’s the right place?



I’m also using 2FA in case that helps.



Martin



- - - - - -



Hi Martin,



in which file did you replace it?



You were on the right track there, but make sure to add the entry to the

koha-conf.xml file used by your koha instances/sites. You might have

changed the template instead of the used file.



Hope this helps,



Katrin



On 10.11.23 16:02, Martin Morris wrote:


Hello all,
I’m having trouble logging into our staff interface this morning.  Here’s 
what’s happening:
*   I’m running koha 23.05.04
*   I get an Error 500 page after putting in my credentials
*   The only error message I can see in any log file is in plack-error.log
   *   Exception 'Koha::Exceptions::MissingParameter' thrown 'No 
encryption_key in koha-conf.xml. Please generate a key. We recommend one of at 
least 32 bytes. (You might use 'pwgen 32' to do so.)'
*   I currently have the following line in my koha-conf.xml file, as the last 
entry before 
   *   
__ENCRYPTION_KEY__

*   I’ve tried generating a password with ‘pwd 32’, copying the first entry 
and replacing __ENCRYPTION_KEY__ with that entry, and have rebooted, but it 
didn’t make any difference so I reverted.
Is this a bug?  A known issue?
Thanks in advance!
Martin
___
Koha mailing list  http://koha-community.org
Koha at lists.katipo.co.nz<https://lists.katipo.co.nz/mailman/listinfo/koha>
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

___

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


Re: [Koha] Deleting biblios and items

2023-11-10 Thread Katrin Fischer

Hi,

there is a command line script to create a new superlibrarian user, see:

http://kohageek.blogspot.com/2018/07/create-super-librarian-by-command-line.html

Hope this helps,

Katrin

On 10.11.23 16:35, Aida Djikic wrote:

Hi Anke,

I thought borrowers in this case meant users other than superuser; I should
have skipped that as I did before. But the zebraidx was doing nothing, and
I could not even quit the database; I had to close Putty.

It's good to know there's a way to re-create the super user; I'll try to
find that. If I don't manage, I'll create another instance - that has
already been suggested to me. I did indeed spend a lot of time on
customizations, but I saved a lot of that code so it's nothing I can't
afford to lose. This installation is literally me trying, failing, then
trying again. I am determined to get Koha working properly, no matter how
many times I have to redo it.

On Fri, Nov 10, 2023 at 2:52 PM Bruns, Anke  wrote:


Hi Aida, you may have accidentally deleted your super user if you
truncated the borrowers table.

There is a workaround to re-create the super user, afaik, but I'm not sure
where I got this info. Perhaps s.o. else can help?

Otherwise, if you haven't yet invested lots of work in customizing the
instance, it might be easiest to create a new instance and start again from
scratch.

Best regards, Anke


Am 10.11.2023 14:30 schrieb Aida Djikic :

Hello Anke and others,

I tried this again today; truncated the zebraqueue, and reset the zebra
index as listed on the wiki:

Reset Zebra index
  zebraidx -c /etc/koha/sites/your_koha_library/zebra-authorities-dom.cfg
-g iso2709 -d authorities init
  zebraidx -c /etc/koha/sites/your_koha_library/zebra-biblios-dom.cfg -g
iso2709 -d biblios init

(I replaced your_koha_library with the name of my instance) but nothing
happens, and when I try to log into my instance, I get an Error: Invalid
username or password.

Now what? Am I going to have to remove this instance of Koha and create
another?

On Thu, Nov 9, 2023 at 10:11 AM Aida Djikic  wrote:

Hi Anke,

no problem, I'll also keep digging. No, I did not; I didn't know it was
needed. I will have to look up how does one truncate zebraque.

On Thu, Nov 9, 2023 at 10:03 AM Bruns, Anke  wrote:

Hi Aida,



this seems strange to me. Unfortunately I don’t have time right now to dig
deeper into this. Maybe someone else could help?



Did you truncate zebraqueue? No idea if this is relevant to the problem
though.



Best regards,

Anke







--

Anke Bruns M.A. (LIS)

Arbeitsgruppe "Anwendungs- und Informationssysteme"

E-Mail: anke.br...@gwdg.de

-

Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen (GWDG)

Burckhardtweg 4, 37077 Göttingen, URL: https://gwdg.de



Support: Tel.: +49 551 39-3, URL: https://gwdg.de/support

Sekretariat: Tel.: +49 551 39-30001, E-Mail: g...@gwdg.de



Geschäftsführer: Prof. Dr. Ramin Yahyapour

Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger

Sitz der Gesellschaft: Göttingen

Registergericht: Göttingen, Handelsregister-Nr. B 598

-

Zertifiziert nach ISO 9001 und ISO 27001

-







*Von:* Aida Djikic 
*Gesendet:* Donnerstag, 9. November 2023 09:59
*An:* Bruns, Anke 
*Cc:* koha@lists.katipo.co.nz
*Betreff:* Re: [Koha] Deleting biblios and items



Hello Anke,



yes, I had to go back and rebuild it because I forgot to do it the first
time. I used



sudo koha-rebuild-zebra -f -v instancename



but they are still there: when I go to Authorities > Search main heading,
I get a list of 580 entries. Some of them are personal names, some are
topical terms though none of them are marked as such, only as Default. I'm
not sure why they weren't removed.







On Thu, Nov 9, 2023 at 9:45 AM Bruns, Anke  wrote:

Hi Aida,



good to know that it worked well. As to the autorities, if you also
truncated the auth_header table they should be gone. What you see might be
the Zebra index entries – did you rebuild the Zebra index (or if you use
ElasticSearch, I suppose the index has to be rebuilt as well after deleting
the records).



Best regards,

Anke



*Von:* Aida Djikic 
*Gesendet:* Mittwoch, 8. November 2023 12:07
*An:* Bruns, Anke 
*Cc:* koha@lists.katipo.co.nz
*Betreff:* Re: [Koha] Deleting biblios and items



Hello Anke,



thank you for the directions; I have followed them and have managed to
remove all records. When I run an authority search, I get a list of all of
them, though they are now lacking a heading type (it is now marked as
"Default"). Is it possible to bulk remove all of them from search results
as well or will I need to delete them one by one?



The ones that were not attached to records have a Delete option, but the
few that were have only an Edit option which leads to a "The authority
record you requested does not exist" note.

Re: [Koha] Demand - on Koha import

2023-11-10 Thread Katrin Fischer

Hi,

I can see a few things that could cause you issues:

952

$2 = Koha expects the code of the classification scheme here, not the
description. You can find all the available codes under administration >
classification configuration. For DDC it's ddc.

$d = The accession is probably the wrong format. We usually use
-MM-DD. I haven't tested if the date in the format chosen in the
DateFormat system preference works as well.

How many records do you have in your file? The process bar might appear
stuck at 0% for a big file.

I think I'd set the index in the matching rule without the :w and use
just Title-cover.

Hope this helps,

Katrin

On 09.11.23 17:06, Olcese Martina EXT wrote:

Dear Ladies and Sirs,

Following the exchange on the Koha mailing list on bulk upload, I wish to 
request your advice regarding own import process.

Steps:

1.We converted our source excel into Marc .mrk format via Marcedit.
=LDR  0nam a220Ia 4500
=008  231106sxx\||\||und||
=020  \\$a9780691228662
=100  \\$aGoldin, Claudia
=245  \0$aCareer and Family.$bWomen's Century-Long Journey toward Equity
=260  \\$aPrincenton$bPrincenton University 
Press$c2021
=300  \\$bBook
=700  \\$aCameron, Bruce G.Selva, Daniel
=942  \\$cBK
=952  \\$10$2Dewy Decimal 
Classification$aITER-LIBRARY$bITER-LIBRARY$d10/31/23$i02250$o331.42$p02250$yBK

=LDR  0nam a220Ia 4500
=008  231106sxx\||\||und||
=020  \\$a9781292110844
=100  \\$aCrawley, Edward F.
=245  \0$aSystem architecture.$bStrategy and product development for complex 
systems
=260  \\$aEdinburgh$bGlobal Edition$c2015
=300  \\$bBook
=942  \\$cBK
=952  \\$10$2Dewy Decimal 
Classification$aITER-LIBRARY$bITER-LIBRARY$d10/31/23$i02252$o620$p02252$yBK

2.and then staged the .mrc file as per instructions on various sites
Home<https://koha-admin.iter.org/cgi-bin/koha/mainpage.pl>  - 
Tools<https://koha-admin.iter.org/cgi-bin/koha/tools/tools-home.pl> - Stage MARC records 
for import<https://koha-admin.iter.org/cgi-bin/koha/tools/stage-marc-import.pl>
No profile - Bibliographic - UTF-8 - MARC - 245a matching rule  - replace 
existing record with incoming record if match- add incoming record if no match  
- check imbedded items

3.The staging of the two sample files was successful:
MARC staging results
Processing bibliographic records
2 records in file
0 records not staged because of MARC error
2 records staged
0 records with at least one match in catalog per matching rule "245"
0 item records found and staged

4.Yet, the batch import into the catalogue did not work. The import 
batch into catalog remained blocked at 0%.
Home<https://koha-admin.iter.org/cgi-bin/koha/mainpage.pl> 
Tools<https://koha-admin.iter.org/cgi-bin/koha/tools/tools-home.pl> Manage staged MARC 
records<https://koha-admin.iter.org/cgi-bin/koha/tools/manage-marc-import.pl> Batch 
40<https://koha-admin.iter.org/cgi-bin/koha/tools/manage-marc-import.pl?import_batch_id=40>

Would you please help us to clarify why the process does not work? Is there an 
error in the .mrk file?






5.   Further, I notice that the 245a matching rule is not 
working, as it seems not able to retrieve records with the same title already 
on Koha

Home<https://koha-admin.iter.org/cgi-bin/koha/mainpage.pl> 
Administration<https://koha-admin.iter.org/cgi-bin/koha/admin/admin-home.pl> Record matching 
rules<https://koha-admin.iter.org/cgi-bin/koha/admin/matching-rules.pl> Modify record matching 
rule<https://koha-admin.iter.org/cgi-bin/koha/admin/matching-rules.pl?op=edit_matching_rule_id=4>
Description: 245a - Match threshold 1000  - Search index Title-cover:w  -  
Score 1000  - Tag 245 - subfield a - normalization none
May I ask you either there is a mistake on the setting of the matching rule?


Thank you very much in advance for your kind help.



___

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


Re: [Koha] Issue logging into staff interface [Plack log complains about missing encryption key]

2023-11-10 Thread Katrin Fischer

Hi Martin,

in which file did you replace it?

You were on the right track there, but make sure to add the entry to the
koha-conf.xml file used by your koha instances/sites. You might have
changed the template instead of the used file.

Hope this helps,

Katrin

On 10.11.23 16:02, Martin Morris wrote:

Hello all,

I’m having trouble logging into our staff interface this morning.  Here’s 
what’s happening:


   *   I’m running koha 23.05.04
   *   I get an Error 500 page after putting in my credentials
   *   The only error message I can see in any log file is in plack-error.log
  *   Exception 'Koha::Exceptions::MissingParameter' thrown 'No 
encryption_key in koha-conf.xml. Please generate a key. We recommend one of at 
least 32 bytes. (You might use 'pwgen 32' to do so.)'
   *   I currently have the following line in my koha-conf.xml file, as the last 
entry before 
  *   
__ENCRYPTION_KEY__

   *   I’ve tried generating a password with ‘pwd 32’, copying the first entry 
and replacing __ENCRYPTION_KEY__ with that entry, and have rebooted, but it 
didn’t make any difference so I reverted.

Is this a bug?  A known issue?

Thanks in advance!

Martin



___

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


Re: [Koha] Wrong person listed in 245$c statement of responsibility after import

2023-11-07 Thread Katrin Fischer

Hi Aida,

I don't know your process, but the thing that matters is how the data
presents in the MARC file you import into Koha. So this should have one
952 per item.

Katrin


On 06.11.23 12:15, Aida Djikic wrote:

Hello Katrin,

 if you have the author in 100$a and 245$c it should work out.

I re-exported from Excel and double-checked to make sure they are the
same (100$a has the author as Surname, Name, and 245$c as Name Surname).

could you please clarify this part, I'm not sure what you meant:

 Maybe one common mistake: when creating items and maybe other
fields,
 make sure that all subfields for one item are within the same field:
 952$a...$b... instead of separate 952 fields.

Do you mean keeping them all in same column in Excel or joining them
later in MarcEdit?

Message: 2
Date: Sat, 4 Nov 2023 12:46:19 +0100
From: Katrin Fischer 
To: koha@lists.katipo.co.nz
Subject: Re: [Koha] Wrong person listed in 245$c statement of
        responsibility after import
Message-ID: <49b4feae-d137-4076-ae8e-362df8fed...@web.de>
Content-Type: text/plain; charset=UTF-8; format=flowed

Hi,

I don't see any obvious mistake in the mapping, but if you have the
author in 100$a and 245$c it should work out.

Koha imports the MARC record as is, not making changes to it (unless you
are using MARC modification templates).

Maybe one common mistake: when creating items and maybe other fields,
make sure that all subfields for one item are within the same field:
952$a...$b... instead of separate 952 fields.

Hope this helps,

Katrin


--
Regards,
Aida

___

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


Re: [Koha] Question on MARC Frameworks and Staging/Importing records

2023-11-04 Thread Katrin Fischer

Hi Anke,

we only use the default framework usually, apart from locally catalogued
items, so there might be other tricks I am missing.

The framework use for a record is stored in biblio.frameworkcode. And
you could update it with SQL. Not sure if it's cached and if that would
take effect immediately, but that's easy to find out.

Hope this helps,

Katrin

On 03.11.23 14:24, Bruns, Anke wrote:

Hi,

as I inadvertently imported some batches of records with the standard
framework instead of the library's configured one, I think about how this
can be corrected without having to repeat the imports.

Can one
a) recognize and
b) batch change the MARC framework with which records have been imported via
the WWW interface?

Thanks in advance and best regards,
Anke




___

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


Re: [Koha] Wrong person listed in 245$c statement of responsibility after import

2023-11-04 Thread Katrin Fischer

Hi,

I don't see any obvious mistake in the mapping, but if you have the
author in 100$a and 245$c it should work out.

Koha imports the MARC record as is, not making changes to it (unless you
are using MARC modification templates).

Maybe one common mistake: when creating items and maybe other fields,
make sure that all subfields for one item are within the same field:
952$a...$b... instead of separate 952 fields.

Hope this helps,

Katrin

On 31.10.23 11:25, Aida Djikic wrote:

Hello all,

What could I be doing wrong when it comes to my attempt to import theses
and dissertations into Koha via MarcEdit? They were exported from an old
program not really meant for libraries and have been saved as an Excel
file. Some of these records would be treated as items in Koha, but in that
program they were duplicates distinguished by additional designation added
to the call numbers.

After some early issues I thought I had worked them out, and have focused
on cleaning up the data since so I can continue importing it. However,
recently I noticed that the persons listed in 245$c statement of
responsibility do not correspond to the person that should be there (the
author of the thesis).

I am wondering where I could have made a mistake in the import process that
could have resulted in such an error. These are the fields I ultimately
decided to use in Excel, with the help of Fred and Lauren (names in the
example redacted for privacy):

003$0 Control number identifier BA-SaSST
040$c Transcribing agency BA-SaSST
041$a Language eng
080$a UDC 004.65
080$x UDC aux (043.2)
100$a Author Surname, Name
245$a Title Software application for accounting and quantity management of
goods :
245$b Remainder of title undergraduate thesis /
245$c Statement of responsibility, etc. Name Surname
264$a Place of publication Sarajevo
264$b Publisher N. Surname
264$c Year of publication 2008
300$a Physical description (pages) [ ], [ ] pages
300$b Physical description (illustr. etc.) ill. ;
300$c Physical description (dimensions) 30 cm.
500$a General note Includes an abstract.
502$a Dissertation note Computer Science major with Economics minor
502$b Degree type Undergraduate degree
502$c Degree granting institution [dgg] University Sarajevo School of
Science and Technology
502$d Year degree granted 2008
504$a Bibliographical and other notes Includes bibliography and other notes.
526$a Study program information Undergraduate degree in Computer Science
and Economics
563$a Binding Perfect paperback
700$a Thesis advisor [name] Surname, Name
700$e Thesis advisor [relator term] Thesis advisor
546$a Language English
650$a Subject added entry Computer science
653$a Index term - uncontrolled Economics
942$c Koha Item type TH
952$a Home library LBRM21
952$b Current library LBRM21
952$1 Lost 0
952$8 Collection code BSc_CS-ECON
952$c Location THESES
952$i Inventory number T0013/2008
952$o Full call number 004.65(043.2) SUR Sof
952$t copy number 1
952$p Barcode SSSTKL001
952$y Item TH

Should I only import records at first, then add items from within Koha?

In addition to the above issue, I have also noticed that the import doesn't
result in a record + an item in cases where I have two or more copies of a
thesis but it imports them as separate records. How can I make sure to
import multiple copies as items?

I was thinking about asking this at the next cataloging SIG but I am not
certain I would make it. Thank you in advance!



___

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


Re: [Koha] null values

2023-11-02 Thread Katrin Fischer

Hi Paulo,

your Koha won't function correctly if you are missing homebranch,
holdingbranch or itemtype in your items. If you removed the MARC
reference, you should restore it. For MARC21 the default mappings are:

952$a homebranch

952$b holdingbranch

952 $y itype

If you are using UNIMARC, you'll need to check a standard Koha for the
correct defaults.

Hope this helps,

Katrin

On 02.11.23 17:45, Paulo Neto wrote:

Hello Katrin,

Thank you for your answer. We dont have any marc reference for the holding 
branch defined on the bibliographic model as far as i have checked so in terms 
of the database this makes sense for the null value
Showing up, wehave a record for the home branch but we wont have a record for 
the holding branch.

Paulo Neto
DSIGA / DPGI
Tel. (+351) 21 844 2228
http://www.dgadr.gov.pt







-Mensagem original-
De: Koha  Em Nome De Katrin Fischer
Enviada: 30 de outubro de 2023 16:53
Para: koha@lists.katipo.co.nz
Assunto: Re: [Koha] null values

Hi Paulo,

please check if you have hidden the homebranch (952$a) and holdingbranch
(952$b) in your frameworks. If you have only one branch, you can use a default 
value, if you have multiple, make them visible again and they will be 
automtically pre-set with the homebranch of the cataloger.

Hope this helps,

Katrin

On 30.10.23 17:05, Paulo Neto wrote:

Hello,

I am able to solve the problem (thanks to Kaitrin) but i am not able to prevent it, how 
can i prevent "holding branch" getting null values at item table, i think this 
is happing to every new items created in the koha database.
I am not a librarian myself, does this have to do how our librarian coleagues 
are creating the items, am i missing any configuration set up parameter?

++-+---++
| itemcallnumber | barcode | holdingbranch | homebranch |
++-+---++
| 9349/M | 9349/M  | NULL| BACOSTA|
| 23623/M| 23623/M | NULL  | BACOSTA|
| 23624/M| 23624/M | NULL  | BACOSTA|
| 23625/M| 23625/M | NULL  | BACOSTA|
| 23626/M| 23626/M | NULL  | BACOSTA|
| 23627/M| 23627/M | NULL  | BACOSTA|
| 23628/M| 23628/M | NULL  | BACOSTA|
| 23629/M| 23629/M | NULL  | BACOSTA|
| 23630/M| 23630/M | NULL  | BACOSTA|
| 23631/M| 23631/M | NULL  | BACOSTA|
++-+---++

Best regards,

Paulo Neto
DSIGA / DPGI
Tel. (+351) 21 844 2228
http://www.dgadr.gov.pt







___

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
___

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


Re: [Koha] null values

2023-10-30 Thread Katrin Fischer

Hi Paulo,

please check if you have hidden the homebranch (952$a) and holdingbranch
(952$b) in your frameworks. If you have only one branch, you can use a
default value, if you have multiple, make them visible again and they
will be automtically pre-set with the homebranch of the cataloger.

Hope this helps,

Katrin

On 30.10.23 17:05, Paulo Neto wrote:

Hello,

I am able to solve the problem (thanks to Kaitrin) but i am not able to prevent it, how 
can i prevent "holding branch" getting null values at item table, i think this 
is happing to every new items created in the koha database.
I am not a librarian myself, does this have to do how our librarian coleagues 
are creating the items, am i missing any configuration set up parameter?

++-+---++
| itemcallnumber | barcode | holdingbranch | homebranch |
++-+---++
| 9349/M | 9349/M  | NULL| BACOSTA|
| 23623/M| 23623/M | NULL  | BACOSTA|
| 23624/M| 23624/M | NULL  | BACOSTA|
| 23625/M| 23625/M | NULL  | BACOSTA|
| 23626/M| 23626/M | NULL  | BACOSTA|
| 23627/M| 23627/M | NULL  | BACOSTA|
| 23628/M| 23628/M | NULL  | BACOSTA|
| 23629/M| 23629/M | NULL  | BACOSTA|
| 23630/M| 23630/M | NULL  | BACOSTA|
| 23631/M| 23631/M | NULL  | BACOSTA|
++-+---++

Best regards,

Paulo Neto
DSIGA / DPGI
Tel. (+351) 21 844 2228
http://www.dgadr.gov.pt







___

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


Re: [Koha] Problems found

2023-10-24 Thread Katrin Fischer

Hi Paulo,

have a look at these page:

https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix

It's a problem that exists with certain DBMS versions. If your version
is still affected, you need to fix the data and implement the fix
suggested there to keep it from happening.

To clean the data the easiest way is to delete the listed entries from
the deleted* and old* tables.

Hope this helps,

Katrin

On 24.10.23 18:24, Paulo Neto wrote:

Hello,

At koha intranet , opções system information (about koha) i get the fallowing 
on problems found:

You got record, x,y,z,w on both tables biblio and deletedbiblio

You got record, f,g,h,x on both items and deleteditems

You got record, g,h,y  on both tables issues e old_issues

How can i solve this withouth causing database consistency issues.

Best regards,

Paulo Neto
DSIGA / DPGI
Tel. (+351) 21 844 2228
http://www.dgadr.gov.pt







___

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


Re: [Koha] Possible Batch Permissions Modification Plug-In broken with v23.05.04

2023-10-23 Thread Katrin Fischer

Hi,

have you checked if maybe not the plugin is faulty, but a change in the
permissions is required?

23.05 includes this new feature that could be related to your problem:

*Bug 20256*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20256> - Add
ability to limit editing of items to home library or library group

Also: plugin problems should always be filed as issues on the repository
of the plugin itself.

Hope this helps,

Katrin

On 21.10.23 00:33, Rudy Hinojosa wrote:

I implemented the Bywater solution Batch Permissions Modification plug
in with previous versions of Koha and had no issues, until I upgraded
to v23.05.04. Suddenly I started receiving client tickets stating that
librarians that were not super librarians could not edit their own
library items. My client is configured in a consortium style on one
database.

I noticed there is more granular permissions that have been added with
this new release. Maybe that has possibly created a mismatch in the
bitvector logic for the plug in.

My temporary solution was to make the normal staff template assign
super librarian roles to everyone temporarily.

Has anyone come across this issue yet?


___

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


Re: [Koha] FW: errors on opac log

2023-10-23 Thread Katrin Fischer

Hi Paulo,

you could create an SQL report in the reports module. Something along
these lines should work:

select itemcallnumber, barcode, holdingbranch, homebranch from items
where holdingbranch is null or homebranch is null;

Hope this helps,

Katrin

On 23.10.23 12:14, Paulo Neto wrote:

Hi David,

Thank you for the fast answer.

I dont think ISBD display is customized.

Can you give me a hint on how can i identify items for records with invalid or 
non-existent home and current library values ?

Best regards,


Paulo Neto
DSIGA / DPGI
Tel. (+351) 21 844 2228
http://www.dgadr.gov.pt/


De: David Nind <mailto:da...@davidnind.com>
Enviada: 20 de outubro de 2023 17:55
Para: Paulo Neto <mailto:pn...@dgadr.pt>
Cc: koha <mailto:koha@lists.katipo.co.nz>
Assunto: Re: [Koha] errors on opac log

Hi Paulo.

I can't replicate on the current master with the sample data, using the 
development environment (KTD or koha-testing-docker).

Some ideas (these probably don't have anything to do with the issue):
- Have you customised the default  ISBD display using the OPACISBD system 
preference?
- Do you have any items for records with invalid or non-existent home and 
current library values? You may need to create a report to identify these.

David Nind
New Zealand

On Fri, 20 Oct 2023 at 08:20, Paulo Neto <mailto:pn...@dgadr.pt> wrote:
Hello,

I am getting lots of these errors on opac log -opac-error.log-

[Thu Oct 19 17:24:15.428577 2023] [cgi:error] [pid 19289] [client 
xxx.xxx.xxx:35920] AH01215: [Thu Oct 19 17:24:15 2023] op
ac-ISBDdetail.pl: Use of uninitialized value $holdingbrtagf in string eq at 
/usr/share/koha/lib/C4/Biblio.pm line 755.: /us
r/share/koha/opac/cgi-bin/opac/opac-ISBDdetail.pl

How can i solve this ?

Paulo Neto

DGADR
DSIGA / DPGI
Tel. (+351) 21 844 2200







___

Koha mailing list  http://koha-community.org
mailto: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

___

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


Re: [Koha] Loan periods

2023-10-19 Thread Katrin Fischer

Reply below:

On 19.10.23 14:07, Wagner, Alexander wrote:

And you could use the item type to
create some "alert" on checkin/checkout to remind your staff about the
special use case.

Those would show once staff returns the items in the admin interface, right?


Yes, you could use the checkin note configurable in the itemtype
administration page. With a little jQuery you could also do some time of
alert on the checkout page.




Sometimes item types and material types overlap, but not always.

Maybe it's just the words that confused me a bit, as I had read `item` like 
`material`. The examples are a bit suggestive in this sense.

I know that the German translation is not helping here. I think for a
lot of libraries material types and loan types  correlate, but it
doesn't make sense for every library.



You'll find that you can pretty much hide
the item type from display anywhere in the OPAC using configuration. If
you are looking for something specific, let us know.

Thank you. I'll shout out loud for help if I get lost :)



Katrin
___

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


Re: [Koha] HTML Display in Normal View

2023-10-18 Thread Katrin Fischer

Hi Erlanda,

Koha is not supporting HTML in MARC records. It might work in some 
places, but not in all and might get changed at some point. It could 
also create issues if you want to exchange your record with other systems.


Katrin


On 16.10.23 08:17, erlanda_simon...@flib.sci.am wrote:

Hello List,
we are using Koha version 21.11.05

For better display in 520 field we are using some HTML commands.
In the ISBD view of the record the 520 field is displayed in accordance with 
HTML commands.
But in the Normal view all HTML commands are not suppressed (see the display 
below).
Is this a bug?
Is it possible to suppress the HTML commands in the Normal View?

thanks,
Erlanda


Summary: 1887, Թիւ 1 ՀՆՉԱԿ, Լօնդօն, Հայկական ազատ տպարան: 1888, Թիւ 2- Թիւ 11/12 ՀՆՉԱԿ, Լօնդօն, Հայկական ազատ տպարան: 1889, ԵՐԿՐՈՐԴ ՏԱՐԻ, Թիւ 1 - Թիւ 4 ՀՆՉԱԿ, Լօնդօն, Հայկական ազատ տպարան: 1890, ԵՐՐՈՐԴ ՏԱՐԻ, Թիւ 1 - Թիւ 12 ՀՆՉԱԿ, Լօնդօն, 
Հայկական ազատ տպարան: 1891, ՉՈՐՐՈՐԴ ՏԱՐԻ, Թիւ 1 - Թիւ 16 ՀՆՉԱԿ, Լօնդօն, Հայկական ազատ տպարան: 1892, ՀԻՆԳԵՐՈՐԴ ՏԱՐԻ, Թիւ 1 - Թիւ 9 ՀՆՉԱԿ, Լօնդօն, Հայկական ազատ տպարան: 1892, ՀԻՆԳԵՐՈՐԴ ՏԱՐԻ, Թիւ 10 - Թիւ 12 ՀՆՉԱԿ, Աթէնք, Հայկական ազատ տպարան: 1893, ՎԵՑԵՐՈՐԴ 
ՏԱՐԻ, Թիւ 1 - Թիւ 11/12 ՀՆՉԱԿ, Աթէնք, Հայկական ազատ տպարան: 1894, ԵՕԹԵՐՈՐԴ ՏԱՐԻ, Թիւ 1 - Թիւ 13 ՀՆՉԱԿ, Աթէնք, Հայկական ազատ տպարան: 1895, ՈւԹԵՐՈՐԴ ՏԱՐԻ, Թիւ 1 - Թիւ 10 ՀՆՉԱԿ, Աթէնք, Հայկական ազատ տպարան: 1895, ՈւԹԵՐՈՐԴ ՏԱՐԻ, Թիւ 11 ՀՆՉԱԿ, Լօնդօն, 
Հայկական ազատ տպարան: 1895, ՈւԹԵՐՈՐԴ ՏԱՐԻ, Թիւ 12 - Թիւ 24 ՀՆՉԱԿ : ԿԵՆՏՐՕՆԱԿԱՆ ՕՐԳԱՆ ՀՆՉԱԿԵԱՆ ԿՈՒՍԱԿՑՈՒԹԵԱՆ , Լօնդօն, Տպարան "Հնչակի": 1896, ԻՆՆԵՐՈՐԴ ՏԱՐԻ, Թիւ 1 - Թիւ 22 ՀՆՉԱԿ : ԿԵՆՏՐՕՆԱԿԱՆ ՕՐԳԱՆ ՀՆՉԱԿԵԱՆ ԿՈՒՍԱԿՑՈՒԹԵԱՆ , Լօնդօն, Տպարան "Հնչակի": 1897, 
ՏԱՍՆԵՐՈՐԴ ՏԱՐԻ, Թիւ 1 - Թիւ 12 ՀՆՉԱԿ : ԿԵՆՏՐՕՆԱԿԱՆ ՕՐԳԱՆ ՀՆՉԱԿԵԱՆ ԿՈՒՍԱԿՑՈՒԹԵԱՆ , Լօնդօն, Տպարան "Հնչակի": 1898, ՏԱՍՆԵՒՄԷԿԵՐՈՐԴ ՏԱՐԻ, Թիւ 1 - Թիւ 3 ՀՆՉԱԿ : ԿԵՆՏՐՕՆԱԿԱՆ ՕՐԳԱՆ ՀՆՉԱԿԵԱՆ ԿՈՒՍԱԿՑՈՒԹԵԱՆ , Լօնդօն, Տպարան "Հնչակի": 1899, ՏԱՍՆԵՒԵՐԿՐՈՐԴ ՏԱՐԻ, Թիւ 1, Թիւ 
2 ՀՆՉԱԿ : ԿԵՆՏՐՕՆԱԿԱՆ ՕՐԳԱՆ ՀՆՉԱԿԵԱՆ ԿՈՒՍԱԿՑՈՒԹԵԱՆ , Լօնդօն, Տպարան "Hentchak":
___

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


Re: [Koha] Restrict suggestions shown on OPAC

2023-10-18 Thread Katrin Fischer

Hi,

try the OPACViewOthersSuggestions system preference. It should make it
so only logged in users can see their own suggestions.

Hope this helps,

Katrin

||

On 17.10.23 07:20, Ms. Naveen Ali wrote:

Dear Sir,

Thank you for your response. I have updated this preference.
Problem is still not resolved.

Looking forward to support please.

With best regards,

Naveen Ali

ITM-JE (EAKL)
Inst Representative for
HEC Digital Library Resources.
NEDUET, Karachi.


- Original Message -

From: "Zahid Iqbal"
To:nav...@neduet.edu.pk, "koha"
Sent: Thursday, 12 October, 2023 7:30:51 PM
Subject: Re: [Koha] Restrict suggestions shown on OPAC

Hi,
you have to disable / do not allow the AnonSuggestions in opac preferences
Regards,

___

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


Re: [Koha] Koha as an identity provider

2023-10-18 Thread Katrin Fischer

Hi,

I think others have already done a great job in explaining why the
password/userid file approach won't work like that. But there is the
ILS-DI and the REST API that can be used to implement authentication
with external services if none of the other suggestions is an option.

Hope this helps,

Katrin

On 18.10.23 07:13, Rupinder Singh wrote:

Hi,
I am thinking I can use koha as an identity provider for other Librayr
services like repository and off-campus remote access, etc.
Because, In koha, we usually already have complete details of our patrons,
and we also give koha login credentials to them, I was thinking if we use
the borrower table from the database, and share the username and password
fields for other external services.
just a thought, please give your views on this possibility.

Thank you
Rupinder Singh
___

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


Re: [Koha] Single Item due mail

2023-10-18 Thread Katrin Fischer

Hi,

<> doesn't work in this notice. You'll need to use
<> or Template Toolkit syntax. For some information on
the repeatable information in some notices see here:
https://wiki.koha-community.org/wiki/Notice_documentation_rfc

Hope this helps,

Katrin

On 17.10.23 11:52, JITHIN N wrote:

I checked the "digest" checkbox in the messaging preference also verified
in the patron page. The message of DUEDGST notice is customised as

*The Following books in Due*



*<>Thank you,*
*Librarian*


But the result as below which does not have the bibliographic
information(Book Titles )


*The Following books in Due*


*Thank you,*
*Librarian*



Please Help


With regards
Jithin N



On Sun, Oct 15, 2023 at 2:15 PM JITHIN N  wrote:


The Item due notice mail sending as individual mails to patron for each
book. Is there any way to sent the details (Bibliographic Information) that
are due in a single mail .


With regards
JITHIN N


___

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


Re: [Koha] Loan periods

2023-10-15 Thread Katrin Fischer

Hi Alexander,

some thoughts/ideas what you could try:

For the newly acquired materials:

* You could use the "Item modifications by age" too to automatically
move them from a short term loan itemtype to a different item type using
some rules and the "age" of the items.

* You could also use the course reserves module to give them a temporary
item type that is then switched to the final one when they are removed
from the 'shelf'/course reserve.

For the databases/licenses

* I also lean towards manually entering the due date on checkout, as
Caroline suggested.  You could then summarize those under one itemtype
like 'individual loan period' or 'license/subscription' and have that
show up in the OPAC search filters. And you could use the item type to
create some "alert" on checkin/checkout to remind your staff about the
special use case.

In general we also use the item types to indicate the type of use
'reference material' or 'normal loan'. Sometimes item types and material
types overlap, but not always. You'll find that you can pretty much hide
the item type from display anywhere in the OPAC using configuration. If
you are looking for something specific, let us know.

Hope this helps,

Katrin

On 12.10.23 15:28, Wagner, Alexander wrote:

Hello!

Being pretty new to Koha I still struggle to get a solution for our loan 
periods.

I understand that Koha specifies loan periods based on `item types` and `patron 
types` and then calculates the loan period using the circulation matrix. I also 
believe I have an understanding of this matrix and I also know such concepts 
from other ILS.

However, in our library we assume that all patrons are created equal.

Now, we (currently) assume that not all books (just to take one item type) are 
created equal.

IOW in our current system we have books with a loan period of 4 weeks (usual default) while we also 
have books with a loan period of 3 days (being open 24/7 with self service checkout this is our 
`not for loan`) and others with 2 years. Currently, any patron (they are all equal) can have items 
with any of these loan periods. Eg. I got Peskin/Schroeder as as desktop reference for 2 years. 
Then go to the library during my usual working hours (10pm or so ;) and up pick Bailin/Love from 
the open shelves to prepare the next lecture and while I am there I spot this interesting "new 
piece over there" and add it to the lot not noticing that it should stay there for a week or 
so. (Telling our SIP terminal "you can not take this" will not work well, especially as 
most of our patrons would not notice the red frownie and no-one would notice the beeps at the 
entrance in the middle of the night.)

However, till here I can model most of it by creating an item type `book` along 
with `desktop reference` for the first two items. I do not yet see the new 
items shelve (a temporary location) where items stay for a week till they move 
to their permanent location with a regular loan period of 4 weeks. (IOW in our 
current system the loan period sometimes depends on temporary locations.)

Still, this requires to add a new item type for each loan period.

When it comes to databases we now have a number of different loan periods, as 
we model them as the subscription period minus some contract dependent time to 
allow for cancellation (or renewal). E.g. some are subscriptions for campus 
(real not for loan) with some contract running a year. The next contract runs 3 
years with 4 month before it's end for cancellation.

Then we have individually licensed accesses ranging from a monthly or bi-monthly period 
to years. Those are currently checked out to the patrons who have the access and we use 
the reminders as notification to our patrons ("should we renew?") and the 
renewals as a notification to us that the contract should indeed be renewed for another 
period. How would I model this in Koha? Do I really create a host of item types with 
funny names like

1 week, 2 weeks, 3 weeks, 4 weeks, 5 weeks, 6 weeks, 7 weeks, 8 weeks, 1 month, 
2 months, 3 months, 4 months, 5 months, 6 months, 7 months, 8 months, 9 months, 
10 months, 11 months, 12 months, 18 months, 24 months, 30 months, 36 months, 42 
months, 48 months, 54 months, 60 months, 66 months, 72 months, 78 months

It looks a bit messy in cataloguing but these would also show up in the OPAC 
(eg. in the advanced search limiters).

In our current system I just had a subfield on item level where I could specify 
a loan period. Do I get it right that this concept does not exist and can not 
be modeled in Koha? How can I get around this? How do others handle this? Maybe 
I need a different angle to look at it...


___

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


Re: [Koha] Cannot stage authority files in 22.11.

2023-10-15 Thread Katrin Fischer

Hi,

I've looked in bugzilla and found this bug:

*Bug 34965*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34965> -
Authority match failing due to possible encoding conflicts

I am not sure if it's related, but maybe something to look into.

Hope this helps,

Katrin

On 25.09.23 06:25, Raymund Delahunty wrote:

We moved from 21.11 to 22.11 recently and since then attempts to stage and 
import authority record have failed. We are using the LC-card-number index as 
the matchpoint and have tried changing the normalisation rule from None to 
Remove spaces but the stage still fails. We can stage without matching, but 
when we change the matchpoint afterwards to LC-card-number (auth 010$a) we 
receive an Error 500. We have also had a problem with diacritics in authority 
searches when using Zebra and on our test server this is solved using 
Elasticsearch which we are testing out. But ES has not resolved our auth 
staging problem. Any ideas?

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 listhttp://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


Re: [Koha] [translate] Migrate Pootle to Weblate

2023-10-15 Thread Katrin Fischer

Hi,

I added some notes at the bottom of the wiki page.

Hope it helps,

Katrin

On 29.09.23 15:14, Jonathan Druart wrote:

Hello everybody,

A quick update, I am back on this and I logged the progress on the wiki:
https://wiki.koha-community.org/wiki/Translation_server_migration_weblate
If you have worked with Weblate already and know it well, please let me
know, I have a couple of questions :)

Cheers,
Jonathan

Le jeu. 13 juil. 2023 à 17:12, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> a écrit :


Hello everybody,

If you are a translator of Koha you should read this.

Pootle is dead and we should move to Weblate, which is an active and
well maintained project.
We have been setting up a test server to let translators see how it goes.
THIS IS A TEST SERVER: none of the changes will be saved!

There are some changes in how the projects are structured.
We will now have 2 projects: "koha" and "koha-manual". Each will
contain several "components".
One component in Pootle can only track on po file, which means we need
one component per po file:
https://translate.test.koha-community.org/projects/koha/ shows
https://snipboard.io/rtKdTS.jpg

It can be a bit disturbing at first, but there is this view:
https://translate.test.koha-community.org/languages/es/koha/ that
shows the progress per language: https://snipboard.io/UCJ1Ky.jpg

The big win are:
* We should no longer get "Critical errors: Python brace placeholders"
(to be confirmed)
* Translation changes will be propagated between the components of a
given project, and so between versions: if you modify a string for
23.05 it will also modify it for the other branches! (to be confirmed
as well!)

guest user (not logged in) can only make suggestions:
https://translate.test.koha-community.org/

User reviewer/6Mx1$HU*1KNbzCZV can accept suggestions.

You are welcome to test and provide feedback!

There is still a lot of work before effectively doing the migration,
but we need first to know if users/translators are happy with it!

Let us know!
Cheers,
Jonathan

PS: About the structure of the projects, I've contacted the author of
Weblate: https://github.com/WeblateOrg/weblate/discussions/9556
Next version will add a mecanism to structure components within a project!


___

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


Re: [Koha] Single Item due mail

2023-10-15 Thread Katrin Fischer

Hi,

did you check the "digest" checkbox in the messaging preferences?

The DUEDGST notice is then used and includes information on all items
becoming due.

Hope this helps,

Katrin

On 15.10.23 10:45, JITHIN N wrote:

The Item due notice mail sending as individual mails to patron for each
book. Is there any way to sent the details (Bibliographic Information) that
are due in a single mail .


With regards
JITHIN N
___

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


Re: [Koha] [Koha-translate] Translators - Do not wrap strings in PO files

2023-10-11 Thread Fischer, Katrin
Hi Jonathan,

 

I think it doesn’t present like that in Pootle. All the strings on multiple 
lines are amended:

 

https://translate.koha-community.org/de/23.05/translate/#search=Summer 
<https://translate.koha-community.org/de/23.05/translate/#search=Summer=source,target>
 =source,target

 

It’s only visible if you edit the po files directly. I haven’t checked how 
Weblate handles them.

 

Hope this helps,

 

Katrin

 

Von: Koha-translate  Im 
Auftrag von Jonathan Druart
Gesendet: Mittwoch, 11. Oktober 2023 10:58
An: koha-transl...@lists.koha-community.org; koha 
Betreff: Re: [Koha-translate] Translators - Do not wrap strings in PO files

 

Well, of course it has been wrapped!

It should read like: http://paste.debian.net/1294738/

 

Le mer. 11 oct. 2023 à 10:50, Jonathan Druart 
mailto:jonathan.dru...@bugs.koha-community.org> > a écrit :

Hello,

 

I have a question for translators: do you like how strings are wrapped in PO 
files?

 

In the context of moving our translations server to weblate we will have to 
reorder the PO files, and maybe we could take that opportunity for other 
changes.

 

One of them could be to not wrap lines, and have a single long line instead.

 

For instance:

Now:

msgid ""
"%s %sSpring%s %s %sSummer%s %s %sFall%s %s %sWinter%s %s %sSpr%s %s %sSum%s "
"%s %sFal%s %s %sWin%s %s %s %s "
msgstr ""
"%s %sPrintemps%s %s %sÉté%s %s %sAutomne%s %s %sHiver%s %s %sPrtps%s %s "
"%sÉté%s %s %sAut%s %s %sHiv%s %s %s %s"

 

After:

msgid "%s %sSpring%s %s %sSummer%s %s %sFall%s %s %sWinter%s %s %sSpr%s %s 
%sSum%s %s %sFal%s %s %sWin%s %s %s %s "
msgstr "%s %sPrintemps%s %s %sÉté%s %s %sAutomne%s %s %sHiver%s %s %sPrtps%s %s 
%sÉté%s %s %sAut%s %s %sHiv%s %s %s %s"

 

For those who translate directly in the PO files, which version do you like 
more?

 

Regards,

Jonathan

 

Context:

https://wiki.koha-community.org/wiki/Translation_server_migration_weblate

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35024

___

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


Re: [Koha] link_bibs_to_authorities

2023-10-02 Thread Katrin Fischer

Hi,

are these other fields linked to a thesaurus in your bibliographic
framework configuration?

Hope this helps,

Katrin

On 02.10.23 06:53, Сычев Игорь Алексеевич wrote:

Hello!

Using the script "link_bibs_to_authorities.pl ".
Binds only one Unimarc field? Only 700?
How do I make multiple fields linked?
For example, there are 600, 700, 701 in the bibliographic record.
These fields were linked in another ILS.

Good Luck!

Igor A. Sychev
Tomsk Polytechnic University
https://lib.tpu.ru


___

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


Re: [Koha] Error 500 when opening records with attached items

2023-09-29 Thread Katrin Fischer

Hi,

I think you need to check the server logs for the full error, so we can
see what might be the source of the issue.

more_subfields_xml is used to store additional item information that
hasn't been mapped to any of the standard fields. Odd is that $d in
MARC21 should be mapped to items.dateaccessioned, but I am not sure if
this could be the source of your problem.

Are you using MARC21 and have you changed anything about the Koha to
MARC mappings?

Katrin

On 27.09.23 20:23, bong...@uks.co.za wrote:

Good day Katrin,

I found a few items without item types. I have added these to the items where 
they were missing. I still get the error 500. I have run the rebuild, but still 
the error is there. Now, all items have the correct home and holdings locations 
as well as correct item types.

The error 500 appears when:

Checking out items
Renewing items
Checking in items
Viewing the detailed display of records
Batch editing/deleting items

It looks like where there is anything to do with items, this error appears. I ran a 
report that outputs all items fields, and a few have entries in the field 
"more_subfields_xml". Here is an example of one entry:

"
http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation=""http://www.loc.gov/MARC21/slim 
http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd";
   xmlns=""http://www.loc.gov/MARC21/slim";>


a  
   
 2022-05-19
   


"

What does this field mean?


Kind regards,

Bongiwe Shongwe
Chief Technology Officer
Universal Knowledge Software
Tel.:  +27(11) 375-4700
Fax : +27(11) 375-4710
e-mail: bong...@uks.co.za
Web: www.uks.co.za

  
--

7. Re: Error 500 when opening records with attached items
   (Katrin Fischer)

Message: 7
Date: Mon, 18 Sep 2023 21:00:25 +0200
From: Katrin Fischer 
To: koha@lists.katipo.co.nz
Subject: Re: [Koha] Error 500 when opening records with attached items
Message-ID: <88b7e0c0-be32-dab5-f22e-e94973030...@web.de>
Content-Type: text/plain; charset=UTF-8; format=flowed

Hi,

did you check the itemtype as well? It would also cause a 500 in the OPAC.

Hope this helps,

Katrin

On 18.09.23 20:06, bong...@uks.co.za wrote:

Good day, Thomas

Thank you for your response. I checked all the items and all have the
correct homebranch and holdingbranch


Kind regards,

Bongiwe Shongwe
Chief Technology Officer
Universal Knowledge Software
Tel.:  +27(11) 375-4700
Fax : +27(11) 375-4710
e-mail: bong...@uks.co.za
Web: www.uks.co.za




-Original Message-
From: Thomas Klausner 
Sent: Tuesday, September 5, 2023 2:43 PM
To: bong...@uks.co.za
Cc: koha@lists.katipo.co.nz
Subject: Re: [Koha] Error 500 when opening records with attached items

Hi!

On Tue, Sep 05, 2023 at 02:17:59PM +0200, bong...@uks.co.za wrote:


We have just migrated our database to another server with an upgraded
version of KOHA (23.05.01.000). On the new server we encounter
problems with opening bibliographic records in NORMAL view after
performing a search. We get the "error 500". This only happens in records

with attached items.

Records with no items attached to them open successfully in this view.

First guess: The items have no homebranch and holdingbranch. Make sure that
every item has a (correct) value for those columns.

Greetings,
domm




------

Message: 8
Date: Mon, 18 Sep 2023 21:03:18 +0200
From: Katrin Fischer 
To: koha@lists.katipo.co.nz
Subject: Re: [Koha] output of authors' subfields
Message-ID: 
Content-Type: text/plain; charset=UTF-8; format=flowed

Hi,

Koha uses XSLT stylesheets to display bibliographic and optionally
authority data. Instead of using the default, you can also define your
own - look for XSLT in the system preferences.

But it might also be worth reporting an enhancement request for this one
if it's about following the MARC standard.

Hope this helps,

Katrin

On 15.09.23 16:37, Сычев Игорь Алексеевич wrote:

Hello!

How to do if 7xx $g and $b are filled, output only $g?
Both subfields are being displayed now.
Is this reaction only in Unimarc?
Example:
700
$aAufderstraße
$bH.
$gHartmut

https://koha.lib.tpu.ru/cgi-bin/koha/opac-detail.pl?biblionumber=667189
https://koha.lib.tpu.ru/cgi-bin/koha/opac-detail.pl?biblionumber=22141
https://koha.lib.tpu.ru/cgi-bin/koha/opac-detail.pl?biblionumber=634386

Good Luck!

Igor A. Sychev
Tomsk Polytechnic University
https://lib.tpu.ru


___

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


--

Subject: Digest Footer

___
Koha mailing list
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/ko

Re: [Koha] Request for Listing a Paid Support Service Provider

2023-09-29 Thread Katrin Fischer

Hi,

I have added your company to the Koha support provider's list.

https://koha-community.org/support/paid-support/country/#vietnam

Please let me know if any changes are needed.

Katrin

On 25.09.23 09:27, Bui Tien Phong wrote:

Dear Katrin,
Please accept my apologize for late reply. I've came back from a business trip.
We added koha-community.org on the top of the banner in our website: 
https://koha.vn
Thank you,
Phong

-Original Message-
From: Koha  On Behalf Of Katrin Fischer
Sent: Friday, September 15, 2023 12:30 AM
To: koha@lists.katipo.co.nz
Subject: Re: [Koha] Request for Listing a Paid Support Service Provider

Hi,

we require a link back to the koha-community.org website in order to be listed 
as a Koha support provider.

Can you please point me to the link on your website?

Katrin

On 12.09.23 05:13, Bui Tien Phong wrote:

Dear Koha Community,

Greetings from Vietnam!

D Technology Integration and Consulting, JSC (D Tech) has been
providing Koha services for more than 10 years and contributed to the
Wiki of the community 8 years ago:
https://wiki.koha-community.org/wiki/D%26L_TECH.,_JSC.

Could you please assist us in adding our company to this site: :
https://koha-community.org/support/paid-support/country/ ?

Below, you will find our company information:

Company Name: D Technology Integration and Consulting., JSC

Contact Person: Phong Bui

Contact email: phong@dlcorp.com.vn
<mailto:phong@dlcorp.com.vn>

Website: https://koha.vn | https://dlcorp.com.vn

Telephone: +84912678987

Thank you,

Phong Bui



___

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


___

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


Re: [Koha] memcached

2023-09-29 Thread Katrin Fischer

Hi,

this is more a warning than an error and you should be able to safely
ignore it. See:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22217

Hope this helps,

Katrin

On 26.09.23 16:38, Сычев Игорь Алексеевич wrote:

Hello!

What is the error?

root@koha:~# systemctl status memcached
● memcached.service - memcached daemon
  Loaded: loaded (/lib/systemd/system/memcached.service; enabled; vendor 
preset: enabled)
  Active: active (running) since Sat 2023-09-23 20:52:52 +07; 3 days ago
Docs: man:memcached(1)
Main PID: 696931 (memcached)
   Tasks: 10 (limit: 4657)
  Memory: 14.4M
 CPU: 3min 27.948s
  CGroup: /system.slice/memcached.service
  └─696931 /usr/bin/memcached -m 64 -p 11211 -u memcache -l 
127.0.0.1 -P /var/run/memcached/memcached.pid

Sep 23 20:52:52 koha systemd[1]: Started memcached daemon.
root@koha:~# koha-translate --update ru-RU

Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are the 
unix socket permissions set properly? Is the host reachable?
If you ignore this warning, you will face performance issues

Good Luck!

Igor A. Sychev
Tomsk Polytechnic University
https://lib.tpu.ru


___

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


Re: [Koha] Error when trying to display item OPAC view.

2023-09-29 Thread Katrin Fischer

Hi Andrew,

this might point to some invalid MARC record:

Field 035 must have at least one subfield at
/usr/share/perl5/MARC/File/XML.pm line 483.

If you have a 035 field, it should have at least one subfield with content.

Hope this helps,

Katrin

On 25.09.23 21:06, Andrew Hartung wrote:

I'm getting a error page when trying to see an item's OPAC view. I've
verified that the OPAC address is correct in the OPACBaseURL preference.
Here are some possibly relevant log files:






==> /var/log/koha/cbc_library/indexer-error.log <==
20230920 14:46:51 cbc_library-koha-indexer: client (pid 1317) killed
by signal 15, stopping
20230920 15:14:03 cbc_library-koha-indexer: client (pid 1319) killed
by signal 15, stopping

==> /var/log/koha/cbc_library/plack-error.log <==
Field 035 must have at least one subfield at
/usr/share/perl5/MARC/File/XML.pm line 483.
Field 035 must have at least one subfield at
/usr/share/perl5/MARC/File/XML.pm line 483.
Field 035 must have at least one subfield at
/usr/share/perl5/MARC/File/XML.pm line 483.
Field 035 must have at least one subfield at
/usr/share/perl5/MARC/File/XML.pm line 483.
Field 035 must have at least one subfield at
/usr/share/perl5/MARC/File/XML.pm line 483.
Field 035 must have at least one subfield at
/usr/share/perl5/MARC/File/XML.pm line 483.
Field 035 must have at least one subfield at
/usr/share/perl5/MARC/File/XML.pm line 483.
Field 035 must have at least one subfield at
/usr/share/perl5/MARC/File/XML.pm line 483.
Field 035 must have at least one subfield at
/usr/share/perl5/MARC/File/XML.pm line 483.
Field 035 must have at least one subfield at
/usr/share/perl5/MARC/File/XML.pm line 483.

==> /var/log/koha/cbc_library/plack-intranet-error.log <==
[2023/09/20 16:02:01] [WARN] Argument "" isn't numeric in subroutine
entry at /usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line
241.
[2023/09/20 16:02:23] [WARN] Use of uninitialized value in string eq
at /usr/share/koha/intranet/cgi-bin/cataloguing/addbiblio.pl line 545.
[2023/09/20 16:02:35] [WARN] Use of uninitialized value in string eq
at /usr/share/koha/intranet/cgi-bin/cataloguing/addbiblio.pl line 545.
[2023/09/20 16:02:42] [WARN] Argument "" isn't numeric in subroutine
entry at /usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line
241.

==> /var/log/koha/cbc_library/plack.log <==
192.168.1.207 - - [20/Sep/2023:16:31:30 -0500] "GET
/intranet/mainpage.pl HTTP/1.1" 200 45712 "-" "Mozilla/5.0 (X11; Linux
x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0
Safari/537.36"

==> /var/log/koha/cbc_library/plack-opac-error.log <==
[2023/09/20 14:55:57] [WARN] Use of uninitialized value in hash
element at /usr/share/koha/opac/cgi-bin/opac/opac-detail.pl line 678.
[2023/09/20 15:13:41] [WARN] Use of uninitialized value in hash
element at /usr/share/koha/opac/cgi-bin/opac/opac-detail.pl line 678.
[2023/09/20 15:15:26] [WARN] Use of uninitialized value in hash
element at /usr/share/koha/opac/cgi-bin/opac/opac-detail.pl line 678.

==> /var/log/koha/cbc_library/worker-error.log <==
20230920 14:46:51 cbc_library-koha-worker: client (pid 1256) killed by
signal 15, stopping
20230920 14:46:51 cbc_library-koha-worker-long_tasks: client (pid
1290) killed by signal 15, stopping
20230920 15:14:03 cbc_library-koha-worker: client (pid 1230) killed by
signal 15, stopping
20230920 15:14:03 cbc_library-koha-worker-long_tasks: client (pid
1271) killed by signal 15, stopping

==> /var/log/koha/cbc_library/worker-output.log <==
Cannot connect to the message broker, the jobs will be processed
anyway (Failed to connect: Error connecting to localhost:61613:
Connection refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving
up at /usr/share/perl5/Net/Stomp.pm line 27.
) at /usr/share/koha/bin/workers/background_jobs_worker.pl line 90.
Cannot connect to the message broker, the jobs will be processed
anyway (Failed to connect: Error connecting to localhost:61613:
Connection refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving
up at /usr/share/perl5/Net/Stomp.pm line 27.
) at /usr/share/koha/bin/workers/background_jobs_worker.pl line 90.
Cannot connect to the message broker, the jobs will be processed
anyway (Failed to connect: Error connecting to localhost:61613:
Connection refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving
up at /usr/share/perl5/Net/Stomp.pm line 27.
) at /usr/share/koha/bin/workers/background_jobs_worker.pl line 90.
Cannot connect to the message broker, the jobs will be processed
anyway (Failed to connect: Error connecting to localhost:61613:
Connection refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving
up at /usr/share/perl5/Net/Stomp.pm line 27.
) at /usr/share/koha/bin/workers/background_jobs_worker.pl line 90.

___

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

Re: [Koha] Template toolkit question.

2023-09-21 Thread Katrin Fischer

Hi all,

I've added this hint to the wiki:

https://wiki.koha-community.org/wiki/Notices_with_Template_Toolkit#Don.27t_generate_e-mail_for_a_patron_category

Katrin

On 06.09.23 12:47, Kyle Hall wrote:

There is a trick which basically boils down to "If the rendered notice is
empty, it doesn't get sent". So your WELCOME notice could contain something
like:

[%- IF patron.categorycode == "STAFF" %]
This is where your actual welcome notice is!
[%- END %]

That way it is empty for non-staff users and shouldn't get sent.

Kyle

---
http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )


On Tue, Sep 5, 2023 at 3:14 AM Raymund Delahunty 
wrote:


We are having some successes in using TT code to improve notices. Dealing
with singular / plural issues, different wording of notices for different
patron categories... that sort of thing. What we would like to do is to use
TT to send the WELCOME notice to staff only. Has any TT expert any tips how
we could set up the WELCOME notice (and potentially other ones usually sent
to all, like MEMBERSHIP_EXPIRY) so that emails are only sent to some
patrons, based on IF-type rules?

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@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

___

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


Re: [Koha] KOHA is not sending mails through SMTP server

2023-09-21 Thread Katrin Fischer

Hi,

you could try the following:

* Check your mail server settings under Administration > SMTP servers.
If you set the Debug mode to 'enabled' you might be able to find a more
helpful error in your logs.

* Check that you have set a valid email address in KohaAdminEmailAddress
and maybe also for your libraries under Administration > Libraries

Hope this helps,

Katrin

On 21.09.23 13:33, Nirmit Krishnatray wrote:

Hi,

Hope you're well. KOHA is not sending mails when a user is checking out or 
checking in. I checked the notices and it displayed Unhandled email failure, 
check the logs for further details. Please support on this

Best Regards


___

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


Re: [Koha] output of authors' subfields

2023-09-18 Thread Katrin Fischer

Hi,

Koha uses XSLT stylesheets to display bibliographic and optionally
authority data. Instead of using the default, you can also define your
own - look for XSLT in the system preferences.

But it might also be worth reporting an enhancement request for this one
if it's about following the MARC standard.

Hope this helps,

Katrin

On 15.09.23 16:37, Сычев Игорь Алексеевич wrote:

Hello!

How to do if 7xx $g and $b are filled, output only $g?
Both subfields are being displayed now.
Is this reaction only in Unimarc?
Example:
700
$aAufderstraße
$bH.
$gHartmut

https://koha.lib.tpu.ru/cgi-bin/koha/opac-detail.pl?biblionumber=667189
https://koha.lib.tpu.ru/cgi-bin/koha/opac-detail.pl?biblionumber=22141
https://koha.lib.tpu.ru/cgi-bin/koha/opac-detail.pl?biblionumber=634386

Good Luck!

Igor A. Sychev
Tomsk Polytechnic University
https://lib.tpu.ru


___

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


Re: [Koha] Error 500 when opening records with attached items

2023-09-18 Thread Katrin Fischer

Hi,

did you check the itemtype as well? It would also cause a 500 in the OPAC.

Hope this helps,

Katrin

On 18.09.23 20:06, bong...@uks.co.za wrote:

Good day, Thomas

Thank you for your response. I checked all the items and all have the
correct homebranch and holdingbranch


Kind regards,

Bongiwe Shongwe
Chief Technology Officer
Universal Knowledge Software
Tel.:  +27(11) 375-4700
Fax : +27(11) 375-4710
e-mail: bong...@uks.co.za
Web: www.uks.co.za




-Original Message-
From: Thomas Klausner 
Sent: Tuesday, September 5, 2023 2:43 PM
To: bong...@uks.co.za
Cc: koha@lists.katipo.co.nz
Subject: Re: [Koha] Error 500 when opening records with attached items

Hi!

On Tue, Sep 05, 2023 at 02:17:59PM +0200, bong...@uks.co.za wrote:


We have just migrated our database to another server with an upgraded
version of KOHA (23.05.01.000). On the new server we encounter
problems with opening bibliographic records in NORMAL view after
performing a search. We get the "error 500". This only happens in records

with attached items.

Records with no items attached to them open successfully in this view.

First guess: The items have no homebranch and holdingbranch. Make sure that
every item has a (correct) value for those columns.

Greetings,
domm



___

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


Re: [Koha] Koha running number of background job process and CPU high usage

2023-09-18 Thread Katrin Fischer

Hi,

I was trying to find the string "You must log in using" in Koha, but I
didn't find it. Neither in codebase nore translations.

Could it be part of a customization that is causing the trouble?
You could check IntranetUserJS or HTML customizations containing JavaScript.

Or maybe part of some data?

Hope this helps,

Katrin

On 17.09.23 19:41, JITHIN N wrote:

Am using Koha 22.11.07. My server running 6 instances. I noticed my disk
was filling up because worker-output.log was getting several hundred of
these per second:



*[2023/09/17 22:41:14] [WARN] Frame not processed - malformed JSON string,
neither tag, array, object, number, string or atom, at character offset 0
(before "You must log in usin...") at
/usr/share/koha/bin/workers/background_jobs_worker.pl
<http://background_jobs_worker.pl> line 118. main::catch {...}
  /usr/share/koha/bin/workers/background_jobs_worker.pl
<http://background_jobs_worker.pl> (120)*


while checking the terminal it ran a number of background jobs and CPU
usage became very high. can I have any solution for this?




With Regards
JIthin
___

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


Re: [Koha] Email for suggestion book

2023-09-18 Thread Katrin Fischer

Hi Tony,

that sounds unusual. Some things to check:

* Did you set the SendAllEmailsTo system preference?

* Do you have multiple addresses in your library patrons? Maybe one
being the library? Maybe check EmaiFieldPrimary

* Do the notices show in the notices tab of the patron?

There are 2 versions each year, so there is no version 20 or 23 - the
last release was 23.05 in May and the next will be 23.11 in November.

Hope this helps,

Katrin

On 18.09.23 10:48, Toni Afandi wrote:

Dear all,

After upgrading to Koha 23 from koha 20, I noticed something strange about
the suggestion notification email. Now I receive email when a patron
suggestion is received or declined, but no to the patron who suggests. So
where should I set the email so they would receive it?

I noticed that koha made a notification, but it is set to me not to the
patrons.

Thank you

*Toni Afandi*
*Librarian*
*STT SAAT*
*(Southeast Asia Bible Seminary)*
Jl. Bukit Hermon No 1, Tidar Atas
Malang, Jawa Timur 65151
Indonesia
www.seabs.ac.id
___

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


Re: [Koha] Request for Listing a Paid Support Service Provider

2023-09-14 Thread Katrin Fischer

Hi,

we require a link back to the koha-community.org website in order to be
listed as a Koha support provider.

Can you please point me to the link on your website?

Katrin

On 12.09.23 05:13, Bui Tien Phong wrote:

Dear Koha Community,

Greetings from Vietnam!

D Technology Integration and Consulting, JSC (D Tech) has been providing
Koha services for more than 10 years and contributed to the Wiki of the
community 8 years ago:
https://wiki.koha-community.org/wiki/D%26L_TECH.,_JSC.

Could you please assist us in adding our company to this site: :
https://koha-community.org/support/paid-support/country/ ?

Below, you will find our company information:

Company Name: D Technology Integration and Consulting., JSC

Contact Person: Phong Bui

Contact email: phong@dlcorp.com.vn <mailto:phong@dlcorp.com.vn>

Website: https://koha.vn | https://dlcorp.com.vn

Telephone: +84912678987

Thank you,

Phong Bui



___

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


Re: [Koha] Minimum permissions needed for patron search

2023-09-11 Thread Katrin Fischer

Hi all,

there is a bug with some discussion on this:

*Bug 30230*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30230> -
Search for patrons in checkout should not require edit_borrowers permission

Hope this helps,

Katrin

On 08.09.23 16:52, Сычев Игорь Алексеевич wrote:

Hi Joel!
Earlier I wrote about a similar problem.
https://lists.katipo.co.nz/public/koha/2023-April/059340.html
I have tried different options, the search ends with an error if 
"edit_borrowers" is not allowed.
Now version 23.05.03 the problem remains.

Good Luck!

Igor A. Sychev
Tomsk Polytechnic University
https://lib.tpu.ru


-Original Message-
From: Koha  On Behalf Of Coehoorn, Joel
Sent: Friday, September 8, 2023 9:00 PM
To: koha
Subject: [Koha] Minimum permissions needed for patron search

We're a small college using Koha for our library circulation. Our library uses 
workstudy students to man the desk and do *basic *circulation tasks.
Anything advanced, like adding or receiving holds, fines, etc, and the student 
will get an actual librarian.

These workstudy students are also regular patrons, so the workstudy job is accomplished with a 
dedicated login, with the password saved on the circulation PC so the students don't actually know 
how to login as a staff person otherwise. FERPA and related laws require us to treat this as an 
extremely low-trust position. Historically, this login has only had the "View Patron Infos 
from any Libraries (view_borrower_infos_from_any_libraries)" permission in the "Add 
Modify Patron Information (borrowers)" section. We also use SAML for authentication.

Recently, this account is no longer able to search for patrons by name. If a 
student comes to the desk to checkout a book and forgets their card, our 
workstudy account used to be able to search them by name and proceed with the 
checkout process. Now, this enters a SAML redirect loop trying to validate 
permissions for the login, which is detected and broken with an error by the 
identity provider. I can't find where in Koha, if anywhere, this is being 
logged to help resolve it. They are otherwise able to circulate material if 
they can lookup the patron by barcode.

I discovered the problem goes away if we add the "Add, modify and view patron 
information (edit_borrowers)" to the login. Then they are able to continue 
circulation as normal. However, we don't want this account to be able to add or modify 
borrows, especially as this information all syncs from our student information system. We 
don't want manual edits... ever.

How can I fix this? Why do we need to give edit permissions just to do a search?

*Joel Coehoorn*
Director of Information Technology
*York University*
Office: 402-363-5603 |jcoeho...@york.edu  | york.edu

*Please contacthelpd...@york.edufor technical
assistance.*


The mission of York University is to transform lives through Christ-centered 
education and to equip students for lifelong service to God, family, and 
society ___

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

Koha mailing listhttp://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


Re: [Koha] Has NFC vs. NFD encoding changed for Unicode in koha?

2023-09-09 Thread Katrin Fischer

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

___

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


Re: [Koha] Format of Barcode

2023-09-09 Thread Katrin Fischer

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 3451710004719930 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

___

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


Re: [Koha] check out problem in koha v23.05

2023-09-09 Thread Katrin Fischer

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
 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


___

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


Re: [Koha] Request for Listing a Paid Support Service Provider

2023-09-09 Thread Katrin Fischer

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

___

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


Re: [Koha] Request for Listing a Paid Service Provider, Texas, USA based.

2023-09-09 Thread Katrin Fischer

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

___

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


Re: [Koha] Koha to MARC mapping

2023-09-06 Thread Katrin Fischer

Hi,

I am not sure about UNIMARC, but for MARC21 942$c would be correct.

Can some UNIMARC user help?

Katrin

On 25.08.23 06:48, Сычев Игорь Алексеевич wrote:

Hello!

New install Koha 23.05.02

MARC bibliographic framework test
itemtype NOT mapped
the biblioitems.itemtype field MUST :
  be mapped to a MARC subfield,
  the corresponding subfield MUST have "Authorized value" set to "itemtype"

Koha to MARC mapping
biblioitems.itemtype099 t   Koha item type
biblioitems.itemtype942 c   Koha item type

Leave only 942 for Unimarc?

Good Luck!

Igor A. Sychev
Tomsk Polytechnic University
https://lib.tpu.ru
___

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


Re: [Koha] check out problem in koha v23.05

2023-09-06 Thread Katrin Fischer

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


Re: [Koha] An Acqusition Module problem

2023-09-06 Thread Katrin Fischer

Hi Naveen,

I believe you have run into an old bug. See:

*Bug 20118*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20118> -
System picks Active currency by default while adding suggestion to vendor

Hope this helps,

Katrin

On 25.08.23 09:55, Ms. Naveen Ali wrote:

Dear All,

I have come across a problem in Koha Acquisition Module.
Using Koha version 22.05

When a currency other than default is selected in the Suggestions Module for a 
tile is not reflected when an order is placed for the same suggestion.

I would like to know if others are also facing the same problem. In that case 
it can be reported as a bug.


With best regards,

Naveen Ali

Exec. IT Manager
Engr Abul Kalam Library
NED University of Engineering & Technology
Karachi, Pakistan.


___

Koha mailing listhttp://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


Re: [Koha] How to change the language of default marc framework?

2023-09-06 Thread Katrin Fischer

Hi,

the descriptions for the fields are stored in the database. Which
language the frameworks are installed in, depends on the language
selected in the web installer when the instance is created. But of
course also depends on availability of the translation.

Importing a translated default framework 'should' work, but you might be
facing a bug :(

*Bug 34488*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34488> -
Import default framework

Hope this helps,

Katrin

On 19.08.23 15:44, Alipio Luiz de Souza Silva wrote:

Hey,
Is there a way to translate the default marc framework to another language?

I already tried importing a CSV file from a translated framework, but it
didn't work.



___

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


Re: [Koha] OPACAuthorIdentifiers

2023-09-06 Thread Katrin Fischer

Hi,

could you please file a bug for this?

Thanks!

Katrin

On 28.08.23 10:55, Сычев Игорь Алексеевич wrote:

Hello!

Please add to OPACAuthorIdentifiers "MARC21 only" in 
cgi-bin/koha/admin/preferences.pl?tab=opac#opac_Features
In Unimarc "Display" leads to an error.
Later I looked in 
https://koha-community.org/manual/23.05/en/html/opacpreferences.html#opacauthoridentifiers.

Good Luck!

Igor A. Sychev
Tomsk Polytechnic University
https://lib.tpu.ru


___

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


Re: [Koha] print password as text

2023-09-06 Thread Katrin Fischer

Hi Igor,

there is currently no way to print the generated password.

There is an old bug report about this:

*Bug 23764*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23764> - Add
printable version of "Change password" in patron details

It should probably be combined with forcing a password reset on first login:

*Bug 33462*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33462> -
Force password change for new patrons entered by staff

Hope this helps,

Katrin


On 05.09.23 10:29, Сычев Игорь Алексеевич wrote:

Hello!

cgi-bin/koha/members/member-password.pl?member=2
Change username and/or password for ...
How can I print the password after "Click to fill with a randomly generated 
suggestion. Passwords will be displayed as text."?

Good Luck!

Igor A. Sychev
Tomsk Polytechnic University
https://lib.tpu.ru



___

Koha mailing listhttp://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


Re: [Koha] Staff Login Issues after updating OPAC to SSL

2023-09-06 Thread Katrin Fischer

Hi Scott,

have you been able to resolve your issue?

It sounds like it might be an Apache problem, but I am not a sysadmin.

One thing in Koha to check could be the *BaseURL system preferences.

Hope this helps,

Katrin

On 30.08.23 23:23, Scott Marriott wrote:

We recently updated our OPAC to use SSL. The problem we're now having it
that when we log into our staff interface using our old http://
koha.com:8080 site we're getting and error messages and every time we move
to another link on the site it's going back to the login screen and
requiring us to login again, before continuing on to the correct link.

Any suggestions where to check first? (I'm not seeing anything in the Koha
log files.

Thank You, Scott

Scott Marriott
Emerson
___

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


Re: [Koha] Template toolkit question.

2023-09-06 Thread Katrin Fischer

Hi Ray,

you can affect the content of an email with Template Toolkit, but I
don't see a way where it could be used to prevent generation/sending of
the email in the first place.

Christopher Brannon filed a bug to make this configurable:

*Bug 15834*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15834> -
Ability to limit AutoEmailNewUser to specific patron categories

I believe there would be general interest in this feature.

Hope this helps,

Katrin

On 05.09.23 09:13, Raymund Delahunty wrote:

We are having some successes in using TT code to improve notices. Dealing with 
singular / plural issues, different wording of notices for different patron 
categories... that sort of thing. What we would like to do is to use TT to send 
the WELCOME notice to staff only. Has any TT expert any tips how we could set 
up the WELCOME notice (and potentially other ones usually sent to all, like 
MEMBERSHIP_EXPIRY) so that emails are only sent to some patrons, based on 
IF-type rules?

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 listhttp://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


Re: [Koha] web installer appears on upgrade

2023-09-06 Thread Katrin Fischer

Hi Daniel,

I think this got lost when we had a bit of trouble with the mailing list.

Were you able to resolve your issue?

While we are working on the fix, the workaround suggested on the bug
might help you to finish the update:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34516#c2

Katrin

On 14.08.23 23:44, Daniel Owens wrote:

I opened a bug report, but I imagine it will take awhile before this
is fixed. Is there any documentation about how to downgrade on Linux
(Ubuntu)? I do have a backup.

Daniel

On 8/10/23 4:09 PM, Fridolin SOMERS wrote:

On 22.11.x index on publishercode seems OK :
  KEY `publishercode` (`publishercode`(191)),

The size on index has been added by :
Bug 18336: Convert schema from utf8 to utf8mb4

I've look at old databases, the index is OK.

Please open a bug report.

Best regards

Le 10/08/2023 à 04:43, Daniel Owens a écrit :

This worked the last time I had the problem, but with the latest
upgrade I got the web installer again. After running:

$ sudo service memcached restart
$ sudo koha-upgrade-schema hbc

Upgrading database schema for hbc
Upgrade to 22.11.07.003  [14:01:47]: Bug 34029 - Extend datatypes in
biblioitems and deletedbiblioitems tables to avoid import errors
     Updated biblioitems.place to text
     Updated deletedbiblioitems.place to text
ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed:
BLOB/TEXT column 'publishercode' used in key specification without a
key length at /usr/share/koha/lib/C4/Installer.pm line 741

Can anyone give me a pointer about where to go from here?

Daniel

On 7/11/23 10:18 AM, Bruns, Anke wrote:

Hi,

in our case, when this occurs, the solution is usually to restart
the memcached and then perform koha-upgrade-schema .

Hope this helps.

Best regards,
Anke



___

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

___

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


Re: [Koha] Incremental fine in KOHA

2023-08-28 Thread Katrin Fischer

Hi,

at the moment Koha can only apply the same fine amount per fine
interval. I am sorry, but what you want to do cannot be achieved without
development at this point in time.

Hope this helps,

Katrin

On 10.08.23 12:06, Rupinder Singh wrote:

HI,
Our library has a fine rule that attracts a fine amount of 25 per day for
the first week after the due date.
after the first week, it is 50 per day
and after the second week, it is 75 per day.

The out-of-the-box installation of koha only gives the option to put one
rate of fine for a user category.
How can I configure my koha to have the incremental fine calculation.?
I can tweak some settings, but I am not an expert coder.. please help


thank you
Rupinder Singh
___

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


Re: [Koha] Auto check-in problem in Koha v23.05

2023-08-28 Thread Katrin Fischer

Hi,

can you explain a bit more about how the problem presents?

If you look at the reading history of the user, has the item been
checked out? When does the checkin appear?

The automatic checkin feature works with a cronjob, so it should not
happen immediately after checkout. It might be something else you are
seeing.

Hope this helps,

Katrin

On 17.08.23 03:15, zen zenitram wrote:

We upgraded our koha to v23.05. when the patron borrowed books it is
automatically check-in even though auto check-in is not check or activated.

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


Re: [Koha] Failing to edit MARC Frameworks in Koha 22.05.05.000

2023-08-09 Thread Katrin Fischer

Hi Antony,

I am sorry, I am not sure what could be wrong there then.

Maybe check configuration in all your frameworks separately. Maybe the
field is not configured or misconfigured in just one of them?

Hope this helps,

Katrin

On 03.08.23 10:52, Antony Kujenga wrote:

Hi Katrin,

Yes, they are:
items.holdingbranch 952 b   Current library  Add  Remove
items.homebranch952 a   Home library


Regards

AK



On Wed, 2 Aug 2023 at 22:03, Katrin Fischer 
wrote:

Hi,

check the Koha-to-MARC mappings in administration to see if 952$a and
952$b are linked correctly. If not, restore the link to
items.homebranch
and items.holdingbranch from there.

Hope this helps,

Katrin

On 02.08.23 21:51, Antony Kujenga wrote:
> Hi Lauren,
>
> Yes, I've been trying to edit the 952 $a subfield (Home Library)
under the
> "Tag 952 Subfield constraints"
>
> Regards
>
> AK
> On Wed, 2 Aug 2023 at 15:36, Lauren Denny 
wrote:
>
>> Did you edit the 952 MARC field in the Frameworks? This is
connected to
>> the items record.
>>
>> On Wed, Aug 2, 2023 at 8:54 AM Antony Kujenga
 wrote:
>>
>>> Hi Jonathan,
>>>
>>> No, it does not return anything.
>>>
>>> Regards
>>>
>>>
>>> AK
>>>
>>>
>>> On Wed, 2 Aug 2023 at 13:56, Jonathan Druart <
>>> jonathan.dru...@bugs.koha-community.org> wrote:
>>>
>>>> Does this SQL query return something?
>>>>
>>>> SELECT frameworkcode, tagfield, tab, authorised_value FROM
>>>> marc_subfield_structure WHERE ( kohafield = "items.homebranch" OR
>>>> kohafield = "items.holdingbranch" ) AND authorised_value !=
>>>> "branches";
>>>>
>>>> Le mer. 2 août 2023 à 11:25, Antony Kujenga
 a
>>> écrit :
>>>>> Dear Community,
>>>>>
>>>>> I've been trying to edit some frameworks in our Koha
22.05.05.000
>>>> instance
>>>>> running on Ubuntu 22.04. Upon running the framework test,
I'm getting
>>>> this
>>>>> error report:
>>>>>
>>>>> homebranch NOT mapped the items.homebranch field MUST :
>>>>>
>>>>>     - be mapped to a MARC subfield,
>>>>>     - the corresponding subfield MUST have "Authorized
value" set to
>>>>>     "branches"
>>>>>
>>>>> holdingbranch NOT mapped the items.holdingbranch field MUST :
>>>>>
>>>>>     - be mapped to a MARC subfield,
>>>>>     - the corresponding subfield MUST have "Authorized
value" set to
>>>>>     "branches"
>>>>>
>>>>>
>>>>> I have tried changing the stated fields numerous times but
the system
>>>> will
>>>>> not effect the changes.
>>>>>
>>>>> I tried running
>>>>>
>>>>> $ sudo koha-shell -c
'/usr/share/koha/bin/batchRebuildBiblioTables.pl
>>> -c'
>>>>> your_koha_name
>>>>>
>>>>> with our instance name but it hasn't helped.
>>>>>
>>>>> Any urgent help would be most appreciated.
>>>>>
>>>>> Regards
>>>>>
>>>>>
>>>>> AK
>>>>> ___
>>>>>
>>>>> 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
>>>
> ___
>
> 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


___

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


Re: [Koha] faceting by date [collection faceting]

2023-08-09 Thread Katrin Fischer

Hi Eric,

if you add collections to your items (952$8) the facet should already be
configured and work automatically.

Hope this helps,

Katrin

On 04.08.23 20:04, Eric Lease Morgan wrote:

How can I can get faceting by date to work; in what MARC field must I insert a 
year value in order to facet by year? --Eric Morgan, University of Notre Dame


[Okay. I have not seen any examples on the Web of date faceting, thus, I will 
assume date faceting is not necessarily a choice, and I'll ask a similar 
question about collection faceting instead.]

How do I implement collection faceting? Suppose I have two collections: 1 
Collection Orange, and 2) Collection Red. How do I configure Koha, and what 
sorts of values go into what MARC fields so I can limit my searches to either 
Collection? I have done such a thing with types, but right now I only have a 
single type.

--
Eric Morgan


___

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


Re: [Koha] faceting by date

2023-08-09 Thread Katrin Fischer

Hi Eric,

facets are not fully configurable yet, like you can't make up new
facets. There is already a bug for adding a publication date facet:

*Bug 10734*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10734> - Add
Publication Date Facet in Searching

Hope this helps,

Katrin

On 04.08.23 18:29, Eric Lease Morgan wrote:

How can I can get faceting by date to work; in what MARC field must I insert a 
year value in order to facet by year? --Eric Morgan, University of Notre Dame


___

Koha mailing listhttp://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


Re: [Koha] 23.05 Multiple items - some items display incorrect shelving locations

2023-08-09 Thread Katrin Fischer

Hi Elaine,

you might see side effects of this bug:

*Bug 34086*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34086> - On
detail.tt if item.permanent_location is NULL no shelving location will show

It's a display issue where when there are some items with and some
without location the permanent location will display for items where
it's not set.

The bugfix was just released and hopefully should resolve any issues.

Hope this helps,

Katrin

On 28.07.23 02:10, Elaine Bradtke wrote:

Koha 23.05
When looking at bib records that include multiple items with different
locations, we sometimes see the following:

- The results list shows the correct information.
- The bib record holdings view gives the shelving location of one item
in the list for some  subsequent items.
- Edit items displays the correct locations.
- The OPAC record displays correctly.

This does not happen with all the records that have multiple items with
different shelving locations. In some cases only one or two items in the
holdings list are displayed incorrectly.  I have not been able to discover
why it happens to some records and not others.
Link to three screenshots:https://photos.app.goo.gl/ocFn48hF6E9GiszQ6  The
bib record with incorrect location display, edit items with correct
location information and OPAC view with correct information.

It is similar, but not the same as bug 34122
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34122  -
The records concerned have not been updated / edited;  the information is
correct in the database, but displaying incorrectly in some views.

The location that seems to be misbehaving  (but possibly because it's the
easiest error to detect) is "Off-site" appearing where it shouldn't.  Would
the - be causing a problem?

Has anyone else seen something like this?

Elaine Bradtke
VWML<https://www.vwml.org>
English Folk Dance and Song Society<https://www.efdss.org>
Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY
Tel+44 (0) 20 7485 2206 (This number is for the English Folk Dance and
Song Society in London, England. If you wish to phone me personally, send
an e-mail first. I work off site)
--
Registered Company No. 297142
Charity Registered in England and Wales No. 305999
___

Koha mailing listhttp://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


Re: [Koha] Self Registeration

2023-08-09 Thread Katrin Fischer

Hi,

you can use the PatronSelfRegistrationBorrowerUnwantedField system
preference to make the patron category visible in the form. Renaming of
fields can be done with jQuery. The jQuery library in the wiki might
have some useful examples.

Hope this helps,

Katrin

On 03.08.23 08:31, Himanshu Aggarwal wrote:

In Patron Self Registration how to make category editable?..Also if I wish
to change Zip Code to Pin Code. How to do it.


___

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


Re: [Koha] Failing to edit MARC Frameworks in Koha 22.05.05.000

2023-08-02 Thread Katrin Fischer

Hi,

check the Koha-to-MARC mappings in administration to see if 952$a and
952$b are linked correctly. If not, restore the link to items.homebranch
and items.holdingbranch from there.

Hope this helps,

Katrin

On 02.08.23 21:51, Antony Kujenga wrote:

Hi Lauren,

Yes, I've been trying to edit the 952 $a subfield (Home Library) under the
"Tag 952 Subfield constraints"

Regards

AK
On Wed, 2 Aug 2023 at 15:36, Lauren Denny  wrote:


Did you edit the 952 MARC field in the Frameworks?  This is connected to
the items record.

On Wed, Aug 2, 2023 at 8:54 AM Antony Kujenga  wrote:


Hi Jonathan,

No, it does not return anything.

Regards


AK


On Wed, 2 Aug 2023 at 13:56, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:


Does this SQL query return something?

SELECT frameworkcode, tagfield, tab, authorised_value FROM
marc_subfield_structure WHERE ( kohafield = "items.homebranch" OR
kohafield = "items.holdingbranch" ) AND authorised_value !=
"branches";

Le mer. 2 août 2023 à 11:25, Antony Kujenga  a

écrit :

Dear Community,

I've been trying to edit some frameworks in our Koha 22.05.05.000

instance

running on Ubuntu 22.04. Upon running the framework test, I'm getting

this

error report:

homebranch NOT mapped the items.homebranch field MUST :

- be mapped to a MARC subfield,
- the corresponding subfield MUST have "Authorized value" set to
"branches"

holdingbranch NOT mapped the items.holdingbranch field MUST :

- be mapped to a MARC subfield,
- the corresponding subfield MUST have "Authorized value" set to
"branches"


I have tried changing the stated fields numerous times but the system

will

not effect the changes.

I tried running

$ sudo koha-shell -c '/usr/share/koha/bin/batchRebuildBiblioTables.pl

-c'

your_koha_name

with our instance name but it hasn't helped.

Any urgent help would be most appreciated.

Regards


AK
___

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


___

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


Re: [Koha] Import data from excel to koha and Cover image using Manual data entry

2023-07-26 Thread Katrin Fischer

Hi,

you will need to convert your data from Excel spreadsheets to MARC21.
Tools like MARCEdit can help with that.

There is a section in the manual describing how to upload single or
multiple local covers and how to activate this feature:
https://koha-community.org/manual/23.05/en/html/cataloging.html#adding-cover-images

Hope this helps,

Katrin

On 22.07.23 06:18, Tahir Jan, Assistant Librarian, Central Library, UoP
wrote:

Dear All
I am facing problem in importing excel data to koha. Is anyone help me in
this regards.
Secondly when we are doing manual entry in koha then how can we upload
cover image of book.
Regards
Dt Jan
___

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


Re: [Koha] to catalog or not to catalog, that is my question

2023-07-26 Thread Katrin Fischer

Hi Eric,

there are a lot of libraries with this many and more records using Koha.
It's usually easier and faster to use the command line script
bulkmarcimport.pl for loading records during migration. The script can
load bibliographic and authority records.

For authorities this might have some helpful information:
https://bywatersolutions.com/education/authorities-town-hall-recap

Hope this helps,

Katrin

On 25.07.23 19:00, Eric Lease Morgan wrote:

On Jul 17, 2023, at 10:43 AM, Eric Lease Morgan  wrote:


To catalog or not to catalog, that is my question. ... All that said, my questions to 
y'all are, "What sorts of technology gotcha's might I encounter if I were to try to 
import .25 million articles into Koha? And how could I automate assigning authorities to 
each record?"


Please tell me, what sorts of issues might I encounter if I try to import as 
many as .25 million MARC records, and what sorts of automated authorities 
process might you suggest? --Eric Morgan, University of Notre Dame





___

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


Re: [Koha] Upgrade question: 22.05 -> 23.05 better directly or via 22.11?

2023-07-26 Thread Katrin Fischer

Hi Anke,

assuming you will do a test run of the update anyway, I don't think
there is an advantage in updating to 22.05 first. It's very common to
jump over multiple versions and you should always end up with the exact
same database structure, no matter where you are coming from.

Hope this helps,

Katrin

On 20.07.23 10:39, Bruns, Anke wrote:

Hi all,

we are considering an upgrade from 22.05 to 23.05 - in your experience would
it be good to upgrade directly or to go first to 22.11 and then from there
to 23.05?

Thanks and best regards,
Anke


___

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


Re: [Koha] ChatGPT

2023-07-26 Thread Katrin Fischer

Hi Igor,

ChatGPT made up the "Generation Rule" section. This doesn't exist in Koha.

If you want to automatically generate inventory numbers, have a look at
the stocknumberAV.pl value builder. It can be linked to a field like
952$i in the bibliographic frameworks and uses an authorised value to
store counters for different prefixes.

Hope this helps,

Katrin

On 25.07.23 07:34, Сычев Игорь Алексеевич wrote:

Hello!
Asked a question in ChatGPT:
How to set up an inventory number generator in ILS Koha?
Received a response:
To set up an inventory number generator in ILS Koha, you will need to follow 
these steps:

Log in to ILS Koha with administrator credentials.

Go to "Admin" and select "Local Administration".

In the "Items and Bibliographic Records" section, select "Item Types".

Select the instance type you need or add a new one by clicking on the "New" 
button.

In the "Generation Rule" section, select a specific rule or create a new one by clicking 
on the "New" button.

Enter the necessary settings for generating an inventory number, such as 
prefix, number template, and other parameters.

Save your changes.

Your inventory number generator is now set up in ILS Koha. Each time you create 
a new instance, the system will automatically generate an inventory number 
according to the settings you have specified.

I don't see "Generation Rule". Lying?

Good Luck!

Igor A. Sychev
Tomsk Polytechnic University
https://lib.tpu.ru


___

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


Re: [Koha] koha index issue

2023-07-19 Thread Katrin Fischer

Hi,

yes, that's the line and the reason are the German umlauts. If you don't
need that to work, you can juse remove the (oe).

Hope this helps,

Katrin

On 19.07.23 11:41, Viliam Polonec wrote:

maybe I found it

/etc/koha/zebradb/etc/word-phrase-utf.chr


equivalent Œœöø(oe)


Viliam





Dňa 19.07.2023 o 11:13 Thomas Klausner napísal(a):

Hi!

On Wed, Jul 19, 2023 at 10:13:05AM +0200, Viliam Polonec wrote:

The issue is only with oe at the end of string

Not sure if this helps anything, but maybe some part of your search
infrastructure (Zebra or ElasticSearch?) interprets the "oe" as German
Umlaut ö? And this then causes either the search string or the data in
the index to interpreted the wrong way?

Greetings,
domm



___

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


  1   2   3   4   5   6   7   8   9   10   >