Terry Reese Gray Family Chair for Innovative Library Services ...

24
Terry Reese Gray Family Chair for Innovative Library Services Oregon State University Email: [email protected] Introduction to MarcEdit, from first run to philosophy

Transcript of Terry Reese Gray Family Chair for Innovative Library Services ...

Terry Reese Gray Family Chair for Innovative Library

Services Oregon State University

Email: [email protected]

Introduction to MarcEdit, from first run to philosophy

What I’ve been up to

Getting Started 1.  Sample Data Files

  Sample MARC records need to be downloaded.   Get them from:

http://oregonstate.edu/~reeset/marcedit/examples/session_data.zip (~5 MB)

  Unzip the data to the Desktop   Right click, Extract all to Desktop.

  Worksheet File   Includes the examples that I’ll be working from:

  http://oregonstate.edu/~reeset/marcedit/examples/marc_worksheet.docx

  When you start MarcEdit for the first time, it will ask you to update. Don’t. Tell it no – then we’ll turn off the automated update checker.

  We’ll use this information later.

Keypoints   What is MarcEdit?

  Background   System Requirements

  Installation Notes   First Run

  Understanding the Application Settings   Editor Settings   Language settings

  Accessing Application Data   MarcEdit Infrastructure   Getting Help   Questions

What is MarcEdit?   Started development in 1999

 Originally coded in 3 programming languages: Assembler (libraries), Visual Basic (UI) and Delphi (COM).

  Initially designed as a replacement for LC’s DOS-based MARCBreakr/MARCMakr software

What is MarcEdit?   Today:

 Written in C#  Continues to be freely available   Supports both UTF/MARC8 charactersets  MARC Neutral  XML aware

Important notes   Installation notes

  As a C# application, it requires the installation of the .NET 3+ framework and MDAC 2.8 components.

  If Using a previous version (prior to January 2009, you should *uninstall* then reinstall MarcEdit

  System Requirements   Any version of Windows that supports .NET   Fully supported on Linux   Partially supported on MAC (using MONO)

  Upgrade/Support   Upgrade cycle is approximately 4-6 months, with bug fixes released as they are

reported.   I answer every question I get about MarcEdit.   Will be starting a listserv for users to ask and answer their own questions.

Installing MarcEdit   Windows:

  Installing from the Windows Installer   32-bit version:

http://people.oregonstate.edu/~reeset/marcedit/software/development/MarcEdit_Setup.msi

  64-bit version: http://people.oregonstate.edu/~reeset/marcedit/software/development/MarcEdit_Setup64.msi

  Installing using a Zip file:   http://oregonstate.edu/~reeset/marcedit/software/development/

marcedit.zip

Installing on Linux   1.1 INSTALLATION FROM ZIP

a) Ensure that the dependencies have been installed 1) Dependency list: i) MONO 2.4+ (Runtime plus the System.Windows.Forms library [these are sometimes separate]) ii) YAZ 3 + YAZ 3 develop Libraries + YAZ++ ZOOM bindings iii) ZLIBC libraries iV) libxml2/libxslt libraries b) Unzip marcedit.zip c) Navigate to the MarcEdit program directory and run linux_bootloader.exe (example, mono linux_bootloader.exe) d) Yaz.Sharp.dll.config -- ensure that the dllmap points to the correct version of the shared libyaz object. e) main_icon.bmp can be used for a desktop icon f) On first run: a) mono MarcEdit.exe b) Preferences tab will open, click on other, and set the following two values: i) Temp path: /tmp/ ii) MONO path: [to your full mono path]

Installing on a Mac MAC OSX INSTALLATION PROCEDURE:

1.2 INSTALLATION FROM ZIP

a) Ensure that the dependencies have been installed

1) Dependency list:

a) Using X11 Server

i) MONO 2.4+ (Runtime plus the System.Windows.Forms library [these are sometimes separate downloads])

ii) Install X11 Server (on the Mac Install Disk)

b) Using Native Carbon Interface

