$\"Figure$ <\/a>

Figure 3: Language Preferences<\/p><\/div>\n

Over the years, a very large and active international user community has developed around MarcEdit. \u00a0In an effort to provide better support for that community and non-native English speakers in general, I’ve been experimenting with different types of language options. \u00a0At this point, MarcEdit utilizes a concept of language packs.<\/p>\n

[table] $\"tip\"$ <\/a>[attr style=”width:90px”],”Language packs are just XML files that include the English language strings found in the application. \u00a0While I attempt to keep the language packs up to day, they do not currently contain all of the string data found in the application.”<\/p>\n

[\/table]<\/p>\n

A language pack is a special resource file that includes all of the string data used by the program. \u00a0These packages are generated automatically by a program that scans MarcEdit for new text strings. \u00a0The process then utilizes Microsoft’s language translation tools to provide an automated translation of the string. \u00a0Since these are machine translations, they sometimes are hilariously bad — but users are welcome to change them, update them, and provide the changes back to the community.<\/p>\n

Export Settings<\/h3>\n
$\"Figure$ <\/a>
Figure 4: Export Settings<\/p><\/div>\n
MarcEdit includes the ability to export MARC records directly into record management systems that support TCP\/IP import. \u00a0This functionality emulated the OCLC Gateway Export functionality found in tools such as Passport for Windows, CatME, and Connexion. \u00a0Users wishing to utilize this option to make sure that their integrated library system (ILS) support TCP\/IP exports, and speak to their system administrator to determine the host name and port number setup to accept exported data.<\/p>\n
MarcEdit includes two additional options. \u00a0The timeout option determines how long MarcEdit will wait before giving up on a connection. \u00a0By default, the timeout is set for 30 seconds. \u00a0The second option, Export Receipt, will capture any data returned by the ILS as part of an export transaction and will present that information back to the user after the export has been completed. \u00a0Many ILS systems, like Innovative Interface’s Millennium system, provide a detailed log of records created, record numbers and errors when data is passed through the system’s export port. \u00a0Enabling this option will allow MarcEdit to capture that information.<\/p>\n
[table] $\"tip\"$ <\/a>[attr style=”width:90px”],”While capturing the Export Receipt will return logging information about a specific set of transactions, it also significantly slows down the process since MarcEdit must process one record at a time. \u00a0Turning off this option allows MarcEdit to process export requests in larger record groups.”<\/p>\n
[\/table]<\/p>\n
[table] $\"tip\"$ <\/a>[attr style=”width:90px”],”Use caution when disabling the Export Receipt option. \u00a0MarcEdit has the ability to export thousands of records per second, and some ILS systems may not be able to handle more than one record at a time. \u00a0Consult your system administrators for guidance.”<\/p>\n
[\/table]<\/p>\n
MARCEngine Settings<\/h3>\n
$\"Figure$ <\/a>
Figure 5: MARCEngine Settings<\/p><\/div>\n
The MARCEngine is one of the key components of the MarcEdit application. \u00a0The MARCEngine processing library controls all aspects of processing both MARC and non-MARC by the application. \u00a0The MARCEngine options are broken into 4 grouping: General Options, XML Options, XSLT Engine options and Unicode Normalization. \u00a0Individuals working with MarcEdit and working with data that is\u00a0not<\/strong> in MARC21 or are international users working with diacritical data should carefully consider which of these options will best meet their needs. \u00a0Likewise, individuals utilizing MarcEdit to process XML encoded data or are using MarcEdit to output XML encoded data should evaluate these options to ensure that MarcEdit can best meet their individual needs.<\/p>\n
General Options<\/strong><\/p>\n
\n
Use Diacritics when breaking<\/i>: \u00a0Recommended Value: Checked<\/strong>. \u00a0When this option is selected, MarcEdit will replace non-UTF-8 encoded diacritics with mnemonics. \u00a0For example, file encoded in MARC-8, that includes a diacritic with an A with an acute, would be represented as {acute}a or {aacute} when rendered in the MarcEditor. \u00a0Once compiled, this data will be converted back to the byte equivalents of the mnemonic values. \u00a0For nearly all users, this option should nearly always be selected. \u00a0Only those users that are creating and editing data in an alternative characterset (like Big-5) should consider unchecking this option. \u00a0However, if you uncheck this option, you much also change the MarcEditor Preference, Default encoding to match your record encoding.<\/span><\/span>For example, if a user’s data is encoded in Big-5, and they wish to render their data in Big-5 and have a keyboard configured to enter Big-5 format, you would configure MarcEdit to treat record data as Big-5 by unchecking the\u00a0Use Diacritics when breaking<\/em> and setting MarcEditor’s Default Encoding to Big-5. \u00a0However, outside of this narrow use case, users are encouraged to always select this option.<\/li>\n
Records in MARC21 format<\/em>: \u00a0Recommended Value: Checked<\/strong>. \u00a0Since most national libraries are moving towards a more universal acceptance of MARC21 as the privilaged flavor of MARC, I recommend that this value remained selected. \u00a0The purpose of this configuration option is to signal to the MARCEngine when it is ok to manipulate the MARC leader for setting character encodings. \u00a0MarcEdit has the ability to convert between multiple character encodings, and in MARC21, there is a specific byte in the leader that must be set to identify when a record is in UTF-8 or in something else. \u00a0If you know that your data is not<\/strong> in MARC21, and you will be converting data from one character encoding to UTF-8, you should<\/strong> uncheck this option to prevent MarcEdit from incorrectly flipping the leader byte.For example, if a user’s bibliographic data is in UNIMARC and the data’s characterset is encoded in MARC-8 and the user is going to use MarcEdit to convert the data from MARC-8 to UTF-8…the user\u00a0should<\/strong> uncheck this value prior to running the conversion.<\/li>\n<\/ul>\n
XML Options<\/strong><\/p>\n
\n
MARCXML XSLT<\/em>: \u00a0As discussed in subsequent chapters, MarcEdit’s XML framework is designed around using MARCXML as a mediator schema when moving metadata between schemas. \u00a0In previous versions of MarcEdit, all XML transformations were handled via XSLT. \u00a0While this is no longer the true in the case of MARCXML conversions, users still have the option of forgoing MarcEdit’s native MARCXML processing algorithms in\u00a0lieu\u00a0of an XSLT approach. \u00a0While MarcEdit’s native processing algorithm is orders of magnitude faster and has no size limitations when processing MARCXML data, the XSLT approach allows the user greater flexibility in customizing the output generate by the transformation. \u00a0For users wanting to utilize this approach, unselect the\u00a0Use Native Option (Non-XSLT process)<\/em> and enter the path to the custom XSLT file that MarcEdit should utilize when processing MARCXML data.<\/span><\/span> [table] $\"tip\"$ <\/a>[attr style=”width:90px”], “Please note, users wishing to modify the MARCXML stylesheet should not modify the default stylesheet provided by the application. \u00a0MarcEdit treats that file as protected, and will overwrite the source file on update. \u00a0Users should create their own MARCXML stylesheet if they wish to make modifications.”[\/table]<\/li>\n
Use Native Option (Non-XSLT Process):\u00a0<\/em>Recommended Value: Checked<\/strong>. \u00a0MarcEdit provides two methods for translating MARCXML formatted data into MARC: an XSLT option and a Native option. \u00a0If this value is checked, MarcEdit will utilize the native option, which utilizes a SAX processing approach to translation. \u00a0If the user unselects this value, MarcEdit will utilize the XSLT file defined in the\u00a0MARCXML XSLT<\/em>\u00a0and utilize an XSLT process when transforming MARCXML data to MARC.[table] $\"tip\"$ <\/a>[attr style=”width:90px”], “MarcEdit’s native Option is capable of processing MARCXML data at high speeds and with no size limitations.”[\/table] [table] $\"tip\"$ <\/a>[attr style=”width:90px”], “The largest MARCXML file I \u00a0have processed, is ~1 TB utilizing the Native Option.”[\/table]<\/li>\n
Use Namespaces<\/em>:\u00a0Recommended Value: Checked<\/strong>. \u00a0Namespaces in XML allow for disambiguation. \u00a0However, they also significantly increase the file size of a document. \u00a0By unselecting this option, the MARCEngine will not<\/b> output namespaces when generating MARCXML data<\/li>\n<\/ul>\n
XSLT Engine<\/strong><\/p>\n
MarcEdit includes two XSLT processing engines are part of the application; the MSXML engine which is a part of the .NET framework, and Saxon.NET, developed by Michael Kay [ref]Saxon XSLT and XQuery Project,\u00a0http:\/\/sourceforge.net\/projects\/saxon\/<\/a>[\/ref]. \u00a0Both engines have their strengths and weaknesses. \u00a0By default, MarcEdit selects the MSXML engine, since this XSLT engine has been optimized for speed…but that speed does come with a cost. \u00a0Users are encouraged to evaluate the differences between the two options and make the choice that best suites their circumstances.<\/p>\n
\n
MSXML<\/em>:\u00a0<\/span>Recommended Value: Selected. \u00a0<\/strong>The MSXML engine provides support for XSLT 1.0 and XQuery 1.0. \u00a0Users wishing to utilize XSLT 2.0 or XQuery 2.0 should select the SAXON.NET processor. \u00a0The MSXML engine is selected by default for two reasons: 1) the engine has a smaller footprint due to the integration with the .NET framework, and 2) the engine is\u00a0noticeably more responsive when processing small to medium size XML documents. <\/span><\/li>\n
SAXON.NET<\/em>: The SAXON.NET engine is a .NET implementation of the SAXON XSLT engine. \u00a0This XSLT engine support XSLT 2.0 and XQuery 2.0. \u00a0This engine tends to have a\u00a0noticeably\u00a0slower loading time, but provides better performance on large to medium-large XML documents. \u00a0<\/span><\/li>\n<\/ul>\n
[table] $\"tip\"$ <\/a>[attr style=”width:90px”], “The XSLT Engine option sets the default XSLT engine to be used by MarcEdit. \u00a0However, users can override this default value and specify a specific XSLT engine at the transformation level.”[\/table]<\/p>\n
<\/p>\n
Unicode Normalization<\/strong><\/p>\n
With \u00a0more and more library metadata being encoded or translated into UTF-8, issues related to Unicode normalization are becoming more common. \u00a0While many metadata libraries believe that simply moving metadata into UTF-8 will fix the indexing issues that libraries currently face when working with diacritical data, the solution isn’t that simple. \u00a0What many people do not realize, is that not all Unicode data is created the same. \u00a0One of the issues related to MARC-8 encoded data is that diacritical data isn’t represented as a single value. \u00a0For example, and A with an acute is represented by the letter ‘a’ and a value representing the acute symbol. \u00a0When indexed, the diacritical information is lost. \u00a0The same thing can occur with UTF-8 data depending on the normalization in use. \u00a0Within the library community, the U.S. Library of Congress recommends the use of the Compatibility Decomposition or KD notation. \u00a0This notation emulates the MARC-8 encoding structure, in that diacritical data are represented as two separate codepoints: a codepoint representing the ‘a’ and a codepoint representing the diacritical mark. \u00a0Display of the diacritic happens at the display level, but for indexing purposes, the diacritical information is lost. \u00a0For users outside of the United States, the preferred Unicode normalization is the Canonical Decomposition or C notation. \u00a0In this case, diacritical data is represented as a single codepoint, so the ‘a’ with an acute is represented by a single value representing that character. \u00a0The diacritical information is then represented correctly at the display level and is indexed correctly. \u00a0Presently, the U.S. Library of Congress specifies the use of the KD notation for all records encoded in MARC21 to ensure the ability to round-trip data between MARC-8 and UTF-8.<\/p>\n
\n
Compatibility Decomposition (KD)<\/em>:\u00a0Recommended Value: Selected.\u00a0<\/strong>\u00a0 My personal opinion is that this notation should be dropped in lieu of the Canonical Decomposition, but for users working with MARC21 and sharing data with libraries within North America, OCLC or the Library of Congress…the KD notation should be used.<\/span><\/span><\/li>\n
Canonical Decomposition (C)<\/em>: \u00a0This option will convert all UTF-8 diacritical pairs to their single codepoint representation.<\/li>\n<\/ul>\n[table] $\"tip\"$ <\/a>[attr style=”width:90px”],”While the KD notation is recommended for purposes of compatibility with MARC-8, MarcEdit has the ability to maintain that compatibity between UTF-8 data encoded using the C notation and MARC-8. \u00a0The process occurs seamlessly for the user.”[\/table]<\/p>\n
Update Settings<\/h3>\n
$\"Figure$ <\/a>
Figure 6: Update Settings<\/p><\/div>\n
<\/p>\n
Due to the irregular nature of the MarcEdit development cycle, tracking and managing updates manually can be a laborious process. \u00a0To simplify the tracking and installation of updates, MarcEdit includes a set of configuration options that allows the program to self manage itself. \u00a0When enabled, MarcEdit will automatically track new application updates and notify the user when a new build \u00a0is available for download. \u00a0For enterprise users, MarcEdit can be configured to not only track updates, but self install, by embedding authentication credentials into the application.<\/p>\n
\n
Automatically Check for Updates:\u00a0<\/strong><\/em>Recommend Value: Checked.<\/strong>\u00a0 When this value is selected, MarcEdit will ping the MarcEdit servers to retrieve information on the current build number. \u00a0When a new update is available, MarcEdit will notify the user, providing a workflow to download and install the update.<\/span><\/span><\/span><\/span>[table]<\/span> $\"tip\"$ <\/a>[attr style=”width:90px”],”When automatic updates are enabled, MarcEdit will attempt to ‘phone home’ each time the application is run. \u00a0The update process retains no information from the transaction, save for regular web statistics. \u00a0For information about what information is capture and how it is recorded, please see the MarcEdit Privacy Policy.”[\/table]<\/span><\/li>\n
Use system Proxy Settings<\/em>: \u00a0Users utilizing a proxy to connect to the internet should check this option. \u00a0MarcEdit will attempt to utilize the systems defined proxy settings to manage its connection.<\/span><\/span><\/li>\n
User Information:<\/em>\u00a0\u00a0Within enterprise environments, its becoming increasingly common for all application management be handled by a central information technology unit. \u00a0For software with regular release cycles, this type of centrally managed approach works very well. \u00a0However, MarcEdit’s irregular release cycle can be a support nightmare. \u00a0To simplify the management of updates within enterprise environments, administrators can embed a limited username and password dedicated to the management of MarcEdit on a specific machine. \u00a0Authentication information is encrypted using a 128-bit key, randomly generated using the systems MAC address and a generate GUID.<\/span><\/span><\/li>\n
Automatically Check for Validate Updates:<\/em> \u00a0Recommended Value: Checked.<\/strong>\u00a0 Configures MarcEdit to evaluate the default MARCValidator rules file to check for updates. \u00a0This is just a notification service. \u00a0MarcEdit will not overwrite the current Validator rules unless specifically instructed by the user.<\/span><\/li>\n<\/ul>\n
<\/p>\n
\u00a0File Association Settings<\/h3>\n
$\"Figure$ <\/a>
Figure 7: File Associations<\/p><\/div>\n
During MarcEdit\u2019s installation process, MarcEdit will automatically associate 3 file types with the MarcEdit application: .mrc extension, .mrk extension, and the .mrk8 extension. \u00a0When clicked on, these file extensions will automatically initiate specific MarcEdit actions upon the file.<\/p>\n
Actions:<\/em><\/p>\n
\n
.mrc extension: \u00a0File type is associated with the MarcBreaker. \u00a0This file extension is reserved for binary MARC data files. \u00a0Clicking on a file with this extension will automatically open the MARC Tools window, and the program will be ready to Break the file. \u00a0The MarcEdit installation program also adds a context menu to Windows, so when a user right clicks on a .mrc file, an option to Preview the file will be found in the menu list.<\/li>\n
.mrk extension: \u00a0File type is associated with the MarcEditor. \u00a0This file extension is reserved for the MarcEdit mnemonic format. \u00a0Clicking on a file with this extension will automatically open the file into the MarcEditor for editing.<\/li>\n
.mrk8 extension: \u00a0File type is associate with the MarcEditor. \u00a0\u00a0This file extension is reserved for UTF-8 data encoded in the MarcEdit mnemonic format. \u00a0Clicking on a file with this extension will automatically open the file into the MarcEditor for editing.<\/li>\n<\/ul>\n
<\/p>\n
[table]<\/p>\n
$\"tip\"$ <\/a>[attr style=”width:90px”],”A common question that comes up on the MarcEdit listserv revolves around the applications ability to process a specific file extension. \u00a0To a large extent, file extensions have no intrinsic meaning, rather; they are essentially shortcuts within an operating system to associate a set of actions with a group of files. \u00a0File associations that become ubiquitous due to their association with a specific tool or program, inherit additional associations due to the shared experiences of a group of users. \u00a0This is all to say that MarcEdit’s ability to process a particular file extension has nothing to do with the extension of the file itself, but is completely dependent on the data found inside that file. \u00a0While many tools that export MARC records have come to utilize MarcEdit’s .mrc file extension to represent MARC data, other tools like OCLC’s Connexion program utilize the .dat file extension to represent MARC files, while Innovative Interfaces export program generates .out files for it’s MARC records. \u00a0MarcEdit can each of these file types.”<\/p>\n
[\/table]<\/p>\n
One of the benefits of MarcEdit\u2019s longevity is that MarcEdit\u2019s default file extension for Binary MARC data (.mrc) \u00a0has largely been co-opted by the library vendor community to represent binary MARC data. \u00a0For MarcEdit users, this means that these files are automatically associated with the application and the application\u2019s shortcuts. \u00a0However, some tools like Innovative Interfaces export program utilize a different file extension to output MARC data. \u00a0In this case, the Innovative program utilizes a .out file extension to represent MARC data outputted from the program. \u00a0For users that find themselves working with common alternative file extensions may want to associate the extension with a specific MarcEdit action.<\/p>\n
MarcEdit provides a built-in process for associating additional file extensions with the application by modifying the File Association Settings. \u00a0Looking at Figure 8, one can see that by default, the ability to edit MarcEdit\u2019s three primary file associations are disabled. \u00a0This is due to the fact that MarcEdit\u2019s installer installs these file associations at a system level, so users need to have administrative access to modify these global associations. \u00a0For additional file extensions, MarcEdit utilizes a different process, creating associations with files at the user level, so different users, logged onto the same computer could have different file extensions assigned to the application.<\/p>\n
<\/iframe> MarcEdit: Managing File Associations<\/p>\n<p>[table]<\/p>\n<p><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\"><img decoding=\"async\" loading=\"lazy\" class=\"alignnone size-full wp-image-26\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\" alt=\"tip\" width=\"85\" height=\"75\" \/><\/a>[attr style=”width:90px”], “While MarcEdit’s user defined file associations occur at the user profile level, it should be noted that individuals wanting to associate new file types with MarcEdit should use some caution. \u00a0Some file extensions utilized by tools like Connexion, are used in other contexts within the operating system. \u00a0While it would be unlikely that associating a specific file extension with MarcEdit would cause issues with a user’s system, it is also difficult to know for certain all the potential consequences related to changing the file association of a system file. \u00a0As such, it’s best to treat the following file extensions as special and not associate them with MarcEdit: .bin and .dat.”<\/p>\n<p>[\/table]<\/p>\n<p>[table]<a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\"><img decoding=\"async\" loading=\"lazy\" class=\"alignnone size-full wp-image-26\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\" alt=\"tip\" width=\"85\" height=\"75\" \/><\/a>[attr style=”width:90px”], “When MarcEdit associates a new file extension through the File Associations Settings tool, the program assigns a generic icon to the file type. \u00a0If you want to change the icon used — MarcEdit’s found file type icons (for .mrc, .mrk, .mrk8, and a generic icon) can be found in the Application Program directory\\shadow\\icons. ”<\/p>\n<p>[\/table]<\/p>\n<p> <\/p>\n<h3>Locations<\/h3>\n<div id=\"attachment_319\" style=\"width: 787px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_locations.png\" rel=\"attachment wp-att-319\"><img aria-describedby=\"caption-attachment-319\" decoding=\"async\" loading=\"lazy\" class=\"wp-image-319 size-full\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_locations.png\" alt=\"Figure 8: Locations\" width=\"777\" height=\"577\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_locations.png 777w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_locations-300x223.png 300w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_locations-768x570.png 768w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_locations-624x463.png 624w\" sizes=\"(max-width: 777px) 100vw, 777px\" \/><\/a><p id=\"caption-attachment-319\" class=\"wp-caption-text\">Figure 8: Locations<\/p><\/div>\n<p>By default, MarcEdit utilizes system defined folders for storing user configuration data, temp files, etc. \u00a0However, in some environments, users may want to share tasks or configuration settings; in others, they may utilize a network drive as their default file path. \u00a0This preference section allows users to customize where MarcEdit should look for and store data (at least specific types of data).<\/p>\n<h3>Other Settings<\/h3>\n<div id=\"attachment_320\" style=\"width: 787px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_other.png\" rel=\"attachment wp-att-320\"><img aria-describedby=\"caption-attachment-320\" decoding=\"async\" loading=\"lazy\" class=\"size-full wp-image-320\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_other.png\" alt=\"Figure 9: Other Settings\" width=\"777\" height=\"577\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_other.png 777w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_other-300x223.png 300w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_other-768x570.png 768w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_other-624x463.png 624w\" sizes=\"(max-width: 777px) 100vw, 777px\" \/><\/a><p id=\"caption-attachment-320\" class=\"wp-caption-text\">Figure 9: Other Settings<\/p><\/div>\n<p>As seen so far, MarcEdit’s configuration settings tend to be group by a specific component or action. \u00a0The Other Settings configuration group was created for those options that don’t fit neatly into a specific component or action subgroup. \u00a0In most cases, items found in this grouping deal with record description issues. \u00a0For example, options defining the Title tag, the Author Tag, the Call Number tag and the Control number tag define what fields within a MARC data file that can be utilized for purposes of display or record sorting. \u00a0Given MarcEdit’s MARC agnostic nature, these values must be use defined so that the application can interpret the data correctly for purposes of display. \u00a0By default, MarcEdit will utilize MARC21 values if the user does not provide their own: Title tag set to the 245$a, Author tag to the 1xx$a, Call number tag to the 050$a and Control Number tag to the 001.<\/p>\n<p>As noted above, these display values are utilized throughout the application. \u00a0Within the MarcEditor, the defined values can be utilized for record sorting; within the Extract Selected Records, the Title tag is used to set the default display field data. \u00a0In the Z39.50 tool, the Title field is used to set the default title field used for display. \u00a0While MarcEdit does not utilize these values for any specific processing tasks (save for sorting), these values play an important role in helping the program understand how data is to be displayed back to the user.<\/p>\n<p>In addition to configuring MARC tag definitions,\u00a0the tool provides access to two sorting preferences:<\/p>\n<ol>\n<li><span style=\"line-height: 12.997159004211426px;\"><span style=\"line-height: 12.997159004211426px;\"><em>880: Use linking field for sort<\/em>:\u00a0<strong>Recommended Value: Checked. \u00a0<\/strong>When unchecked, the tool will sort all 880 fields together, regardless of which field it is paired to. \u00a0When check, the tool will sort the 880 field together, but use the linked field to sort field groups together.<\/span><\/span><\/li>\n<li><em>Infile 880 fields and field pairs:<\/em>\u00a0When checked, this will sort the 880 fields next to the field that they are linked to.<\/li>\n<\/ol>\n<p> <\/p>\n<h3>\u00a0Direct ILS Integration<\/h3>\n<div id=\"attachment_321\" style=\"width: 787px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_ils_integation.png\" rel=\"attachment wp-att-321\"><img aria-describedby=\"caption-attachment-321\" decoding=\"async\" loading=\"lazy\" class=\"size-full wp-image-321\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_ils_integation.png\" alt=\"Figure 10: ILS Integration\" width=\"777\" height=\"577\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_ils_integation.png 777w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_ils_integation-300x223.png 300w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_ils_integation-768x570.png 768w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_ils_integation-624x463.png 624w\" sizes=\"(max-width: 777px) 100vw, 777px\" \/><\/a><p id=\"caption-attachment-321\" class=\"wp-caption-text\">Figure 10: ILS Integration<\/p><\/div>\n<p><\/p>\n<p>The simple truth is that library tools and systems don’t function in a vacuum, but are becoming much more connected and integrated. \u00a0Within the library ILS space, this has given rise to a host of application programming interfaces (API) designed to give tool developers that ability to interact directly with the underlying data in the libraries metadata management system. \u00a0This level of integration is a very new occurrence within the library community and is still very much a work in progress. \u00a0Anticipating new opportunities for integration and the potential to update old workflows, an ILS mediation layer was built into MarcEdit. \u00a0This mediation layer was designed to facilitate the interactions between MarcEdit and an ILS systems API, handling issues related to authentication, sessioning, searching, data conversion, and error handling. \u00a0As new library management systems expose their underlying APIs, users will find that MarcEdit is ready to work with them.<\/p>\n<p>In Fall 2012, MarcEdit developed the first proof of concept around this notion of direct ILS integration. \u00a0Working with the open source Koha system, a small code library was developed to encapsulate the Koha API for use within the MarcEdit application. \u00a0Once created, the library was made available to the library community and embedded into MarcEdit. \u00a0The result is a dramatic shift in workflows. \u00a0When enabled, the direct ILS integration allows users to directly search for individual or batches of records and automatically pull that data into MarcEdit for editing. \u00a0In the Koha example, the API exposed the ability to create and modify bibliographic content, as well as the ability to create and modify holdings information for a bibliographic record. \u00a0So, using the API, users never had to export, or make, or break any bibliographic data. \u00a0Rather, the information is directly pulled into the MarcEditor where it can be edited, validated, and then pushed back to the catalog. \u00a0At the time of writing, the direct ILS integration features are limited to the Koha ILS system. \u00a0While other ILS system vendors are currently developing or testing API access to their systems, they have yet to become publicly available.<\/p>\n<p>[table]<\/p>\n<p><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\"><img decoding=\"async\" class=\"alignnone wp-image-175\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\" alt=\"tip\" \/><\/a>\u00a0[attr style=”width:90px”],”As ILS vendors open their API’s, it will be up to the MarcEdit community to help build the relationships that will allow the development of direct integration to other ILS systems.”<\/p>\n<p>[\/table]<\/p>\n<p>The ILS integration settings provide the information MarcEdit needs to configure direct access to an ILS system using MarcEdit’s mediation layer. \u00a0MarcEdit provides the systems compatible with the ILS integration function in the\u00a0<strong>Select System<\/strong> listing. \u00a0Users need only to highlight a specific ILS system and fill in the required information related to the systems HostName, authentication information, and if Z39.50 should be utilized to search the resource.<\/p>\n<p>[table]<\/p>\n<p><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\"><img decoding=\"async\" class=\"alignnone wp-image-175\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\" alt=\"tip\" \/><\/a>\u00a0[attr style=”width:90px”],”If you don’t see your ILS in the\u00a0<strong>Select System<\/strong> list and you know your system provides an API that supports record management tasks, contact your vendor and tell them you want them to work with MarcEdit.”<\/p>\n<p>[\/table]<\/p>\n<p><iframe loading=\"lazy\" src=\"http:\/\/www.youtube.com\/embed\/sYC6nME0WoI\" width=\"420\" height=\"315\" frameborder=\"0\" allowfullscreen=\"allowfullscreen\"><\/iframe><\/p>\n<p>MarcEdit: Setting up direct ILS integration [Koha]<\/p>\n<p> <\/p>\n<p><iframe loading=\"lazy\" src=\"http:\/\/www.youtube.com\/embed\/jkcAt-KcSeQ\" width=\"420\" height=\"315\" frameborder=\"0\" allowfullscreen=\"allowfullscreen\"><\/iframe><\/p>\n<p>MarcEdit: Direct ILS Integration [Koha Searching Example]<\/p>\n<p> <\/p>\n<p><iframe loading=\"lazy\" src=\"http:\/\/www.youtube.com\/embed\/oM1VBc1LWco\" width=\"420\" height=\"315\" frameborder=\"0\" allowfullscreen=\"allowfullscreen\"><\/iframe><\/p>\n<p>MarcEdit: Direct ILS Integration [Koha; Updating\/Creation of records]<\/p>\n<p> <\/p>\n<h3>OCLC Integration<\/h3>\n<div id=\"attachment_322\" style=\"width: 787px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_oclc_integration.png\" rel=\"attachment wp-att-322\"><img aria-describedby=\"caption-attachment-322\" decoding=\"async\" loading=\"lazy\" class=\"size-full wp-image-322\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_oclc_integration.png\" alt=\"Figure 11: OCLC API Integration\" width=\"777\" height=\"577\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_oclc_integration.png 777w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_oclc_integration-300x223.png 300w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_oclc_integration-768x570.png 768w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mepreferences_oclc_integration-624x463.png 624w\" sizes=\"(max-width: 777px) 100vw, 777px\" \/><\/a><p id=\"caption-attachment-322\" class=\"wp-caption-text\">Figure 11: OCLC API Integration<\/p><\/div>\n<p>One of the most significant and welcome changes for libraries that also happen to be OCLC[1] members, is the release of the OCLC Metadata API[2].\u00a0 OCLC’s Metadata API is an outcrop of their WorldShare Management Services, and provides application developers a set of read\/write interfaces into WorldCat.\u00a0 What that means for tools like MarcEdit, is that it is now possible to develop tools and functions that interact directly with the OCLC WorldCat database, at least, in the narrow context as specified by the Metadata API.\u00a0 Within MarcEdit, the Metadata API’s have been utilized to provide two new batch functions: Batch OCLC Holdings Modification and Batch OCLC Record Creation or Edit.\u00a0 These two new tools give MarcEdit users, who also are OCLC members, the ability to interact with WorldCat in new ways.<\/p>\n<p>Users interested in using the OCLC Integration options will first need to determine if they meet a specific set of criteria, the most important being that their institution is a member of the OCLC consortia.\u00a0 The second criteria is the acquisition of a developer key with the capacity to work with OCLC’s Search API and OCLC’s Metadata APIs.\u00a0 Key’s are requested directly from OCLC, and once minted, are then embedded into MarcEdit to activate the OCLC specific functionality.<\/p>\n<p>To activate the OCLC integration tools, users must first enter their information into the Preferences window, and then validate the key.\u00a0 This is done by click on the Validate Keys button.\u00a0 Once that occurs, MarcEdit queries OCLC regarding the status and permissions available to the key entered into the preference screen.\u00a0 The user will receive a message noting the status of the key, and upon successful validation, the OCLC integration tools found in MarcEdit will be enabled.<\/p>\n<h3>Where are My Configuration Settings<\/h3>\n<p>Prior to MarcEdit 5, MarcEdit stored configuration data in the Windows Registry. \u00a0However, over time, this methodology became unwieldy and made the application much less portable. \u00a0So, starting in MarcEdit 5, all the application’s configuration values were migrated out of the Windows Registry and into MarcEdit’s configuration files. \u00a0MarcEdit’s configuration files utilize a simple XML format to store information related to a user’s interactions with the program. \u00a0In addition to the MarcEdit Preferences, MarcEdit stores data related to last save\/open paths, file histories, screen positioning and sizing, and much more. \u00a0These configuration files are autogenerated the first time MarcEdit is run, and are tied to a specific users username.<\/p>\n<p>MarcEdit currently has two types of configuration\/application files. \u00a0There are what I would term as system files, data that should be accessible to all MarcEdit users on a specific system, and user files; resources that should be tied to a specific users username. \u00a0Prior to Windows XP, most Windows applications stored these two file types together in the application program directory.<\/p>\n<p>[table]<\/p>\n<p><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\"><img decoding=\"async\" class=\"alignnone wp-image-175\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\" alt=\"tip\" \/><\/a>\u00a0[attr style=”width:90px”],”The program directory on most systems will be located in one of two locations. \u00a0C:\\Program Files\\{Program Name} or C:\\Program Files (x86)\\{Program Name}” — where program name references MarcEdit + major version number.<\/p>\n<p>[\/table]<\/p>\n<p>Following the release of Windows XP Service Pack 3, Windows underwent a significant restructuring around user access to system directories. \u00a0One of those locations affect was the Programs Directory, and best practice shifted from storing configuration information in the application program directory to a dedicated application program directory attached to a specific username. \u00a0For users and developers, this structure provides a much cleaner experience, but the unintended impact is that it made configuration data difficult to find.<\/p>\n<p>[table]<\/p>\n<p><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\"><img decoding=\"async\" class=\"alignnone wp-image-175\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\" alt=\"tip\" \/><\/a>\u00a0[attr style=”width:90px”],”Between Windows XP and Windows Vista, Microsoft changed the location of the user program directories. \u00a0In Windows XP, configuration data could be found at: C:\\documents and settings\\[username]\\AppData\\MarcEdit. \u00a0In subsequent versions of Windows, the configuration directory path shifted to:\u00a0C:\\Users\\[username]\\AppData\\Roaming\\marcedit.”<\/p>\n<p>[\/table]<\/p>\n<p>In general, most users will not need to access MarcEdit’s system or configuration files directly. \u00a0However there are use cases that exist. \u00a0The most common use cases for access would be a need to access the default MarcEdit XSLT translation files or a desire to modify MarcEdit’s provided language files. \u00a0The two resources are located in wildly different locations, with XSLT translations classified as a system file and stored in the application directory, and the language files classified as a user defined configuration value, so are stored in the user application directory. \u00a0To help users locate these data elements more efficiently, MarcEdit includes a set of application shortcuts that can be used to jump directly to specific classes of configuration data.<\/p>\n<div id=\"attachment_323\" style=\"width: 769px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/meappfolder.png\" rel=\"attachment wp-att-323\"><img aria-describedby=\"caption-attachment-323\" decoding=\"async\" loading=\"lazy\" class=\"size-full wp-image-323\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/meappfolder.png\" alt=\"Figure 12: Application Shortcuts\" width=\"759\" height=\"483\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/meappfolder.png 759w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/meappfolder-300x191.png 300w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/meappfolder-624x397.png 624w\" sizes=\"(max-width: 759px) 100vw, 759px\" \/><\/a><p id=\"caption-attachment-323\" class=\"wp-caption-text\">Figure 12: Application Shortcuts<\/p><\/div>\n<p>Starting from the main MarcEdit window, users can access the Application shortcuts by clicking on the Help Menu as illustrated in\u00a0the above. \u00a0MarcEdit currently provides Application Shortcuts to each class of user data.<\/p>\n<ul>\n<li><span style=\"line-height: 13px;\"><span style=\"line-height: 13px;\"><em>Application Data Path:\u00a0<\/em>The Application Data Path shortcut links directly to the top-level folder showing all available configuration data files. \u00a0This includes resources like macros, tasks, templates, and settings files.<\/span><\/span><\/li>\n<li><em>XSLT Data Path:<\/em> \u00a0The XSLT Data Path shortcut links directly to the local MarcEdit XSLT repository storing the default XSLT translation templates.<\/li>\n<li><em>Language Data Path:<\/em> \u00a0The Language Data Path shortcut links directly to the folder storing all registered language packs recognized by the application.<\/li>\n<\/ul>\n<h3>Sharing Configuration Settings<\/h3>\n<p>When MarcEdit first generates the configuration data for a new user program, the application customizes those configuration settings to the specific users environment. \u00a0These files cannot simply be copies from one users machine to another without a great deal of manual intervention to update remove and replace the system specific information found in the files. \u00a0However, the ability to share or export ones configuration data is a necessary part of any work environment. \u00a0Desktops get replaced, new staff are hired into departments; so the ability to export and share configuration settings across multiple systems can be important. \u00a0Fortunately, MarcEdit provides a built-in tool to facilitate the batch sharing of configuration data between systems.<\/p>\n<div id=\"attachment_324\" style=\"width: 542px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mesharesettings.png\" rel=\"attachment wp-att-324\"><img aria-describedby=\"caption-attachment-324\" decoding=\"async\" loading=\"lazy\" class=\"size-full wp-image-324\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mesharesettings.png\" alt=\"Figure 13: Share Settings\" width=\"532\" height=\"483\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mesharesettings.png 532w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/mesharesettings-300x272.png 300w\" sizes=\"(max-width: 532px) 100vw, 532px\" \/><\/a><p id=\"caption-attachment-324\" class=\"wp-caption-text\">Figure 13: Share Settings<\/p><\/div>\n<p>From the main MarcEdit window, Under the File Menu option, users can select the Share Configuration Settings (Figure 13) option to export or import MarcEdit settings.<\/p>\n<p>MarcEdit’s Export Settings tool allows users to specify what granularity of data that a user wishes to share (Figure 14).<\/p>\n<div id=\"attachment_226\" style=\"width: 373px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/export_settings2.png\"><img aria-describedby=\"caption-attachment-226\" decoding=\"async\" loading=\"lazy\" class=\"wp-image-226 size-full\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/export_settings2.png\" alt=\"Figure 14: Export Settings\" width=\"363\" height=\"452\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/export_settings2.png 363w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/export_settings2-240x300.png 240w\" sizes=\"(max-width: 363px) 100vw, 363px\" \/><\/a><p id=\"caption-attachment-226\" class=\"wp-caption-text\">Figure 14: Export Settings<\/p><\/div>\n<p>Users have the option of exporting copies of just their XSLT data or their Macros and Tasks, or a user can export all of the application’s configuration information. \u00a0On export, MarcEdit sanitizes the configuration data, removing system specific information from the files, prepping them for import into another system. \u00a0Once exported, users simply need to move the exported data file to the new system or machine and then run the Import Settings function. \u00a0Once the user has selected the import file, MarcEdit will reprocess the export file, customizing the shared configuration data for use on the user’s system.<\/p>\n<p> <\/p>\n<p>[table] <a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\"><img decoding=\"async\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\" alt=\"User Tip\" \/><\/a>[attr style=”width:90px”],”When exporting data using MarcEdit’s Export Settings tool, MarcEdit creates a specialized zip file as part of the package. \u00a0The specialized zip file provides the import tool with some additional information that is used to optimize the ingest process. \u00a0However, users can view the files in a MarcEdit .export file by simply changing the extension to a .zip and uncompressing the file. By the same token, users that simply zip their Application Settings directory can import a zip file directly into MarcEdit using the Import Settings tool, though it is highly recommended that the Export tool be used when sharing configuration settings.”<\/p>\n<p>[\/table]<\/p>\n<p>[table]<\/p>\n<p><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\"><img decoding=\"async\" class=\"alignnone wp-image-175\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\" alt=\"User Tip\" \/><\/a>[attr style=”width:90px”],”MarcEdit’s global import settings will overwrite any existing settings previously on the users machine. \u00a0Users looking to share tasks should utilize the Task Management tool to export and import individual tasks. \u00a0This process does not overwrite existing data.”<\/p>\n<p>[\/table]<\/p>\n<h3>Resetting MarcEdit’s Configuration Data<\/h3>\n<p>As noted earlier, MarcEdit stores a great deal of data in its configuration files. \u00a0Aside from the obvious application preferences, the application captures information related to user preference and file histories. \u00a0User preferences include information related to the sizing of windows, the positioning of the application on the screen, and the size of fonts. \u00a0The program also captures convenience information related to last file open, last directory accessed within the application, a history of regular expressions run, and the replacements paired with them. \u00a0These user preferences impact the accessibility of the application, making the program easier to navigate and providing a more consistent experience for the user. \u00a0By the same token, if these user preferences get corrupted, it can negatively impact the application.<\/p>\n<p>So what would cause MarcEdit’s user preference information to get corrupted? \u00a0Generally, it can occur if MarcEdit is improperly terminated. \u00a0While the application goes to great lengths to sanitize and validate data at both the reading and writing stages, forcefully terminating the application can interrupt this process and in extremely rare cases, result in data corruption. \u00a0So how does this corruption manifest itself? \u00a0MarcEdit will be unable to save user preference data into the configuration files, meaning that screen sizes, file paths, etc. will no longer be remembered.<\/p>\n<p>In previous versions of MarcEdit, configuration file corruption occurred a little more frequently, and the fix was to open the config.xml file and manually fix the corrupted data. \u00a0As MarcEdit has matured, these corruption errors have being incredibly rare, though the process for fixing these errors was essentially the same manual process. \u00a0This changed in MarcEdit 5.9+, when a new option was added to the MarcEdit Help menu…the ability to reset your application configuration settings.<\/p>\n<div id=\"attachment_325\" style=\"width: 543px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/meresetconfigdata.png\" rel=\"attachment wp-att-325\"><img aria-describedby=\"caption-attachment-325\" decoding=\"async\" loading=\"lazy\" class=\"size-full wp-image-325\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/meresetconfigdata.png\" alt=\"Figure 15: Reset Configuration Data\" width=\"533\" height=\"488\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/meresetconfigdata.png 533w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/meresetconfigdata-300x275.png 300w\" sizes=\"(max-width: 533px) 100vw, 533px\" \/><\/a><p id=\"caption-attachment-325\" class=\"wp-caption-text\">Figure 15: Reset Configuration Data<\/p><\/div>\n<p>Figure 15 illustrates where the function can be found within the application. \u00a0This function returns MarcEdit’s configuration settings back to their default state. \u00a0On installation, MarcEdit maintains a clean copy of all configuration data with the application program directory, under a resources directory. \u00a0When this function is run, MarcEdit will utilize these clean master files to refresh the users configuration settings.<\/p>\n<p> <\/p>\n<p> <\/p>\n<p> <\/p>\n","protected":false},"excerpt":{"rendered":"<p>In This Chapter: What happens on first run Configuring the MARCEngine Associating Files with MarcEdit Setting up MarcEdit’s Automatic Update Miscellaneous Settings Where are my configuration settings Congratulations! \u00a0You’ve installed MarcEdit and now you are ready to start using the application. \u00a0But where do you start? \u00a0Like most applications, MarcEdit’s user interface has gone through […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":23,"menu_order":2,"comment_status":"open","ping_status":"open","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/pages\/117"}],"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=117"}],"version-history":[{"count":63,"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/pages\/117\/revisions"}],"predecessor-version":[{"id":547,"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/pages\/117\/revisions\/547"}],"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=117"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}