Re: [Koha] To be listed as a Koha Support provider in Malaysia

[Katrin Fischer]

Hi Jesse,

in order to be listed we require a visible link to the
koha-community.org website. I couldn't spot one on your website. Please
point me to it or let me know when you have added one.

See here: https://koha-community.org/support/paid-support/how-to-get-listed/

Thanks,

Katrin

On 11.04.21 10:26, JESSE KAH wrote:

*Dear Koha Community,*



Lemonjar has been providing service and support in Malaysia for Koha ILS and 
other open source platform for couple of years.

We would also like to require community to list us for service and service 
provider for Koha ILS in Malaysia.



Our detail as follow:



Company Name: *Lemonjar Software Media Sdn. Bhd. (1039463-K)*

Contact Person: *Mdm. Jesse Kah Ingland / Mr. Chong*

Contact Email: sa...@lemonjar.com.my / sa...@edgetech.com.my

Website: https://www.lemonjar.com.my

Contact Tel: *+603-7859 9226/ +6088-713226*



We provide service from implementation, system architecture design for Koha, 
customization, migration service, Koha Payment Gateway, as well as integration 
according to needs.

Further information on our service on Koha ILS can be found at: 
https://www.lemonjar.com.my/



Thanks & have a nice day!





Best Regards,

Jesse Kah Ingland

Lemonjar Software Media Sdn. Bhd.

-- Managing Director --

Mobile: +6 (016) 8606 826

Tel: +6 (03)7859 9226 (Selangor Office) | +6 (088) 713226 (Sabah office)

Fax: +6 (088) 713226

Website: https://www.lemonjar.com.my

  https://www.edgetech.com.my

Other Email: mailto:lemonja...@gmail.com / mailto:lemonjar.sa...@gmail.com





Lemonjar Facebook page: https://www.facebook.com/lemonjarsoftmed/

Edgetech Facebook page: https://www.facebook.com/edgetechengineering/

YouTube page: https://www.youtube.com/channel/UCLV34OjYVdG6KQK_uTC2f3A/featured





___

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] Publication date (yyyy-yyyy) advanced search option not working in my Koha instance

[Katrin Fischer]

Hi Cindy,

I am sorry, I am not spotting anything unusual :(

I've also tried the date range search in 20.05 and on master and it
appears to work correctly there. Maybe some of our Zebra experts could
chime in?

Katrin

On 09.02.21 17:49, Cindy Murdock Ames wrote:

Hi Katrin,

Thanks for the response.  To answer your questions:

-- Are you using Zebra or Elasticsearch?

Zebra, version 2.0.59

-- Is 008 pos. 7-10 cataloged correctly for the records in question?

I think so?  Here's a couple samples:
   @ 110102s2020 nyua 000 0 eng d
@ 180420s2019 nyua j 000 1 eng d

-- Can you share how the search link looks like that does work vs. the one
that doesn't?

If I do a "yr,st-year" search via keyword search (which works):
https://circ.ccfls.org/cgi-bin/koha/catalogue/search.pl?advsearch=1=kw=yr%2Cst-year%3A2019-2020_by=relevance

If I search from the "Publication date (-)" search:
https://circ.ccfls.org/cgi-bin/koha/catalogue/search.pl?advsearch=1=yr%2Cst-year=2019-2020_by=relevance

 From Bywater's Koha demo using Publication date (-):
https://intranet.bywatersolutions.com/cgi-bin/koha/catalogue/search.pl?advsearch=1=yr%2Cst-year=2011-2012=and=kw=and=kw_by=relevance

(I used a different date range because there was only one result for
2019-2020 in the demo system.)

Thanks much,
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] "Item Due Reminder"

[Katrin Fischer]

Hi Victor,

do you mean you want to send the PREDUE instead of the PREDUEDGST
notice? One will be send with a summary of all items getting due, the
other, I believe, will send one separate notice for each item.

The Digest will be used, when the digest checkbox is checked in the
patron messaging preferences table in the patron account. Otherwise the
other template will be used.

Hope this helps,

Katrin

On 12.02.21 12:25, Victor Barroso Oliveira wrote:

Good Morning,
Koha is sending "Item Due Reminder (Digest)" messages.
How to enable to send messages only through "Item Due Reminder"
Thank you,
Victor
___

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 API

[Katrin Fischer]

Hi,

you can find a list of protocols and APIs Koha supports in the wiki:

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

Besides the JSON reports API Alvaro mentioned the REST API might also be
something to look at.

Hope this helps,

Katrin


On 15.02.21 18:16, Alvaro Cornejo wrote:

Hi

Indeed Koha has an API but don't know about its details. Maybe someone else
can clarify that. Have you checked koha wiki & documentation?

However, depending on what info you need, you might use reports module. You
can create a report, make it "public" and run it from your external
system.  Koha will return the info in JSON format that you can process as
needed.

Hope this helps.

Regards,

Alvaro


||
  Stay safe / Cuídate/  Reste sécurisé
*7* Switch off as you go / Apaga lo que no usas /  Débranchez au fur et à
mesure.
  *q *Recycle always / Recicla siempre / Recyclez toujours
  P Print only if absolutely necessary / Imprime solo si es necesario /
Imprimez seulement si nécessaire


Le lun. 15 févr. 2021 à 04:38, Mr. Sitali C. S.  a
écrit :


Greetings,

I would like to know if there exists a Koha API with a parameter
that returns all parameters for the student like when a book was borrowed.
This API is for integrating with  student information system
Any pointers folks will be appreciated.

Kind regards

Sitali CS


--
Charles Lwanga College of Education,
P. O. Box 660193,
Monze,
ZAMBIA.

Mobile: +26 0979 869471
 +26 0966 869471
SKYPE: Libsitali
___

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] Publication date (yyyy-yyyy) advanced search option not working in my Koha instance

[Katrin Fischer]

Hi Cindy and all,

sorry for the copy and paste error in the email before... guess it as
about time something like that happened.  Trying again to keep the
thread, please just ignore the other email:

I have just tested in our 20.05 test installation and it appears to work
ok there.  Maybe some first things to look into:

Are you using Zebra or Elasticsearch?

Is 008 pos. 7-10 cataloged correctly for the records in question?

Can you share how the search link looks like that does work vs. the one
that doesn't?

Hope this helps,

Katrin

On 04.02.21 17:29, Cindy Murdock Ames wrote:

Hi all,

We recently upgraded to 20.05.08 from 19.11, and we've found that the
advanced search option in the staff interface for publication date by year
range isn't producing any results for us if we use it.  Specifying it with
y,st-year in the keyword search instead *does* produce results though.

Does anyone have any ideas what might cause this?  I've tested it on
Bywater's demo, which is running 20.05.04, and it does work there, so I'm
guessing it's some quirk specific to our system rather than an actual bug
(unless it happened to be introduced between the .04 and .08 releases).
Here's our server specs:

Koha version: 20.05.08.000
OS version ('uname -a'): Linux ccflskoha.ccfls.org 4.15.0-135-generic
#139-Ubuntu SMP Mon Jan 18 17:38:24 UTC 2021 x86_64
Perl interpreter: /usr/bin/perl
Perl version: 5.026001
Perl @INC: /usr/share/koha/lib
/usr/share/koha/installer
/usr/share/koha/lib/installer
/etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.1
/usr/local/share/perl/5.26.1
/usr/lib/x86_64-linux-gnu/perl5/5.26
/usr/share/perl5
/usr/lib/x86_64-linux-gnu/perl/5.26
/usr/share/perl/5.26
/usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base
/var/lib/koha/ccfls/plugins
MySQL version: mysql Ver 15.1 Distrib 10.4.17-MariaDB, for debian-linux-gnu
(x86_64) using readline 5.2
Apache version: Server version: Apache/2.4.29 (Ubuntu)
PSGI: Plack (deployment)
Memcached: Servers: 127.0.0.1:11211 | Namespace: koha_ccfls | Status:
running. | Config read from: koha-conf.xml
Zebra version: Zebra 2.0.59 (C) 1994-2014, Index Data Zebra is free
software, covered by the GNU General Public License, and you are welcome to
change it and/or distribute copies of it under certain conditions. SHA1 ID:
c00bfddbf0f3608340d61298acc61dafb167f9b2 Using ICU
Date and time: 02/04/2021 11:16
Time zone: Used: America/New_York | Config: Undefined | Environment (TZ):
Undefined

Many 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] Search does not work

[Katrin Fischer]

Hi Inês,

I believe that was not the cause of the issue, but just that the default
setup of UNIMARC is a bit different to the MARC21 one and less
standardized at this point.

The English default for the item fields looks like this currently:

https://git.koha-community.org/Koha-community/Koha/src/branch/master/installer/data/mysql/en/marcflavour/unimarc/mandatory/unimarc_framework_DEFAULT.sql#L193

I notice there is no subfield set up for items.cn_sort, but also some
others like damaged status (items.damaged) or internal note
(items.itemnotes_nonpublic) appear to be missing.

If you compare to the French files, these look a bit different and more
complete:

https://git.koha-community.org/Koha-community/Koha/src/branch/master/installer/data/mysql/fr-FR/marcflavour/marc21/Obligatoire/marc21_framework_DEFAULT.sql#L105

So it looks like this depends on the language you chose for your
installation at least and possibly reinstalling is not going to fully
solve it. I'd recommend having a close look at the mappings and
available fields in items again to see that you can complete this a bit
more. You could also report any problems with the defaults to bugzilla,
so we can see about improving them.

The shelf browser should work in theory if your items all have a
callnumber set and that is mapped to items.itemcallnumber correctly.

Hope this helps,

Katrin


On 02.02.21 12:05, Inês M. Ferreira wrote:

Hello again,

We were finally able to check the indexing configuration and you were right 
that it was set to MARC21 while the rest was UNIMARC. Thank you so much!

I still have a question, however. Is it possible that this problem with the 
MARC flavours messed up some of the Koha to MARC mappings? For instance, 
items.cn_source is not mapped to anything.

Meanwhile we upgraded to 20.11 and I've noticed I cannot add local cover images 
to items (I'm assuming because of the MARC mappings). The shelf browser is also 
flaky, it works for some items but not all.

Would it be best to uninstall and install again with the correct settings from 
the start? Or are these symptoms of something else?

Thank you again!
Inês


De: Koha  em nome de Katrin Fischer 

Enviado: domingo, 31 de janeiro de 2021 17:09
Para: koha@lists.katipo.co.nz 
Assunto: Re: [Koha] Search does not work

Hi Inês,

the indexing process looks for the biblionumber of your records in a
specific field and the error points to it not finding it in the field it
expected it. UNIMARC and MARC21 use different fields for this, so one
reason can be a configuration mismatch.

So this is the first thing I would check:

Your Koha installation and your indexing configuration both need to be
set to UNIMARC.

For the installation this is set by the MARC flavor in the web
installer. As you could catalog your records without issues, I expect
that to be set correctly. You can also check the marcflavour system
preference to make sure.

for the index configuration it's set when the instance is created. It
defaults to MARC21, so needs to be changed to UNIMARC explicitly.
Possibly the best way to check this is having a look at your
koha-conf.xml file. If there is a lot MARC21 listed there, it might be
the source of the issue you are seeing.

Another thing to check in Koha: Go to the Koha-to-MARC-Mappins and look
up what field biblio.biblionumber is mapped to.

Hope this helps,

Katrin


On 27.01.21 17:36, Inês M. Ferreira wrote:

Hello all,

I was hoping you could guide us through our issue with search.

We have installed Koha a few months ago and we cannot get the search to work. 
Both the OPAC and the staff interface always present the result “No results 
found”, even though we know we have over 600 records and 1000+ items (e.g. a 
link to the details page works).

Version Koha:20.05.04.000
Version SO ('uname -a'):  Linux koha 5.4.0-58-generic #64-Ubuntu 
SMP Wed Dec 9 08:16:25 UTC 2020 x86_64

We use UNIMARC.


When attempting to reindex zebra we get the following error:

zebraidx(135744) [warn] Record didn’t contain match fields in 
(bib1,Local-number)


Why doesn’t it work? Where do we start?

Thank you,
Inês M. Ferreira
___

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] Age restriction no longer working?

[Katrin Fischer]

Hi Sue,

I just tested this on the latest development version and it will works
here. Could you maybe share some more information?

What I did in order to test:

- Set system preference AgeRestrictionMarker to FSK
- Went to the bibliographic frameworks and made sure 521$a was set to be
visible in OPAC, editor and staff interface
- Went into the Koha to MARC mappings and set 521,a for
biblioitems.agerestriction
- Changed one of my records to have 521$aFSK99 $aFSK 99
- Made sure my patron was under the age of 99
- Tried to check the item out and got: Age restriction FSK 99 | FSK99.

What is the exact version of Koha you are using? Did it stop working
after an upgrade? Could there have been any changes to your frameworks
or the mapping?

Maybe something to check first is that the age restrictions are still
stored correctly in your database via the mapping. Something like this
for a test record:

SELECT agerestriction FROM biblioitems WHERE biblionumber = XX

Hope this helps,

Katrin

On 03.02.21 22:57, Sue McMillan wrote:

Good morning,

We have been using Age restriction in Koha for 2 years, using field 521$a to 
input our restriction information (FSK 13) and mapping that to 
biblioitems.agerestriction - to restrict the age of adult graphic novels to 
people over the age of 13.  AgeRestrictionMarker is set in Administration. This 
has suddenly stopped working.  I have checked the manual but it doesn’t appear 
to have changed.  Is this an error in Koha?


Ngā mihi

Sue McMillan
Kaiārahi Whakarārangi Pukapuka me ngā Whakahaere Pūnaha | Cataloguing and 
Systems Administrator
Te Kaunihera ō Taranaki ki Te Tonga | South Taranaki District Council
46 High Street | Private Bag 902, Hāwera 4640, NZ
Waea/Phone: +64 6 278 0555 | 0800 111 323 | 
www.southtaranaki.com

This e-mail and any attachments may contain confidential and privileged 
information. If you are not the intended recipient, please notify the sender 
immediately by return e-mail, delete this e-mail and destroy any copies. Any 
dissemination or use of this information by a person other than the intended 
recipient is unauthorised and may be illegal. Please note that this 
communication does not designate an information system for the purposes of the 
Contract and Commercial Law Act 2017.
___

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] X Wildau: Stundenplan anschauen und sinnvolle Termine ermitteln,X Wildau: Rückmeldung an Stundenplan - abwarten und nächste Woche bei den Studierenden nachfragen

[Katrin Fischer]

Hi Cindy,

I have just tested in our 20.05 test installation and it appears to work
ok there.  Maybe some first things to look into:

Are you using Zebra or Elasticsearch?

Is 008 pos. 7-10 cataloged correctly for the records in question?

Can you share how the search link looks like that does work vs. the one
that doesn't?

Hope this helps,

Katrin

On 04.02.21 17:29, Cindy Murdock Ames wrote:

Hi all,

We recently upgraded to 20.05.08 from 19.11, and we've found that the
advanced search option in the staff interface for publication date by year
range isn't producing any results for us if we use it.  Specifying it with
y,st-year in the keyword search instead *does* produce results though.

Does anyone have any ideas what might cause this?  I've tested it on
Bywater's demo, which is running 20.05.04, and it does work there, so I'm
guessing it's some quirk specific to our system rather than an actual bug
(unless it happened to be introduced between the .04 and .08 releases).
Here's our server specs:

Koha version: 20.05.08.000
OS version ('uname -a'): Linux ccflskoha.ccfls.org 4.15.0-135-generic
#139-Ubuntu SMP Mon Jan 18 17:38:24 UTC 2021 x86_64
Perl interpreter: /usr/bin/perl
Perl version: 5.026001
Perl @INC: /usr/share/koha/lib
/usr/share/koha/installer
/usr/share/koha/lib/installer
/etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.1
/usr/local/share/perl/5.26.1
/usr/lib/x86_64-linux-gnu/perl5/5.26
/usr/share/perl5
/usr/lib/x86_64-linux-gnu/perl/5.26
/usr/share/perl/5.26
/usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base
/var/lib/koha/ccfls/plugins
MySQL version: mysql Ver 15.1 Distrib 10.4.17-MariaDB, for debian-linux-gnu
(x86_64) using readline 5.2
Apache version: Server version: Apache/2.4.29 (Ubuntu)
PSGI: Plack (deployment)
Memcached: Servers: 127.0.0.1:11211 | Namespace: koha_ccfls | Status:
running. | Config read from: koha-conf.xml
Zebra version: Zebra 2.0.59 (C) 1994-2014, Index Data Zebra is free
software, covered by the GNU General Public License, and you are welcome to
change it and/or distribute copies of it under certain conditions. SHA1 ID:
c00bfddbf0f3608340d61298acc61dafb167f9b2 Using ICU
Date and time: 02/04/2021 11:16
Time zone: Used: America/New_York | Config: Undefined | Environment (TZ):
Undefined

Many 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] Hourly backup

[Katrin Fischer]

Hi Raphael,

you could try running the command manually to see if there are any
errors first and try to see if that gives you a clue.

Also, this doesn't look like you are using the standard tools to backup
Koha that are part of the packages. You can see the standard setup in
the last line here:

https://git.koha-community.org/Koha-community/Koha/src/branch/master/debian/koha-common.cron.daily#L30

Some more information can be found here:

https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_packages#koha-run-backups

Hope this helps,

Katrin

On 05.02.21 00:53, Raphael Meyer wrote:

I used this command:

*/60 * * * * mysqldump -ukoha_library -p... Koha_library | xz > 
/home/koha/backup/koha_library.sql.xz

Last it worked was on Sunday March 31 at 6 am my time. Has not worked since.


On 04.02.21 17:10, MJ Ray wrote:

Raphael Meyer  wrote:

