File definitions and Process - Checked by Vexira DEMO version -
Hi Everyone, Several weeks ago my co-worker Owen Leonard posted a message to the list asking for methodologies pertaining to the transition from one database to the KOHA database. In other words did you sit down and go through file printouts of each database and fit the puzzle together? Did you actually electronically dump the original database into KOHA and looked @ the results of what was missing? Or did you use another process. (Keep in mind I am not a techie--thanks!) Also, if you look at the index of all the KOHA files, for example -- branchtransfers--what is branchtransfers--what does that mean? There are many file names that we don't know what they mean--therefore we don't know if that file is important to us. Any help you can give us is appreciated greatly! Thank you and take care. Lauren Miller Librarian Athens County Library Services
Lauren Miller schrieb:
In other words did you sit down and go through file printouts of each database and fit the puzzle together? Certainly not.
Did you actually electronically dump the original database into KOHA and looked @ the results of what was missing? Or did you use another process. We are running Koha at the moment in "Alpha-status". That means the plain script with about 20 test-items, I added manually (with special characters and so on). When Koha seems to me to satisfy my needs, we'll switch over to "beta-status". That means our old database (flatfile) will be migrated to Koha. Since I'm familiar with programming (I wrote our old opac myself), I see no problem in filling the SQL-Tables (this is the place where Koha stores it's data).
To put it in a nutshell: The changeover will be no problem if the old data is in a very simple format (or in marc-format of course). When you are storing more information then Koha supports at the moment, feel free to make a feature-request.
Also, if you look at the index of all the KOHA files, for example -- branchtransfers--what is branchtransfers--what does that mean? There are many file names that we don't know what they mean--therefore we don't know if that file is important to us. One of Koha's advantages is to handel a distributet library system with several local branches. When a user requests a book, which is held in a different branch than he requests it, it has to be transferred to the requesting branch. If you are not in a library network, you won't need this feature (nevertheless you shouldn't delete any files)
Dorian
To put it in a nutshell: The changeover will be no problem if the old data is in a very simple format (or in marc-format of course).
Well, that counts us out ;-) But seriously, MARC data is only a tiny part of our data--all the item information and circulation records, patron records, etc. will have to be transferred as well.
Also, if you look at the index of all the KOHA files, for example -- branchtransfers--what is branchtransfers--what does that mean? When a user requests a book, which is held in a different branch than he requests it, it has to be transferred to the requesting branch.
I think Lauren was using that as an example, but the explanation helps. We may be back with a whole list of questions like that as we sift through the tables in our existing database to see where items match up with Koha's database. If no one else has done it before, then we may end up writing the Koha database description ourselves as part of our conversion process, and have you all check it for accuracy. If anyone has done anything similar in the past, we'd love to hear about it. -- Owen ---- Web Site Developer Athens County Library Services http://www.athenscounty.lib.oh.us
Hi - Just a quick message as I'm about to head off on holiday, we certainly have transfered information from a "full" library system, including reserves, members details, fines etc not just the biblio information. Hopefully Olwen who did this work is watching and may be able to share with you, otherwise please feel free to drop me a line and I'll pass it on.
To put it in a nutshell: The changeover will be no problem if the old data is in a very simple format (or in marc-format of course).
Well, that counts us out ;-) But seriously, MARC data is only a tiny part of our data--all the item information and circulation records, patron records, etc. will have to be transferred as well.
Yep - the other data is definitly a challenge - not loosing all your reserve data etc is pretty crucial.
If no one else has done it before, then we may end up writing the Koha database description ourselves as part of our conversion process, and have you all check it for accuracy. If anyone has done anything similar in the past, we'd love to hear about it.
There has been work on manuals etc which may cover this, we have an old database description here but Koha has been changing pretty rapidly over the last 6 months and I suspect it is well out of date. Sorry not to be of more immediate help. I'll check in again in 10 days time. Cheers Rachel _____________________________________________________________ Rachel Hamilton-Williams Katipo Communications WEBMISTRESS ph 021 389 128 or +64 04 934 1285 mailto:rachel@katipo.co.nz PO Box 12487, Wellington http://www.katipo.co.nz New Zealand Koha Open Source Library System http://www.koha.org
participants (4)
-
Dorian Meid -
Lauren Miller -
Owen Leonard -
Rachel Hamilton-Williams