Re: [Koha] Data Migration, TLC to Koha
On 1 August 2014 4:16:02 pm NZST, Vinod Kumar Mishra <vinod_librarian@rediffmail.com> wrote:
Hello,
Yes you can convert your own data into marc format there are various methods to do that, If you can generate reports in Marc/iso/excel formats etc. from existing software than it can be converted.
This is true, but there is far more data than just the bibliographic data. That is always the easiest bit. There is circulation, patrons, fines, acquisitions etc etc. It is a non trivial task, however it is certainly possible to do it yourself given enough time.
Please see the link below, if you don't mind may i know how much they quote and your data size/record?
I imagine the quotes will have been provided as commercial in confidence. And as such sharing them without permission is not a good look. Collection size is actually pretty immaterial to how long a migration will take. Getting the data out in a good format is the hardest but and whether it's 1000 or 100000 it takes about the same time. Chris
http://manual.koha-community.org/3.2/en/marceditexcel.html
On Fri, 01 Aug 2014 01:46:28 +0530 Ronn Raszetnik wrote
Hi everyone,
I am new to the list here. I am an electronic resources librarian at an independent public library in Florida. We are interested in migrating from our current self-hosted TLC system to Koha. Quotes we have received from vendors are higher than we had hoped, mainly because of hefty migration fees. Is it realistic to think we could do the migration ourselves?
I installed Koha on an old server that we have, and it seems simple enough to use. Honestly, I don't think we need training or ongoing support, but the data migration (bib, patron, fine records) makes me a bit uneasy. I can work my way around Linux a bit, but I am not a database expert.
Does anyone have experience migrating from TLC to Koha? What is involved?
Thanks,
Ronn
_______________________________________________
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha
With regards, Vinod Kumar Mishra, Assistant Librarian, (Library In-Charge) Biju Patnaik Central Library, NIT Rourkela, Mob:91+9439420860 91+6612462103 (O) email: vinod_librarian@rediffmail.com : mishravk79@gmail.com _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
On 1 August 2014 07:21:57 CEST, Chris Cormack <chrisc@catalyst.net.nz> wrote:
Collection size is actually pretty immaterial to how long a migration will take. Getting the data out in a good format is the hardest but and whether it's 1000 or 100000 it takes about the same time. I'd suggest that more records in the collection increases the chance of something strange or undocumented that causes problems in one record, which is one reason why migration quotes increase with collection size.
I also agree that publishing quotes without warning may harm trust with suppliers before you've even started working together. Some suppliers will be cool with it but many seem not to be. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
MJ Ray schreef op vr 01-08-2014 om 07:45 [+0200]:
I'd suggest that more records in the collection increases the chance of something strange or undocumented that causes problems in one record, which is one reason why migration quotes increase with collection size.
In my experience, it seems to be roughly logarithmic. So, a 1,000 record system will have almost as many oddities as a 10,000 record system which will have almost as many oddities as a 100,000 record system. In no small part this tends to be due to the software handling the larger systems does a better job at data integrity and exporting. I've seen small systems where the XML exporter (which is the only way to get everything out) produces invalid XML, and larger systems where everything is pretty much a normalised database dump, exported with proper escape characters and consistent character sets. The smaller systems are also less good at enforcing data consistency, and I expect that the staff at smaller places tend to be a bit more relaxed about what's going into the system. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
participants (3)
-
Chris Cormack -
MJ Ray -
Robin Sheat