One of the most common questions posed by potential MarcEdit users is around the scope of the application. \u00a0Technical services and metadata librarians utilize a lot of different tools to edit, create, and manipulate their metadata…how is MarcEdit different and what does it offer that other tools might not? \u00a0It’s a great question…technology is changing rapidly and the library metadata environment is currently in a state of flux. \u00a0Understanding what MarcEdit does and does not do can help a potential user determine if the tool is worth investing the time and effort to learn. \u00a0So exactly what is MarcEdit used for?<\/p>\n

$\"connexion\"$ <\/a>

Figure 1: OCLC Connexion record display<\/p><\/div>\n

Many systems and tools have been designed in a way that they are unable to separate the physical presentation of a bibliographic record from the physical format. \u00a0Figure 1 provides a screen shot from OCLC’s Connexion interface, and would be an interface that metadata librarians would be familiar. \u00a0The problem is that this is what many librarians associate with MARC — they see this display, the tags and their inherent meanings with the AACR2 rules, and conflate the two together. \u00a0For MarcEdit’s purposes, MARC is used to describe the binary format, as seen in Figure 2.<\/p>\n

$\"hex\"$ <\/a>

Hexadecimal representation of a MARC Record<\/p><\/div>\n

For a good explanation of the MARC bibliographic format please see, “Understanding MARC”[ref]U.S. Library of Congress, Understanding MARC,\u00a0 http:\/\/www.loc.gov\/marc\/umb\/<\/a>[\/ref].<\/p>\n

Of course, the discussion of MARC is all well and good, but exactly what does MarcEdit do and can it help me? \u00a0The short answer, if your library utilizes MARC or XML-based library data, MarcEdit likely can be useful within your environment. \u00a0As noted above, MarcEdit was designed to help facilitate the creation, editing, and manipulation of MARC data…large sets of MARC data. \u00a0While libraries have done a very good job of creating shared metadata catalogs they have had less success creating local metadata repositories that can easily be manipulated. \u00a0MarcEdit was designed to fill that niche. \u00a0Consider the following scenarios:<\/p>\n

Scenario<\/i>\u00a01:<\/em><\/p>\n

Your library purchased\u00a0eBooks\u00a0from vendor X. \u00a0Vendor X provides provider neutral MARC records for each of the items that your library purchases. \u00a0However, before these records can be added to your local library catalog, you need to add a local specific note, generate call numbers, and remove all but one of the URLs in the record (since only one is applicable to your library). \u00a0<\/em><\/p>\n

Scenario<\/i>\u00a02:\u00a0<\/em><\/p>\n

Your library utilizes DSpace to store and catalog all your institution’s theses and dissertations. \u00a0In addition to having the metadata in your Institutional Repository, you’d like to load records into your local library catalog, but don’t want to have to copy and paste text from one system to another.\u00a0<\/em> The above scenarios play out everyday across libraries across the world. \u00a0Libraries are provided metadata by vendors or have existing metadata in other systems and are looking for workflows to simplify the process of editing that data. \u00a0This is what MarcEdit can do for libraries. \u00a0MarcEdit provides a set of built in tools that could allow a librarian to process all the records provided by a vendor in one or two easy steps or can facilitate the transformation and ingest of library metadata into both non-MARC and MARC formats. \u00a0MarcEdit was designed to fill in gap for libraries, the ability to easily process large batches of library metadata — and demystify the batch editing process so that the work can be done by metadata librarians and not library technology.<\/p>\n

