I forgot to cc the list... On Wed, Apr 28, 2010 at 10:13 AM, jason sherman <jsherman@usao.edu> wrote:

Jane,

Thanks for the fast response!  I understand that the borrowernumber is the unique id as opposed to the cardumber which is the patron's barcode.  I was hoping to simply carry over the known unique ids from the old system to Koha, because it would allow me to migrate patron data and checkout data in one fell swoop, without having to ask koha for the id of each patron as I'm importing checkouts.

On Wed, Apr 28, 2010 at 9:45 AM, Jane Wagner <jwagner@ptfs.com> wrote:

...

borrowernumber is the internal database unique identifier and it is sequential.  I think you probably want to migrate your current numbers into the cardnumber field.  That's the patron barcode.

Jane Wagner Library Systems Analyst PTFS Inc. Content Management and Library Solutions 6400 Goldsboro Road, Suite 200 Bethesda, MD  20817 (301) 654-8088 x 151 jwagner@ptfs.com

-----Original Message----- From: koha-bounces@lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of jason sherman Sent: Wednesday, April 28, 2010 9:41 AM To: koha@lists.katipo.co.nz Subject: [Koha] bulk patron import - specifying borrowernumber?

Hi all,

I am in the process of preparing our library for migration to Koha 3.00.04.019.  After examining the patron import starter file from my test server as well as the issues database table, I thought it made sense to specify the borrowernumber based on values in our old system to make moving current borrower checkouts easier.  The problem is that even though I specify borrowernumbers in the patron import file, Koha keeps using auto_increment for the value.  I've been fussing around with various settings in Koha to try to get it to take my values, but I can't get it it to do so.  If this isn't going to happen without hacking koha's scripts or db config, I can write my checkouts migration script to find each user's Koha borrowernumber by checking their cardnumber, but I thought I would do a sanity check first.

So, my questions are: Is there a setting that I'm missing or something that I've misconfigured? Is this a bug in my version of Koha, either by including fields that I can't use in the patron import starter file, or by not accepting data that it should? Or is this just intended behavior that I should expect?

Thanks in advance for any advice you can share,

-- Jason Sherman Systems Librarian University of Science and Arts of Oklahoma 405.574.1340 _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

-- Jason Sherman Systems Librarian University of Science and Arts of Oklahoma 405.574.1340

-- Jason Sherman