The hourly back up has stopped working on my machine. Have Ubuntu 20
and Koha 20. I tried the Crontab -e but it did not work either. I
have no idea how I lost it but would like to put it back.

Br Raphael

Which instructions did you use to set it up?

When did you last know it worked and can you find any messages in any
logs from that time?

Do you still have some package called something like "cron" installed
on there? Maybe systemd-cron?

Hope that helps,

___

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 add Dataly Tech on Paid support in Greece and Cyprus

[Katrin Fischer]

Hi George,

I have added your contact information to the paid support directory on
the website. Please check if everything is correct.

Katrin

On 17.02.21 10:04, gvera...@dataly.gr wrote:

Hi All / Koha Community

I would like to ask to add company 'Dataly Tech' to Koha directory for
paid support in Greece and Cyprus.

We have already submit some patches, sign-off , testing and we prepare
to add more as we develop more and more..
Also as company we support Koha for National Library of Greece and
National Library of Cyprus, among other 80 Libraries on both countries.

Company Name: Dataly Tech
Contact Person: George Veranis
Contact email: i...@dataly.gr
Website: https://dataly.gr
Telephone: +30 231231 4264


Best Regards,
George Veranis
CTO Dataly Tech

___

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 a Koha Support provider in Taiwan

[Katrin Fischer]

Hi Frank,

thank you for adding the link. I've added your company to the list of
support companies. Please check if everything is correct and let me know
if anything needs to be changed.

Best regards,

Katrin

On 19.04.21 03:21, SYDT - Frank Chou wrote:

Dear Kartrin,

We've modified our koha traditional Chinese web site and add a link to Koha
community web site as you suggested.
https://www.sydt.com.tw/pro-lm_Koha.asp
Is there any point we don't catch and need to modify?
Please advise and thanks a lots.

Best regards,

Frank
--
碩陽數位科技有限公司
Shou Yang Digital Technology
Tel: 02-82280288
Fax: 02-82265022
10F. No. 166, Jianyi Rd., Chung Ho Dist., New Taipei City 23511, Taiwan,
R.O.C.
23511新北市中和區建一路166號10F
http://www.sydt.com.tw


SYDT - Frank Chou  於 2021年4月7日 週三 上午9:53寫道：


Dear Katrin,

We've add "*更多Koha相關資訊, 請至 *Koha Community  (More
Koha information, please link to Koha Community
)*" *in Traditional Chinese Koha page. (
https://www.sydt.com.tw/pro-lm_Koha.asp)
Thanks for your kindly reminder.

Best Regards,

Frank

--
碩陽數位科技有限公司
Shou Yang Digital Technology
Tel: 02-82280288
Fax: 02-82265022
10F. No. 166, Jianyi Rd., Chung Ho Dist., New Taipei City 23511, Taiwan,
R.O.C.
23511新北市中和區建一路166號10F
http://www.sydt.com.tw


Hi Frank,

I found the link to the Koha community website on your English website,
but was not able to locate it on the traditional Chinese one. Could you
please add a link there as well and let us know?

Please see:
https://koha-community.org/support/paid-support/how-to-get-listed/

Thanks,

Katrin

___

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 be listed as a Koha Support provider in Malaysia

[Katrin Fischer]

Hi Jesse,

thx for adding the link and making the other suggested corrections. I've
added your company to the list of support companies. Please check if
everything is correct and let me know if anything needs to be changed.

Regards,

Katrin

On 13.04.21 08:26, jesse...@edgetech.com.my wrote:

Dear Katrin,

Apologize for the late reply as we were outstation and hardly get
internet connection.

I've check with my web master and it's their mistake didn't written in
the URL.
However, we have update it.

You may check the URL for our page:
https://www.lemonjar.com.my/index.php/about-koha-ils/

also at the same time, we have link users to Koha Community via our
Demo Koha page and it can be access via: https://demoopac.lemonjar.com.my/

Kindly check and let me know then.

Thanks & have a nice day!


Regards,
Jesse
Lemonjar Software Media Sdn. Bhd.
Managing Director



Sent from my Huawei phone


 Original message 
From: Katrin Fischer 
Date: Mon, 12 Apr 2021, 5:17 am
To: JESSE KAH , koha@lists.katipo.co.nz
Subject: Re: [Koha] To be listed as a Koha Support provider in Malaysia

Hi Jesse,

in order to be listed we require a visible link to the
koha-community.org website. I couldn't spot one on your website.
Please
point me to it or let me know when you have added one.

See here:
https://koha-community.org/support/paid-support/how-to-get-listed/

Thanks,

Katrin

On 11.04.21 10:26, JESSE KAH wrote:
> *Dear Koha Community,*
>
>
>
> Lemonjar has been providing service and support in Malaysia for
Koha ILS and other open source platform for couple of years.
>
> We would also like to require community to list us for service
and service provider for Koha ILS in Malaysia.
>
>
>
> Our detail as follow:
>
>
>
> Company Name: *Lemonjar Software Media Sdn. Bhd. (1039463-K)*
>
> Contact Person: *Mdm. Jesse Kah Ingland / Mr. Chong*
>
> Contact Email: sa...@lemonjar.com.my / sa...@edgetech.com.my
>
> Website: https://www.lemonjar.com.my
>
> Contact Tel: *+603-7859 9226/ +6088-713226*
>
>
>
> We provide service from implementation, system architecture
design for Koha, customization, migration service, Koha Payment
Gateway, as well as integration according to needs.
>
> Further information on our service on Koha ILS can be found at:
https://www.lemonjar.com.my/
>
>
>
> Thanks & have a nice day!
>
>
>
>
>
> Best Regards,
>
> Jesse Kah Ingland
>
> Lemonjar Software Media Sdn. Bhd.
>
> -- Managing Director --
>
> Mobile: +6 (016) 8606 826
>
> Tel: +6 (03)7859 9226 (Selangor Office) | +6 (088) 713226 (Sabah
office)
>
> Fax: +6 (088) 713226
>
> Website: https://www.lemonjar.com.my
>
>   https://www.edgetech.com.my
>
> Other Email: mailto:lemonja...@gmail.com /
mailto:lemonjar.sa...@gmail.com
>
>
>
>
>
> Lemonjar Facebook page: https://www.facebook.com/lemonjarsoftmed/
>
> Edgetech Facebook page:
https://www.facebook.com/edgetechengineering/
>
> YouTube page:
https://www.youtube.com/channel/UCLV34OjYVdG6KQK_uTC2f3A/featured
>
>
>
>
>
> ___
>
> 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 be listed as a Koha Support provider in Malaysia

[Katrin Fischer]

Hi Jesse,

thx, I forgot to change the default setting. It's fixed now.

Katrin


On 22.04.21 01:07, jesse...@edgetech.com.my wrote:

Dear Karin,

Thanks for the add.
I've checked.
Can you kindly assist to update the "Personal Email" to "Work Email"?
Other than that, all are good =)

Thanks & have a nice day!


Regards,
Jesse
Lemonjar Software Media Sdn. Bhd.


Sent from my Huawei phone


 Original message ----
From: Katrin Fischer 
Date: Thu, 22 Apr 2021, 2:09 am
To: koha@lists.katipo.co.nz
Cc: jesse...@edgetech.com.my
Subject: Re: [Koha] To be listed as a Koha Support provider in Malaysia

Hi Jesse,

thx for adding the link and making the other suggested
corrections. I've added your company to the list of support
companies. Please check if everything is correct and let me know
if anything needs to be changed.

Regards,

Katrin

On 13.04.21 08:26, jesse...@edgetech.com.my
<mailto:jesse...@edgetech.com.my> wrote:

Dear Katrin,

Apologize for the late reply as we were outstation and hardly
get internet connection.

I've check with my web master and it's their mistake didn't
written in the URL.
However, we have update it.

You may check the URL for our page:
https://www.lemonjar.com.my/index.php/about-koha-ils/
<https://www.lemonjar.com.my/index.php/about-koha-ils/>

also at the same time, we have link users to Koha Community
via our Demo Koha page and it can be access via:
https://demoopac.lemonjar.com.my/
<https://demoopac.lemonjar.com.my/>

Kindly check and let me know then.

Thanks & have a nice day!


Regards,
Jesse
Lemonjar Software Media Sdn. Bhd.
Managing Director



Sent from my Huawei phone


---- Original message 
From: Katrin Fischer 
<mailto:katrin.fischer...@web.de>
Date: Mon, 12 Apr 2021, 5:17 am
To: JESSE KAH 
<mailto:jesse...@edgetech.com.my>, koha@lists.katipo.co.nz
<mailto:koha@lists.katipo.co.nz>
Subject: Re: [Koha] To be listed as a Koha Support provider in
Malaysia

Hi Jesse,

in order to be listed we require a visible link to the
koha-community.org website. I couldn't spot one on your
website. Please
point me to it or let me know when you have added one.

See here:
https://koha-community.org/support/paid-support/how-to-get-listed/
<https://koha-community.org/support/paid-support/how-to-get-listed/>

Thanks,

Katrin

On 11.04.21 10:26, JESSE KAH wrote:
> *Dear Koha Community,*
>
>
>
> Lemonjar has been providing service and support in
Malaysia for Koha ILS and other open source platform for
couple of years.
>
> We would also like to require community to list us for
service and service provider for Koha ILS in Malaysia.
>
>
>
> Our detail as follow:
>
>
>
> Company Name: *Lemonjar Software Media Sdn. Bhd.
(1039463-K)*
>
> Contact Person: *Mdm. Jesse Kah Ingland / Mr. Chong*
>
> Contact Email: sa...@lemonjar.com.my
<mailto:sa...@lemonjar.com.my> / sa...@edgetech.com.my
<mailto:sa...@edgetech.com.my>
>
> Website: https://www.lemonjar.com.my
<https://www.lemonjar.com.my>
>
> Contact Tel: *+603-7859 9226/ +6088-713226*
>
>
>
> We provide service from implementation, system
architecture design for Koha, customization, migration
service, Koha Payment Gateway, as well as integration
according to needs.
>
> Further information on our service on Koha ILS can be
found at: https://www.lemonjar.com.my/
<https://www.lemonjar.com.my/>
>
>
>
> Thanks & have a nice day!
>
>
>
>
>
> Best Regards,
>
> Jesse Kah Ingland
>
> Lemonjar Software Media Sdn. Bhd.
>
> -- Managing Director --
>
> Mobile: +6 (016) 8606 826
>
> Tel: +6 (03)7859 9226 (Selangor Office) | +6 (088)
713226 (Sabah off

Re: [Koha] Serials entry

[Katrin Fischer]

Hi Mohammad,

I think we will need more information in order to be able to help you
with your issue.

What is the exact version of Koha you are using?

Is this a new installation or an updated one, how was it installed?

Where are you adding the record, from the cataloguing module or the
serials module?

Did adding records work before or is this a problem from the beginning?

What do the log files of Koha show when the problem appears?

Hope this helps,

Katrin

On 16.08.21 15:26, Mohammad Shamim Afzal wrote:

After entering MARC RECORDS by selecting CREATE RECORD we get the message
REQUEST GATEWAY TIME OUT.

How to resolve this.


___

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

Re: [Koha] Keyword search not working

[Katrin Fischer]

Hi Steve,

I am not sure what could cause this. But some additional information
might help to get this resolved:

Which search engine are you using? Zebra or Elasticsearch?

What is the exact version of your Koha installation? You can find this
information on the About page.

Hope this helps,

Katrin

On 18.08.21 21:56, Steve Austin wrote:

Hi team...

Kindly help me sort out this:

When I search for an item on the OPAC without specifying if I want to
search by title, call number, barcode number etc it show no results have
been found but if I specify either the title, call number, barcode etc it
shows the item...

How can I sort this such that it searches without having to click on the
drop down box to choose the search option?
___

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] Interoperate with Search Engines

[Katrin Fischer]

Hi Victor,

can you explain a bit more about the functionality you are thinking about?

One feature that came to mind was the sitemap script that helps you to
have your Koha catalog indexed by search engines: See
https://koha-community.org/manual/21.05/en/html/cron_jobs.html?highlight=sitemap#sitemap

Hope this helps,

Karin

On 18.08.21 19:59, Victor Barroso Oliveira wrote:

Does Koha Interoperate with Search Engines?
___

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] Search/List RSS feeds (trigger? add call number?)

[Katrin Fischer]

Hi Tasha,

I can't answer all your questions, but maybe I can provide a bit of
information.

I think that for the RSS feed on lists the date the record is added to a
list is used. Would that match with what you see?

I think adding the call number to the RSS feed might not be straight
forward, because this information would have to be taken from the items
instead of the record. As there can be many items per record and the
call numbers can vary between the different branches and locations of a
library system, the task of displaying this information in a useful and
nice way is not an easy one. Maybe filing an enhancement request on
bugzilla to discuss this more would be a good first step to discuss this
further.

Hope this helps,

Katrin

On 19.08.21 15:51, Bales (US), Tasha R wrote:

Good morning,

I'm writing with a couple questions about out-of-the-box RSS feeds for 
searches.  I'm interested in how to modify them (I really need one or more of 
our call numbers/classification numbers to be included), and how they are 
triggered.  I see two types of feeds, below.

"Subscribe to this search"

* The manual says this feed "will allow you to see when a new item is added 
to the catalog".

* How is a "new item" defined?  I've taken a look at opac-opensearch.tt and 
opac-search.pl, in order to under how date limiting is coming in to play, specifically (which 
dates, what comparison, what fields, etc.).  I do see reference to an 005 date "hack" for 
Atom, but it seems like only the RSS portions of the code are relevant.  I'd like to determine if I 
can only ever expect newly added records to be returned, or would/could updated records also be 
returned?

"Subscribe to this list"

* I don't see information about this feed in the manual.

* Since this is a search about already-cataloged, known items, it wouldn't make 
sense for the RSS to retrieve only newly cataloged records.  Therefore, what should 
trigger a subscriber to receive an update about their list if an item has been updated?  
Is it the bib 005, or something else?  I've tried editing a few records in a list I am 
subscribed to, expecting to get a new email, but I didn't receive a message.  Although 
this last part may sound confusing, I'm leaving as is, as it may help explain 
context-I've added the feeds to my Microsoft Outlook, where each matching item shows up 
as a discrete "email" message in my RSS Feeds folder.

Maybe the problem here is my understanding of RSS.  My feeds appear to be refreshed every 
time I check my mail, but I'm only receiving RSS for newly added records.  I didn't 
receive a new feed today of records in my "list" that I edited yesterday.

Finally, I find that the RSS output is not usable for my patrons.  We really need call 
number to be included in the RSS.  It looks like we could modify the template line below 
to swap out isbn with another identifier, but I'm not sure how to know what term to swap 
in after "SEARCH_RESULT.":

ISBN:[% SEARCH_RESULT.isbn | html %]

I've tried "report-number", "callnum", "lcn", and "local-classification", which 
all failed to produce results.

Please advise if there are any known examples about customizing the RSS templates for the basic 
searches above (I didn't see anything promising in the Wiki, when I searched for "RSS" or 
"opensearch.tt").

Thanks so much for your time,


Tasha Bales
Enterprise Services
http://isesi.web.boeing.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] Upgrade procedure

[Katrin Fischer]

Hi Tom,

others might add to this, but

a) you don't need to update from one version to another in steps/stages.
You can directly update from 19.11 to 20.11.

b) the update will take care of the database changes required for all
instances of a Koha installation.

That said, it's always recommended to do a backup before any major
update and if possible to test on a test server first.

Hope this helps,

Katrin

On 23.08.21 16:50, Tom Burke wrote:

Hello the list

I am a new volunteer IT help for a small number of community libraries in 
Sheffield, UK. I have been tasked with researching what we need to do to 
upgrade our Koha installation, but so far have not been able to find any 
definitive guidance. (I may of course have been looking in the wrong place.) 
I’d welcome some advice from the list, please.

We have a server running Debian Buster on which we have installed Koha 19.11 
Common. Then we have 5 actual instances configured, one each for each of the 
community libraries. We would like to upgrade from 19.11 to a later release. 
I’ve gained some experience in installing and configuring Koha to a basic 
degree on local test sites and would now like to test the upgrade procedure; 
however, I have been unable to find any documentation about the procedure to 
follow.

Among the questions I’ve got are:
a) we assume that if we wanted to move from 19.11 to 20.11, we would 
have to do it in two stages, i.e. first to 20.05 and subsequently to 20.11 - is 
this a correct assumption?; and
b) does the upgrade procedure amend the database schema, etc, for 
multiple instances that are using the same Koha Common installation?

My apologies if I’m asking in the wrong place, or if I‘ve simply missed some 
clear instructions on all this.

Tom Burke
___

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 procedure

[Katrin Fischer]

Hi Tom,

also, some information on the upgrade process can be found here:

https://wiki.koha-community.org/wiki/Koha_on_Debian#Upgrade

Katrin

On 23.08.21 17:29, Katrin Fischer wrote:

Hi Tom,

others might add to this, but

a) you don't need to update from one version to another in steps/stages.
You can directly update from 19.11 to 20.11.

b) the update will take care of the database changes required for all
instances of a Koha installation.

That said, it's always recommended to do a backup before any major
update and if possible to test on a test server first.

Hope this helps,

Katrin

On 23.08.21 16:50, Tom Burke wrote:

Hello the list

I am a new volunteer IT help for a small number of community
libraries in Sheffield, UK. I have been tasked with researching what
we need to do to upgrade our Koha installation, but so far have not
been able to find any definitive guidance. (I may of course have been
looking in the wrong place.) I’d welcome some advice from the list,
please.

We have a server running Debian Buster on which we have installed
Koha 19.11 Common. Then we have 5 actual instances configured, one
each for each of the community libraries. We would like to upgrade
from 19.11 to a later release. I’ve gained some experience in
installing and configuring Koha to a basic degree on local test sites
and would now like to test the upgrade procedure; however, I have
been unable to find any documentation about the procedure to follow.