Getting Started<\/h3>\n
Like most programs, users looking to use MarcEdit need to make sure that their system is capable of running the application. \u00a0This means knowing a little bit about the environment in which the application will be run. \u00a0What is the operating system being utilized? \u00a0If it is Windows, is it Windows XP SP3+ (MarcEdit 6-), or Windows Vista+ (MarcEdit 7+)? \u00a0On OSX, 10.8+ (Version 2-) or MacOS 10.10+ (Version 3+)? \u00a0Do the Windows machines already have the .NET framework installed? \u00a0Is the machine managed locally by you, the individual, or is the machine part of a larger enterprise environment and managed by your local IT system? \u00a0Is my operating system use a 32 or 64 bit architecture? \u00a0Do I think that I will be using MarcEdit’s developers tools to create scripts to automate the program? \u00a0These are all questions that go into deciding the specific flavor of MarcEdit to install. \u00a0And while that may all sound complicated, it’s really not. \u00a0Once most users make their way to the MarcEdit download page, the correct version to download and use is fairly straightforward.<\/p>\n
For users within an enterprise environment, like a university technical services department, where one’s machines are managed by a central IT, the MarcEdit installer\/application does support push installation. \u00a0What’s more, the program includes the capability to provide automated software updates utilizing system group policies. \u00a0More information will be provided about this process in Chapter 3: Understanding the MarcEdit Preferences.<\/p>\n
<\/p>\n\n\n\n
$\"tip\"$ <\/a><\/td>\n MarcEdit is written in C# and designed to run on any system with a flavor of the .NET Framework installed. For Windows users, the .NET framework is considered a part of the current generation operating system, though you may need to update to a current version of the framework if out of date. If you are running a Linux System, you will want to go to http:\/\/www.mono-project.com\/Main_Page<\/a> to download the Mono Framework, and open source alternative to Microsoft’s .NET framework, for your particular operating system. \u00a0Mac users will find their own download, which requires no additional downloads (save for Z39.50 components)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
<\/p>\n
Because of the ubiquity of the .NET and Mono frameworks, most current generation Windows and Linux systems will likely have some variation available for use. \u00a0for most users, you will just need to determine if your version of the framework will support MarcEdit. \u00a0If you are unsure what version of the framework you may have installed, or are unsure if you have a version of the framework installed, MarcEdit’s installer does evaluate your operating system and will warn you if specific dependencies are not available or are out of date.<\/p>\n
<\/p>\n
System Requirements<\/h3>\n
Prior to MarcEdit 5+, users had to know a great deal about their systems prior to installing MarcEdit. \u00a0In previous versions, MarcEdit made use of a variety of operating system components that may or may not be installed as part of the system. \u00a0For example, MarcEdit 3 and 4, required users to ensure that they had installed the msxml libraries, MDAC, and the Excel OBDC redistributable. \u00a0Their were other optional components that previous versions of MarcEdit may also use, but the program could function if they were missing. \u00a0Unfortunately, the wide range of system requirements sometimes made adoption of the application difficult.<\/p>\n
For MarcEdit 5 and 6, the only system requirement is the presence of the .NET Framework, specifically, the 4.0 Client Profile or later. For MarcEdit 7, the requirements have changed, as the program takes advantage of a number of new .NET language elements, so users must have version 4.6.1+ of the .NET Framework installed. Much like an application developed in Java, the .NET framework includes all the necessary requirements for MarcEdit to function. \u00a0This alleviates the user from having to install multiple pre-requisites and hopefully simplifies the installation processes. \u00a0The downside to using a framework like the .NET framework is that MarcEdit can only run on systems that are supported by the framework itself. \u00a0This means that very old versions of Windows (XP SP 2 and lower) will be unable to run MarcEdit because they are no longer supported by a compatible version of the framework. \u00a0As of this writing, the following Windows-based systems are supported:<\/p>\n
[table]<\/p>\n
.NET Framework 4.0 Client Profile<\/strong><\/p>\n
Windows XP SP3 (32\/64)<\/p>\n
Windows Vista (32\/64)<\/p>\n
Windows 7 (32\/64)<\/p>\n
Windows 8 (32\/64)<\/p>\n
Windows Server 2003 SP2<\/p>\n
Windows Server 2008<\/p>\n
Windows 10 (All versions)<\/p>\n
[\/table]<\/p>\n
[table]<\/p>\n
.NET Framework 4.6.1+<\/strong><\/p>\n
Windows Vista (32\/64)<\/p>\n
Windows 7 (32\/64)<\/p>\n
Windows 8 (32\/64)<\/p>\n
Windows Server 2008<\/p>\n
Windows 10 (all versions)<\/p>\n
[\/table]<\/p>\n
Using the tables below, users can quickly determine what flavor of the .NET framework is supported. \u00a0At present, MarcEdit 5 and 6 is complied against the 4.0 Client Profile, and MarcEdit 7+ is compiled against the 4.6.1 Framework but users are always recommended to install and run the most current version of the framework.<\/p>\n
\n
Download the .NET 4.0 Client Profile:\u00a0 http:\/\/www.microsoft.com\/en-us\/download\/details.aspx?id=24872<\/a><\/span><\/li>\n
Download the .NET 4.6.1 Framework: https:\/\/www.microsoft.com\/en-us\/download\/details.aspx?id=49981<\/a><\/li>\n<\/ul>\n
<\/p>\n\n\n\n
$\"tip\"$ <\/a><\/td>\n Windows users should generally download the .NET Framework using the Automatic Update Tool in Windows. \u00a0Using that tool will ensure that the proper version of the software is installed.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
<\/p>\n
So what happens if my operating system isn’t on the list? \u00a0Well, you can check the Mono project. \u00a0Sometimes, the Mono project’s version of the framework maintains compatibility with unsupported systems, though I wouldn’t count on that. \u00a0At present date, Microsoft maintains the .NET Framework for any version of their operating system that is currently “supported”. \u00a0This is why versions of Windows XP, prior to Service Pack 3, are not supported. \u00a0If you are running an older Windows-based system that is not on one of these tables, your best option really is to update your system, or consider running a current version of Linux.<\/p>\n
Installing MarcEdit<\/h3>\n
Still convinced you want to give MarcEdit a try? \u00a0Great! \u00a0MarcEdit can be downloaded from: http:\/\/marcedit.reeset.net\/downloads\/<\/a>. \u00a0The link provides access to the following downloads:<\/p>\n
\n
32-bit Windows Installer (non-Adminstrator and Administrator Downloads)<\/li>\n
64-bit Windows Installer (non-Administrator and Administrator Downloads)<\/li>\n
Linux bin file<\/li>\n
OSX dmg download<\/li>\n
zip file<\/li>\n<\/ul>\n
Try before installing<\/strong><\/p>\n
In reality, MarcEdit doesn’t have to be “installed” in the traditional sense. \u00a0Installing MarcEdit is done to allow the program to integrate better with the operating system. \u00a0On a Windows system, for example, installing the program registers specific file types with the application, as well as installs MarcEdit’s development libraries. \u00a0For users wanting to just try out the program or work in an environment where they cannot install software — it is possible to simple download a zip file containing the MarcEdit program files, and run the application.<\/p>\n
<\/p>\n\n\n\n
$\"tip\"$ <\/a><\/td>\n Users wanting a portable version of MarcEdit can also utilizing the MarcEdit zip file. \u00a0Simply extract the contents to a USB drive…now you can run MarcEdit on any machine with the .NET framework installed.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
<\/p>\n
Installing on a Supported Windows-based System<\/strong><\/p>\n
When installing on a Windows-based system, users will need to decide which version of the application they wish to install, the 32-bit or 64-bit installer. \u00a0Users running a 32-bit version of Windows can only installed the 32-bit installer. \u00a0However, users running a 64-bit system can use either installation file to install MarcEdit. \u00a0So why the difference between the two? \u00a0In really comes down to the Windows Registry. \u00a0On Windows-based systems, applications register their components within the Windows Registry. \u00a0If an application has an Application Programming Interface (API) that they wish to allow other applications to leverage, they need to declare themselves within the Windows Registry. \u00a0MarcEdit’s installer does this during the installation process. \u00a0MarcEdit has a robust API that users can utilize to develop other programs or scripts to enhance their workflows. \u00a0During the installation process, MarcEdit registers this API with the operating system. \u00a0On 64-bit Windows-based systems, there are two versions of the Windows registry…one for 64-bit programs and one for 32-bit programs. \u00a0Components registered in the 32-bit registry can only be accessed by 32-bit programs. \u00a0Components registered in the 64-bit registry can only be accessed by 64-bit programs. \u00a0So, if a user wants to be able to access MarcEdit’s programming libraries from with a 64-bit environment, they have to install MarcEdit using the 64-bit installer so that the program can properly register the application components in the registry. \u00a0Not doing so essentially hides the API from Windows so it cannot be easily accessed by other tools and programs. \u00a0Confused? \u00a0I wouldn’t be surprised. \u00a0The main take away — if you want everything to work right, make sure you install the version of the application that matches your operating system.<\/p>\n
<\/p>\n\n\n\n
$\"tip\"$ <\/a><\/td>\n MarcEdit’s automatic updater will automatically select the correct version of MarcEdit for your system…regardless of the version you originally install.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
<\/p>\n
Installing MarcEdit on Linux<\/strong><\/p>\n
Installing MarcEdit on non-Windows-based systems generally takes a little more expertise, in part, because there traditionally hasn’t been a single installer to manage the process. \u00a0Prior to MarcEdit 6, users wanting to install MarcEdit on Linux-based system would need to follow the following instructions:<\/p>\n
Ensure that the dependencies have been installed<\/em><\/p>\n
\n
Dependency list:\n
\n
MONO (Current Version) (Runtime plus the System.Windows.Forms library [these are sometimes separate])<\/li>\n<\/ul>\n<\/li>\n
Unzip marcedit.zip<\/li>\n
On first run:\n
\n
mono MarcEdit.exe<\/li>\n
Preferences tab will open, click on other, and set the following two values:\n
\n
Temp path: \/tmp\/<\/li>\n
MONO path: [to your full mono path]<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n
Installing MarcEdit on Linux<\/p>\n
The video above provides a screencast of the process, from start to finish. \u00a0For individuals familiar with Linux, the installation process was pretty straightforward, the biggest challenging being the installation of the Mono Framework, as sometimes, the System.Windows.Forms library would be missing and need to be installed as a separate package. \u00a0Today, this process has been simplified. \u00a0Linux users now have the option to download the MarcEditSetup.bin file. \u00a0This is a self contained shell script that includes all the necessary files to install the program. \u00a0Running the shell script will instruct MarcEdit to install the program and analyze the system for missing dependencies, prompting the user to install missing dependencies as necessary. \u00a0What’s more, to simplify the install process, some dependencies are being completely removed. \u00a0All packages related to Yaz are being deprecated in the application for a customized solution for the application. \u00a0Removing these dependencies greatly simplifies installing the application, and will hopefully make it easier for Linux-based users to work with the application.<\/p>\n
Installing MarcEdit on OSX<\/strong><\/p>\n
As of June 2015, a native Mac OSX version of MarcEdit is being made available for download. \u00a0This version is being made available as a dmg installation file.<\/p>\n
Installation Steps:<\/strong><\/p>\n
\n
If you have the old OSX download prior to June 2015 and have installed it into the App Directory \u2014 delete it before going any further.\u00a0 The older builds and the native app are not compatible with each other and I honestly don\u2019t know how well one will overwrite the other.<\/li>\n
Download the MarcEdit OSX version from http:\/\/marcedit.reeset.net\/downloads<\/a><\/li>\n
Click on the DMG and mount the MarcEdit OSX Setup Disk.<\/li>\n
Drag the MarcEdit Icon into the Application Directory.<\/li>\n
(Optional) Z39.50 Support \u2014 MarcEdit includes a Z39.50 Client that utilizes the Yaz library.\u00a0 This must be installed on your system, and preferably using Homebrew.\u00a0 Use the following instructions:\n
\n
Install Homebrew: http:\/\/brew.sh\/<\/li>\n
If Homebrew is already installed, run the update command: >> brew update<\/li>\n
Install Yaz using the universal option.\u00a0 MarcEdit doesn\u2019t use functions in the icu library \u2014 you can install with or without this dependency setting: >> brew install yaz \u2013without-icu4c<\/li>\n
And that\u2019s it.\u00a0 If you install Yaz via other matter, MarcEdit will warn you the first time you\u00a0use the Z39.50 client letting you know that the dependency may not be available.\u00a0 It\u2019s looking specifically in the \/usr\/local\/Cellar\/yaz directory.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n
<\/p>\n
<\/p>\n
Other Downloads<\/strong><\/p>\n
In addition to the application, users have the opportunity to download other content from the MarcEdit downloads page. \u00a0 Specifically, there are two elements that need to be highlighted. \u00a0These items are:<\/p>\n
\n
MSICleaner<\/span><\/li>\n
XSLT Files<\/li>\n<\/ol>\n
MarcEdit’s Windows-based installation program utilizes the Microsoft Installer (MSI), utilizing the .msi file extension. \u00a0MarcEdit utilizes the MSI installer to take advantage of the installation repair features built into the operating system. \u00a0And by and large, users will never have a problem with either installing or upgrading the application. \u00a0However, when problems do occur, sometimes they can prevent MarcEdit from being uninstalled or updated. \u00a0In those rare cases, the MSICleaner can be utilized to manually remove references to the MarcEdit installer from the operating system. \u00a0The MSICleaner must be run with administrator permissions, and attempts to make the following changes:<\/p>\n
\n
Removed references to the MarcEdit’s installer from the registry<\/span><\/li>\n
Attempts to remove MarcEdit’s shared components from the registry<\/li>\n
Attempts to remove MarcEdit’s shared libraries from the Global Assembly Cache<\/li>\n
Attempts to unassociate file extensions from the registry<\/li>\n<\/ol>\n
When the program completes, it will provide a status message indicating the success or failure of the process. \u00a0If the MSICleaner is able to successfully complete its tasks, the program is essentially “uninstalled” from the operating system. \u00a0At this point, it is now safe to re-install MarcEdit.<\/p>\n
For users making use of MarcEdit to process non-MARC data, the MarcEdit website provides a handful of custom XSLT libraries that can utilized to convert data from a wide variety of formats. \u00a0These transformations are generally created by me (unless otherwise noted) and are offered to anyone that might want to use them. \u00a0In MarcEdit, XSLT translations need to be registered into the application before use. \u00a0For information on how XSLT transformations are registered into MarcEdit, please see Chapter #: #####.<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
In This Chapter: Can MarcEdit Help Me? Getting Started Installing MarcEdit Other Downloads Can MarcEdit Help Me? One of the most common questions posed by potential MarcEdit users is around the scope of the application. \u00a0Technical services and metadata librarians utilize a lot of different tools to edit, create, and manipulate their metadata…how is […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":23,"menu_order":1,"comment_status":"open","ping_status":"open","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/pages\/55"}],"collection":[{"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/comments?post=55"}],"version-history":[{"count":60,"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/pages\/55\/revisions"}],"predecessor-version":[{"id":550,"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/pages\/55\/revisions\/550"}],"up":[{"embeddable":true,"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/pages\/23"}],"wp:attachment":[{"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/media?parent=55"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}