Category: MarcEdit

Posted an updated version of MarcEdit.  Updates a few stylesheets, removes an artificial limit in the Z39.50 client that limited results to 1000 (you now are limited only by available memory), and modified some install behaviors in terms of checking some local config. files for changes before overwriting them.   Also, I need to post…

Quick update to MarcEdit 5.0.  The following has been updated: Support for .pac files in the Z39.50/SRU client I think that this works.  We don’t use pac files anymore — so lets just say that if the documentation that I have was correct — it should work.  Corrected problem with Find function.  (The program wouldn’t…

FYI — a couple of changes to the MarcEdit website.  First, the homepage now pulls its information for the current news from my blog.  Second, I’ve started putting all the MarcEdit documentation into a Wiki.  This should allow me to more easily create documentation as well as export the documentation both in PDF and HTML…

Ok — I’ve done my testing and am sufficiently happy that the new XSLT engine switching works and that the Saxon engine will work with current XSLT stylesheets.  Benchmarks: MARCXML => MARC MSXML Engine 500 Records: first run (1.2 secs) 500 Records: second/third run (0.09 secs) Saxon.NET 500 Records: first run (5.4 secs) 500 Records:…

So I spent a little more time last night doing my final testing before uploading the new build of MarcEdit which includes the choice of utilizing the Saxon or MSXML XSLT engines, and I ended up making a last minute change to make XSLT processing more granular.  When completed, users will now have two locations…

Anyway, once MarcEdit starts allowing users to utilize the Saxon XSLT engine, a new COM property will be made available to allow users scripting to the MARCEngine the ability to modify which engine is in use.  Here’s how it would look: Const MSXML = 1 Const SAXON = 2 lret = 0 Set obj_MARC=CreateObject(“MARCEngine5.MARC21”) obj_MARC.Set_XSLT_Engine…

So I’ve just about finished making the changes to MarcEdit 5.0 to include Saxon’s .NET component into the application.  This will allow users the ability to support XSLT 1.0, 2.0, XPath, Xquery, etc.  By default, the application will continue to utilize the customized version of the System.XML classes provided by default in .NET since they…

I’ve posted an update.  Some of the highlights of the change: New functions added to the MarcEngine/COM objects that allow for the streaming of text into the MARCEngine for direct translation to MARC.  Traditionally, MarcEdit has been a file based tool (i.e., you send it a file and it prints the results to a new…

Ok — I ran the preupdate through some more extensive testing and I’m happy with it.  I’ve also made a few other changes.  The biggest changes: Entity resolution — ability to set entity resolution by translation. Installation improvements — I’ve made some changes to the program so now MarcEdit 5.0 can be installed on machines…