MarcEdit 5.6 available

By reeset / On / In MarcEdit

MarcEdit 5.6 has been posted for download.  If you are currently running MarcEdit via Windows and have the automatic updating function enabled, you’ll be notified of the update automatically. 

The current changes to the application are as follows:

  • Bug Fix: Swap fields tool — when moving data from a variable field to a control field using a find criteria, the newly created control field would inherit the indicators and subfields of the swapped variable field.
  • Bug Fix: Screen resolution — When using MarcEdit with the DPI resolution set above 100%, the controls were not redrawing properly
  • New Feature: MarcEdit includes a tool for querying registered xslt crosswalks and downloading them for use with MarcEdit  (see: http://blog.reeset.net/archives/964)
  • Enhancement: MARCEngine diacritics expansion — MarcEdit’s diacritics engine has been expanded to recognize ~70 new diacritic mnemonic codes. (http://blog.reeset.net/archives/966)
  • Enhancement: MarcEditor Intellisense — when placing a { in the MarcEditor, MarcEdit will now display a list of available diacritic mnemonic codes. (http://blog.reeset.net/archives/968)
  • Enhancement: MarcEdit Options: Users can disable the MarcEditor Intellisense by modifying the value found in the MarcEditor tab.
  • Enhancement: MarcEdit MARCValidator: When validating data from within the MarcEditor, a new option (identify invalid records) has been made available.  This function specifically looks for structural issues with the mnemonic file format that can cause issues related to record compilation or cause issues related use of the global functions.  Errors are reported and ranked based on their likelihood of causing record compiling issues, using the scale of Warning, Serious, Critical.
  • Enhancement: Updated Help documentation.
  • Enhancement: Users can now place data marked for the 260c into the 008 when using the delimited text translator.
  • Informative: MarcEdit version number has changed to 5.6

 

For information about individual updates, please view subsequent posts.

–TR