<\/p>\n
One of MarcEdit’s biggest strengths and weaknesses is that it supports many different processes and workflows.\u00a0 This is a good thing because the program is oftentimes flexible enough to fit within a users existing processes, but can be challenging for new users, because there are oftentimes so many ways to do the same thing.<\/p>\n
When MarcEdit was first developed for public use, the application had very rigid lines drawn between the parts of the application that handled binary MARC data and those that handled MarcEdit’s mnemonic format.\u00a0 The MARC Tools component was the part of the application that handled that compiling and decompiling of MARC data.\u00a0 However, as the program has evolved, these lines have blurred and the role that the MARC Tools component plays has shifted as well.<\/p>\n
I believe that the MARC Tools component is still the primary jumping off point for users when the are looking to compile and decompile MARC data.\u00a0 But this part of the application has also been transformed into more of a hub, providing access to MARC tools that perform actions upon the files themselves (not the individual records).\u00a0 While again, users can certainly access these tools from a number of different places within the application, the MARC Tools component provides a singular portal for this information.<\/p>\n