\n<\/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>\nWhen 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<\/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>\nInstalling 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>\nAs 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>\nIn 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}]}} | |