MarcEdit Updates

By reeset / On / In MarcEdit

This weekend, I posted a new MarcEdit update.  This is one of the biggest changes that I’ve made in a while.  While the actual changelog is brief – these changes represented ~17k lines of code Windows (~10K not related to UI work) and ~15.5k lines of code on the OSX side (~9K not related to UI work).

Specific changes added to MarcEdit:

Windows/Linux:

  • Enhancement: UNIMARC Tools: Provides a lite-weight tool to convert data to MARC21 from UNIMARC and to UNIMARC from MARC21.
  • Enhancement: Replace Function: Option to support External search/replace criteria.
  • Enhancement: MARCEngine COM Object Updates

MacOSX

  • Enhancement: UNIMARC Tools: Provides a lite-weight tool to convert data to MARC21 from UNIMARC and to UNIMARC from MARC21.
  • Enhancement: Replace Function: Option to support External search/replace criteria.
  • Update: Installation has been changed to better support keeping configuration information sync’d between updates.
  • Bug Fix: Add/Delete Function — Add field if not a duplicate:  Option wasn’t always working.  This has been corrected.

I’m created some videos to demonstrate how these two elements work, and then a third video showing how to use the Add Field if not a duplicate (added in the previous update).  You can find these videos here:

Add Field If Not a Duplicate
URL: https://youtu.be/ObRKgAD9ye8

MarcEdit’s UNIMARC Tools:
URL: https://youtu.be/4rdzOCAwhSU

MarcEdit: Batch Replacement using External Criteria
URL: https://youtu.be/uJB9Uqg6bJs

You can get the changes from the downloads page or through MarcEdit’s automated update tool.

–tr

3 thoughts on “MarcEdit Updates

  1. This is fantastic, Mr. Reese! Thank you! If you could see your way to allow the 9xx fields to also be converted back and forth between MARC21 and UNIMARC, that would be most helpful. Or, if that is more work than is feasible, perhaps allowing the 9xx to remain intact somehow?

    Best regards, Charles

    1. Hi Charles,

      So, I know just enough UNIMARC to be dangerous — and what is here, is pretty much the extent of my experience working with the format. Since the 9xx fields are locally defined in MARC21, there is no guidance around how they may or may not map into UNIMARC, so I’ve left them out. If they represent a 1-1 capture, I can add that to the conversion templates. If there is more to it than that, then this is where I’ll need someone that actually uses UNIMARC to help provide some additional guidance.

      –tr

      1. I see. For my purposes, I believe a 1-1 capture is what I would be after. I mean, a straight transfer of the content of the field as it is, with only delimiter and UNIMARC formatting. In any case, I appreciate your efforts on this.