Sep 022014
 

I’ve just posted a new update to MarcEdit.  In addition to fixing the following three issues:

  • Check URL crashes when running…this has been fixed.
  • Delimited Text Translator doesn’t show finishing message…fixed
  • Debugging messagebox shows when processing mnemonic files not using MarcEdit’s documented format.

In addition to these three bug fixes, MarcEdit is including a new tool called MARCNext for testing BibFrame principles. Please note, the BibFrame Testbed currently *does not* work on the MAC platform under MONO.  This is due to an incompatibility in the current version of saxon with the runtime.  It appears that downgrading the version will correct the problem, but I need to make sure there are not any unforeseen issues.  I’ll be working to correct this during the week.

I’ve recorded a couple videos documenting the new functionality.  You can find there here:

You can download the update via MarcEdit’s automated update tool or view the MarcEdit downloads page at: http://marcedit.reeset.net/downloads

–tr

 Posted by at 7:58 pm
Aug 252014
 

As I noted in my last post (http://blog.reeset.net/archives/1359), I’ll be adding a new area to the MarcEdit application called MARCNext.  This will be used to expose a number of research tools for users interested in working with BibFrame data.  In addition to the BibFrame Testbed, I’ll also be releasing a JSON Object Viewer.  The JSON Object Viewer is a specialized viewer designed to parse JSON text and provide an object visualization of the data.  The idea is that this tool could be utilized to render MARC data translated into Bibframe as JSON for easy reading.  However, I’m sure that there will be other uses as well.  I’ve tried to keep the interface simple.  Essentially, you point the tool at a JSON file and the tool will render the file as objects.  From there, you can search and query the data, view the JSON file in Object or Plain text mode, and ultimately, copy data for use elsewhere. 

image

Some additional testing needs to be done to make sure the program works well when coming across poorly formed data – but this tool will be a part of the next update.

–tr

 Posted by at 9:31 pm
Aug 232014
 

While developing MarcEdit 6, one of the areas that I spent a significant amount of time working on was the MarcEdit Research Toolkit.  The Research Toolkit is an easter egg of sorts – it’s a set of tools and utilities that I’ve developed to support my own personal research interests around library metadata – specifically, around the future of library metadata including topics the current BibFrame testing and linked data.  I’ve kept these tools private because they tend to not be fully realized concepts or ideas and have very little in the way of a user interface.  Just as important, many of these tools represent work being created to engage in the conversation that the library community is having around library metadata formats and standards, so things can and do change or drop out of the conversation and are then removed from my toolkit.

While developing MarcEdit 6, one of the goals of the project was to find a way to make some or parts of these tools available to the general MarcEdit community.  To that end, I’ll be making a new area available within MarcEdit called MARCNext.  MARCNext will provide a space to make proof of concept tools available for anyone to use, and offer a simple to use interface that anyone can use to test new bibliographic concepts like BibFrame. 

Presently, I’m evaluating my current workbench to see which of the available tools can be made public.  I have a handful that I think may be applicable – but will need some time to move them from concept to a utility for public consumption.  With that said, I will be making one tool immediately available as part of the next MarcEdit update, and that will be the BibFrame Testbed.  This is code that utilizes the LC XQuery files being developed and distributed at: https://github.com/lcnetdev/marc2bibframe with a handful of changes made to provide better support within MarcEdit.  These are my base files that will enable librarians to easily model their MARC metadata in a variety of serializations.  And using this initial work, I’ll likely add some additional serializations to the list. 

I have two goals for making this particular tool available.  First and foremost, I would like to enable anyone that is interested the ability to take their existing library metadata and model it using Bibframe concepts.  Currently, Library of Congress makes available a handful of commandline tools that users can utilize to process their metadata – but these tools tend to not be designed for the average user.  By making this information available in MarcEdit – I’m hoping to lower the barrier so that anyone can model their data and then engage in the larger discussion around this work. 

Secondly, I’m currently engaging in some work with Zepheira and other early implementers to take Bibframe testing mainstream.  Given the number of users working with MarcEdit, it made a lot of sense to provide tools to support this level of integration.  Likewise, by taking the time to move this work from the concept stage, I’ve been able to develop the start of a framework around these concepts. 

So how is this going to work?  On the next update, you will see a new link within the Main MarcEdit Window called MARCNext. 

image 
MarcEdit Main Window

Click on the MARCNext link, and you will be taken to the public version of the Research Toolkit.  At this point, the only tool being made publically available is the BibFrame Testbed, though this will change.

image 
MarcEdit’s MARCNext Window

Selecting the BibFrame Testbed initializes a simple dialog box to allow a user to select from a variety of library metadata types and convert them using BibFrame principles into a user-defined serialization. 

image 
BibFrame Testbed window

As noted above, this test bed will be the first of a handful of tools that I will eventually be making available.  Will they be useful to anyone – who knows.  Honestly, the questions that these tools are working to answer are not ones that come up on the list serv, and at present, aren’t going to help much in one’s daily cataloging work.  But hopefully they will enable every cataloger that wants to, the ability to engage with some of these new metadata concepts and at least take their existing data and see how it may change utilizing different serializations and concepts.

Questions – feel free to ask.

–tr

 Posted by at 9:36 pm
Aug 142014
 

Latest update has been posted.  The following has been fixed:

  • Bug Fix: Delimited Text Translator — The Edit LDR, Load Template, and AutoGenerate buttons were not responding.  This has been corrected.
  • Bug Fix: MARCCompare — when processing data with improperly formatted mnemonic data, the program doesn’t correctly trap the generated formatting error.
  • Bug Fix: Edit Field Data: When processing control fields by position, the replacement would generate duplicate data.
  • Bug Fix: MARC Tools — the MARC8 and UTF8 conversion checkbox would become grayed out when selecting new functions from the function list.
  • Bug Fix: Task Lists — The Delete Subfield Text task wasn’t respecting the option to delete the entire subfield option.
  • Performance Fix: Re-did the paging code so that for files under 50 MBs, the program utilizes a different, faster method of reading data.  This method utilizes more memory because data processing happens in memory rather than on disk, but this gives a 50 to 75% improvement in speed over the past method.
  • Bug Fix: Classify Tool — when processing dates, if the 008 wasn’t present, the program wouldn’t capture date information from the 260 or 264.
  • Enhancement: Classify Tool — The program now utilizes prefixes within the control number to eliminate false control number matches.
  • Bug Fix: Merge Records Tool — when merging on the 035, the program wasn’t properly normalizing all data for matching.

You can get the update automatically or from the download page at: http://marcedit.reeset.net/downloads

–tr

 Posted by at 10:02 pm
Jul 222014
 

What is MARCCompare/RobertCompare?

Very rarely do I create programs for individuals to meet very specific user needs.  I’ve always taken the approach with MarcEdit that tools should be generalizable, and not tied to a specific individual or project.  RobertCompare was different.  The tool was created to support Mr.Robert (Bob) Ellett’s (ALA Tribute, Link to Dissertation Record in WorldCat) research for his Ph.D. dissertation, and only after completion, was the tool generalized for wider use. 

When I moved MarcEdit from the 4.x to the 5.x codebase, I dropped this utility because it had seemed to have run its course.  This was something Bob would periodically give me a hard time about — I think that he liked the idea of RobertCompare kicking around.  Of course, the program was terribly complicated, and without folks asking for it, converting the code from assembly to C# just wasn’t a high priority. 

Well, that changed last year when Bob suddenly passed away.  I liked Bob a lot — he was immeasurably kind and easy to get along with.  After his passing, I decided I wanted to bring RobertCompare back…I wanted to do something to remember my friend.  It’s taken a lot more time than I’d hoped, in part due to a move, a job change, and the complexity of the code.  However, after an extended absence, RobertCompare is being reintroduced back into MarcEdiit with MarcEdit 6.0. 

MARCCompare/RobertCompare 2.0

The original version of RobertCompare was designed to answer a very specific set of questions.  The program didn’t just look for differences between records, but rather, utilizing a probability engine, made determinations regarding the types of changes that had been made in the records.  Bob’s research centered around the use of PCC records at non-PCC libraries, and he was particularly interested in the types of changes these libraries were making to the records when downloading them for use.  The original version of RobertCompare was very good at analyzing record sets and generating a change history based on the current state of the records.  But the program was incredibly complicated and slow…really, really slow. 

In order to make this tool more multi-use, I’ve removed much of the code centered around probability matrix, and instead created a tool that utilizes a differential equation to generate an output file that graphically represents the changes between MARC files.  The output of the file is in HTML and at this point, pretty simple – but has been created in a way that I should be able to add additional functionality if this tool proves to have utility within the community.

So what does it look like?  The program is pretty straightforward.  There is a home menu where in identify the two files that you want to compare, and then a place to designate a save file path. 

image
Figure 1: MARCCompare/RobertCompare main window

The program can take MARC files and mnemonic files and compare them to determine what changes have been made between each record.  At this point, the files to be compared need to be in the same order.  This has been done primarily for performance reasons, as it allows the program to very quickly chew through very large files which was what I was looking for as part of this re-release. 

As noted above, the output of the files has changed.  Rather than breaking down changes into categories in an attempt to determine if changes were updated fields, new fields or deleted field data – the program now just notes additions/changes and deletions to the record and outputs this as an HTML record.  Figure 2 shows a sample of what the report might look like (format is slightly fluid and still changing). 

image 
Figure 2: MARCCompare/RobertCompare output

Final thoughts

While I’m not sure that RobertCompare was ever widely used by the MarcEdit community, I do know that it had its champions.  Over the past year, I’ve heard from a handful of users asking about the tool, and letting me know that they still have MarcEdit 4.0 on their systems specifically to utilize this program.  Hopefully by adding this tool back into MarcEdit, they will finally be able to send MarcEdit 4.x into retirement and jump to the current version of the application.  For me personally, working on this tool again was a chance to remember a very good man, and finish something that I know probably would have given him a good laugh.  

–TR

Jun 212014
 

One of the changes that will be present in MarcEdit 6 is an expansion of the Material Types Report.  Currently, the program provides an option to allow users to generate a report detailing the type of record as designated by the LDR and 008.  This allows users to get a quick snapshot of how the records are coded within the file.  One of the limitations of this process has been that these reports are read only.  Once a user ran a report, if they wanted to see, for example, all the Computer Files – they would need to construct that query themselves. 

In MarcEdit 6, this will change.  The program has reorganized the Materials Report menu, creating a new entry for Generating the Report, an a new set of subcommands that allow users to designate a material type and find the records that correspond to that type. 

image
Figure 1: Finding the Material Types Report

image
Figure 2: Material Type Report Results.  One new enhancement has been the ability to copy data to the clipboard from this window.  This impacts all functions that utilize this generic results window.

image
Figure 3: Menu to Find Records of a specific type

image
Figure 4: Material Results query and results

This is a request that comes up periodically – hopefully, these changes will make querying and examining record types easier for users.

–tr

 Posted by at 10:00 pm
Jun 212014
 

Thought I’d give the folks that are interested an idea of where I am with the MarcEdit update.  In terms of new features, that is pretty much set at this point.  I have one feature request regarding conditional field editing by field position that I’m still mulling over, but otherwise, I’m pretty much finished.  The last things todo right now is to finish the installers for Linux and Mac systems, and then make sure that the installs work exactly as I want them to.  One thing that I have found with the Linux and Mac systems – the Z39.50 dependencies are one of the biggest dependency hurdles (I can’t really automate their install well) – so I’m working on a method of creating a Z39.50 web service at marcedit.reeset.net that I can then call via non-Windows systems.  This will be functionally equivalent with the locally loaded Z39.50 libraries, though there will likely be a performance hit (small one, you shouldn’t notice too much) – but will remove a major dependency making the program much easier to install.  Also, I’m just not sure how often the Z39.50 client actually gets used at this point (when can we finally phase that out) – so I’m hoping this will be a good enough compromise. 

MarcEdit on Linux:

At this point, I’m testing MarcEdit on Suse and it looks to be going well.  The installer is now a single .sh file, that will expand creating the directory, run the bootloader, and create a shortcut on the desktop.  What it doesn’t do yet is make sure Mono is installed – not certain if that will be part of the first installer, but this should get you to the point that if you have mono installed, you will just run the installer and an icon will be on the desktop ready to be activated. 

Couple of the current screenshots:

image
Figure 1: Start Screen on Linux

image
Figure 2: MarcEditor

image
Figure 3: Delimited Text Translator

image
Figure 4: RDA Helper

image

Figure 5: MARC Tools Window

At this point, on Linux, the version looks and feels pretty much like you’d expect the Windows version to work.  I’m testing performance, especially with larger files in the Editor (for rendering) and it looks like all UI issues should be dealt with in MarcEdit 6.  I’m starting the process of doing the same type of testing using the current version of OS X with Mono 3.4 – hopefully I’ll see the same UI smoothness.

Some Stats on the Update

Some stats – refactoring, I’ve removed close to 15,000 lines of code streamlining older processes (these are things you likely won’t see, outside of maybe a few things being faster).  New code – I’ve written close to 27,000 lines of code developing new features or enhancements for this update.  Much of this has been around multiple platform support, new functions in the editing tools, etc.  Once MARCCompare has been completed, that number will jump to around 37,000 lines – so this will be a significant update in which a number of tools and functions have had significant revisions made too improve code maintenance, performance, add new features or correct bugs, or all three. 

Below you will find a list of topics the represent some of the areas where changes are being made.  This is a subset of a report from the internal issue tracker I use for tracking issues/enhancement requests.  At this point, it still looks like this update will be scheduled for Mid-July.

–tr

 

Tracking Report

Summary

Category

Sharing Tasks which refer to other tasks

Bug

Add/Delete Field — Find What Field

Bug

Refresh the Delimited Text Translator

Enhancement

MARC Tools window refresh

Performance

Changing Capital Letters with Diacritics to lower case

Bug

RDA Helper

Bug

Script Wizard — add/delete field with modifier

Bug

Adding multiple fields in the Add/Delete Function

Enhancement

UI Issue — Validation

Bug

Task List — Swap Field not saving Process one per field

Bug

Allow tasks to have comments

Enhancement

Edit Subfield and Swap Field Edits

Enhancement

Task Manager & Task List tool

Enhancement

Task List: Allowing Description to show in Task Manager and Task Editor

Enhancement

Plugin Updates — make it easier to track plugin updates

Enhancement

Ability to import RIS format

Enhancement

Mac Fonts

Bug

Prompt for confirmation of task deletion

Enhancement

Koha Integration – unable to authenticate when using self-signed certificates

Enhancement

merge records tool — customizing match points causes merges to not occur

Bug

Validate Temp File Path Before Generating files

Bug

 Posted by at 8:53 am
Jun 122014
 

This summer, I have been spending a lot of my free development preparing MarcEdit to make the transition from 5.9 to 6.0.  This will be a big update, and at the same time, and update that I’m not sure folks will necessarily see many of the changes.  But maybe that will be a good thing, I don’t know.  So, a couple of notes about the update.

User Interface Changes

So, MarcEdit has been around for a very long time – 1999 to be exact.  Because of that, there are some very old tools in the application…tools who’s interface haven’t been updated in 6-7 years – even if the underlying functionality has changed.  Well, I’m taking the time to refresh a number of the forms found within the application.  The places where most users will see these changes are in the Delimited Text Translator (the Windows 2000 Wizard interface is going away) and the MARC Tools interface.  There are a few others that will see updates; but these are the two that you’ll see for sure.

Delimited Text Translator (screen 1)

image

Delimited Text Translator (screen 2)

image

MARC Tools Revisions (proposed)

image

These are proposed changes – but are being done to make the look more consistent as well as make some screens easier to work with (the MARC Tools window for instance was getting really long).

Bug fixes

For two months, I’ve been going through my internal ticketing system, and closing every open issue.  When I post this update, every bug report that has been saved, will be closed.  This has required rewriting a lot of code within the application – which for many older functions – is definitely a good thing.  At present – this means that 13 bug tickets have been closed.  All are minor, with general workarounds – but this should have a practical impact for folks.

New features

At present, 7 enhancements/new features have been added to the program.  The remaining change to be completed (if it’s completed) will be the re-inclusion of MARCCompare (or RobertCompare as I fondly referred to it).  This is a specialized diff tool for comparing MARC records that is smarter than just a plain diff because it takes into account MARC structured data.

Cross Platform Work

One of the pseudo supported options in MarcEdit has been the ability to run the tool on non-windows platforms.  Being written in C#, the program runs fine under MONO on both Linux and Mac systems.  However, this has traditionally worked much better for Linux users because: MONO was created by a bunch of people on Linux, and I work a lot on Linux so I would test there.  One of the big efforts this time around has been to try and identify where UI issues or other issues exist and put solid support for folks interested in working with MarcEdit within non-Windows environments.  The tool will likely always run best there – but I’d like to provide a version with installers, for both Linux and Mac systems and 6.0 will represent the first attempt at that.  I’ll admit, I have some trepidation around doing this and providing more formalized support because I don’t own a Mac so I won’t get to test and do the kind of dedicated development as I might like – but I have regular enough access to one that I’m willing to give it a go.  At the very least – users will get a much easier process for installing and that at least is a win.

Go live date

This is still in the air a little bit.  I’d hoped for early July but my wife and I are buying a house, I’m doing a little travelling for work – so this is definitely pushing things back.  But ideally, these changes will start being rolled out in July 2014.

If you have questions – feel free to give me a holler.

-tr

 Posted by at 1:15 am
Apr 042014
 

One of the new functions in MarcEdit is the inclusion of a Field Edit Data function.  For the most part, batch edits on field data has been handled primarily via regular expressions using the traditional replace function.  For example, if I had the following field:

=999  \\$zdata1$ydata2

And I wanted to swap the subfield order, I’d use a regular expression in the Replace function and construct the following:
Find: (=999.{4})(\$z.*[^$])(\$y.*)
Replace: $1$3$2

This works well – when needing to do advanced edits.  The problem was that any field edits that didn’t fit into the Edit Subfield tool needed to be done as a regular expression.  In an effort to simplify this process, I’ve introduced an Edit Field Data tool.

image

This tool exposes the data, following the indicators, for edit.  So, in the following field:
=999  \\$aTest Data

The Edit Field Data tool could interact with the data: “$aTest Data”.  Ideally, this will potentially simplify the process of doing most field edits.  However, it also opens up the opportunity to do recursive group and replacements.

When harvesting data, often times subjects may be concatenated with a delimiter, so for example, a single 650 field may represent multiple subjects, separated by a delimiter of a semicolon.  The new function will allow users to capture data, and recursively create new fields from the groups.  So for example, if I had the following data:
=650  \7$adata – data; data – data; data – data;

And I wanted the output to look like:
=650  \7$adata – data
=650  \7$adata – data
=650  \7$adata – data

I could now use this function to achieve that result.  Using a simple regular expression, I can create a recursively matching group, and then generate new fields using the “/r” parameter.  So, to do this, I would use the following arguments:
Field: 650
Find: (data – data[; ]?)+
Replace: $$a$+/r
Check Use Regular Expressions.

 image

The important part of the above expression is in the Replacement syntax.  To tell MarcEdit that the recursion should result in a new line, the mnemonic /r is used at the end of the string to tell the tool that the recursion should result in a new line.

This new function will be available for use as of 4/7/2014. 

–tr

 Posted by at 8:44 pm
Mar 192014
 

After posting the update last night, a user noted that the Delimited Text Translators 008 generation utilized some older defaults that were causing some validation issues.  So, I’ve posted a limited update to correct this specific problem.

If you have automatic updating turned on, MarcEdit will prompt you automatically.  Otherwise, you can download from:

–tr

 Posted by at 9:38 pm