On 16/10/12 10:50, Chris Cormack wrote:
On 16 October 2012 12:43, BWS Johnson <[email protected]> wrote:
Salvete!
We undertook a stocktake earlier this year using Koha 3.4. We didn't use
the stocktake module though. What we did was return all items through the
circulation desk. This changes their last seen date to the current date. Once
we had done that I then made a report which showed the biblio/item details and
included whether the item was on loan or not and the date last seen.
Any item not on issue or not seen prior to the date the stocktake began was
considered missing and its status was changed to lost.
We have undertaken stocktakes using the same process and with three different
Library Management Systems and have come to the conclusion it is the best
method. Using a laptop with scanner and wifi connection means you aren't
dragging books to the issue desk.
Below is the report I use, which could also be used as a shelf check list. If
you only have one branch then take out the highlighted line. Not sure that it
would work in your version but worth a try :)
I concur that this is a stellar way to ensure accuracy. A side benefit is
that you can shelf read, weed, and shift as you go along.
I hate to be the bearer of bad news, but there is no reports module in
2.2.9 (not in the way there is in 3.2.0 onwards anyway). So without
access to the db itself (and a knowledge of sql as the tables are a
bit different), that report won't be able to be used.
However on the good news front, the rest of the method will work just
fine. The trick will be getting the data out of the database.
Here is how you can back up the database,
http://wiki.koha-community.org/wiki/Backing_up_Koha#Complete_dump
(You are running the Koha server on linux eh?).
Now for some more bad news, upgrading from 2.2.9 (which is I think 6
years old now and about 27 versions behind) is not super easy. Here
are some instructions
http://wiki.koha-community.org/wiki/Upgrading_2.2 . HOWEVER don't do
this on your live system, please set up a copy of it somewhere, and
upgrade that first to test.
Hope this is some help
Chris
I'd actually go further and recommend not upgrading from 2.2.9 (although
you can do so). I think you'll get a cleaner result by exporting your
data from 2.2.9 and importing it to a fresh install of 3.8.x. Of course
it depends on how much history you need or want to retain and the
expertise available to help you, but there are several pain points in
coming all the way from 2.2.9 (which as Chris says is very old now) to 3.8.
Just my opinion, hope it helps.
Bob Birchall
Calyx
_______________________________________________
Koha mailing list http://koha-community.org
[email protected]
http://lists.katipo.co.nz/mailman/listinfo/koha