Among the questions I’ve got are:
a) we assume that if we wanted to move from 19.11 to 20.11, we
would have to do it in two stages, i.e. first to 20.05 and
subsequently to 20.11 - is this a correct assumption?; and
b) does the upgrade procedure amend the database schema, etc, for
multiple instances that are using the same Koha Common installation?

My apologies if I’m asking in the wrong place, or if I‘ve simply
missed some clear instructions on all this.

Tom Burke
___

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 to Add our name to the list of Paid support providers for Koha

[Katrin Fischer]

Hi,

I've added your company's information to the Koha support provider list
as requested:

https://koha-community.org/support/paid-support/alpha/

At the moment the community's only requirement for listing is a 'visible
link to the Koha community website', which is not very specific. I had a
bit of trouble locating it at first on your website, but then found it
behind the logo in the top right corner. It would be great if you could
also provide a text link somewhere.

Katrin


On 10.08.21 12:04, Sudhir Gandotra wrote:

Hello,

As requested earlier also, please add our details to the list of Koha paid
services providers:

 *Company Name*:  BESTBOOK BUDDIES TECHNOLOGIES PVT. LTD.

 *Contact Person*:  SUDHIR GANDOTRA

 *Contact email*:  sud...@bestbookbuddis.com

 *Website*:  www.bestbookbuddies.com

 *Telephone*:  +91-93-124-65666 / 91-97-185-26699

Please note that we are the team that introduced Koha in India with the
first commercial implementation at Delhi Public Library and currently we
are providing Koha support to more than 700 libraries across 30 countries.

Thanks and warm regards,



___

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 Add our name to the list of Paid support providers for Koha

[Katrin Fischer]

Hi Giorgos,

I've added your company's information to the Koha support provider list
as requested:

https://koha-community.org/support/paid-support/alpha/

Katrin


On 10.08.21 17:14, Giorgos Anastasakis wrote:

Dear Sirs,

We would like to be listed on your site as a Koha Support provider.

Please see below the part of our website which refers to our KOHA activity.

https://www.interoptics.gr/index.php/2011-12-05-14-29-26/internet/koha-integrated-library-system

You will also see a link to the KOHA community website on the right side of our 
central webpage.


Company Name: INTEROPTICS

Contact Person: Manos Kollias

Contact email: i...@interoptics.com.gr

Website: www.interoptics.gr

Telephone: +30 210 9027203

Categories: Greece, Cyprus, Europe

___

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] [EXTERNAL] Re: Search/List RSS feeds (trigger? add call number?)

[Katrin Fischer]

Hi Tasha,

sorry for my late reply.

I am sorry, I don't have the time to take a closer look at the
templates, but usually it will not be possible to display arbitrary MARC
fields. You could try the column names from biblio and biblioitems, but
it might not work, as it depends on what was made available to the
template as variables.

An enhancement request is a bug on bugzilla with importance
"enhancement" selected. For Koha the term bug is also used for new
features and improvements.

Hope this helps,

Katrin

On 23.08.21 16:18, Bales (US), Tasha R wrote:

Thanks for your reply, Katrin.

Your comments on including a call number in an RSS make perfect sense.  We could use a 
bibliographic attribute instead, such as technical report number in 027, thus my attempt 
to sub in "report-number" for isbn. I don't know if I'm on the right track with 
respect to syntax (i.e., what are the possible terms that could be subbed in for isbn?), 
but I haven't tried 001 or 035 yet; I will give those a try too.

I am surprised by the behavior of the "Subscribe to this list" RSS.  I was 
really hoping that would allow for reappearance in the feed if an item in the list was 
edited.  Thanks for your suggestion to file an enhancement request (is that just a bug 
report, or is there a separate option for enhancement requests?).

If anyone has knowledge of what code we would look at in addition to 
opac-opensearch.tt and opac-search.pl, please advise.  Maybe there is something we 
can tweak fundamental to RSS to allow for reporting on records with an 005 that is 
>= a specified value.  I believe we could use a custom feed, but I think that 
would only work for users on a case-by-case basis, which would be unmanageable.  
Thanks again for your time.


Tasha Bales
Enterprise Services
http://isesi.web.boeing.com/

-Original Message-
From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Katrin Fischer
Sent: Monday, August 23, 2021 5:38 AM
To:koha@lists.katipo.co.nz
Subject: [EXTERNAL] Re: [Koha] Search/List RSS feeds (trigger? add call number?)

EXT email: be mindful of links/attachments.



Hi Tasha,

I can't answer all your questions, but maybe I can provide a bit of information.

I think that for the RSS feed on lists the date the record is added to a list 
is used. Would that match with what you see?

I think adding the call number to the RSS feed might not be straight forward, 
because this information would have to be taken from the items instead of the 
record. As there can be many items per record and the call numbers can vary 
between the different branches and locations of a library system, the task of 
displaying this information in a useful and nice way is not an easy one. Maybe 
filing an enhancement request on bugzilla to discuss this more would be a good 
first step to discuss this further.

Hope this helps,

Katrin

On 19.08.21 15:51, Bales (US), Tasha R wrote:

Good morning,

I'm writing with a couple questions about out-of-the-box RSS feeds for 
searches.  I'm interested in how to modify them (I really need one or more of 
our call numbers/classification numbers to be included), and how they are 
triggered.  I see two types of feeds, below.

"Subscribe to this search"

* The manual says this feed "will allow you to see when a new item is added 
to the catalog".

* How is a "new item" defined?  I've taken a look at opac-opensearch.tt and 
opac-search.pl, in order to under how date limiting is coming in to play, specifically (which 
dates, what comparison, what fields, etc.).  I do see reference to an 005 date "hack" for 
Atom, but it seems like only the RSS portions of the code are relevant.  I'd like to determine if I 
can only ever expect newly added records to be returned, or would/could updated records also be 
returned?

"Subscribe to this list"

* I don't see information about this feed in the manual.

* Since this is a search about already-cataloged, known items, it wouldn't make 
sense for the RSS to retrieve only newly cataloged records.  Therefore, what should 
trigger a subscriber to receive an update about their list if an item has been updated?  
Is it the bib 005, or something else?  I've tried editing a few records in a list I am 
subscribed to, expecting to get a new email, but I didn't receive a message.  Although 
this last part may sound confusing, I'm leaving as is, as it may help explain 
context-I've added the feeds to my Microsoft Outlook, where each matching item shows up 
as a discrete "email" message in my RSS Feeds folder.

Maybe the problem here is my understanding of RSS.  My feeds appear to be refreshed every 
time I check my mail, but I'm only receiving RSS for newly added records.  I didn't 
receive a new feed today of records in my "list" that I edited yesterday.

Finally, I find that the RSS output is not usable for my patro

Re: [Koha] Batch check outs timing out after upgrade and migration

[Katrin Fischer]

Hi Matthew,

is there anything on the "About Koha" page that might give a clue?

* Is Memcached running?
* Is Plack configured and running?
* Is there any error or warning displayed on the System information tab?

Hope this helps,

Katrin

On 10.09.21 06:03, Matthew Lindfield Seager wrote:

Hi All,

I'm a Koha newbie so I hope this is the appropriate forum for this
question, please let me know if not!

I'm the ICT Manager in a small school in Phnom Penh that had a working Koha
installation. One of our physical servers died and, rather than replace it
to get back up to full redundancy, we decided to move our on-prem servers
to an IaaS provider (Linode).

In the process of restoring Koha onto the new server I discovered we were
running Koha 20.05 on the old server and 21.05 on the new server. I then
made the fateful mistake of proceeding with both changes at once (despite
knowing better ). I upgraded the old server to 21.05 and then backed up
and restored onto the new server (both Ubuntu 20.04 LTS). I also added TLS
using Let's Encrypt at the same time.

It all seemed to go smoothly but we're now experiencing slow performance
when checking out and looking up patrons and we're getting gateway timeouts
when we try to use Batch Check Out.

Does anyone have any tips on how to troubleshoot this? So far I've:

- checked specs (new server is a "dedicated" 4GB VM with specs
equivalent to or better than the old server)
- tried to find any configuration differences between the old server and
the new server
- looked through the wiki pages on performance
  and tuning
  to see if
there's anything we'd done on the old server but not on the new

In the process I discovered that the old server was running on
MariaDB 10.3.31 whereas I installed MySQL 8.0.26 on the new server. Could
that be the source of all our issues or is that a red herring?

To rule out MariaDB as the issue I've tried backing up the new server and
restoring it on to an even newer server with MariaDB installed but so far
I've not been successful in getting Koha running on MariaDB, despite
successfully running the restore (after adjusting the SQL dump to change
from MySQL's `utf8mb4_0900_ai_ci` collation to MariaDB's
`utf8mb4_general_ci `).

Has anyone got any nuggets of wisdom? I fear our next best option might be
to create a new (MariaDB) server from the original back ups and manually
re-enter the past 4 days worth of borrowing and returns 

Regards,
Matt
___

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] New community member introduction and question

[Katrin Fischer]

Hi David,

welcome!

Currently it's not possible to make the Price field visible in the OPAC
normal view. If you go to Administration > Table settings > OPAC >
holdingst you can see all columns that can be made visible/be hidden
from the table.

Maybe putting/copying the price to OPAC note (item_notes) could work for
your use case?

Hope this helps,

Katrin

On 10.09.21 17:50, da...@penkler.net wrote:

Hi,
I work as a volunteer in a non-profit association that runs the
library for culture and religion at the Theological Centre in Meylan
near Grenoble in France. My main task is cataloguing.

We receive many books through book donations and bequests with the
result that we have a large number of duplicates (circa 2500 books out
of some 4). We are setting up a framework to sell the duplicates
for a token amount. To this end we have added a item.notforloan value
"For Sale" which we use to generate a report of books for sale from
which we create a virtual shelf that can be consulted by the patrons.
I am trying to figure out how to add a "Price" column with items.price
to the Holdings tab of the opac details page for folks viewing the
"For Sale" virtual shelf in the "Normal View". The price is shown in
the "Marc view". Any advice is gratefully accepted.
Thanks,
-David Penkler
___

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 in koha 21.05 all users from LDAP

[Katrin Fischer]

Hi,

as others have pointed out, there is no way to do this via LDAP in Koha
at the moment.

What you could do is maybe get a list of patron information from your AD
to use with the patron import tool. You could regularly import the new
patrons manually or automated via the available command line tools.
There are also REST API endpoints for patron data that might be useful.

Hope this helps,

Katrin

On 10.09.21 10:45, Tadas G wrote:

Hello,

We have Koha 21.05 installed and configured to work with AD. Everything is
fine, users can login to Koha using AD credentials, but in Patron list they
appear only after successful authorisation. It is quite annoying, because
if you want to assign book to the reader, he/she has to be in patron list.
Is it possible to create Cron job to import users to patron list
automatically from AD (it is enough to import only a few fields, all other
fields can be updated after user login)?

Thanks for the answers
___

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 make the Price field visible in the OPAC normal view.

[Katrin Fischer]

Hi David,

I believe currently copying from one field into another is not an option
with the batch edit tool for items.

Katrin

On 14.09.21 09:38, da...@penkler.net wrote:

Hi Katrin,
Thank you very much for the suggestion to use the item_notes field.
That works perfectly for our needs.
Is there a way to use the batch operations to add the note from the
items.price field ?
Many thanks,
-David

On 2021-09-12 12:48, Katrin Fischer wrote:

Hi David,

welcome!

Currently it's not possible to make the Price field visible in the OPAC
normal view. If you go to Administration > Table settings > OPAC >
holdingst you can see all columns that can be made visible/be hidden
from the table.

Maybe putting/copying the price to OPAC note (item_notes) could work for
your use case?

Hope this helps,

Katrin

___

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

Re: [Koha] JSON report only contains partial results

[Katrin Fischer]

Hi Tasha,

the caching is done server side, so switching the browser would not make
a difference. Try reducing the time the results are cached maybe.

There is also a limit on how many results the JSON reports will show.
This is set by the SvcMaxreportRows system preference. The default is 10
so that can also explain surprising results. I think changing the LIMIT
is just a way to overwrite that preference, so you could do that for
individual reports or up the global limit.

Hope that helps,

Katrin

|
|

On 16.09.21 20:48, Bales (US), Tasha R wrote:

Any idea why my public report would return almost 2000 results, but the JSON 
URL for that report (accessed right after I ran the report), would only display 
a list of 9 results?

I've tried reindexing to no avail.  I've also tried duplicating and rerunning the report, 
as well as changing the report category back to "Cataloging" instead of the 
custom category I'd added.

In my initial experimentation with reports and their JSON URL's, everything worked perfectly. 
 Now, besides the above, I'm noticing odd behavior with the "=1" 
parameter, in that if I access the annotated report, then subsequently strip off that 
parameter and navigate again to the report, the output is still annotated.  I attributed this 
to caching, but I get this behavior even if I try to access the not annotated URL in a 
different browser.  That doesn't seem possible; I presume there is something about JSON I 
just don't understand.


Tasha Bales
Enterprise Services
http://isesi.web.boeing.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] Keyword search (2)

[Katrin Fischer]

Hi Michael,

I haven't had the time to test this out properly as I hoped for, but
from past experience I believe these preferences could explain the
difference:

 * QueryAutoTruncate
 * QueryFuzzy
 * QueryStemming

Are the results still different when you turn all of those off making
the normal search as "exact" as possible? In our test installation
search results match up perfectly as soon as I turn off QueryAutoTruncate.

Hope this helps,

Katrin

On 29.06.21 21:21, Michael Kuhn wrote:

Hi

In our library we are using an unchanged Zebra configuration as coming
with Koha 20.11.00.

The keyword search is described in
https://koha-community.org/manual/20.11/en/html/searching.html#basic-searching

There it says: "When a single word is entered, a keyword search is
performed. You can check this out by typing one word into the form and
note the number of results located. Then, repeat the search with a
minor change. In front of the search word, type ‘kw=’ followed by the
same search term. The results will be identical."

This is NOT TRUE. Instead there is quite a difference.

Search for: life
* URL: .../search.pl?q=life
* 821 results

Search for: kw=life
* URL: .../search.pl?q=kw%3Dlife
* 788 results

Does anyone know what is going on here?

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 21.11 release dates

[Katrin Fischer]

Hi,

I can see that there has been a bug reported for adding that feature,
but there is currently no developer working on this (no assignee set):

*Bug 27323*
 -
Plugin for Place of Publication 260$a

Katrin

On 15.10.21 17:39, Himanshu Aggarwal wrote:

I was hoping that you can make 260$b that is Place of Publication autofill
just like name of publisher in 260$c

On Thu, Oct 14, 2021 at 12:41 PM Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:


Hello everybody,

Here is the timeline for the 21.11 major release:

* Oct 29th - "Soft" feature freeze, nothing big or with high risk of
side-effects will be included into the final release if not marked as
Passed QA
* Nov 3-5 - "Hard" feature freeze, nothing considered as an
improvement will be pushed if not marked as Passed QA
* Nov 10th - String freeze, draft of release notes published
* Nov 17th - Only bug fixes considered major, critical or blocker
will be pushed
* Nov 26th - Final release

Let me know if you have any comments or modification requests!

Regards,
Jonathan
___

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" on Opac

[Katrin Fischer]

Hi Bruce,

I am not sure what might be going on there, but maybe some things to check:

- What does the link on the result list look like? Does it correctly
contain the biblionumber in the link?
- When you look at the same record in your staff interface and use the
display in OPAC link: Is the link the same and does it work correctly?
- Did you make any local changes to your XSLT files that are used for
the results display?

Hope this helps,

Katrin


On 17.10.21 00:44, Bruce Yelen wrote:

Being rather new to this list, I will apologize in advance if I'm
mis-framing this question.



After upgrading from Koha 20.05 to 21.05, I started receiving an HTTP 500
error when an OPAC user clicks on a specific title in the list returned by a
catalog search.  This does not occur when doing a catalog search on the
staff pages.  I have looked through the various Koha logs, but cannot find
any errors pointing to a script, or anything.  Any ideas and suggestions of
where to look for the cause and resolution of this would be helpful.



Many Thanks!



Bruce Yelen

___

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] Searching within a virtual shelf

[Katrin Fischer]

Hi David,

I don't think it's possible a the moment, but there is a bug already
filed asking for this feature:

*Bug 20172*
 - Add
a search bar in list tables

If you add yourself CC you will get updates on any changes.

Katrin

On 08.10.21 11:01, da...@penkler.net wrote:

Hi,
We have some virtual shelves with a large number of entries. Is it
possible to configure OPAC to allow a user to search within a virtual
shelf for author, title etc ?
Thanks,
-David
___

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] Reason to define Koha item type in 942

[Katrin Fischer]

Hi Caroline and all,

to add to the list of things:

- 942$c is used as the pre-selected item type when adding new items.
- 942$c will be used for record level article requests to determine
which circulation rule applies.
- I also believe that 942$c plays a role in record level hold requests,
but I couldn't quite pinpoint that. I seem to remember that it was used
for the max number of possible record level holds for an item type.

Hope that helps,

Katrin

On 15.10.21 16:22, Caroline Cyr-La-Rose wrote:

Hello!

I'd like to add to Indranil's explanation.

952$y is mandatory for circulation IF item-level_itypes is set to
"specific item". Otherwise, 942$c is used as the item type for
circulation.

Another thing that I have observed about 942$c is that it is indexed
for the search in the same way as 952$y. So if you have records
without items (for journal articles, websites or ebooks for example),
these will still be searchable through the item type filter.

Also, if 942$c and 952$y are not the same in one record (for example,
942$c is Book and 952$y is Reference), they will show in the results
of a search for either type.

I'm making a note to compile all our comments to add into the manual,
since that's where you searched for the information first.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29252

Best regards,

