- Koha - lists.katipo.co.nz

Re: [Koha] 952$ j Shelving control
by Katrin Fischer 10 Jul '21

10 Jul '21

Hi, thx for explaining. I wonder if callnumber ($o) and or copynumber ($t) could be helpful for your use case - both can be displayed in OPAC and staff detail pages or already display by default. See Administration > Table settings or Column settings. Katrin On 10.07.21 12:47, Himanshu Aggarwal wrote: > Thank you Katrin for replying to me what I have done is inserted Shelf > No, of that particular book in which it is kept. And created Authority > For Row and Rack No. as public note. Now in this manner atlease public > note I can see in the display but not the Shelving Control no. > > On Sat, Jul 10, 2021 at 3:55 PM Katrin Fischer > <katrin.fischer.83(a)web.de <mailto:katrin.fischer.83@web.de>> wrote: > > Hi, > > at the moment it's not possible to display the shelving control number > in the detail displays, but it should show in the MARC view item > table. > > I've always wondered a little about how this field is supposed to be > used. Can you maybe explain a bit on how you are using it or > planning to > use it? > > Katrin > > On 03.07.21 12:34, Himanshu Aggarwal wrote: > > I want to see Shelving control number in holdings information > of Staff and > > OPAC..what is the option for this > > > _______________________________________________ > > Koha mailing list http://koha-community.org > <http://koha-community.org> > Koha(a)lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > <https://lists.katipo.co.nz/mailman/listinfo/koha> > > > > -- > Assistant Librarian, > Confucius Institute Scholar 13-14, > R.D. National College, > Bandra (W.)

1 0

952$ j Shelving control
by Himanshu Aggarwal 10 Jul '21

10 Jul '21

I want to see Shelving control number in holdings information of Staff and OPAC..what is the option for this -- Assistant Librarian, Confucius Institute Scholar 13-14, R.D. National College, Bandra (W.)

2 1

Re: [Koha] Koha Concurrent and Simultaneous Use of Records
by dcook＠prosentient.com.au 09 Jul '21

09 Jul '21

