We have this problem as well and have been devoting a great deal of time and effort. We had figured out a "hack" for 3.0 that doesn't work in 3.2 It is out greatest obstacle to being able to migrate to Koha. On 1:59 PM, Stefano Bargioni wrote:
This is an autoreply :-) I wonder why nobody have had this problem before. How can be preserved internal links -contained in fields like 77x- without preserving the system number? I'll try to solve it hacking the code (C4::Biblio), but in my opinion Koha needs a way to do this, an option in bulkmarcimport for instance. Bye. Stefano
On Jan 20, 2011, at 11:27 , Stefano Bargioni wrote:
I'm trying to migrate about 140,000 records. Each of them has 001 with the original value. I copied it into 999c and 999d. Importing in Koha, 999c and 999d are replaced by a new (autoincremented) bibliotemnumber. How can I force Koha to assign bibliotemnumbers using 001 or 999c/d? Thank you. SB _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- 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