Advice for manipulating the patron database with code
We have a separate database of users that we want to sync (one way) with Koha. Since I have experience working with databases, I plan to add a column to the Koha MySQL patron table that I will use as a reference to the record in the other database. Then everyday I'm going to run a cron job that makes sure the Koha database of patrons all have the correct email address, name, address, etc, based on our other database. I'm pretty sure this will work. The reason I'm saying all this is just so that if anyone out there has any advice for me before I begin, I would take it. Perhaps there are pitfalls to guard against, or perhaps there is some feature of Koha I don't know about since I'm not all that familiar with it yet. Thank you. p.s. this other database we have lives on a different server that we only have limited api access into, so I don't think it will work to use it as some sort of active directory server. -- Tim -- View this message in context: http://koha.1045719.n5.nabble.com/Advice-for-manipulating-the-patron-databas... Sent from the Koha-general mailing list archive at Nabble.com.
magmatic schreef op wo 30-10-2013 om 19:17 [-0700]:
I'm pretty sure this will work. The reason I'm saying all this is just so that if anyone out there has any advice for me before I begin, I would take it. Perhaps there are pitfalls to guard against, or perhaps there is some feature of Koha I don't know about since I'm not all that familiar with it yet.
This ought to work fine. There aren't any particular gotchas with the borrowers table really. If you get a script with the proper mapping, and you never change the borrower number (which I wouldn't expect to happen anyway) then this should be an effective way of doing this. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
participants (2)
-
magmatic -
Robin Sheat