So the problem with a blog describing a migration like this is that there’s no motivation to keep posting while everything is going well. And right now, everything is trundling along well! I played with the reports function a little yesterday, as I needed to get a list of all the students with their borrower numbers, for their ID cards. I ended up with this:
SELECT borrowers.cardnumber,borrowers.surname,borrowers.firstname,borrowers.categorycode FROM borrowers WHERE borrowers.branchcode=<<branchcode|branches>> ORDER BY borrowers.categorycode asc
Which does the trick, although I did have to remove all the not-students in excel afterwards. When I have a little more time on my hands, I do want to investigate this all more thoroughly so I have an actual clue as to what that means.
I’ve also made a change to my original install preferences. When I first set everything up, I set each of the student categories to expire after 14 months, thinking that, after all, they will change categories every 12 months anyway. I ran into a problem with that almost immediately – as the patron import from Athena included the date they first registered, all the students in year 8 and above were expired before they even got to Koha! I went to the Koha mailing list and got a fix for it, which worked:
So to answer your question with a question. Do you have access to the database either from the commandline or via some tool like phpmyadmin?
If so you can run
UPDATE borrowers SET dateexpiry = ‘2012-12-31’;
And thanks to Chris Cormack for that suggestion. But I still think I was doing it wrong in the first place. Why not just have the student categories expire after 7 years, so that for the most part the students graduate before they expire, and a year’s leeway for anyone who does a three-year VCE or repeats a year? Will be less work on my part in the long term, after all! However writing this I’ve suddenly realised I’ve no idea how one would promote students from one category to the next! Okay, need to look into that too.