[Koha] Trouble circulating freshly imported records (Settign Peermanant Location?)

[ed c]

Thanks for the reply Joe, but I double-checked and using the kohaadmin user is not the cause of our issues. The person doing the importing doesn't even have the kohaadmin user password. When I asked her about thi, she said:

"I always have logged in [with my username] and I always choose CDC which is in the upper right.  If fact I had seen something like this answer online so I also toggled the preference under circulation called
"homeorholdingbranch" from holding branch to home branch thinking that
might make a difference but it did not."

Edward

--- On Mon, 6/15/09, Joe Atzberger <ohiocore at gmail.com> wrote:

> From: Joe Atzberger <ohiocore at gmail.com>
> Subject: Re: [Koha] Trouble circulating freshly imported records (Settign  Peermanant Location?)
> To: "ed c" <terrapin44 at yahoo.com>
> Cc: "Koha List" <koha at lists.katipo.co.nz>
> Date: Monday, June 15, 2009, 11:27 AM
> The item homebranch is what is
> important.  It sounds like you may have cataloged the items
> as the koha root user, who isn't a real user and
> therefore doesn't have a valid associated branch to
> populate into the item record.  So try it as a normal user
> who has a valid homebranch and adequate permissions. 
> 
> 
> -- 
> Joe Atzberger
> LibLime - Open Source Library Solutions
> 
> 
> 
> On Mon, Jun 15, 2009 at 10:38 AM,
> ed c <terrapin44 at yahoo.com>
> wrote:
> 
> 
> 
> Hello All,
> 
> 
> 
> We have managed to bulk import a number of records and have
> created items during the import in our new Koha 3.0.2
> install. However, when we try to circulate them, we get the
> following error:
> 
> 
> 
> 
> 
> Koha error
> 
> The following fatal error has occurred:
> 
> 
> 
> No branchcode argument to new.  Should be
> C4::Calendar->new(branchcode => $branchcode) at
> /usr/share/koha/lib/C4/Circulation.pm line 2321
> 
> 
> 
> (followed by some systems info)
> 
> 
> 
> 
> 
> If we locate the bib record in "Manage Staged MARC
> Records" and then go and edit the item, changing
> nothing in the form, we do not get this error anymore.
> That's the good thing, the bad thing is this takes a lot
> of clicks and steps for each record. It looks like just the
> fact that we went in and saved the item, automatically
> populated a few fields including:
> 
> 
> 
> 
> Source of classification or shelving scheme
> 
> Permanent location
> 
> Date last seen
> 
> Price effective from
> 
> 
> 
> The one that I'd guess is important is Permanent
> Location. I am not sure why this is not being set during the
> import. Current Location is being set during the import. Any
> ideas?
> 
> 
> 
> Edward
> 
> 
>