Caroline

On 2021-10-15 10 h 02, Indranil Das Gupta wrote:

Hi Tasha,

942$c - defines the type of material the bibliographic record
represents,
sort of like it's GMD (general material description). Has no bearing on
circulation of material. Stored as marcxml in biblio_metadata.

952$y - defines the item-level item, and is used mandatorily for Koha's
circulation rules which work as a permutation of (a) branchcodes (b)
patron
categories and (c) item-level item types. Stored as itype column in
items
table.

Hope this helps
Indranil

On Fri, 15 Oct, 2021, 12:44 am Bales (US), Tasha R, <
tasha.r.ba...@boeing.com> wrote:


Good afternoon,

I recall reading (in the Koha manual?) the explanation for why it is
advantageous to define Koha item type in the bib 942 field.  I
believe it
has to do with exporting records, or the scope of records that is
included
when doing some type of report?  I'm trying to locate that information
again, but can't find it for the life of me.

Does this seem familiar to anyone?  Thanks.


Tasha Bales
Enterprise Services
http://isesi.web.boeing.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

Caroline Cyr La Rose, M.S.I.
Bibliothécaire | Responsable de produit

Tél. : 1-833-465-4276, poste 221
caroline.cyr-la-r...@inlibro.com


INLiBRO | Spécialistes en technologies documentaires | www.inLibro.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] Recursive auth import via SRU

[Katrin Fischer]

Hi,

I am not aware of a feature like that in Koha at the moment, but I found
an older bug in bugzilla that might be interesting:

*Bug 11300*
 - Add
a new authority linker which searches for authority links on a Z39.50
server.

Hope that helps,

Katrin

On 05.10.21 13:26, Thomas Klausner wrote:

Hi!

When we catalouge a new book by importing it via SRU, various
authorities are created (based on
BiblioAddsAuthorities/AutoCreateAuthorities), but only with the minimal
data available in the bibliographic record we're importing:

For example, a book might have an author:
100 1  _0(DE-588)133178706
_0https://d-nb.info/gnd/133178706
_0(DE-101)133178706
_aLensing, Thorsten
_eVerfasser
_4aut
_eIllustrator
_4ill
_2gnd

This will create a new authority record, but without all the nice,
additional data available at https://d-nb.info/gnd/133178706

Is there a way to "recursively" fetch more auth records (like geographic
info, keywords, ..)?

Greeting,
domm


___

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

Re: [Koha] Deleted Visible Records

[Katrin Fischer]

Hi Charles,

can you give an example for a report that still shows the deleted records?

Katrin

On 30.09.21 04:27, Charles Kelley wrote:

Hi, all!

 Some months ago, I deleted several records. None of the deleted records
shows up in a regular search of the catalog. However, all three show up
when I run a report on framework codes, they suddenly show up.

 When I go look by the bib. record number (999 $c), I see "NoTitle", and
when I click on the link to "NoTitle", Koha tells me that the record does
not exist. So the records show up only in the report(s), the evidence tells
me, not in a general catalog search.

 Is this a known bug? Is there a fix yet if it is a known bug?

 Many thanks, all.


___

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

Re: [Koha] Excluding fields from the OPAC search

[Katrin Fischer]

Hi,

unfortunately the problem is a bit more complicated. :(

I think since our switch from grs-1 to dom indexing, the kw index
includes the whole record, where before that switch it was 'everything
that is indexed'. So changing the configuration of individual
fields/indexes won't make a difference. See:

*Bug 15050*
 -
Nonpublic note searchable from OPAC

I am not sure if this is solved already with Elasticsearch.

Some things you could do to avoid issues is linking 952$e to a vendor
record using the id. I've been thinking it would be nice if we had a
value builder to do this for a while. If you add items from acquisition
it will also fill source of acquisition with the id, so that would make
things more consistent.

For internal notes I think a good rule of thumb would be to avoid using
personal names whenever possible. For some use cases internally agreed
on codes or the cardnumber might work. Having a separate feature for
adding notes that don't end up in the MARC records (and possible
exports, OAI etc.) might be a good idea anyway.

Hope this helps

Katrin

On 06.10.21 13:04, Owen Leonard wrote:

(e. g.
MARC 952$e the source of acquisition, or MARC 952$x the non-public note)

If these are indexed by default I think that should be considered a bug.

  -- Owen


___

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

Re: [Koha] stack number cannot be stored in Koha 21.05

[Katrin Fischer]

Hi Michael,

ah ok, that was a local change then?

Because it looks like it has always been tinyint:

https://git.koha-community.org/Koha-community/Koha/src/branch/master/installer/data/mysql/kohastructure.sql#L3015

https://git.koha-community.org/Koha-community/Koha/src/branch/18.11.x/installer/data/mysql/kohastructure.sql#L932

https://git.koha-community.org/Koha-community/Koha/src/branch/3.2.x/installer/data/mysql/kohastructure.sql#L994

varchar should work on database side, I am not aware of a code side
check, but there could be one. Anything helpful in the logs maybe?

Maybe worth checking if deleteditems was altered as well.

Katrin

|
|


On 06.10.21 21:39, Michael Kuhn wrote:

Hi Katrin

> 952$j is mapped to items.stack by default that has the datatype
> tinyint(1) in the database. A common problem I have encountered here
> is that it won't save when you try to store something non-numeric or
> outside the range of tinyint. Could that be the issue?

Yes, this would indeed be a problem... Thank you very much for the hint!

Our library was working with Koha 18.11 before - where it was possible
to store content like "m011577".

Looking into http://schema.koha-community.org/18_11/tables/items.html
shows that in this version the datatype was BIT(0) which seems to mean
mean "tinyint". In my Koha 21.05 demo installation I see it actually
is "tinyint".

However when asking the actual Koha 21.05 library database the
datatype is given as "varchar"!

So it seems like someone has unscrupulously changed the datatype of
this field in the past (a very bad idea). But then again - shouldn't
the database accept value "m011577" when the datatype is "varchar"? At
least in Koha 18.11 it seems to have worked.

I was able to successfuilly insert "011577". But not "m011577". Is
there maybe a script that checks if the values are of the correct
datatype when trying to store anything in the database? Maybe the guy
responsible for this problem also changed the datatype in such a script?

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] stack number cannot be stored in Koha 21.05

[Katrin Fischer]

Hi Michael,

952$j is mapped to items.stack by default that has the datatype
tinyint(1) in the database. A common problem I have encountered here is
that it won't save when you try to store something non-numeric or
outside the range of tinyint. Could that be the issue?

Katrin

On 06.10.21 20:47, Michael Kuhn wrote:

Hi

In our library we use Koha 21.05.02 on Debian GNU/Linux 11.

As we found out it not possible to store the content of field 952$j
(stack / shelving control number) in the Koha database. I have also
tested this on my demo installation with Koha 21.05.00 and on another
demo installation with Koha 21.05.04 - everywhere the same.

Can anyone please confirm this? If yes, I will open a bug report.

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] How to Update and Upgrade Koha

[Katrin Fischer]

Hi Hector,

I've confirmed your wiki account request. Happy editing! :)

Katrin

On 22.09.21 18:23, Hector Gonzalez Jaime wrote:

Hi, I'd like to, but I didn't have an account for the wiki, so I'm
waiting for it to be enabled.

On 9/20/21 4:47 AM, Jonathan Druart wrote:

Hi Hector, Well detailed instructions, it would help to have them on
the wiki page :)
Would you mind updating the existing section?
https://wiki.koha-community.org/wiki/Koha_on_Debian#Upgrade



___

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

Re: [Koha] Deleted Visible Records

[Katrin Fischer]

Hi Charles,

as Magnus was pointing out, I was looking for the SQL you are running to
see if the deleted records might have been included in the report.

Katrin

On 01.10.21 02:09, Charles Kelley wrote:

Hi, Katrin!

    In our latest exchange, on 1 Oct. 2021 at 8:00 [JST], I received
the following:

can you give an example for a report that still shows the deleted
records?

Katrin


    How's this sample from the report:

Bib. Record Number  Author                                      Main Title
biblionumber        author    title
11752               [Department of Legal Affairs(Seychelles)] Laws of
Seychelles:
11753               Ebata, Kensuke    The Gulf War / | Shin gunji ko :
16121     Jane's avionics 1985-86.

    When I enter this search in the catalog search, this is the result.

SN=11752

Title  Location
    No title  Action ^

    Many thanks for your response.

--

  気を付けて。 /ki wo tukete/ = Take care.

    -- Charles.
Charles Kelley, MLS
    PSC 704 Box 1029
    APO AP 96338

    Charles Kelley
Tsukimino 1-Chome 5-2
Tsukimino Gaadenia #210
    Yamato-shi, Kanagawa-ken
    〒242-0002 JAPAN

    +1-301-741-7122 [US cell]
    +81-80-4356-2178 [JPN cell]

mnogoja...@aol.com  [h]
cmkelley...@gmail.com  [p]

linkedin.com/in/cmkelleymls 
Meeting Your Information Needs. Virtually.

___

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

Re: [Koha] Case Sensitivity and Koha SQL Statements

[Katrin Fischer]

Hi Charles,

the runtime parameters are not part of SQL, but are Koha specific. They
are replaced with proper SQL before being run. If you can point us to
where the documentation or Koha behavior is wrong, we can fix that. Best
would be to file bugs on https://bugs.koha-community.org/ separately for
the manual and Koha itself.

Hope this helps,

Katrin

On 01.10.21 06:35, Charles Kelley wrote:

Hello, all!

 In my previous experience with SQL, case did not matter, but here it
does?

 I've been tearing out my hair -- and I'm bald -- for the last several
hours over a reported syntax error in a SQL statement I have been
composing. It turns out that it wasn't a syntax error, per se -- and I
studied for a doctorate in theoretical syntax -- rather a case sensitivity
error.

 The portion of the statement at hand is

... WHERE items.itype = <>

 It turns out "ITEMTYPES" ought to be written "itemtypes". Only through
trial and error did I learn that some identifiers are case sensitive. I
sought in the Koha wiki confirmation, refutation, and qualification that
CASE INDEED MATTERS IN IDENTIFIERS, but I could not find anything about
that.

 If case does indeed matter, please update the online and print SQL
manual(s) accordingly. I would not have spent two hours on this if the
correct word had been used in the error message. So please adjust the
wording, too.

 Many thanks.


___

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

Re: [Koha] Renewal notice email

[Katrin Fischer]

Hi,

by default Koha processes the message queue for sending out prepared
notices every 15 minutes. If you renew in the OPAC or in the staff
client and renewal notices are configured, that should apply to them as
well.

For a package installation you can see the default cron setting here:

https://git.koha-community.org/Koha-community/Koha/src/branch/master/debian/koha-common.cron.d

Did you mean auto renewal notices by chance? In that case the issue
would probably be a bit more complicated.

Hope this helps,

Katrin


On 29.09.21 04:33, Shafrizan Affendi wrote:

Anyone can help me out please 

On Tue, 28 Sep 2021, 6:52 am Shafrizan Affendi,  wrote:


I do have access to the server. Can you tell me which *.pl that i need to
set in cron.hourly? i tried
process_message_queue.pl in cron.hourly but not successful.



On Tue, 28 Sep 2021, 12:25 am Coehoorn, Joel,  wrote:


This is possible, but it's managed via the linux cron tables rather than
via the Koha user interface. You'll need someone who can ssh into the
server and is comfortable using a linux cli prompt to edit files.

Joel Coehoorn
Director of Information Technology
York College of Nebraska


On Mon, Sep 27, 2021 at 8:28 AM Shafrizan Affendi 
wrote:


Hi there. Im using Koha ver 21.05.

I would like to ask how can I generate renewal notice (email) and send
message que in every hour?

If im not mistaken, default koha will send the email in the midnight.

For example, i renew 1 book at 10 am. and will get the email notice at
midnight. I want to make koha send the notice email right after i renew
the
book so that i can receive the email at 11.01 am.

Can anyone help me? Thanks in advance
___

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] Framework Reports

[Katrin Fischer]

Hi Charles,

for the existing runtime parameters you can refer to the manual:

https://koha-community.org/manual//21.05/en/html/reports.html#report-from-sql

The one for frameworks is <>

Hope this helps,

Katrin

On 01.10.21 01:51, Charles Kelley wrote:

Hi, all!

 I frequently use the following SQL report, which I think I got from the
Koha wiki.

SELECT bib.biblionumber AS 'Bib. Record Number', bib.author AS 'Author',
bib.title AS 'Title'
FROM biblio bib
WHERE bib.frameworkcode = <>

 This serves us well, but as you might guess, one must know the
framework code in order for the report to function correctly. Moreover,
pressing "Run the report" without entering a framework leads to an
out-of-memory error. (An empty submission would be equivalent to the
default framework, but this seems not to be the case.)

 Is there a way to modify it so that one can select from a list, e.g.,

SELECT bib.biblionumber AS 'Bib. Record Number', bib.author AS 'Author',
bib.title AS 'Title'
FROM biblio bib
WHERE bib.frameworkcode = <>

 I have looked for the name of an equivalent to my FRAMEWORK_CODE list
in the Koha wiki but alas, for I have not found it.

 So, I duplicated the description in an ad-hoc authorized list, my
FRAMEWORK_CODE above, but that means updating the new ad-hoc list every
time we add or rid a framework. If there isn't already access to such a
list, I'll submit a feature request.

 Many thanks.


___

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

Re: [Koha] Fwd: New Koha minor versions released - security fixes included, UPGRADE!

[Katrin Fischer]

Hi Tom,

for your version you can read all database updates in updatedatabase.pl:

https://git.koha-community.org/Koha-community/Koha/src/branch/19.11.x/installer/data/mysql/updatedatabase.pl#L20705

There have only been changes as part of bug fixes - the bug numbers for
each change are referenced in the print lines, if you want to read up on
them.

Is there a specific thing you are worried about with a schema change?
The update process should always take care of those.

Hope this helps,

Katrin


On 27.09.21 18:01, Tom Burke wrote:

Can I seek a bit of reassurance, please? We have a server running several 
instances which is currently on 19.11.00.000. Obviously we want to upgrade 
this. We have tried doing a significant upgrade (to 20.11) on a test site, and 
have run into some issues which we are still investigating. We might therefore 
decide to meet the present security-driven upgrade requirement by simply going 
from 19.11.00 to 19.11.22 . Is it safe to assume that there is no schema change 
in such an upgrade?

Tom Burke




Begin forwarded message:

From: Jonathan Druart 
Subject: [Koha] New Koha minor versions released - security fixes included, 
UPGRADE!
Date: 27 September 2021 at 13:52:31 BST
To: koha , koha-devel 


Hello everybody,

I am announcing, on behalf of the whole Koha release team,
synchronised releases for the four release versions we are currently
supporting.

The release notes are available below:
21.05.04 - 
https://koha-community.org/koha-21-05-04-released-%e2%9a%a0-security-release/
20.11.10 - 
https://koha-community.org/koha-20-11-10-released-%e2%9a%a0-security-release/
20.05.16 - 
https://koha-community.org/koha-20-05-16-released-%e2%9a%a0-security-release/
19.11.22 - 
https://koha-community.org/koha-19-11-22-released-%e2%9a%a0-security-release/

As they contain security bug fixes we suggest you upgrade all the Koha
instances you are in charge of as soon as possible.

Let us know if you have any questions.

Regards,
Jonathan
___

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] Display of Damage Status (952 ‡4)

[Katrin Fischer]

Hi Charles,

I think what you describe, has been reported as

*Bug 18062*
 -
Damaged Status shows unavailable in results

I am not aware of a way to change this at the moment.

OpacHiddenItems would hide the damaged items from view and if there are
only damaged items, the record would be hidden as well.

Hope this helps,

Katrin

On 24.09.21 06:56, Charles Kelley wrote:

Hi, all!

 My library has a fairly significant number of books with yellowing
paper. The books are still usable -- we would withdraw it otherwise -- and
we plan to keep them in circulation until the paper turns brown or brittle.
We have marked such books with the appropriate damage value in 952 ‡4.

 Unfortunately, this has led to confusion among some staff and almost
all the patrons because Koha reports the books

 "Availability: No items available: Damaged (1)."

 We would like to show a different statement, something akin to:

 "Availability: every item available but 1 damaged."

 The latter would mean that all items are available for circulation but
one is damage. Of course, if all items are available but none is damaged,
the notice would read "Availability: every item available."

 Is this possible? Might the OPACHiddenItems list be a solution to this?

 Many thanks, everyone!


___

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

Re: [Koha] DBMS auto increment

[Katrin Fischer]

Hi Scott,

yes, the wiki page has all the current information and suggestions on
how to solve this issue. It also notes the DBMS versions where the
problem will be fixed.

The easiest way to resolve the problem is deleting the doubled up
entries from the old* and deleted* tables. Then you can implement the
fix and restart your DBMS server to reset the primary keys to the
correct values. This will prevent the creation of more doubled up IDs
between the tables.

Hope this helps,

Katrin

On 22.09.21 21:37, Scott Owen wrote:

Hi All,

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


Is this still the best procedure when getting the following error ?




You should not ignore this warning.

The problem is that InnoDB does not keep auto_increment across SQL server
restarts (it is only set in memory). So on server startup the
auto_increment values are set to max(table.id)+1.

To know how to avoid this problem see the related wiki page: DBMS auto
increment fix
Problems foundCheckouts

The following ids exist in both tables issues and old_issues:

4782, 4781




Any sql to clean things up in the two tables ?
___

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 ugrade from 3.22.21 to 19.05.17

[Katrin Fischer]

Hi George,

in newer versions you can no longer log into Koha with the database
user. You have to create a staff user separately with the required
permissions. If you don't have one yet, there is a script to create one.
This blog post might be helpful:

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

Katrin

On 22.10.21 12:44, George Mikuchadze wrote:

