Hi!
The format is incorrect. It should be like this:
2013-06-14 16:35:28     issue   5       000002
2013-06-17 16:29:04     return  000002
And the question is the sequential issuance of the same item. 
You can't give out one item without handing it in. Or can you?

Good Luck!

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

-----Original Message-----
From: Koha <koha-boun...@lists.katipo.co.nz> On Behalf Of Alipio Luiz de Souza 
Silva
Sent: Tuesday, August 15, 2023 7:54 PM
To: koha@lists.katipo.co.nz
Subject: [Koha] Import offline circulation (.koc file): No branchcode argument 
passed

Hi...
I'm trying to import a .koc file using offline circulation. However, it's not 
working.
When I select the records and click on 'Process', I get the following
message:

AH01215: No branchcode argument passed to Koha::Calendar->new at 
/usr/share/koha/lib/C4/Circulation.pm line 3839.: /usr/share 
/koha/intranet/cgi-bin/offline_circ/process.pl, referer:
http://koha.domain:8080/cgi-bin/koha/offline_circ/list.pl

The .koc file is as follows:

Version=1.0     Generator=kocPY     GeneratorVersion=0.1
2013-06-14 16:33:20 010       issue   5       000002
2013-06-14 16:35:28 010       issue   5       000002
2013-06-17 16:29:04 010       return  000002
2013-06-17 17:26:40 010       issue   5       000002
2013-06-17 17:37:20 010       return  000002
2013-06-17 17:37:20 010       return  000002
2013-06-17 17:37:20 010       issue   5       000002
2013-06-17 17:39:28 010       return  000002
2013-06-17 17:41:36 010       return  000002
2013-06-17 17:41:36 010       issue   5       000002

Is there a way to inform the branchcode in the .koc file or something like 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

Reply via email to