Hi Charles, Koha uses the "The ever popular do-nothing-approach". In theory, this is problematic and certainly bothers me, but in practice I think it's fairly rare that two staff members are working on the same record at the same time. Locking and lock timeouts come with a lot of complexity, and I think the majority of libraries would actually prefer risk accidental overwrites rather than lock contention and session timeouts. I would love to see a locking feature added, but I don't know if it's anyone's priority at the moment. David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -----Original Message----- Date: Fri, 9 Jul 2021 07:23:55 +0900 From: Charles Kelley <cmkelleymls(a)gmail.com> To: Discussion Group Koha <koha(a)lists.katipo.co.nz> Subject: [Koha] Koha Concurrent and Simultaneous Use of Records Message-ID: <CAM8F7wpRpmGDAsfd1DUNuz7ye=k5HEhnrbcFzVHsguCymPcazQ(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Hi, all! My library is preparing to migrate our Koha ILSA to the cloud. For reasons I shan't bore everyone with, I have a question about simultaneous and concurrent use of records: What happens if two or more parties try to access a bib. record or patron record at the same time? In my experience with other ILSs, there are several ways to handle such simultaneous use: - To lock the record when the first record accesses and queue up the rest for access in succession. - Party 1 works on the record and finishes -- the record is released. Every other party is blocked until the record is released. - Party 2 then works on the record and finishes -- the record is released. Every other party is blocked until the record is released. - Party 3 then works on the record and finishes -- the record is released. Every other party is blocked until the record is released. - To timestamp changes and then incorporate the changes based on the timestamp of the changes in a queued batch operation. A risk of data corruption. - The ever popular do-nothing-approach: to let multiple parties work on the same record simultaneously in real time, incorporating changes as they are submitted in real; another risk of data corruption. So if I may repeat my question: How does Koha handle simultaneous use of records? Many thanks, everyone! -- 気を付けて。 /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] mnogojazyk(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.

2 3

Koha Concurrent and Simultaneous Use of Records
by Charles Kelley 09 Jul '21

09 Jul '21

Hi, all! My library is preparing to migrate our Koha ILSA to the cloud. For reasons I shan't bore everyone with, I have a question about simultaneous and concurrent use of records: What happens if two or more parties try to access a bib. record or patron record at the same time? In my experience with other ILSs, there are several ways to handle such simultaneous use: - To lock the record when the first record accesses and queue up the rest for access in succession. - Party 1 works on the record and finishes -- the record is released. Every other party is blocked until the record is released. - Party 2 then works on the record and finishes -- the record is released. Every other party is blocked until the record is released. - Party 3 then works on the record and finishes -- the record is released. Every other party is blocked until the record is released. - To timestamp changes and then incorporate the changes based on the timestamp of the changes in a queued batch operation. A risk of data corruption. - The ever popular do-nothing-approach: to let multiple parties work on the same record simultaneously in real time, incorporating changes as they are submitted in real; another risk of data corruption. So if I may repeat my question: How does Koha handle simultaneous use of records? Many thanks, everyone! -- 気を付けて。 /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] mnogojazyk(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.

1 0

Field 830v won't display
by Javi Legido 08 Jul '21

08 Jul '21

Hi there. =Steps to reproduce= 1. Login admin interface 2. Click 'Cataloging' 3. Click 'New record' button 4. Click 'Default framework' 5. Click '8' tab 6. Click '830 SERIES ADDED ENTRY...' to expand it =Expected behavior= Find a text box with 'v Volume/sequential designation', as per: https://www.loc.gov/marc/bibliographic/bd830.html =Found behavior= Missing that field =Errors= None Any guidance will be appreciated. Thanks.

2 2

Re: [Koha] Help_EMAIL_Settings_Issue
by Mohan Kumar K.V. 07 Jul '21

07 Jul '21

Hi All, I Apologies for cross-posting, please ignore my email. With regards Mohan On Tue, Jul 6, 2021 at 10:26 PM Mohan Kumar K.V. <moni090(a)gmail.com> wrote: > Hi All, > > I am trying to configure Email for DSpace 6.3 but unfortunately, I am > ending up with an Internal System error. > > I had followed instructions provided for EMail Settings from DSpace > Documentation but it did not work. > > Hence i kindly request somebody to help on My Email Settings in DSpace. > > For more information, i had enclosed my system DSpace log files as well. > > Thanks once again for your help in advance. > > > -- > > With regards, > > > > Mohan > -- With regards, Mohan Kumar K V Information Analyst, Hewlett-Packard Labs India Bangalore 560 030 India

1 0

Hold policy and settings
by Nalisha Tamang 06 Jul '21

06 Jul '21

Dear all, Please help me to set a hold policy settings from all the starting till the end. I tried to place a hold and it says ' There are no items that can be placed on hold. i have not done any settings or hold fee or any cron jobs .please help me out thank you nalisha

2 1

Question on magazine local images
by Manos PETRIDIS 05 Jul '21

05 Jul '21

I understand that magazines are handled in koha under Serials / Continuing resources, with a record for the magazine, and one or more items for the magazine issues. I also understand that one may upload one or more local images at the record level. I wonder if/how may one upload local images at the item level, so that every item (magazine issue) has the cover image pertaining to the specific issue. TIA Manos Petridis

2 2

Koha common upgrades fails as rabbitmq service is not running
by Mike Lake 03 Jul '21

03 Jul '21

Hi I have a problem with our library and RabbitMQ. Koha version: 21.05.00.000 on Debian 9.13 During the latest update just tonight .... Setting up koha-common (21.05.00-1) ... Upgrading database schema for library <== this instance is disabled Upgrading database schema for libtest2 <== this instance is running OK Plugin configuration unchanged. .... Applying plugin configuration to rabbit@asf3... failed. * Could not contact node rabbit@asf3. Changes will take effect at broker restart. * Options: --online - fail if broker cannot be contacted. --offline - do not try to contact broker. Job for rabbitmq-server.service failed because the control process exited with error code. See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details. systemctl shows rabbitmq service is not running and it cannot start because: # cat /var/log/rabbitmq/startup_log ERROR: node with name "rabbit" already running on "asf3" and in the intranet About Koha / System Information for instance libtest2 says: Impossible to connect to the message broker There is an error when trying to connect to the message broker (RabbitMQ), check the Koha log files. Maybe it is not installed and configured correctly? Contact your system administrator. In /etc/rabbitmq/rabbitmq-env.conf all options are commented out. When this instance was installed last year there was nothing that suggested that this needed to be configured. I also see in worker-output.log I'm getting: Error connecting to localhost:61613: Connection refused at /usr/share/perl5/Net/Stomp.pm line 26. I'm not sure if this is a firewall issue or not. I am running the stock Debian fail2ban. Thanks -- Mike

2 4

Re: [Koha] Self check issue
by Jeremiah Henderson 02 Jul '21

02 Jul '21

Thank you Marcus, I have done all of those steps exactly, and it is still prompting for the staff login first. Den 02.07.2021 09:29, skrev Jeremiah Henderson: > Hello, > > Now that I have a working version of Koha, I am attemping to turn on the AutoSelfCheckAllowed feature, but after I turn it on and put in the correct username and password, the self checkout page still requires a staff username and password. Not sure what I am doing wrong? You do need to create a staff user that the SCO can log in as. This user needs to have the "self_checkout_module" permission. https://koha-community.org/manual/21.05/en/html/circulationpreferences.html… If you then set SelfCheckoutByLogin = "Username and password", patrons will be able to log into SCO with their own username and password. https://koha-community.org/manual/21.05/en/html/circulationpreferences.html… Best regards, Magnus Enger Libriotech _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

1 0