I've upgraded empty koha(on ubuntu 18.04) from 3.22.21 to 19.05.17 using
only the tarball file(without sudo apt-get install koha-common).
Everything was nice - until I tried to login intranet site with a super
admin account after a successful web installer procedure of upgrading the
koha tables:  "Error: Invalid username or password". I checked the
koha-conf.xml file and the username and password were unchanged! What
happened with koha - did the Memcached server change the settings?

George Mikuchadze
National Scientific Library of Georgia
___

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] Default values

[Katrin Fischer]

Hi Carlo,

you can do so in the bibliographic MARC frameworks in the administration
module. You can use the default value setting for the @ subfield to add
a default for the whole field, but you can't define a default just for a
single position of a control field.

Hope this helps

Katrin

On 02.12.21 08:58, Carlo Dumontet wrote:

Can anyone please point me in the right direction.

I'd like to add default values in a Bibliographic Framework for: Leader,
007, 008.

Is it possible?

Many thanks!



___

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] Dynamic XSLT labels based on framework "Text for OPAC"?

[Katrin Fischer]

Hi Tasha,

at the moment it's not possible to use the framework descriptions in the
XSLT files. The descriptions of the fields are part of the XSLT file. I
think with the current mechanisms it would not be trivial to add the
database descriptions.

Unfortunately, the framework code doesn't seem to be available either as
a bug for this is still open:

*Bug 11523*
 - Make
framework code available to stylesheets to allow for more customized display

When you make changes to the files, you usually have to restart Plack
for your instance to make the change visible immediately.

Hope this helps

Katrin

On 01.12.21 00:34, Bales (US), Tasha R wrote:

Good afternoon,

I'd like to check my understanding on MARC frameworks.  In my frameworks, I've changed the "Text for 
OPAC" of various fields, and they display as desired in the "MARC view", but not in the 
"Normal view".  I am sure this is occurring because these are local 9xx fields; I had to customize 
the Detail XSLT to get them to show up at all in the OPAC.

My question is... how can I get the XSLT to use the text that is defined in the Framework 
for this record?  For instance, I have several frameworks that contain a 926 field, but 
each framework has a different "Text for OPAC".  Is it possible to add a test 
below?  Just now I tried deleting the label text entirely to see what would happen, but 
Ctrl+f5 and/or trying in a new browser doesn't reflect my results (a different mystery I 
am sometimes flummoxed by).  As always, if this is too complex a question, even a pointer 
would help.  Thanks in advance.

Here is my XSLT (sometimes, "Original Release Date" is correct-other times, "Date of 
Basic" is needed-it all depends on the framework):


 Original 
Release Date: 
 
 
 
   
 
 a
 


 
 ; 

 
 



Tasha Bales
Enterprise Services
http://isesi.web.boeing.com/

___

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] Printing labels in other languages

[Katrin Fischer]

Hi Rizwan,

can you explain your problem a bit more? Did you try to print with other
scripts and it didn't work? I think from the GUI it should work just the
same.

Katrin

On 01.12.21 06:19, Rizwan Majeed wrote:

Dear All

Printing labels in Koha using the English language is very easy. Because
the English language is the default language of Koha. Would anybody guide
me to print labels in other languages like  Arabic or Urdu?

Regards!

Rizwan
___

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 sets due date to current date when checking out

[Katrin Fischer]

Hi Michael,

there are some mechanisms in Koha that can lead to a shortened due date
- maybe they could be a starting point for your investigation?

* The patron is about to expire (system preference ReturnBeforeExpiry)
* When there are holds on the item, the due date can be shortened
(system preference decreaseLoanHighHolds* and 'Decreased loan period for
high holds (day)' in circulation rules)
* Double/triple check the circulation rules. Was a hard due date set? Is
there any other rule with "0" that could be applied instead?

Hope this helps

Katrin


On 06.12.21 12:14, Michael Kuhn wrote:

Hi

Our library is working with Debian GNU/Linux 10 and Koha 21.05.05.

Since the update the check out process does no more respect the
circulation conditons regarding the due date (the loan period is 1643
days) but instead sets the due date to the current date!

So If I check out a book today the due date is today.

In logfile "intranet-error.log" the following is reported:

[Mon Dec 06 12:04:52.123486 2021] [cgi:error] [pid 21882] [client
134.130.93.46:38068] AH01215: Argument "" isn't numeric in addition
(+) at /usr/lib/x86_64-linux-gnu/perl5/5.28/DateTime/Duration.pm line
70.: /usr/share/koha/intranet/cgi-bin/circ/circulation.pl, referer:
http://79.143.185.37:18080/cgi-bin/koha/circ/circulation.pl
[Mon Dec 06 12:04:52.196908 2021] [cgi:error] [pid 21882] [client
134.130.93.46:38068] AH01215: Argument "" isn't numeric in addition
(+) at /usr/lib/x86_64-linux-gnu/perl5/5.28/DateTime/Duration.pm line
70.: /usr/share/koha/intranet/cgi-bin/circ/circulation.pl, referer:
http://79.143.185.37:18080/cgi-bin/koha/circ/circulation.pl

There are no errors in Koha menu "About Koha > System information".

Is this a bug that I should report?

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] Automatic setting of branch library on login

[Katrin Fischer]

Hi,

I haven't seen this behavior in Koha or a bug reported for it yet.

What is your exact 21.05 version? Are you using Independentbranches?

Could a local customization (like IntranetUserJS) cause the issue?

Katrin

On 02.12.21 11:40, Admire Mutsikiwa wrote:

  Good day. We are running Koha  21.05 in a multi-branch setup. I have noted
that our Koha system is longer setting the correct home branch library a
staff member belongs to. Instead, staff members have to use the Set Library
option, which becomes a challenge if you have a low  timeout as staff
members have to set the Library repeatedly.

Could there be a System preference I could have set wrongly.




Kind Regards,


___

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

Re: [Koha] Help about GDPR policy settings

[Katrin Fischer]

Hi,

I think it doesn't show in the staff interface, but you could create a
report to check for users that haven't accepted. You'd have to look for
borrowernumbers not present in the patron_consent table.

Hope that helps,

Katrin

On 02.12.21 13:27, Tadas G wrote:

Hello
I using Koha 21.05

I setting up GDPR consents with GDPR_Policy. Everything works fine. but i
do not find intra staff page who agreed and who has not yet agreed terms.
How administrator can see if that person is agreeing with policy?

Thanks for the help
___

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] Authorized values for category COUNTRY

[Katrin Fischer]

Hi Igor,

you can tie authorised values to MARC subfields and they will provide a
pull down to make it possible to pick by description, but store the
code. - Is that what you had in mind?

Hope this helps

Katrin

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

Hello Koha Community!
Question about Authorized values for category COUNTRY.
Do they fill out all the codes themselves?
I see exports. And how to import?

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] upgrading from 21.5 to 21.11

[Katrin Fischer]

Hi Victor,

what do you mean by the installation screen? Koha will bring up the web
installer during initial installation, but also if there are database
updates that need to be run. Have you tried logging into the web
installer to see where it takes you?

Hope this helps

Katrin

On 13.12.21 14:49, Victor Barroso Oliveira wrote:

Hi
I have Koha on a server with multiple instances.
After upgrading from 21.5 to 21.11 one of the instances is showing the
initial Koha installation screen.
How to fix this error?
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] Changing status of item

[Katrin Fischer]

Hi Jo,

are you using the standard status or have you created your own? A common
mistake is that the authorised value codes for LOST and DAMAGED need to
be numerical, as the columns in the item table expect a numerical value
and the status won't be saved otherwise.

Hope this helps,

Katrin

On 15.12.21 21:54, TS Library wrote:

Hi everyone

When I change the lost or damaged status of an item the changes are not
saved. Can anyone suggest why this is?

*Jo Atkinson*

*Senior Librarian*

Geoffrey Hodson Library

Theosophical Society in New Zealand Inc

18 Belvedere Street, Epsom, Auckland



*e:* *libr...@theosophy.org.nz *
*p: 09 523 1797*
*m: 021 250 1675*
*w:* *theosophy.nz *
___

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] Upload files in cataloguing

[Katrin Fischer]

Hi Beda,

which version of Koha are you using? There has been a bug with the
upload feature in the newest versions:

*Bug 29747*
 -
Cataloguing upload plugin broken

Could this be the issue?

Katrin

On 30.12.21 14:25, Beda Szukics wrote:

Hi all

I would like to upload a file and make it visible through the 856$u
field. I followed the instructions on
http://kohageek.blogspot.com/2015/12/attaching-files-to-catalog-records.html

The plugin appears and I can upload the file. But when I select the
Choose (or Auswählen) buttom nothing happens. The same with the
Download and the "Löschen" buttom. If I click on koha_upload I'm able
to download (and maybe delete - I haven't checked) the file.

What is wrong?

Thank you

Beda

___

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] New Record page is giving a 500 error

[Katrin Fischer]

Hi Sterling,

I am not sure what is going wrong there, but can you tell us the exact
version you updated to? It will be listed at the top of the About Koha page.

Katrin

On 22.12.21 00:55, Sterling Jenson wrote:

Greetings all,

When I try to add a new record, I get a 500 Server Error when I try to
catalogue a new title through either "Advance Editor" or "New Record"
options; however not through "New from Z390.50/SRU."  I was able to use
these editors before and, so point an update did not go as smoothly as I
had thought.

Looking through the logs, I get this error:

[[cgi:error] [pid 603367] AH01215: {UNKNOWN}: DBI Exception: DBD::mysql::db
selectall_arrayref failed: You have an error in your SQL syntax; check the
manual that corresponds to your MySQL server version for the right syntax
to use near ',servername' at line 3  at
/usr/share/perl5/DBIx/Class/Schema.pm line 1118.:
/usr/share/koha/intranet/cgi-bin/cataloguing/editor.pl, referer:
~/cgi-bin/koha/cataloguing/addbooks.pl

Thoughts on how I might fix problem?

Best,

Sterling
___

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 with "Additional contents (HTML customizations)"

[Katrin Fischer]

Hi Michael,

I can't replicate this behavior in my dev environment. Could you check
if there are any remaining entries for ABC in your additional_contents
table?

select * from additional_contents;

Katrin

On 30.12.21 13:25, Michael Kuhn wrote:

Hi

We are working on a completely new host with Debian GNU/Linux 11 and
Koha 21.11.00. I have also tested this on my demo installation with
Koha 21.11.00 - same problem.

We found the following issue with menu "Tools > Additional contents
(HTML customizations)".

When adding a new entry (e. g. for display location
"OpacMainUserBlock") we are able to add e. g. text "ABC" and then
save. The OPAC will show "ABC" as expected". It is also possible to
delete this entry in the menu.

But the OPAC will still show the original text "ABC", even after
emptying the browser cache (Ctrl+F5) or restarting memcached, apache2
and koha-common.

But even more, if we add another entry e. g. with text "XYZ" the OPAC
will now show "ABC" and then "XYZ" on another line. After deleting the
entry in the menu the OPAC will still show both texts, "ABC" and "XYZ".

Can anyone please confirm this issue?

But especially: How can we get rid of the unwanted old texts?

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] update error

[Katrin Fischer]

Hi Ana,


better to copy the error into the email as attachments will be removed
on the mailing list:


Upgrade to 21.05.00.016 [14:16:28]: Bug 24387 - Rename opac_news with
additional_contents

ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: FUNCTION
koha.biblioteca.REGEXP_REPLACE does not exist at
/usr/share/koha/lib/C4/Installer.pm line 738


Are you using MySQL or MariaDB and which is the version?



Katrin


On 30.12.21 17:36, anabela semedo wrote:

hello ever one

i have a problem here, trying to update koha to the latest version and
i have this error here that i am not able to resolve. can anybody help
me? thankyou. Ana Bela Semedo


___

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

Re: [Koha] OpacNavRight issue

[Katrin Fischer]

Hi,

I have filed a bug because we have seen different reports on the mailing
list so far concerning removing content from additional contents:

*Bug 29778*
 -
Deleted additional_contents remain visible

Could you check if the content you are trying to remove shows in the
additional_contents table still?

select * from additional_contents;

What is your exact Koha version?

Katrin

On 22.12.21 09:12, Mif wrote:

Thank you, it moved again under HTML Customizations, but i cannot find it 
anywhere.
I did flush memcached and restarted all other services and it still shows in 
OpacNavRight.

Sent with [ProtonMail](https://protonmail.com/) Secure Email.

‐‐‐ Original Message ‐‐‐
On Tuesday, December 21st, 2021 at 15:33, Mif  wrote:


I have Flushed the Cache, loaded in incognito and also on another device, the 
old content is still there.

Sent with [ProtonMail](https://protonmail.com/) Secure Email.

‐‐‐ Original Message ‐‐‐
On Tuesday, December 21st, 2021 at 15:18, Mif  wrote:


Hi, I have just updated to 21.11 and for some reason the OpacNavRight old 
content cannot be deleted.
I deleted every single item in custom html however the old content of 
OpacNavRight is still there.

Where can one manual delete the OpacNavRight content?

Sent with [ProtonMail](https://protonmail.com/) Secure Email.

___

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] search results inconsistent with items.location

[Katrin Fischer]

Hi Guiseppe,

that sounds like your search index (Zebra or Elasticsearch) might be out
of date. When resaving the record it's reindexed and that would correct
the display. Could you try and run a full reindex and see if that fixes
your problem?

Hope this helps,

Katrin

On 24.12.21 07:04, Giuseppe Angilella wrote:

Hi,

(using Koha 21.11.00.000 on Ubuntu 18.04)

from the administrator's interface, when a catalogue search yields
several results, the listed "location" is sometimes not up to date.

Checking a given bibliorecord, I can see that the "location" for the
item in question is updated. I have to "edit" the item in question,
confirm the location (which was actually correct), save it again, and
then the search results gives the correct location for that item.

It seems that "location" (items.location) is saved in some other table
(other than "items"), which is where the Search looks for. At some
point of system upgrading, the two tables may have lost
synchronization, which has to be restored manually for some items.

Which are the two tables I should look at in the database (one is
"items"), in order to identify any extant inconsistency?

Many thanks!

Giuseppe.

___

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] Locally stored cover images randomly fail to display in full details page

[Katrin Fischer]

Hi Martin,

did you activate any other cover services besides the local covers and
did you replicate these settings on the sandbox?

It might be worth filing a bug on https://bugs.koha-community.org for this.

Hope this helps

Katrin


On 21.12.21 19:00, martinbmor...@gmail.com wrote:

Hello



I recently upgraded from 21.05 to 21.11 at which point I noticed that some
locally stored cover images would fail to display on the full details page
for a biblio.  The cover does always display under the Picture tab on the
details page.



The images display normally in the listing of multiple results, and images
downloaded using Coce display properly both in results listings and in the
full details page for the biblio.



*   Here is an example of a biblio with a properly displayed local cover
image:
https://katalogo.biblioteko.ca/cgi-bin/koha/opac-detail.pl?biblionumber=164
*   .and here is one that will not display the image:
https://katalogo.biblioteko.ca/cgi-bin/koha/opac-detail.pl?biblionumber=2189
*   Here is a multiple results listing page showing a cover for the
title above whose cover fails to display in the full biblio:
https://katalogo.biblioteko.ca/cgi-bin/koha/opac-search.pl?q=su:%22Holmes%2C
%20Sherlock%22



I have checked the logs, which give no clues at all. I have also tested by
removing the custom CSS and JS I have in OpacUserCSS and OpacUserJS and
restarting Apache - this does not help.  Recreating the biblios on the PTFS
sandbox doesn't replicate the issue - so it does seem to be something to do
with my set up.



Hope this is clear - any help would be gratefully received!



Thanks



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] broken auto-generated barcode

[Katrin Fischer]

Hi Bruce,

as 21.11.01 has just been released, the bug fix will most likely be
available in the next release: 21.11.02.

You could try to make the changes in the attached patch file on the bug
report manually in your system, but it might be a little tricky.

Katrin


On 28.12.21 20:50, Bruce Yelen wrote:

Hi all,



Any idea of when the solution for bug 29689 (broken auto-generated barcode)
will be included in a fix (Currently running on 21.11.01.00, still broken).
I see it's passed QA.  If it will be a while, is there any work-around or
minor patch I could apply?



Thanks, and continued best wishes during this holiday season!



*   Bruce

___

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] Linking via 830$w

[Katrin Fischer]

Hi Thomas,

is this an 830 from a traced series entry?

https://git.koha-community.org/Koha-community/Koha/src/commit/a5a3a330cfc7c7d6c35db13326745dabf8fe0df3/koha-tmpl/intranet-tmpl/prog/en/xslt/MARC21slimUtils.xsl#L506

The 830 here is used for a traced series entry in combination with a 490
ind. 1 = 1.

In this case linking horizontally to the other parts of the series
instead of linking to the set record was chosen by design, assuming it
would make more sense to the user. Especially since untraced series
don't have a set record and the link can only link to the parts.

But it could be changed locally of course as you said by just changing
the index. If you don't want to change the XSLT file this can also be
done quite easily with jQuery in OpacUserJs:

$('span.series a').attr('href', function(_,v){ return
v.replace(/rcn/g,'Control-number')});

Hope this helps

Katrin


On 21.12.21 16:07, Thomas Klausner wrote:

Hi!

We have encountered an interesting behaviour and are not sure if it's a
bug in Koha, in our data, or something else:

