RE: Koha Digest, Vol 24, Issue 40
Hello all I want to comment on the SirsiDynix migration possibilities. I have a bunch of library friends in a consortium with Sirsi and I wondered if they were ever going to be able to get out of the proprietary patch hell. I am currently in line to join their group but I am have serious doubts and that this would be a dead end in the near future. I am considering Koha for my mid sized library and I was hoping that there was a way to migrate my Sagebrush catalog into Koha with out having to datamap or bar code. Has anyone had any good experience with these issues? I have 76000 bib records and 14K users. We really need to decide soon Sagebrush doesn't answer their phone any more...if you catch my drift. Lee Phillips Butte Silver Bow Public Library Butte, Montana -----Original Message----- From: koha-bounces@lists.katipo.co.nz on behalf of koha-request@lists.katipo.co.nz Sent: Tue 10/30/2007 1:00 PM To: koha@lists.katipo.co.nz Cc: Subject: Koha Digest, Vol 24, Issue 40 Send Koha mailing list submissions to koha@lists.katipo.co.nz To subscribe or unsubscribe via the World Wide Web, visit http://lists.katipo.co.nz/mailman/listinfo/koha or, via email, send a message with subject or body 'help' to koha-request@lists.katipo.co.nz You can reach the person managing the list at koha-owner@lists.katipo.co.nz When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha digest..." Today's Topics: 1. Koha Installation Error - BlueHost.com (Librarian, SAIACS) 2. Re: Koha became a little more of a certainty last night (Dan Scott) 3. Re: Koha on etch - a pain? (Grant Johnson) 4. Re: Koha on etch - a pain? (Beda Szukics) 5. Re: Koha on etch - a pain? (Beda Szukics) ---------------------------------------------------------------------- Message: 1 Date: Tue, 30 Oct 2007 19:52:37 +0530 From: "Librarian, SAIACS" <library@saiacs.org> Subject: [Koha] Koha Installation Error - BlueHost.com To: <koha@lists.katipo.co.nz> Message-ID: <20071030142511.C995910720@daddy.katipo.co.nz> Content-Type: text/plain; charset="us-ascii" Hi, while trying to install koha on Bluehost.com, I encountered following error; Use of uninitialized value in concatenation (.) or string at Install.pm line 1685, <STDIN> line 5. Use of uninitialized value in concatenation (.) or string at Install.pm line 1685, <STDIN> line 5. Use of uninitialized value in concatenation (.) or string at Install.pm line 1685, <STDIN> line 5. Use of uninitialized value in concatenation (.) or string at Install.pm line 1685, <STDIN> line 5. Use of uninitialized value in concatenation (.) or string at Install.pm line 1685, <STDIN> line 5. Use of uninitialized value in concatenation (.) or string at Install.pm line 1709, <STDIN> line 5. Please check permissions in /home/jlcopaco/koha/intranet/scripts/z3950daemon Use of uninitialized value in concatenation (.) or string at Install.pm line 2293, <STDIN> line 5. DBI connect(':','',...) failed: Access denied for user 'jlcopaco'@'localhost' (using password: NO) at /home/jlcopaco/koha/intranet/modules/C4/Context.pm line 411 Can't call method "prepare" on an undefined value at scripts/updater/updatedatabase line 1553. Problem updating database... Can any one help me to rectify this error? Mr. Yesan Sellan Chief Librarian South Asia Institute of Advanced Christian Studies, Kothanur PO Bangalore - 560077 INDIA Alternative Email: yesans@gmail.com Ph: 91-80-2846 5649/5235/5344 Fax: 91-80-2846 5412 ------------------------------ Message: 2 Date: Tue, 30 Oct 2007 13:08:50 -0400 From: "Dan Scott" <denials@gmail.com> Subject: Re: [Koha] Koha became a little more of a certainty last night To: "Joe Atzberger" <ohiocore@gmail.com> Cc: koha@lists.katipo.co.nz Message-ID: <fbb0d11d0710301008n36471abbh80270cd31401a1da@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" On 23/10/2007, Joe Atzberger <ohiocore@gmail.com> wrote: > > On 10/23/07, Dan Scott <denials@gmail.com> wrote: > > > I would strongly suggest posting the code to the sirsiapi repository. > > I'm not a lawyer, but (to my understanding) sirsiapi.org is the only > > SirsiDynix-sanctioned location for hosting code that uses the Unicorn "API" > > to extract information from Unicorn. Sites that have signed a contract with > > SirsiDynix for Unicorn typically have agreed to not reverse-engineer the > > product (meaning that they agree to not try and figure out how the Unicorn > > "API" works) and if they have taken the "API" training course then they have > > agreed to not share any of that information (including code examples) > > outside of the SirsiDynix-sanctioned locations. > > > In my opinion, the repository is an unsuitable venue, since it requires > considerable cost and Sirsi's blessing to even evaluate the (mostly > tentative) code in it. There are less than 40 total contributors to it, all > time. So from a practical perspective, it's the wrong choice. > > As for the legal questions, I'm not a lawyer either, but I do take them > seriously. More seriously, I suspect, than the former management at Sirsi. > > > I attended SD's week-long "API Training" course while in the employ of a > 5-county educational consortium, with whom I had no non-disclosure > agreements at the time, nor any other kind of contract now. (I don't work > there anymore.) Since I was a public employee at the time, literally all > the code I wrote is is a public work-product and like all my correspondence > there, is subject to public disclosure laws. Anyone could ask for it today, > and my former employer would still be obligated to provide copies of it. > > The various warnings from SD about sharing materials did not amount to a > NDA, in my opinion, just an acknowledgment of their copyright to the actual > training materials. (That's funny, since their main docs are a handbook > containing mostly the STDERR "usage" messages from their various > executables, but in an even less readable format.) But even if they *did* > have a bulletproof NDA, I certainly wouldn't have any authority to suspend > state law in order to accept it. > > I would be concerned on behalf of the library posting Unicorn "API" code > > to a public site like SourceForge.net that they could be opening > > themselves up to lawsuits due to breach of contract, if the vendor was to > > get to such a bad state that they started suing their (former) customers. > > > It may be true that SirsiDynix eventually goes the way of SCO, adopting a > litigation-heavy business model. In either case, I don't consider it > ethical to limit my behavior because of this possibility, in particular if > the result is more people stuck paying a litigious vendor they'd prefer to > leave. If spurious liability is the real concern, in the modern era it > would not be difficult to post the code anonymously, or via foreign proxy. > > Any code dealing with the results of using the Unicorn "API" to extract > > data should be openly shareable, because at that point you're just dealing > > with data structures. But I would be worried about openly sharing the actual > > commands, err, "API instructions" required to get that data out of the > > system. > > > Unicorn uses either Oracle or an ancient version of Informix as the back > end database, in conjunction with a bunch of flat files. Nothing > particularly special is required for anyone to access the information > directly. In that way, the API question could be sidestepped entirely. > -- > Joseph Atzberger > SysAdmin, LibLime > http://liblime.com/koha > 1(888)KohaILS > > ps: Needless to say, my comments are my own. > > Fair enough, Joe. We each have our own, non-professional opinion of the legality of publicly publishing code that uses the Unicorn API as part of a migration process. I'm leaning towards the conservative side, whereas you're leaning towards the aggressive side. The original poster has to form their own opinion, and of course I would suggest that they seek out a professional legal opinion on the matter. But then, we've already established that I'm conservative in this regard. Rather than putting the original poster in that position, there is an alternative. As you have the required Unicorn and Koha skills, would you (and your employer) be willing to publish a complete Unicorn-to-Koha migration process & code to koha.org as a contribution from LibLime? I would see this as a great contribution to the open-source ILS community in general. Perhaps more valuable than the technical matters alone, it would be a great test of the matters we've discussed in this thread. -- Dan Scott Laurentian University -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.katipo.co.nz/pipermail/koha/attachments/20071030/2c0ebc73/attac... ------------------------------ Message: 3 Date: Tue, 30 Oct 2007 14:16:33 -0300 From: "Grant Johnson" <FGJohnson@upei.ca> Subject: Re: [Koha] Koha on etch - a pain? To: <koha@lists.katipo.co.nz>, "Beda Szukics" <beda@muri-gries.ch> Message-ID: <47273CC1.5AE3.007F.0@groupwise.upei.ca> Content-Type: text/plain; charset="us-ascii" Hi Beda et al, I've been trying to track this down for about 8 weeks now. Same issue. Apparently the caveats exist in the list archives someplace but I'd sure like them to be pointed out to me. My install works fine except for the addbiblio.pl module. It doesn't matter if I get a record from the "Reservoir or a Z39.50m search I get the same error. The log's don't help me much - But I may not be reading or understanding them properly. Let's keep in touch re this issue - I need to implement on a large scale and need to get this working. Cheers -- F. Grant Johnson 566-0630 / fgjohnson@upei.ca Skype ID = jetsongeorge Systems/Web Coordinator Robertson Library University of Prince Edward Island *************** Attitude is IT! >>> On 10/29/2007 at 4:47 PM, in message <20071029194741.14634.qmail@www.ksobwalden.ch>, "Beda Szukics" <beda@muri-gries.ch> wrote: > Hello people > > Has somebody succeeded in running a koha-2.2.9 recently installed on etch? > > My problem: I can't add new biblios. I had posted some of my problems > before. Now I thougt I'd start again from the buttom up. I deleted the > koha-database in MySQL did a rm -r /usr/lokal/koha and installed koha again. > After entering some library branches, some itemtypes, some borrower > catagories, some z3950-servers and _nothing_ _else_ I tried to add a work > (ISBN 3170183338) and got the same error again: > > [Mon Oct 29 20:32:16 2007] [error] [client 192.168.1.50] Q2 : select > distinct m1.bibid from biblio,biblioitems,marc_biblio,marc_word as > m1,marc_word as m2,marc_word as m3,marc_word as m4,marc_word as m5,marc_word > as m6,marc_word as m7,marc_word as m8,marc_subfield_table as m9 where > biblio.biblionumber=marc_biblio.biblionumber and > biblio.biblionumber=biblioitems.biblionumber and m1.bibid=marc_biblio.bibid > and (m1.bibid=m2.bibid and m1.bibid=m3.bibid and m1.bibid=m4.bibid and > m1.bibid=m5.bibid and m1.bibid=m6.bibid and m1.bibid=m7.bibid and > m1.bibid=m8.bibid and m1.bibid=m9.bibid) and ((m1.word like > 'Neutestamentliches' and m1.tagsubfield in ('245a'))and (m2.word like > 'Arbeitsbuch' and m2.tagsubfield in('245a'))and (m3.word like 'f\xc3\xbcr' > and m3.tagsubfield in('245a'))and (m4.word like 'Religionsp\xc3\xa4dagogen' > and m4.tagsubfield in('245a'))and (m5.word like 'Becker' and m5.tagsubfield > in('245b'))and (m6.word like 'Ulrich' and m6.tagsubfield in('245b'))and > (m7.word like '24' and m7.tagsubfield in('100a'))and (m8.word like 'cm' and > m8.tagsubfield in('100a'))and (m9.subfieldvalue = 'W. Kohlhammer,' and > concat(m9.tag,m9.subfieldcode) in ('300c'))) order by biblio.title ASC term > is Neutestamentliches Arbeitsbuch f\xc3\xbcr Religionsp\xc3\xa4dagogen > Becker Ulrich 24 cm W. Kohlhammer, at > /usr/local/koha/intranet/modules/C4/SearchMarc.pm line 274., referer: > http://bibliotheksverwaltung.kollegium-sarnen.ch/cgi-bin/koha/acqui.simple/a > ddbiblio.pl?oldbiblionumber=0&z3950=1&breedingid=1 > > [Mon Oct 29 20:32:17 2007] [error] [client 192.168.1.50] Arguments must be > MARC::Field object at /usr/local/koha/intranet/modules/C4/Biblio.pm line > 1440, referer: > http://bibliotheksverwaltung.kollegium-sarnen.ch/cgi-bin/koha/acqui.simple/a > ddbiblio.pl?oldbiblionumber=0&z3950=1&breedingid=1 > > [Mon Oct 29 20:32:17 2007] [error] [client 192.168.1.50] Premature end of > script headers: addbiblio.pl, referer: > http://bibliotheksverwaltung.kollegium-sarnen.ch/cgi-bin/koha/acqui.simple/a > ddbiblio.pl?oldbiblionumber=0&z3950=1&breedingid=1 > > I have the feeling koha won't work on etch ... > > Any hints ... Beda > > > _______________________________________________ > Koha mailing list > Koha@lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha -------------- next part -------------- BEGIN:VCARD VERSION:2.1 X-GWTYPE:USER FN:Grant Johnson EMAIL;WORK;PREF:FGJohnson@groupwise.upei.ca N:Johnson;Grant END:VCARD ------------------------------ Message: 4 Date: Tue, 30 Oct 2007 19:40:26 +0100 From: "Beda Szukics" <beda@muri-gries.ch> Subject: [Koha] Re: Koha on etch - a pain? To: "Grant Johnson" <FGJohnson@upei.ca> Cc: koha@lists.katipo.co.nz Message-ID: <20071030184026.18615.qmail@www.ksobwalden.ch> Content-Type: text/plain; charset="utf-8"; format=flowed Hi Grant > I've been trying to track this down for about 8 weeks now. > Same issue. Lucky I'm not the only one. I was questioning my mental health :-) > Apparently the caveats exist in the list archives someplace but I'd sure like them to be pointed out to me. > My install works fine except for the addbiblio.pl module. > It doesn't matter if I get a record from the "Reservoir or a Z39.50m search I get the same error. Same with me. Unfortunately adding new records is what I intend to do every day :-( > Let's keep in touch re this issue - I need to implement on a large scale and need to get this working. I was upgrading a sarge server to etch. Afterwards I tried to install koha on it and had quite some problems with at least one of the required perl modules (I don't quite remember witch one, it had something to do with a new version, witch was buggy). With some help I managed to succeed the installation process. But now I have the mentioned problem. My guess is it has something to do with one of the perl modules, but I have no idea witch one. Unfortunately I wasn't very careful with documenting my steps. It looks like Koha would be the solution witch suited my needs quite well but maybe I have to consider some other solution ... (Do you know one?) Greetings Beda ------------------------------ Message: 5 Date: Tue, 30 Oct 2007 19:54:12 +0100 From: "Beda Szukics" <beda@muri-gries.ch> Subject: [Koha] Re: Koha on etch - a pain? To: "Pablo A. Bianchi" <pablo.bianchi@gmail.com> Cc: koha@lists.katipo.co.nz Message-ID: <20071030185412.18641.qmail@www.ksobwalden.ch> Content-Type: text/plain; charset="utf-8"; format=flowed Hi Pablo > I had installed successfully installed Koha v2.2.5 and v2.2.9 on > Debian etch and now on a Lenny, following the guidelines for Debian > sarge on www.kohadocs.org. I followed that useful document too. I managed to install 2.2.7 on sarge and I managed to upgrade that to 2.2.9 also. But I didn't give much attention to the enconding problem. So I wanted to start all over again and do it properly. (I need a good utf-8 support on Koha because I think that's the only way I can upload my old bibliographical data - I even managed to do so). > The changes are minimal. When did you do your install? Some weeks ago or more than two months? Because I have the feeling the problem has to do with new versions of some perl modules. By the way: Could you do a little test for me? Retrieving a record with the z3950-search I get the data entered in latin1 into the MARC-framework. But I'm quite sure the server delivers the record in utf8 (I checked with MarcEdit). So if you could search ISBN 3170183338 on server aleph.unibas.ch port 9909 database IDS_UTF language MARC21 you should get a title with ü and ä in it. With me the two letters are represented with ? and only if I change the display-encoding in the firefox they appear correctly. I would be most grateful to hear what you get. > Sorry, I couldn't > understand where is the problem on the logs you sent. If you install > it without problem and then it comes using Koha, I think the problem > might be the mysql database. Are you sure you have the right > permissions for all the tables? Yes. I can see everything. I can manage alterations in the sytem parameters. The only thing witch for me didn't work until now is addbiblio Thank you and greetings Beda ------------------------------ _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha End of Koha Digest, Vol 24, Issue 40 ************************************
On 10/30/07, Phillips, Lee <lphillips@bsb.mt.gov> wrote:
I am considering Koha for my mid sized library and I was hoping that there was a way to migrate my Sagebrush catalog into Koha with out having to datamap or bar code.
Don't you always have to datamap when moving from one ILS to another? (Unless you want to pay someone -- like the new ILS vendor -- to do it for you.) As for barcodes, that's a barcode reader issue, not an ILS issue. The barcode reader interprets the barcode and sends it as plain text to the ILS application. Stephen
Hello, I work for the Crawford County Federated Library System, and I thought I'd let you know that we have been migrating successfully from Sagebrush Winnebago/Spectrum to Koha. You didn't mention which Sagebrush ILS you are using. I don't know if they are similar at all. I've written a set of scripts from tranistioning from Winnebago to Koha, and they are available under the GPL as part of the koha-tools project on sourceforge. A number of libraries have used them already, so they can't be that bad ; ) Kyle On Oct 30, 2007 6:30 PM, Phillips, Lee <lphillips@bsb.mt.gov> wrote:
Hello all I want to comment on the SirsiDynix migration possibilities. I have a bunch of library friends in a consortium with Sirsi and I wondered if they were ever going to be able to get out of the proprietary patch hell. I am currently in line to join their group but I am have serious doubts and that this would be a dead end in the near future. I am considering Koha for my mid sized library and I was hoping that there was a way to migrate my Sagebrush catalog into Koha with out having to datamap or bar code. Has anyone had any good experience with these issues? I have 76000 bib records and 14K users. We really need to decide soon Sagebrush doesn't answer their phone any more...if you catch my drift. Lee Phillips Butte Silver Bow Public Library Butte, Montana
-----Original Message----- From: koha-bounces@lists.katipo.co.nz on behalf of koha-request@lists.katipo.co.nz Sent: Tue 10/30/2007 1:00 PM To: koha@lists.katipo.co.nz Cc: Subject: Koha Digest, Vol 24, Issue 40
Send Koha mailing list submissions to koha@lists.katipo.co.nz
To subscribe or unsubscribe via the World Wide Web, visit http://lists.katipo.co.nz/mailman/listinfo/koha or, via email, send a message with subject or body 'help' to koha-request@lists.katipo.co.nz
You can reach the person managing the list at koha-owner@lists.katipo.co.nz
When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha digest..."
Today's Topics:
1. Koha Installation Error - BlueHost.com (Librarian, SAIACS) 2. Re: Koha became a little more of a certainty last night (Dan Scott) 3. Re: Koha on etch - a pain? (Grant Johnson) 4. Re: Koha on etch - a pain? (Beda Szukics) 5. Re: Koha on etch - a pain? (Beda Szukics)
----------------------------------------------------------------------
Message: 1 Date: Tue, 30 Oct 2007 19:52:37 +0530 From: "Librarian, SAIACS" <library@saiacs.org> Subject: [Koha] Koha Installation Error - BlueHost.com To: <koha@lists.katipo.co.nz> Message-ID: <20071030142511.C995910720@daddy.katipo.co.nz> Content-Type: text/plain; charset="us-ascii"
Hi, while trying to install koha on Bluehost.com, I encountered following error;
Use of uninitialized value in concatenation (.) or string at Install.pm line 1685, <STDIN> line 5. Use of uninitialized value in concatenation (.) or string at Install.pm line 1685, <STDIN> line 5. Use of uninitialized value in concatenation (.) or string at Install.pm line 1685, <STDIN> line 5. Use of uninitialized value in concatenation (.) or string at Install.pm line 1685, <STDIN> line 5. Use of uninitialized value in concatenation (.) or string at Install.pm line 1685, <STDIN> line 5.
Use of uninitialized value in concatenation (.) or string at Install.pm line 1709, <STDIN> line 5. Please check permissions in /home/jlcopaco/koha/intranet/scripts/z3950daemon
Use of uninitialized value in concatenation (.) or string at Install.pm line 2293, <STDIN> line 5. DBI connect(':','',...) failed: Access denied for user 'jlcopaco'@'localhost' (using password: NO) at /home/jlcopaco/koha/intranet/modules/C4/Context.pm line 411 Can't call method "prepare" on an undefined value at scripts/updater/updatedatabase line 1553. Problem updating database...
Can any one help me to rectify this error?
Mr. Yesan Sellan Chief Librarian South Asia Institute of Advanced Christian Studies, Kothanur PO Bangalore - 560077 INDIA
Alternative Email: yesans@gmail.com Ph: 91-80-2846 5649/5235/5344 Fax: 91-80-2846 5412
------------------------------
Message: 2 Date: Tue, 30 Oct 2007 13:08:50 -0400 From: "Dan Scott" <denials@gmail.com> Subject: Re: [Koha] Koha became a little more of a certainty last night To: "Joe Atzberger" <ohiocore@gmail.com> Cc: koha@lists.katipo.co.nz Message-ID: <fbb0d11d0710301008n36471abbh80270cd31401a1da@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1"
On 23/10/2007, Joe Atzberger <ohiocore@gmail.com> wrote: > > On 10/23/07, Dan Scott <denials@gmail.com> wrote: > > > I would strongly suggest posting the code to the sirsiapi repository. > > I'm not a lawyer, but (to my understanding) sirsiapi.org is the only > > SirsiDynix-sanctioned location for hosting code that uses the Unicorn "API" > > to extract information from Unicorn. Sites that have signed a contract with > > SirsiDynix for Unicorn typically have agreed to not reverse-engineer the > > product (meaning that they agree to not try and figure out how the Unicorn > > "API" works) and if they have taken the "API" training course then they have > > agreed to not share any of that information (including code examples) > > outside of the SirsiDynix-sanctioned locations. > > > In my opinion, the repository is an unsuitable venue, since it requires > considerable cost and Sirsi's blessing to even evaluate the (mostly > tentative) code in it. There are less than 40 total contributors to it, all > time. So from a practical perspective, it's the wrong choice. > > As for the legal questions, I'm not a lawyer either, but I do take them > seriously. More seriously, I suspect, than the former management at Sirsi. > > > I attended SD's week-long "API Training" course while in the employ of a > 5-county educational consortium, with whom I had no non-disclosure > agreements at the time, nor any other kind of contract now. (I don't work > there anymore.) Since I was a public employee at the time, literally all > the code I wrote is is a public work-product and like all my correspondence > there, is subject to public disclosure laws. Anyone could ask for it today, > and my former employer would still be obligated to provide copies of it. > > The various warnings from SD about sharing materials did not amount to a > NDA, in my opinion, just an acknowledgment of their copyright to the actual > training materials. (That's funny, since their main docs are a handbook > containing mostly the STDERR "usage" messages from their various > executables, but in an even less readable format.) But even if they *did* > have a bulletproof NDA, I certainly wouldn't have any authority to suspend > state law in order to accept it. > > I would be concerned on behalf of the library posting Unicorn "API" code > > to a public site like SourceForge.net that they could be opening > > themselves up to lawsuits due to breach of contract, if the vendor was to > > get to such a bad state that they started suing their (former) customers. > > > It may be true that SirsiDynix eventually goes the way of SCO, adopting a > litigation-heavy business model. In either case, I don't consider it > ethical to limit my behavior because of this possibility, in particular if > the result is more people stuck paying a litigious vendor they'd prefer to > leave. If spurious liability is the real concern, in the modern era it > would not be difficult to post the code anonymously, or via foreign proxy. > > Any code dealing with the results of using the Unicorn "API" to extract > > data should be openly shareable, because at that point you're just dealing > > with data structures. But I would be worried about openly sharing the actual > > commands, err, "API instructions" required to get that data out of the > > system. > > > Unicorn uses either Oracle or an ancient version of Informix as the back > end database, in conjunction with a bunch of flat files. Nothing > particularly special is required for anyone to access the information > directly. In that way, the API question could be sidestepped entirely. > -- > Joseph Atzberger > SysAdmin, LibLime > http://liblime.com/koha > 1(888)KohaILS > > ps: Needless to say, my comments are my own. > > Fair enough, Joe. We each have our own, non-professional opinion of the legality of publicly publishing code that uses the Unicorn API as part of a migration process. I'm leaning towards the conservative side, whereas you're leaning towards the aggressive side. The original poster has to form their own opinion, and of course I would suggest that they seek out a professional legal opinion on the matter. But then, we've already established that I'm conservative in this regard.
Rather than putting the original poster in that position, there is an alternative. As you have the required Unicorn and Koha skills, would you (and your employer) be willing to publish a complete Unicorn-to-Koha migration process & code to koha.org as a contribution from LibLime? I would see this as a great contribution to the open-source ILS community in general. Perhaps more valuable than the technical matters alone, it would be a great test of the matters we've discussed in this thread.
-- Dan Scott Laurentian University
Actually, we were running Winnebago Circ/Cat, an old DOS-based program that our libraries had been running since 1991 or 92. We tried migrating to Spectrum at one point but couldn't get it to work for us. I used the export applications that came with it, however, to get all of our data out except for the patron list (which I did by running a report) and the material records, which I exported though Circ/Cat's export utility. I then used MarcEdit to do most of the processing of the materials. Cheers, Cindy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Cindy Murdock Network Administrator Meadville Public Library | CCFLS http://meadvillelibrary.org | http://ccfls.org Kyle Hall wrote:
Hello, I work for the Crawford County Federated Library System, and I thought I'd let you know that we have been migrating successfully from Sagebrush Winnebago/Spectrum to Koha. You didn't mention which Sagebrush ILS you are using. I don't know if they are similar at all. I've written a set of scripts from tranistioning from Winnebago to Koha, and they are available under the GPL as part of the koha-tools project on sourceforge. A number of libraries have used them already, so they can't be that bad ; )
Kyle
participants (4)
-
Cindy Murdock -
Kyle Hall -
Phillips, Lee -
Stephen Hedges