i) Install MONO 2.2.5 (skip version 2.2.6-2.6.1 -- A major bug was introduced crashing any program that uses messageboxes)

c)

i) For Yaz Installation:

a) Install X11 Server (on the Mac Install Disk...this is used by Mac Ports -- but also can be used in rendering MarcEdit if the native Carbon driver causes problems)

b) Install Xcode Developer Tools (current version).

i) Xcode tools are found at the Apple Developer Connection site (http://developer.apple.com/tools/xcode/) or on your Mac Install Disk. The Xcode tools are required by MacPorts

b) Install MacPorts (http://www.macports.org/) -- follow instructions, here: http://www.macports.org/install.php)

i) Make sure that you run the selfupdate on MacPorts (sudo port -d selfupdate)

c) Once MacPorts is installed, install yaz: sudo port install yaz (this will take some time as it will install both your dependencies and yaz to your /opt/local/lib/ directory.

b) Unzip marcedit.zip

c) Navigate to the MarcEdit program directory and run linux_bootloader.exe (example: mono linux_bootloader.exe)

d) Yaz.Sharp.dll.config -- You need to map the yaz3.dll file to the correct Mac equivalent version. On a Mac, if you install Yaz through the MacPorts, you would set the dllmap to the following:

i) <dllmap dll="yaz3.dll" target="/opt/local/lib/libyaz.3.dylib" />

e) How do you setup an icon for Mac?

f) On first run:

a) To run with X11 server (often times, this is faster and works a bit better than the native Carbon Driver)

i) cd [marcedit program directory]

ii) MONO_MWF_MAC_FORCE_X11=1 mono MarcEdit.exe

b) To run with Carbon Driver:

i) cd [marcedit program directory]

ii) mono MarcEdit.exe

c) Preferences tab will open, click on Other tab, and set the following two values:

i) Temp Path: /tmp/ (or a defined user folder)

ii) Mono Path: [to your full mono path -- generally /usr/bin/mono

Setting up MarcEdit   On first run, MarcEdit will ask you to confirm some settings.

These are broken down into 5 areas  MarcEditor   Language   Export  MARCEngine  Other

MarcEdit Language Preferences  MarcEdit’s interface has the ability to be customized to

different languages   All translations volunteer based  Will translate most data – though I still am working to

incorporate all UI elements into the language files   Language files can be edited by hand (just xml) or using

the language file editor.

MarcEdit Language Properties

MarcEdit Language Editor

MarcEdit Export Properties

  Defines MARC import   Can capture port output

from record input (much in the same way OCLC’s Connexion can)

MARCEngine Settings   Of Note:

  Use Diacritics turns mnemonics on and off

  MARCXML XSLT determines how data moves between MarcEdit’s mnemonic format and MARCXML

  XSLT Engine   Saxon.net supports XSLT 2.0   MSXML supports XSLT 1.0, but is

orders of magnitude faster   Unicode Normalization

  New feature designed to allow international users to break away from MARC21’s preferred KD normalization

MarcEdit – Miscellaneous properties

  Properties that affect sorting, notification, file storage.

Application Data   Three classes

 Application Data: configuration data, rules data, etc.

 XSLT Data: XSLT files used to create MarcEdit’s XSLT/XML Conversions

  Language Data: Access to the Language Data files.

Accessing Application Data

Updating MarcEdit   Automatic Updating

introduced in June 2010

  Can be controlled through the Preferences

  Automatically determines proper version to update (32 v 64 bit)

Sharing Application Settings   MarcEdit includes functions to provide the ability to:

  Export Settings   Import Settings

  General Rules:   Export Settings gives you granularity for exporting

  Import Rules:   Imported data overwrites existing data

Exporting Settings

Debugging Tools: MARCSpy

Getting Help   Youtube videos (just search for marcedit)   You can ask me: [email protected]   MarcEdit Listserv:

http://www.lsoft.com/scripts/wl.exe?SL1=MARCEDIT-L&H=MAIL04.GMU.EDU

  Questions