We have a bibliographic record A where 830$w points to another record B
(to the other records' 001 value, to be precise):

A: 830$w = 12345
B: 001 = 12345

When Koha renders record A, it produces a link to B, but with a bad param:
http://intranet/cgi-bin/koha/catalogue/search.pl?q=rcn:12345

Changing the param from 'rcn' to 'control-number' finds the correct record:
http://intranet/cgi-bin/koha/catalogue/search.pl?q=control-number:12345

We're using ElasticSearch with default mappings. Looking into those, I
see that there are defintions for record-control-number (rcn) and
control-number.

control-number points to 001, and rcn to various 7/8nn$w fields. Now it
makes sense that the search for rcn did not find the value stored in
record B.001, and why chaning the search to control-number finds the
record.

Which leads to my question;

* Should we add 001 to the fields mapped to record-control-number?

* Should we use a different field than 830w$?
   We are quite sure that we shouldn't, as the DNB is also using 830$w:
   https://portal.dnb.de/opac/simpleSearch?query=9783847703389
   "Beziehungen: Die Andere Bibliothek ; Bd. 338", linking to
   (DE-101)015935620:
   
https://portal.dnb.de/opac/opacPresentation?cqlMode=true=true=0=%229783847703389%22%26any=idn%3D015935620

* Should we change the template to produce a link using a different
   param? Feels wrong, becuase it does make sense to link to 'rcn' and
   not to 'control-number'. Also we don't want to mess with the core Koha
   templates...

Any ideas / pointers?

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] Issue with "Additional contents (HTML customizations)"

[Katrin Fischer]

Hi Michael,

I have tried adding OpacNavRight and OpacMainUserBlock entries on your
demo installation, but deleting the entries always makes the content go
away.

Could you provide a step by step guide so we can see where the
difference is?

I believe it would be save to delete these entries.

A happy new year to you too!

Katrin

On 01.01.22 14:38, Michael Kuhn wrote:

Hi Katrin

You wrote:

> I can't replicate this behavior in my dev environment. Could you check
> if there are any remaining entries for ABC in your additional_contents
> table?
>
> select * from additional_contents;

Yes, there are remaining entries, as expected (since I restarted
memcached, apache2 and koha-common).

You can test this issue on my demo installation with Koha 21.11.00
(user: demo / password: demo): https://koha.adminkuhn.ch:8443/

Is it safe to just delete these unwanted entries manually via SQL?

Best wishes & a Happy New Year: Michael

___

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

Re: [Koha] Linking via 830$w

[Katrin Fischer]

Hi Thomas,

when you have a 8xx for a traced series, you usually have a 490 with
first indicator = 1 as well.

See:
https://www.loc.gov/marc/bibliographic/bd490.html
https://www.loc.gov/marc/bibliographic/bd830.html

The 490 is also present in your sample record from DNB.

Hope this helps,

Katrin


Not sure what you mean by "490 ind". But the relationship is definitly
not 1:1, but n:1 (i.e. we're linking from a child to a parent)


In this case linking horizontally to the other parts of the series
instead of linking to the set record was chosen by design, assuming it
would make more sense to the user. Especially since untraced series
don't have a set record and the link can only link to the parts.

I think we are using this 830$w to link not horizontally, but
vertically, from a book up to a sort of series ("Reihe"). We're not 100%
sure this is correct, so we copied what DNB is doing (see again these
links):

https://portal.dnb.de/opac/simpleSearch?query=9783847703389
linking via 830$w to
https://portal.dnb.de/opac/opacPresentation?cqlMode=true=true=0=%229783847703389%22%26any=idn%3D015935620



But it could be changed locally of course as you said by just changing
the index. If you don't want to change the XSLT file this can also be
done quite easily with jQuery in OpacUserJs:

ok, that's another way to correct the param name.

We were just not sure if using 'rcn' instead of 'control-number' was a
bug in Koha or our MARC. It seems it is neither, so we'll use a
workaround to "correct" the param name.

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] Barcodes are not generating automatically anymore after upgrade to 21.11

[Katrin Fischer]

Hi Isabel,

yes, this is a known bug expected to be fixed with the 21.11.02 release:

*Bug 29689*
 -
Update to 21.11 broken auto-generated barcode in 0001 option

Hope this helps,

Katrin

On 03.01.22 23:05, Isabel Pineda wrote:

Hi.

Today I updated our Koha installation to version 21.11, and now in the Cataloguing 
the automatical creation of the barcode is not working anymore. We use the barcode 
type yymm0001

Is this a bug? Or has something gone wrong with the upgrade?

Thank you very much
Isabel Pineda
___

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] Upload files in cataloguing

[Katrin Fischer]

Hi Beda,

you could manually make the changes from the patch on your system, but
if you have found a workaround it's probably better to update to the
next bugfix release.

Best wishes,

Katrin

On 01.01.22 19:39, Beda Szukics wrote:

Hi Katrin

It seems so. But I don't know how to handle the description in the bug
report, especialy item 9

I have found a workaround: Go on the link koha_upload -> select
"Öffentlich" -> copy the link to 856$u

Greetings

Beda



Am 01.01.2022 um 12:55 schrieb Katrin Fischer:

Hi Beda,

which version of Koha are you using? There has been a bug with the
upload feature in the newest versions:

*Bug 29747*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29747> -
Cataloguing upload plugin broken

Could this be the issue?

Katrin

On 30.12.21 14:25, Beda Szukics wrote:

Hi all

I would like to upload a file and make it visible through the 856$u
field. I followed the instructions on
http://kohageek.blogspot.com/2015/12/attaching-files-to-catalog-records.html


The plugin appears and I can upload the file. But when I select the
Choose (or Auswählen) buttom nothing happens. The same with the
Download and the "Löschen" buttom. If I click on koha_upload I'm able
to download (and maybe delete - I haven't checked) the file.

What is wrong?

Thank you

Beda

___

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] Issue with "Additional contents (HTML customizations)"

[Katrin Fischer]

Hi Michael,

thx for pointing this out! I later realized I had only looked at the 
English templates and that is where the issue was. I have found the 
steps to make it happen on master and filed a bug:


*Bug 29778* 
 - 
Deleting additional_contents is incomplete and leaves entries for 
additional languages


Katrin

On 01.01.22 19:48, Michael Kuhn wrote:

Hi Katrin

You wrote:

> I have tried adding OpacNavRight and OpacMainUserBlock entries on your
> demo installation, but deleting the entries always makes the content
> go away.

No, it doesn't - it seems like your last entry in "OpacMainUserBlock" 
was "test". Is that correct? It still can be seen at 
https://koha.adminkuhn.ch/ - together with my own test entry from 
earlier this day (but only until the next reset tomorrow at 5 AM):


Test Kuhn 1.1.2022
test

It is just below the "news" entry when choosing language "Deutsch 
Deutschland (de_DE)".


The menu entry in "Additional contents (HTML customizations)" is gone, 
but as said the original entry in the OPAC is still 
there.https://koha.adminkuhn.ch/


Of course it is also still in the database (along with more stuff that 
shouldn't be there anymore! Since the menu entries are gone the table 
shouldn't contain any entries of category "html_customizations", as 
far as I see it):


| 4 | html_customizations | OpacMainUserBlock_3 | 
OpacMainUserBlock | NULL   | Test Kuhn 1.1.2022    | Test Kuhn 
1.1.2022



  | de-DE   | 
2022-01-01   | 2022-01-01 14:41:45 | NULL   | NULL |     1 |
| 7 | html_customizations | OpacNavRight_6  | OpacNavRight | 
NULL   | kkk   | kkk



  | de-CH   | 
2022-01-01   | 2022-01-01 16:25:41 | NULL   | NULL |     1 |
| 8 | html_customizations | OpacNavRight_6  | OpacNavRight | 
NULL   | iii   | iii



  | it-IT   | 
2022-01-01   | 2022-01-01 16:25:41 | NULL   | NULL |     1 |
|    10 | html_customizations | OpacNavRight_9  | 
OpacMainUserBlock | NULL   | test  | test



  | de-DE   | 
2022-01-01   | 2022-01-01 16:28:36 | NULL   | NULL |     1 |


As I see now, there is more weirs stuff going on: "test" (which you 
included for language "it-IT") can still be seen when choosing the 
main language (de-DE) while Italian is not even one of the possible 
choices!


I believe there is some problem with the "standard" and the different 
languages of menu "Additional contents (HTML customizations)".


> Could you provide a step by step guide so we can see where the
> difference is?
>
> I believe it would be save to delete these entries.

Thanks, for now I'll do that! But of course this isn't really the 
solution.


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] upgrading from 21.5 to 21.11

[Katrin Fischer]

Hi Victor,

you've run into *Bug 29631*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29631> -
21.06.000.12 may fail. If you follow the discussion on the bug,
especially comment#18 that might help you solve the issue. The fix will
be released with 21.11.01.

Hope this helps,

Katrin

On 18.12.21 01:19, Victor Barroso Oliveira wrote:

I have several instances on a server, but only one is not updating the
database, note the error it presents.
koha-upgrade-schema library
Upgrading database schema for library
Upgrade to 21.06.00.012  [21:15:15]: Bug 15067 - Add missing languages
ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate
entry 'AL-                                 region' for key 'uniq_lang'
at /usr/share/koha/lib/C4/Installer.pm line 738

<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Livre de vírus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>.



Em sex., 17 de dez. de 2021 às 19:00, Katrin Fischer
 escreveu:

Hi Victor,

what do you mean by the installation screen? Koha will bring up
the web
installer during initial installation, but also if there are database
updates that need to be run. Have you tried logging into the web
installer to see where it takes you?

Hope this helps

Katrin

On 13.12.21 14:49, Victor Barroso Oliveira wrote:
> Hi
> I have Koha on a server with multiple instances.
> After upgrading from 21.5 to 21.11 one of the instances is
showing the
> initial Koha installation screen.
> How to fix this error?
> 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


___

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

Re: [Koha] Circulation Restriction

[Katrin Fischer]

Hi,

this is currently not possible, circulation rules work by item types only.

Hope that  helps,

Katrin

On 21.11.21 02:04, Ma. Victoria H. Silva-Manuel wrote:

Hi.
Can we set the circulation restrictions by collection code, not by item
type?
___

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] No items expected when receiving shipment

[Katrin Fischer]

Hi Giuseppe,

I see the same on master (current state of development), so I've filed a
bug report:

*Bug 29581*
 -
"Items expected" on receive shipment page is always empty

I think it's likely to just be a display issue that should not affect
functionality.

Hope this helps,

Katrin


On 15.11.21 09:50, Giuseppe Angilella wrote:

Hi,

(using Koha 21.05.05.003 in Ubuntu 18.04)

after closing a basket under Acquisition, I try to "receive a new
shipment", but the "Items expected" column has 0 (zero) for each order.

This did not happen a few releases ago ...

Any suggestion?

Many thanks!

Giuseppe.

___

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] Can't Search Catalog in a Branch Library

[Katrin Fischer]

Hi Ketut,

your setup sounds about right.

Is indexing working in general? Can newly catalogued records be found?

Also, what did you use for the branchcode in your configuration?

Did you change the items manually or did you batch change them/use SQL?

Hope this helps,

Katrin

On 24.11.21 07:52, Ketut Gunawan wrote:

I have two branch libraries in one Koha installation. But I can only search the 
catalogs with a list of catalog results in one library, let's say Library A. The 
result of catalog searching in the other library (Library B) is 'No results 
found!".  I have input library name and code in Basic Parameter, and library 
code in homebranch and holding branch (in library Items). What are missing in my 
installation? Any helps would be appreciated.
___

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] MARC field 008, subfield 33 set to "no fiction" by default

[Katrin Fischer]

Hi Isabel,

you can set the default value for the '@' subfield used for
controlfields in the framework, but it will have to be for the whole
008, you can't just set it for a single position.

Hope that helps,

Katrin

On 26.11.21 15:43, Isabel Pineda wrote:

Hi.

When I am cataloguing a new book record, the subfield 33 (literary form) of the 
008 field is automatically set to 0 (no fiction). I would like to set the 
default to | (not used). I have got a custom framework that I am using for 
cataloguing, but I cannot find out how to customize the settings of the 008 
field, as there are no subfields that can be customized. I can see that the 
field is using a plugin, marc21_field_008.pl. Do I have to change the setting 
in the plugin? If so, how do I do that?

Thank you very much.
Isabel
___

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] Opening bids for KohaCon22

[Katrin Fischer]

Hello dear Koha community,

another year is coming to an end. It's time to turn our attention to the
new year that's coming up, full of possibilities!

If you or your organization would like to organize KohaCon22, please
enter all relevant information on this wiki page:
https://wiki.koha-community.org/wiki/KohaCon22_Proposals (if you do not
already have an account to edit the wiki, you can request one, it is
usually pretty fast to get access).

The community has agreed that KohaCon conferences must be either hybrid
with an in-person conference streamed online, or entirely online. Apart
from keeping the community members safe, this will also allow for
greater accessibility, so that everyone can attend and learn from each
other no matter their availability, ability to travel, or budget.

Know that the community stands behind anyone who volunteers to organize
and that help is always available if you're unsure how to proceed.

Call for proposals will end on January 8, 2022 at 23:59 UTC. If there is
more than one proposal, we will organize a vote, which will be announced
on this mailing list.

Best regards,


Katrin
___

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

Re: [Koha] Web install issue with 21.05.05.000

[Katrin Fischer]

Hi Bruce,

please see *Bug 29378*
 for a
temporary workaround. Packages will be fixed as soon as possible.

Katrin

On 31.10.21 00:05, Bruce Yelen wrote:

I just upgraded my test system from 21.05.04.003 to 21.05.05.000 using the
Debian package.  After the web installer updates the database, it returns
the message "Everything went okay.  Update done.  However when clicking
"Continue to log in to Koha", you're immediate taken to the "Web installer >
Check Perl dependencies" screen again, and the entire process repeats.  If I
exit the web browser, and go back in, I'm taken to the "Welcome to the Koha
21.05 web installer" screen again, asking for the library.koha user and
master password.  So, while obviously a bug, what would be the proper action
at this point?  Should I run the script "koha-upgrade-schema" to try and set
things to normal?



And again, an object lesson to always try out upgrades in test prior to
touching your live production system!



Thanks!



Bruce

___

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] Records visible to those who login

[Katrin Fischer]

Hi,

OpacHiddenItems hides the items and records if all items are hidden.
This worked independent from if you are logged in or not. Then
OpacHiddenItemsExceptions can make items visible for certain patron
categories again, which is an information only available if you are
logged in.

Hope that explains,

Katrin

On 27.10.21 21:57, Cab Vinton wrote:

I looked at those settings but didn't see where logged in status could be
used as the controlling factor.

What am I missing?

Cab Vinton
Plaistow Public Library
Plaistow NH


On Wed, Oct 27, 2021, 11:56 Tomas Cohen Arazi  wrote:


You can do it!

You could use a combination of OpacHiddenItems and
OpacHiddenItemsExceptions.



___

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] MARC modification templates w/ indicators?

[Katrin Fischer]

Hi Tasha,

I believe at the moment it's not possible to use indicators in the MARC
modification tool:

*Bug 21860*
 - Marc
modification templates cannot check or change indicators

Katrin

On 23.10.21 01:41, Bales (US), Tasha R wrote:

Do MARC modification templates support changes based on, or to, MARC indicators?

For instance, I'd like to change all instances of 856 _8 to 956 _ _.  However, 
I don't see a clear way to specify or insert indicators w/ or w/o RegEx.  Are 
the indicators considered part of the field data?

I could do this with MarcEdit, but I'd rather just do it here.  Is MarcEdit the 
only option?

Thanks!!


Tasha Bales
Enterprise Services
http://isesi.web.boeing.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] Disabling holds

[Katrin Fischer]

Hi,

it's even easier using the RequestOnOpac system preference :)

Katrin

On 09.11.21 20:57, Alvaro Cornejo wrote:

Hi MIchael

Don't know from configuration side but it might be possible to use JQuery
to hide hold buttons/menus.

Regards,

Alvaro

||
  Stay safe / Cuídate/  Reste sécurisé
*7* Switch off as you go / Apaga lo que no usas /  Débranchez au fur et à
mesure.
  *q *Recycle always / Recicla siempre / Recyclez toujours
  P Print only if absolutely necessary / Imprime solo si es necesario /
Imprimez seulement si nécessaire


Le mar. 9 nov. 2021 à 07:58, Michael Kuhn  a écrit :


Hi

In our library we use Koha 21.05.01 - we want to disable holds completely.

Koha system preference "maxreserves" ist set to 0.

In Koha menu "Administration > Circulation and fines rules" there is
only one rule, with the following settings:

* Holds allowed (total): 0
* Holds allowed (daily): 0
* Holds per record (count): 0
* On shelf holds allowed: If all unavailable (other possibilities are:
Yes / If any unavailable)
* OPAC item level holds: Don't allow

With all these settings it is still possible to go to a record with an
item attached to it and then place a hold, both in staff client and
OPAC! There is no warning or error when trying to do so.

How is it possible to disable holds completely in Koha?

Best wishes: Michael
--
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
___

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] Disabling holds

[Katrin Fischer]

... only a little, as we will be renaming it in 21.11:

*Bug 29180*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29180> -
System preference RequestOnOpac should be renamed


On 09.11.21 21:43, Tomas Cohen Arazi wrote:

No 'reserve' or 'hold' mentioned in the syspref name. We are so mean.

El mar, 9 nov 2021 a las 17:33, Katrin Fischer
() escribió:

Hi,

it's even easier using the RequestOnOpac system preference :)

Katrin

On 09.11.21 20:57, Alvaro Cornejo wrote:
> Hi MIchael
>
> Don't know from configuration side but it might be possible to
use JQuery
> to hide hold buttons/menus.
>
> Regards,
>
> Alvaro
>
>

