Each vendor probably has a slightly differnt 'Third Party Export Add-on' policy that will come into play. At first blush, I suspect vendors will not make a distinction between creating/using a tool and publishing such a tool/method openly. It's rare in my experience for a Vendor to restrict re-distribution of third-party tools that are otherwise authorized. i.e. "You can write and use a tool with our product, just do not tell anybody else you are doing it" clauses are probably pretty rare. Generally we are allowed to write such tools or we are not.
Something tells me that this will be a case-by-case issue but I agree that we should pass this by Bradly and Tony however. Steve Wills -----Original Message----- From: Tara Robertson [mailto:[email protected]] Sent: Tuesday, August 7, 2012 02:49 PM To: 'Evergreen Discussion Group' Subject: Re: [OPEN-ILS-GENERAL] Symphony extraction scripts Hi, This is not an area I'm an expert in at all, however over the years I've heard concerns from data migration specialists about publicly posting their data extraction methods and migration scripts as they were worried that the proprietary companies might sue them. I have also heard from people who used to work for proprietary vendors who were worried that they might be sued by their former employers. I don't think that posting extraction scripts is the same things as reverse engineering a proprietary system, but I know that various people have felt that this was too risky in the past. I took a quick look and I don't see extraction scripts posted on the Koha community website. Perhaps it might be prudent to check with the SFC and get some advice on this? My two cents, Tara On Tue, Aug 7, 2012 at 8:38 AM, Lori Bowen Ayre <[email protected]> wrote: Hi All, We've talked about finding a place to put data extraction scripts for the various ILSs and I don't think we decided anything yet. Can we upload zip files to the wiki? I ask because what I have here is a zip file that contains three files that can be used for extracting data from your Symphony system. I've attached the files to this message with a trailing Z to the file name. So rename the files you are going to use by removing that z on the extension first. Did they come through? You can get the files from here (I hope): https://www.dropbox.com/sh/p8h4sm5bgk4xz2x/ClAUltwlA- Instructions for using the files in that in the Dropbox Folder and are also below. If you can use these now, great! For the future, where do others think we should keep things like this???? Dropbox doesn't seem like the ideal method but I couldn't figure out a better way and at least that way I can make sure they remain secure. Your suggestions welcome! Lori Instructions for Using the Scripts: Scripts for bothWindows server and Unix servers included. You need command line access toeither the Windows box or the Unix machine. You MUST be logged in as the "sirsi"user (called sirsi). On Windows, I think you can do this as Administrator also?Do NOT run it as root (unless you use an "su - sirsi") On Windows - put the 3 scripts, extract_all.batand extract_all.sh, joinflatbib.plonto the server and run the extract_all.batfile. On Unix - just run extract_all.sh (make sure itis executable, 755) and make surejoinflatbib.plis there and executable. Here’s what the script does: 1.Creates a directory/sirsi/Unicorn/WebCat/Tmpdocs/Data to put the data in. 2.Dumps out the bib data in flat format (text)with holdings, one file for each bibliographic format in Unicorn(that is, BOOK, SERIAL, VM etc.). 3.Then does the same again but this time inISO2709 MARC21. 4.Gets the catalog keys of the shadowedtitles/items in Unicorn in case you want to hide these items from thepublic in the new ILS. 5.Extracts the authority records in ISO2709 MARC(again, one file for each format, TOPIC, PERSONAL, CORPORATEetc.) 6.Dumps the users/borrowers in a flat format. 7.Charges (issues, loans, whatever you want tocall them!) and the holds in flat format. 8.After that, there is a whole load of reportswith statistics (for info only) and a dump of the library's policies (itemlocations, borrower categories etc.). 9.Then, allthe acquisitions stuff comes out (vendors, funds, etc) Finally,it tars and zips all the data up so that you can easily transport it off the server to work with it onthe new system. Therearen't any fines/bills in that script. You can get those if you want by adding: # Get the Bills selbill 2> selbillflat.log | dumpflatbill >flatbill.txt 2>dumpflatbill.log =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-= Lori Bowen Ayre // Library Technology Consultant / The Galecia Group Oversight Board & Communications Committee / Evergreen (707) 763-6869 // [email protected] Availability: http://tungle.me/lori.ayre Specializing in open source ILS solutions, RFID, filtering, workflow optimization, and materials handling =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
