Koha - migrating items' circulation history from current ILS
Is there documentation and/or methodology of migrating the circulation history of items from our current ILS into Koha? I know there is a field for how many times an item has been checked out, and I know there is offline circulation, but what I'm unclear about whether it is the best method to use to migrate our current circulation history information into Koha. Thanks in advance. -- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives& History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824
Hi, There is a table in Koha that holds "old issues" which is very similar to "issues". We have loaded this on some implementations to good effect. The table layout is below and you will have to use sql to load it. Good luck... mysql> desc old_issues; +-----------------+-------------+------+-----+-------------------+-------+ | Field | Type | Null | Key | Default | Extra | +-----------------+-------------+------+-----+-------------------+-------+ | borrowernumber | int(11) | YES | MUL | NULL | | | itemnumber | int(11) | YES | MUL | NULL | | | date_due | date | YES | | NULL | | | branchcode | varchar(10) | YES | | NULL | | | issuingbranch | varchar(18) | YES | | NULL | | | returndate | date | YES | | NULL | | | lastreneweddate | date | YES | | NULL | | | return | varchar(4) | YES | | NULL | | | renewals | tinyint(4) | YES | | NULL | | | timestamp | timestamp | NO | | CURRENT_TIMESTAMP | | | issuedate | date | YES | | NULL | | +-----------------+-------------+------+-----+-------------------+-------+ 11 rows in set (0.00 sec) mysql> desc issues; +-----------------+-------------+------+-----+-------------------+-------+ | Field | Type | Null | Key | Default | Extra | +-----------------+-------------+------+-----+-------------------+-------+ | borrowernumber | int(11) | YES | MUL | NULL | | | itemnumber | int(11) | YES | MUL | NULL | | | date_due | date | YES | | NULL | | | branchcode | varchar(10) | YES | | NULL | | | issuingbranch | varchar(18) | YES | | NULL | | | returndate | date | YES | | NULL | | | lastreneweddate | date | YES | | NULL | | | return | varchar(4) | YES | | NULL | | | renewals | tinyint(4) | YES | | NULL | | | timestamp | timestamp | NO | | CURRENT_TIMESTAMP | | | issuedate | date | YES | | NULL | | +-----------------+-------------+------+-----+-------------------+-------+ 11 rows in set (0.00 sec) On 07/10/2010 19:03, Linda Culberson wrote:
Is there documentation and/or methodology of migrating the circulation history of items from our current ILS into Koha? I know there is a field for how many times an item has been checked out, and I know there is offline circulation, but what I'm unclear about whether it is the best method to use to migrate our current circulation history information into Koha. Thanks in advance.
-- Ian Bays Director of Projects PTFS Europe.com mobile: +44 (0) 7774995297 phone: +44 (0) 800 756 6803 skype: ian.bays email: ian.bays@ptfs-europe.com
* Ian Bays (ian.bays@ptfs-europe.com) wrote:
Hi, There is a table in Koha that holds "old issues" which is very similar to "issues". We have loaded this on some implementations to good effect. The table layout is below and you will have to use sql to load it. Good luck...
Hi To add to Ian's excellent advice, once you have loaded those in, you will want to update the counts on the item, and also the due date on the items. The count is less important, but it does show on the moredetails page so its good to have, but you do want to know if an item is out or not for the search. So you can do this one of two ways run some sql like UPDATE items,issues SET items.onloan = issues.date_due WHERE items.itemnumber = issues.itemnumber; To update the due dates, and then run misc/maintenance/sync_items_in_marc_bib.pl Or you can craft a script that does gets the dates, and the issues count for each item, and calls something like this ModItem({issues => $issue_count->{iscount}, onloan => $issues->{date_due} }, $item->{biblionumber}, $item->{itemnumber}); Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
Thanks for the advice, Chris! On 1:59 PM, Chris Cormack wrote:
* Ian Bays (ian.bays@ptfs-europe.com) wrote:
Hi, There is a table in Koha that holds "old issues" which is very similar to "issues". We have loaded this on some implementations to good effect. The table layout is below and you will have to use sql to load it. Good luck...
Hi
To add to Ian's excellent advice, once you have loaded those in, you will want to update the counts on the item, and also the due date on the items. The count is less important, but it does show on the moredetails page so its good to have, but you do want to know if an item is out or not for the search.
So you can do this one of two ways run some sql like
UPDATE items,issues SET items.onloan = issues.date_due WHERE items.itemnumber = issues.itemnumber;
To update the due dates, and then run misc/maintenance/sync_items_in_marc_bib.pl
Or you can craft a script that does gets the dates, and the issues count for each item, and calls something like this
ModItem({issues => $issue_count->{iscount}, onloan => $issues->{date_due} }, $item->{biblionumber}, $item->{itemnumber});
Chris
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
-- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives& History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824
participants (3)
-
Chris Cormack -
Ian Bays -
Linda Culberson