||
>   Stay safe / Cuídate/  Reste sécurisé
> *7* Switch off as you go / Apaga lo que no usas / Débranchez au
fur et à
> mesure.
>   *q *Recycle always / Recicla siempre / Recyclez toujours
>   P Print only if absolutely necessary / Imprime solo si es
necesario /
> Imprimez seulement si nécessaire
>
>
> Le mar. 9 nov. 2021 à 07:58, Michael Kuhn  a
écrit :
>
>> Hi
>>
>> In our library we use Koha 21.05.01 - we want to disable holds
completely.
>>
>> Koha system preference "maxreserves" ist set to 0.
>>
>> In Koha menu "Administration > Circulation and fines rules"
there is
>> only one rule, with the following settings:
>>
>> * Holds allowed (total): 0
>> * Holds allowed (daily): 0
>> * Holds per record (count): 0
>> * On shelf holds allowed: If all unavailable (other
possibilities are:
>> Yes / If any unavailable)
>> * OPAC item level holds: Don't allow
>>
>> With all these settings it is still possible to go to a record
with an
>> item attached to it and then place a hold, both in staff client and
>> OPAC! There is no warning or error when trying to do so.
>>
>> How is it possible to disable holds completely in Koha?
>>
>> Best wishes: Michael
>> --
>> Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg.
Fachausweis
>> Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
>> T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W
www.adminkuhn.ch <http://www.adminkuhn.ch>
>> ___
>>
>> 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



--
Tomás Cohen Arazi
Theke Solutions (http://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F

___

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

Re: [Koha] Authorized values for category COUNTRY

[Katrin Fischer]

Hi,

at the moment you can only manage the authorised values in the staff
interface, there is no option to export/import them in batch. See:

*Bug 10198*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10198> - Add
the ability to import and export authorized values

If you have some SQL knowledge and access to your database it might be
an option to do it on database level.

Hope this helps

Katrin

On 07.12.21 09:20, Сычев Игорь Алексеевич wrote:

Hi, Katrin!
Thanks for the reply.
But that's not exactly what I wanted to say.
I want to import values to COUNTRY.
Otherwise, I want to transfer from the test version to the product version.
How to do it?

-Original Message-
From: Koha  On Behalf Of Katrin Fischer
Sent: Tuesday, December 7, 2021 5:21 AM
To:koha@lists.katipo.co.nz
Subject: Re: [Koha] Authorized values for category COUNTRY

Hi Igor,

you can tie authorised values to MARC subfields and they will provide a pull 
down to make it possible to pick by description, but store the code. - Is that 
what you had in mind?

Hope this helps

Katrin

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

Hello Koha Community!
Question about Authorized values for category COUNTRY.
Do they fill out all the codes themselves?
I see exports. And how to import?

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 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] Printing labels in other languages

[Katrin Fischer]

Hi Rizwan,

please always keep the discussion on the mailing list.

I've looked in Bugzilla and printing with RTL languages like Arabic
should be possible:

*Bug 12068*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12068> -
label-create-pdf.pl Add support for RTL languages (closed fixed)

Maybe the discussion there could give you some hints. It looks like not
every font supports Arabic and that Text::Bidi might be needed.

Hope this helps,

Katrin


On 07.12.21 05:20, Rizwan Majeed wrote:

I did try several times but results showed symbols like ⌂∑∆∑√¥Ɫ◊. I am
trying to print like لاہور پاکستان

On Mon, Dec 6, 2021 at 4:24 PM Katrin Fischer
 wrote:

Hi Rizwan,

can you explain your problem a bit more? Did you try to print with
other
scripts and it didn't work? I think from the GUI it should work
just the
same.

Katrin

On 01.12.21 06:19, Rizwan Majeed wrote:
> Dear All
>
> Printing labels in Koha using the English language is very easy.
Because
> the English language is the default language of Koha. Would
anybody guide
> me to print labels in other languages like  Arabic or Urdu?
>
> Regards!
>
> Rizwan
> ___
>
> Koha mailing listhttp://koha-community.org
<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 sets due date to current date when checking out

[Katrin Fischer]

Hi Michael,

this one is really puzzling. Would you mind sharing your configuration
from the circulation_rules table? I wonder if something got "stuck" there.

SELECT * from circulation_rules;

Katrin

On 08.12.21 18:24, Michael Kuhn wrote:

Hi Michael

Today you wrote:

> I saw your email on the Koha list serv about the difficulties with a
> patron due date. We had a similar issue earlier this year, and it
> turned out that it was related to the Koha calendar. There were closed
> dates set that were messing up our normal return dates.
>
> It's a long shot, and you've probably already thought of that, but I
> wanted to share it with you just in case. :-)

Thanks for the hint, but yes, I thought of that - in our case the
calendar does not define any kind of holidays. So this can't be the
reason for Koha's abnormal behaviour.

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] Migrate checkouts with koc file

[Katrin Fischer]

Hi Tasha,

the format should still work as described on the wiki:

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

It really is just a text file with a specific header, as you say.

An advantage for migrations is that it works with cardnumbers and
barcodes, a disadvantage is that you can't set the due dates. They will
be calculated from the circulation rules when the transactions are
uploaded to Koha.

Hope this helps,

Katrin

On 10.12.21 19:32, Alvaro Cornejo wrote:

Hi Tasha

By curiosity I checked the master.koc referred and the only content on it
is this three tab separated values:

Version=1.0 Generator=koct-firefox GeneratorVersion=0.1
Hope helps

Regards,

Alvaro


||
  Stay safe / Cuídate/  Reste sécurisé
*7* Switch off as you go / Apaga lo que no usas /  Débranchez au fur et à
mesure.
  *q *Recycle always / Recicla siempre / Recyclez toujours
  P Print only if absolutely necessary / Imprime solo si es necesario /
Imprimez seulement si nécessaire


Le ven. 10 déc. 2021 à 12:47, Bales (US), Tasha R 
a écrit :


Good morning,

I would like to migrate check-outs from Millennium to Koha.  It just
occurred to me I could probably do this with offline circulation.  I'm
writing to ask for help creating a properly formatted .koc file that I can
upload.  From the web, I've gleaned this is just a delimited text file with
a special header and a .koc extension.

I am not permitted to install the Firefox or Windows utilities for offline
circ in order to try to generate an example .koc file.  I see a little info
the .koc file in the Wiki, but I'm not sure if it is current and
comprehensive.  In this 2019 blog,
http://kohageek.blogspot.com/2019/09/importing-of-check-out-entries.html,
I found a link to a template for the .koc file, but it's in Google Drive,
where I also don't have permission to download from.

In short, is there a way to make my own .koc file from scratch by
supplying the extension, necessary columns, and required header?  Thanks
for your time,


Tasha Bales
Enterprise Services
http://isesi.web.boeing.com/



Library Services Catalog upgrade is coming!
For the latest news and FAQ regarding the upgrade, see Library
Announcements.
Questions?  Please contact libr...@boeing.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

___

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

Re: [Koha] Error upgrading to 21.11.

[Katrin Fischer]

Hi Beda,

there is a known issue with the database updates that will be fixed with
21.11.01:

*Bug 29631*
 -
21.06.000.12 may fail

Hope this helps

Katrin

On 10.12.21 15:14, Beda Szukics wrote:


Upgrading from 21.06 the webinstaller stops with:

Upgrade to 21.06.00.012 [15:11:07]: Bug 15067 - Add missing languages
ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate
entry 'IN-region' for key 'uniq_lang' at
/usr/share/koha/lib/C4/Installer.pm line 738

What can I do?

Beda
___

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] Batch item modification does not works for barcode with space

[Katrin Fischer]

Hi Vimal,

have a look at the BarcodeSeparators system preference. I believe
removing the \s could fix your issue.

Hope this helps,

katrin

On 03.12.21 04:51, Vimal Kumar V. wrote:

Dear Friends,
Batch item modification (Tools  > Batch item modification)  does not work
for barcodes with space, e.g. BVB 1021.
My Koha version 21.05.5 on Ubuntu 20.04 LTS.

I remember that batch modification works well with this kind of barcodes in
Koha old versions.
Please see the screenshot link,
https://ibb.co/mB4RLGM
https://ibb.co/4N6kDKv

Regards,


___

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

Re: [Koha] Export koha patron

[Katrin Fischer]

Hi,

moving all this data would be much more complicated than just moving the
patrons from one installation to the other. In order to move the loans,
you'd also need to add the bibliographic records/items to the other
system, possibly matching with existing records, etc. There are
currently no scripts/tools in Koha to do this.

Hope this helps,

Katrin

On 01.12.21 04:11, Bravismore Mumanyi wrote:

Just thinking aloud here. Will this process take care of active loans
linked to these patrons? Any past anonymised stats, etc.

Regards

On Tue, 30 Nov 2021, 19:06 Eric Phetteplace,  wrote:


Hi Russel,

Since you can batch import patrons

using a CSV and export reports to CSV, yes, there's a relatively simple way
to transfer patrons from one instance to another. Write a report that grabs
all the columns and patrons you want to transfer (essentially `SELECT *
FROM borrowers`), download it to a CSV, and import on your other instance.
There are more options and nuances to it, but that is all you have to do.

Best,

ERIC PHETTEPLACE Systems Librarian, Libraries (he/him)

ephettepl...@cca.edu | o 510.594.3660 (cca)

5212 Broadway | Oakland, CA | 94618

CCA is situated on the traditional unceded lands of the Ohlone peoples.

Black-owned bookstores in Oakland: Ashay by the Bay
, Marcus Books


:(){ :|: & };:


On Tue, Nov 30, 2021 at 5:56 AM Russel G. P. Shihepo <
russellge...@gmail.com>
wrote:


Hi,

Is there is a way to batch export patron data from one Koha to another
Koha?

Thank you in advance!

Regards,
Russel
Librarian
Namibia Library and Archives Service
___

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] Koha sets due date to current date when checking out

[Katrin Fischer]

Hi Michael,

It looks like there are 3 rules defined for issuelength, one for 'All 
libraries' and 2 for the branchcode 'FIR'. Could it be that the rules 
for FIR are used? If the empty issuelength was interpreted as 0 that 
could explain the behavior.


Katrin

On 10.12.21 10:51, Michael Kuhn wrote:

Hi Katrin

You wrote:

> this one is really puzzling. Would you mind sharing your configuration
> from the circulation_rules table? I wonder if something got "stuck"
> there.
>
> SELECT * from circulation_rules;

No problem, you'll find the output of the SELECT statement below.

Best wishes: Michael
--
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch



MariaDB [koha_fir]> SELECT * from circulation_rules;
+++--+--+--++ 

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


|  1 | NULL   | NULL | NULL | maxissueqty | 50 |
|  2 | FIR    | PT   | NULL | maxonsiteissueqty    
| 100    |

|  3 | FIR    | PT   | NULL | maxissueqty | 100    |
|  4 | NULL   | NULL | NULL | maxonsiteissueqty    
|    |

|  5 | FIR    | CH   | NULL | maxissueqty | 150    |
|  6 | FIR    | CH   | NULL | maxonsiteissueqty    
| 150    |
|  7 | NULL   | NULL | NULL | restrictedtype    
|    |
|  8 | FIR    | CH   | NULL | restrictedtype    
|    |
|  9 | FIR    | PT   | NULL | restrictedtype    
|    |

| 13 | NULL   | NULL | NULL | fine    | 0.00   |
| 14 | FIR    | CH   | NULL | fine    | 0.00   |
| 15 | FIR    | PT   | NULL | fine    | 0.00   |
| 16 | NULL   | NULL | NULL | finedays |    |
| 17 | FIR    | CH   | NULL | finedays |    |
| 18 | FIR    | PT   | NULL | finedays |    |
| 19 | NULL   | NULL | NULL | maxsuspensiondays    
|    |
| 20 | FIR    | CH   | NULL | maxsuspensiondays    
|    |
| 21 | FIR    | PT   | NULL | maxsuspensiondays    
|    |
| 22 | NULL   | NULL | NULL | suspension_chargeperiod 
   | 1  |
| 23 | FIR    | CH   | NULL | suspension_chargeperiod 
   | 1  |
| 24 | FIR    | PT   | NULL | suspension_chargeperiod 
   | 1  |

| 25 | NULL   | NULL | NULL | firstremind |    |
| 26 | FIR    | CH   | NULL | firstremind |    |
| 27 | FIR    | PT   | NULL | firstremind |    |
| 28 | NULL   | NULL | NULL | chargeperiod    
|    |
| 29 | FIR    | CH   | NULL | chargeperiod    
|    |
| 30 | FIR    | PT   | NULL | chargeperiod    
|    |
| 31 | NULL   | NULL | NULL | chargeperiod_charge_at 
   | 0  |
| 32 | FIR    | CH   | NULL | chargeperiod_charge_at 
   | 0  |
| 33 | FIR    | PT   | NULL | chargeperiod_charge_at 
   | 0  |

| 34 | NULL   | NULL | NULL | accountsent |    |
| 35 | FIR    | CH   | NULL | accountsent |    |
| 36 | FIR    | PT   | NULL | accountsent |    |
| 37 | NULL   | NULL | NULL | issuelength | 1643   |
| 38 | FIR    | CH   | NULL | issuelength |    |
| 39 | FIR    | PT   | NULL | issuelength |    |
| 40 | NULL   | NULL | NULL | lengthunit | days   |
| 41 | FIR    | CH   | NULL | lengthunit | days   |
| 42 | FIR    | PT   | NULL | lengthunit | days   |
| 43 | NULL   | NULL | NULL | hardduedate |    |
| 44 | FIR    | CH   | NULL | hardduedate |    |
| 45 | FIR    | PT   | NULL | hardduedate |    |
| 46 | NULL   | NULL | NULL | hardduedatecompare 
   | -1 |
| 47 | FIR    | CH   | NULL | hardduedatecompare 
   | -1 |
| 48 | FIR    | PT   | NULL | hardduedatecompare 
   | -1 |
| 49 | NULL   | NULL | NULL | renewalsallowed    | 
10 |
| 50 | FIR    | CH   | NULL | renewalsallowed    | 
0  |
| 51 | FIR    | PT   | NULL | renewalsallowed    | 
0  |
| 52 | NULL   | 

Re: [Koha] Actions was initiated by Koha itself

[Katrin Fischer]

Hi,

do you mean that the patron got a hold confirmation, but there was no
hold on the account or is there a hold that wasn't placed by the patron?

I am not aware of any script that would place holds automatically
without some action from staff. There are some automatic options for
cancelling holds and reminding about pick-up. What was written in the
logs specifically?

Could it have been a confusion of accounts?

Hope this helps,

Katrin

On 15.07.21 13:41, Thu Thủy Dương wrote:

Hi all,
I'm having issues related to hold function in Koha. One patron in my
library received notification by email about hold confirmation. But, her
report with the Library is not place hold, and I checked the log
circulation of the system, all librarians of the library also do not
perform this action, whose action is performed by Koha.

As described of Koha, "*In the action_logs table, timestamp always
indicates when the log entry was written, and user is either the
borrowernumber of the staff member taking the action or 0 if the action was
initiated by Koha itself (e.g. in the case of fines added or updated
by fines.pl *).

Can anyone help me find the cause of this issue, and the cases was
initiated by Koha itself? (log *borrowernumber is **0, **e.g. in the case
of fines added or updated by fines *as described by Koha?

Many 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] Update for Demo page on https://koha-community.org/demo/

[Katrin Fischer]

Hi Jason,

I just checked, but looks like Galen beat me to it :)

Katrin

On 23.07.21 15:55, Jason Boyer wrote:

Hi, can the version for the Equinox Open Library Initiative demo server be updated to 
21.05 on the Demo page at https://koha-community.org/demo/ 
 ?

Thanks

Jason


___

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

Re: [Koha] Fwd: Request to list in paid support provider from India

[Katrin Fischer]

Hi,

I've added an entry for your company to the list of Koha support
companies on the website. Please check if everything is correct and let
me know if any changes need to be made.

Katrin

On 17.07.21 04:26, JITHIN N wrote:

Dear Koha Community

 Texicon Software Solutions ( https://www.texicon.in/ )  is an Indian
based software service and support
the company,  offering  service in Koha software since 2018. So far we
automated 200
plus libraries across the country with Koha Library management software and
we
also launched a public  z39.50 server with a collection of 1 lakh plus
regional  language (Malayalam) books bibliographic
data to support the library network of Kerala State. We kindly request you
consider listing our company details in paid support provider of Koha
Community
web site.

Company Name: * TEXICON SOFTWARE SOLUTIONS *

Contact Person:Jithin N

Contact email:  : i...@texicon.in , jithin984...@gmail.com

Website:https://www.texicon.in/

Telephone:+919847314010

With regards


*Texicon Software Solutions*

Padikkal

Malappuram District.

Kerala676317

India



*N.B- We already requested on Feb 17, 2020 . This is a followup of 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] New Koha install - legacy import question

[Katrin Fischer]

Hi Jon,

just confirming you are on the right path there. While changing the item
mappings in Koha is possible, I'd always recommend against it. For
example you'd also have to change the indexing for Zebra/Elasticsearch
to match your new fields. Converting your data to 952 is the better option.

Hope this helps,

Katrin

On 16.07.21 15:57, Jon Witts wrote:

OK, so answering myself...

I think I have got it to work now as best as I can... I imported the MARC
export from our legacy system into MARCEdit, had to then verify it and
remove invalid records. I could then use MARCEdit's switch fields tool and
replace subfields tools to create the required 952 items in the MARC file
ready for import into Koha...

Looking pretty good at the minute; need to do some further checks on the
data, but it is certainly getting closer!

Jon
-

Jon Witts
Director of Digital Strategy
-



On Fri, 16 Jul 2021 at 09:06, Jon Witts  wrote:


Hi there,

I am a new Koha user and have just set up and installed a new Koha
instance for our school library. We are running on a single Ubuntu server
and I followed the Ubuntu/ Debian install documentation and installed from
the packages.

I am now trying to import our catalogue from our legacy system (Softlink
Alice) and have run into some issues...

In the MARC export from our legacy system the details for each item are
stored in the 852 fields, specifically:
* 852,k = Item Library name / location
* 852,h = Item classification i.e. F for fiction or 242 for non-fiction
Dewey code
* 852,i = Item suffix i.e. CAR for author Frank Carr
* 852,p = item barcode
* 852,t = item copy number

I thought that I could use the "Koha to MARC Mapping" to edit this, but
after adding the new mappings in I get an error in the "MARC
bibliographic framework test", specifically:



*ALL items fields MUST :be mapped to the same tag,and they must all be in
the 10 (items) tab*

On the "Koha to MARC Mapping" page it states "If you make any change to
the mappings, you must ask your administrator to run
misc/batchRebuildBiblioTables.pl.", however when I run
the /usr/share/koha/bin/batchRebuildBiblioTables.pl script I get the
following errors:










*unable to locate Koha configuration file koha-conf.xml at
/usr/share/koha/lib/C4/Context.pm line 188.Use of uninitialized value in
concatenation (.) or string at /usr/share/koha/lib/C4/Templates.pm line
154.Use of uninitialized value $db_name in concatenation (.) or string at
/usr/share/koha/lib/Koha/Database.pm line 91.Use of uninitialized value
$db_host in concatenation (.) or string at
/usr/share/koha/lib/Koha/Database.pm line 91.Use of uninitialized value
$db_name in concatenation (.) or string at
/usr/share/koha/lib/Koha/Database.pm line 91.Use of uninitialized value
$db_host in concatenation (.) or string at
/usr/share/koha/lib/Koha/Database.pm line 91.Use of uninitialized value in
concatenation (.) or string at /usr/share/koha/lib/C4/Auth_with_cas.pm line
42.Use of uninitialized value $db_name in concatenation (.) or string at
/usr/share/koha/lib/Koha/Database.pm line 91.Use of uninitialized value
$db_host in concatenation (.) or string at
/usr/share/koha/lib/Koha/Database.pm line 91.Use of uninitialized value
$INC[-1] in string eq at /usr/share/koha/lib/Koha/Plugins.pm line 37.*

Am I going about this the wrong way? How should I be mapping these 852
fields into the 952 / items fields in Koha?

Many thanks,
Jon

-

Jon Witts
Director of Digital Strategy
-



___

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

Re: [Koha] Koha User Restrictions

[Katrin Fischer]

Hi Stephen,

I've also looked through the preferences and configuration options and
could only find: RestrictionBlockRenewing, but nothing about holds. I
think a good starting point might be to file an enhancement request to
add a similar switch for holds and restrictions on
https://bugs.koha-community.org.

Hope this helps,

Katrin

On 20.07.21 15:44, Stephen Graham wrote:

Hi All - we don't fine users for overdue items, but instead we add a 
"restriction" when the second overdue notice is sent out. The restriction, as 
well as stopping users borrowing any more items, prevents users from placing 
reservations/holds. I've looked through the systems preferences and I cannot see any way 
of allowing holds if a user is restricted. We are looking for a way to only prevent 
further borrowing but allow everything else if a user has a restriction. Is this possible 
at all? BTW, we are running 20.11.

Cheers, Stephen

--
Stephen Graham
Library Technology Consultant
Library and Computing Services

University of Hertfordshire
Hatfield, Hertfordshire, AL10 9AB

Tel: +44(0)1707 286111
Ext: 77751
Email: s.grah...@herts.ac.uk
Website: herts.ac.uk

___

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 or modifying extra 0

[Katrin Fischer]

Hi,

it looks like it's not possible to bulk edit barcodes with the batch
item edit tool in Koha. So your best bet might be to
export/update/reimport the records with the items or to change the items
with SQL.

Hope this helps,

Katrin

On 15.07.21 17:44, Himanshu Aggarwal wrote:

I have 1000 barcode which have extra 0s like I00089.
Is there a method bulk modify it where in I can delete the extra 0 in it
and the desired result will be I00898.


___

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

Re: [Koha] New Koha install - legacy import question

[Katrin Fischer]

Hi,

you can't map one MARC field to another, so I am not sure what you are
trying to do. But I think this would be a new question, so better to
start a new thread :)

Katrin


On 24.07.21 17:35, Himanshu Aggarwal wrote:

But can we map 852$j to 952$j?

On Sat, Jul 24, 2021 at 9:01 PM Katrin Fischer
mailto:katrin.fischer...@web.de>> wrote:

Hi Jon,

just confirming you are on the right path there. While changing
the item
mappings in Koha is possible, I'd always recommend against it. For
example you'd also have to change the indexing for Zebra/Elasticsearch
to match your new fields. Converting your data to 952 is the
better option.

Hope this helps,

Katrin

On 16.07.21 15:57, Jon Witts wrote:
> OK, so answering myself...
>
> I think I have got it to work now as best as I can... I imported
the MARC
> export from our legacy system into MARCEdit, had to then verify
it and
> remove invalid records. I could then use MARCEdit's switch
fields tool and
> replace subfields tools to create the required 952 items in the
MARC file
> ready for import into Koha...
>
> Looking pretty good at the minute; need to do some further
checks on the
> data, but it is certainly getting closer!
>
> Jon
> -
>
> Jon Witts
> Director of Digital Strategy
> -
>
>
>
> On Fri, 16 Jul 2021 at 09:06, Jon Witts
mailto:jwi...@queenmargarets.com>> wrote:
>
>> Hi there,
>>
>> I am a new Koha user and have just set up and installed a new Koha
>> instance for our school library. We are running on a single
Ubuntu server
>> and I followed the Ubuntu/ Debian install documentation and
installed from
>> the packages.
>>
>> I am now trying to import our catalogue from our legacy system
(Softlink
>> Alice) and have run into some issues...
>>
>> In the MARC export from our legacy system the details for each
item are
>> stored in the 852 fields, specifically:
>> * 852,k = Item Library name / location
>> * 852,h = Item classification i.e. F for fiction or 242 for
non-fiction
>> Dewey code
>> * 852,i = Item suffix i.e. CAR for author Frank Carr
>> * 852,p = item barcode
>> * 852,t = item copy number
>>
>> I thought that I could use the "Koha to MARC Mapping" to edit
this, but
>> after adding the new mappings in I get an error in the "MARC
>> bibliographic framework test", specifically:
>>
>>
>>
>> *ALL items fields MUST :be mapped to the same tag,and they must
all be in
>> the 10 (items) tab*
>>
>> On the "Koha to MARC Mapping" page it states "If you make any
change to
>> the mappings, you must ask your administrator to run
>> misc/batchRebuildBiblioTables.pl.", however when I run
>> the /usr/share/koha/bin/batchRebuildBiblioTables.pl script I
get the
>> following errors:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *unable to locate Koha configuration file koha-conf.xml at
>> /usr/share/koha/lib/C4/Context.pm line 188.Use of uninitialized
value in
>> concatenation (.) or string at
/usr/share/koha/lib/C4/Templates.pm line
>> 154.Use of uninitialized value $db_name in concatenation (.) or
string at
>> /usr/share/koha/lib/Koha/Database.pm line 91.Use of
uninitialized value
>> $db_host in concatenation (.) or string at
>> /usr/share/koha/lib/Koha/Database.pm line 91.Use of
uninitialized value
>> $db_name in concatenation (.) or string at
>> /usr/share/koha/lib/Koha/Database.pm line 91.Use of
uninitialized value
>> $db_host in concatenation (.) or string at
>> /usr/share/koha/lib/Koha/Database.pm line 91.Use of
uninitialized value in
>> concatenation (.) or string at
/usr/share/koha/lib/C4/Auth_with_cas.pm <http://with_cas.pm> line
>> 42.Use of uninitialized value $db_name in concatenation (.) or
string at
>> /usr/share/koha/lib/Koha/Database.pm line 91.Use of
uninitialized value
>> $db_host in concatenation (.) or string at
>> /usr/share/koha/lib/Koha/Database.pm line 91.Use of
uninitialized value
>> $INC[-1] in string eq at /usr/share/koha/lib/Koha/Plugins.pm
line 37.*
>>
>> Am I going about this the wrong

Re: [Koha] Mapping 852

[Katrin Fischer]

Hi,

at the moment you can copy information from the bibliographic record to
the item callnumber field  using the itemcallnumber system preference,
but there is no option for other fields at the moment.

Hope this helps,

Katrin

On 24.07.21 17:42, Himanshu Aggarwal wrote:

Just like there is option to map 082$a to 952$o is there a possibility to
map 852$j to 952$j for putting Shelving Control number?


___

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

[Koha] Fwd: update error

[Katrin Fischer]

Hi Ana,

please always keep conversation on the mailing list, so others can help
you too.

It looks like REGEXP_REPLACE might be a feature only available in newer
MySQL versions. It doesn't seem to appear in the 5.7 manual, but only in
the 8.0 manual, but I am having trouble finding the version it was
introduced in.

What OS are you using and is updating the DBMS or switching to MariaDB
an option?

Katrin



 Forwarded Message 
Subject:RE: update error
Date:   Tue, 4 Jan 2022 12:10:58 +
From:   anabela semedo 
To: Katrin Fischer 



Hi Katrin, thanks for your time.

I use the mysql, version 5.7.38

I still couldn't solve it.

do I have to uninstall everything?

Upgrade to 21.05.00.016 [14:16:28]: Bug 24387 - Rename opac_news with
additional_contents

ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: FUNCTION
koha.biblioteca.REGEXP_REPLACE does not exist at
/usr/share/koha/lib/C4/Installer.pm line 738

Thanks again,

Ana Bela

*De:*Katrin Fischer [mailto:katrin.fischer...@web.de]
*Enviada:* sábado, 1 de janeiro de 2022 10:53
*Para:* anabela semedo ; Koha

*Assunto:* Re: update error

Hi Ana,

better to copy the error into the email as attachments will be removed
on the mailing list:

Upgrade to 21.05.00.016 [14:16:28]: Bug 24387 - Rename opac_news with
additional_contents

ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: FUNCTION
koha.biblioteca.REGEXP_REPLACE does not exist at
/usr/share/koha/lib/C4/Installer.pm line 738

Are you using MySQL or MariaDB and which is the version?

Katrin

On 30.12.21 17:36, anabela semedo wrote:

   hello ever one

   i have a problem here,

   trying to update koha to the latest version

   and i have this error here that i am not able to resolve.

   can anybody help me?

   thankyou.

   Ana Bela Semedo
___

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

Re: [Koha] Linking via 830$w

[Katrin Fischer]

Hi Anke,

if the search is done horizontally using the rcn index we are looking
for records that have a $w entry matching the number.

If we are looking 'upwards' for the set record, we are using the
Control-number index to look for a matching 001.

It would be possible to combine the 2 searches, looking up both:

rcn:xxx OR Control-number:xxx

But I am not sure about influencing the sorting. It might just work, for
some reasons and depending on sequence of cataloguing etc. Maybe you
could give higher weight to the 001 to rank it higher than the $w with
Elasticsearch? We could also probably add some kind of sorting to the
query. But I haven't experimented with any of this :)

Hope this helps,

Katrin


On 04.01.22 10:45, Bruns, Anke wrote:

Hi Katrin and Thomas,

as I also followed this discussion with interest, I would add my 2 ct. as to 
Koha's behaviour regarding traced and untraced series. Horizontal linking to 
other parts of a series, traced or untraced, makes perfect sense. Yet I wonder, 
if it could be modified slightly for traced series. Is it possible to show the 
series title as first result in the result list, followed by the other titles 
belonging to the series? I find myself scolling endlessly through result lists 
trying to find the series title - so it would be quite helpful for me to see it 
as the first result.

Would it be very complicated to configure this, and is it at all possible with 
Koha?

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] Marc Staging - Failed - (UPLERR_CANNOT_WRITE) undefined

[Katrin Fischer]

Hi Christina,

I think a good candidate would be the directory given in 
in your koha-conf.xml. Checkout About Koha > System information is also
always a good place to start.

Hope this helps,

Katrin||

On 13.01.22 11:38, Fairlamb, Christina wrote:

Hello all,

Having an issue with the "Stage MARC records for import" tool since our
latest upgrade to Koha 21.05, getting the following message:

Failed - (UPLERR_CANNOT_WRITE) undefined

I can see it is a permissions error but don't know where to look to fix the
issue, any pointers?

Thanks for the help


___

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 the Koha Upgradation

[Katrin Fischer]

Hi,

you are trying to update from a real old version of Koha, so it's not so
easy to provide help.

What you could do when running into an error is taking a look at the
next update statement after 3.23.00.040 in updatedatabase.pl. You will
have to check, why it fails on your database and then figure out the
change required to make it work.

In this case this would be:

$DBversion = "3.23.00.041";
if ( C4::Context->preference("Version") < TransformToNum($DBversion) ) {

    my $dbh = C4::Context->dbh;
    my ($print_error) = $dbh->{PrintError};
    $dbh->{RaiseError} = 0;
    $dbh->{PrintError} = 0;
    $dbh->do("ALTER TABLE overduerules_transport_types ADD COLUMN
letternumber INT(1) NOT NULL DEFAULT 1 AFTER id");
    $dbh->{PrintError} = $print_error;

    print "Upgrade to $DBversion done (Bug 16007: Make sure
overduerules_transport_types.letternumber exists)\n";
    SetVersion($DBversion);

The error is that the column already exists in the
overduerules_transport_types table in your database.

I am not sure why that might be. Did you load your old database into an
empty database (no tables yet created by the installer)?

Hope this helps,

Katrin


On 07.03.22 08:27, Shiva Kumara wrote:

Hi All,
We have a koha backup of 3.23 version. We had installed Ubuntu 20.04.04 LTS
and the Koha 21.11 version successfully. We tried to restore the old koha
database to a new version of koha. When we run the command "*sudo
koha-upgrade-schema library*" for upgrading, we are getting the following
error.

root@koha:/home/koha/Documents# sudo koha-upgrade-schema library
Upgrading database schema for library
Upgrade to 3.23.00.000 done (The year of the monkey will be here soon.)
Upgrade to 3.23.00.001 done (Bug 11625 - Add pref
DefaultToLoggedInLibraryCircRules and DefaultToLoggedInLibraryNoticesSlips)
Upgrade to 3.23.00.002 done (Bug 11747 - add pref
DefaultToLoggedInLibraryOverdueTriggers)
Upgrade to 3.23.00.003 done (Bug 8085 - Rename 'Reserve slip' to 'Hold
slip')
Upgrade to 3.23.00.004 done (Bug 9819 - stopwords related code should be
removed)
Upgrade to 3.23.00.005 done (Bug 11569 - Typo in userpermissions.sql)
Upgrade to 3.23.00.006 done ( Bug 8956 - Split serials enumeration data
into separate fields )
Upgrade to 3.23.00.007 done (Bug 13624 - Remove columns branchcode,
categorytype from table overduerules_transport_types)
Upgrade to 3.23.00.008 done (Bug 9303 - relative's checkouts in the opac)
Upgrade to 3.23.00.009 done (Bug 11622 - Add ability to pay fees and fines
from OPAC via PayPal)
Upgrade to 3.23.00.010 done (Bug 9129 - Add the ability to set the maximum
fine for an item to its replacement price)
Upgrade to 3.23.00.011 done (Bug 13592 - Hold fee not being applied on
placing a hold)
Upgrade to 3.23.00.012 done (Bug 15380 - Move the authority types related
code to Koha::Authority::Type[s] - part 1)
Upgrade to 3.23.00.013 done (Bug 14945 - Add the ability to store the last
patron to return an item)
Upgrade to 3.23.00.014 done (Bug 10076 - Add Bcc syspref for
claimacquisition and clamissues)
Upgrade to 3.23.00.015 done (Bug 15443 - Re-code RESERVESLIP as HOLD_SLIP)
Upgrade to 3.23.00.016 done (Bug 8753 - Add forgot password link to OPAC)
Upgrade to 3.23.00.017 done (Bug 14893 - Separate temporary storage per
instance in Upload.pm)
Upgrade to 3.23.00.018 done (Bug 15446 - Fix systempreferences rows where
type=YesNo and value='')
Upgrade to 3.23.00.019 done (Bug 15411 - Change Non Fiction to Non-fiction
in authorised_values)
Upgrade to 3.23.00.020 done (Bug 9021 - Add SMS via email as an alternative
to SMS services via SMS::Send drivers)
Upgrade to 3.23.00.021 done (Bug 15736 - Add a preference to control
whether all items should be shown in checked-in items list)
Upgrade to 3.23.00.022 done (Bug 13534 - Deleting staff patron will delete
tags approved by this patron)
Upgrade to 3.23.00.023 done (Bug 6624 - Allow Koha to use the new read API
from OpenLibrary)
Upgrade to 3.23.00.024 done (Bug 15517 - Tables borrowers and
deletedborrowers differ again)
Upgrade to 3.23.00.025 done (Bug 15526 - Drop nozebra database table)
Upgrade to 3.23.00.026 done (Bug 15343 - Allow patrons to choose their own
password on self registration)
Upgrade to 3.23.00.027 done (Bug 4941 - Can't set branch in staff client
when singleBranchMode is enabled)
Upgrade to 3.23.00.028 done (Bug 14658 - Split
PatronSelfRegistrationBorrowerUnwantedField into two preferences for
creating and editing)
Upgrade to 3.23.00.029 done (Bug 14199 - Unify all organization code
plugins)
Upgrade to 3.23.00.030 done (Bug 15311: Let libraries set text to display
when OpacMaintenance = on)
Upgrade to 3.23.00.031 done (Bug 14395 - Two different ways to calculate
'No renewal before')
Upgrade to 3.23.00.032 done (Bug 15675 - Add issue_id column to
accountlines and use it for updating fines)
Upgrade to 3.23.00.033 done (Bug 14659 - Allow patrons to enter card number
and patron category on OPAC registration page)
Upgrade to 3.23.00.034 done (Bug 11023: Adds field