{"id":293,"date":"2016-01-04T19:14:13","date_gmt":"2016-01-04T19:14:13","guid":{"rendered":"http:\/\/marcedit.reeset.net\/learning_marcedit\/?page_id=293"},"modified":"2017-09-14T14:32:53","modified_gmt":"2017-09-14T14:32:53","slug":"getting-to-know-marc-tools-and-the-marcengine","status":"publish","type":"page","link":"https:\/\/marcedit.reeset.net\/learning_marcedit\/9-2\/getting-to-know-marc-tools-and-the-marcengine\/","title":{"rendered":"Chapter 1: Getting to Know MARC Tools"},"content":{"rendered":"<h3>In this Chapter:<\/h3>\n<ul>\n<li><strong>Getting started with MARC Tools<\/strong><\/li>\n<li><strong>Where do I find things?<\/strong><\/li>\n<li><strong>Processing MARC Data<\/strong><\/li>\n<li><strong>Handling Invalid Data<\/strong><\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h3>Getting Started<\/h3>\n<p>One of MarcEdit&#8217;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<p>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&#8217;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<p>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<h3>MARC Tools Window<\/h3>\n<div id=\"attachment_328\" style=\"width: 807px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2014\/02\/metoolswindow.png\" rel=\"attachment wp-att-328\"><img aria-describedby=\"caption-attachment-328\" decoding=\"async\" loading=\"lazy\" class=\"size-full wp-image-328\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2014\/02\/metoolswindow.png\" alt=\"Figure 1: MARC Tools Window\" width=\"797\" height=\"742\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2014\/02\/metoolswindow.png 797w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2014\/02\/metoolswindow-300x279.png 300w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2014\/02\/metoolswindow-768x715.png 768w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2014\/02\/metoolswindow-624x581.png 624w\" sizes=\"(max-width: 797px) 100vw, 797px\" \/><\/a><p id=\"caption-attachment-328\" class=\"wp-caption-text\">Figure 1: MARC Tools Window<\/p><\/div>\n<p>Figure 1 shows the current iteration of the MARC Tools window.\u00a0 It also illustrates something important about MarcEdit; the MARCEngine, the code library that handles all metadata processing within MarcEdit, only includes 4 built in processing algorithms:<\/p>\n<ol>\n<li>MarcBreaker &#8212; This function decompiles binary MARC data into MarcEdit&#8217;s mnemonic format.<\/li>\n<li>MarcMaker &#8212; This function compiles MarcEdit&#8217;s mnemonic file format into MARC.<\/li>\n<li>MARC=&gt;MARC21XML &#8212; This function translates binary MARC data to MARC21XML.<\/li>\n<li>MARC21XML=&gt;MARC &#8212; This function translates MARC21XML data to binary MARC.<\/li>\n<\/ol>\n<p>These are the only 4 functions directly coded into the MARCEngine, and yet, MarcEdit provides a number of other XML translation functions that have the ability to convert data from an XML metadata format into another user-defined format (be that MARC, MARC21XML, or Other).\u00a0 Unlike MarcEdit&#8217;s built in metadata processing routines, MarcEdit supports XML metadata crosswalking through the use of the eXtensible Stylesheet Language (XSLT), many of which MarcEdit provides on installation or can be created by the user.\u00a0\u00a0The net effect\u00a0of this design is that MarcEdit is able to provide a set of tools for users wanting to work with bibliographic data from a wide range of sources and formats, without becoming a bottleneck when it comes to supported metadata translations. \u00a0The challenge, however, is that the translations that are provided in MarcEdit are oftentimes more like templates &#8212; they implement the most common method for translation between metadata formats, which may, or may not completely suite one&#8217;s needs. \u00a0In those cases where enhancements or changes need to be made, there is an assumption that users will be able to edit the XSLT files directly and update these processes as necessary.<!--nextpage--><\/p>\n<p>[table]<a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\"><img decoding=\"async\" loading=\"lazy\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\" alt=\"tip\" width=\"85\" height=\"75\" \/><\/a>\u00a0[attr style=&#8221;width:90px&#8221;], &#8220;More discussion on how MarcEdit works with XML data can be found in the Chapter: Working with XML Data.&#8221;[\/table]<\/p>\n<p>&nbsp;<\/p>\n<h3>Where do I find things?<\/h3>\n<p>Looking at Figure 1, it may appear that the MARC Tools component only provides access to tools and functions used in translating library metadata.\u00a0 That, however, would be an incorrect assumption.\u00a0 The following functions can be accessed from the MARC Tools component:<\/p>\n<ul>\n<li>MARCSplit &#8212; A tool that can split a single MARC file into multiple files.<\/li>\n<li>MARCJoin &#8212; A tool that can take multiple MARC files and join them into a single MARC file.<\/li>\n<li>Character Conversions &#8212; A tool that supports the ability to translate MARC records from a wide variety of supported character encodings.<\/li>\n<li>Batch Record Processing &#8212; A tool that facilitates the processing of multiple files at one time.<\/li>\n<li>MARCValidator &#8212; a tool for Validating MARC Records.<\/li>\n<\/ul>\n<p>These tools can be accessed via Tools Menu Icon:<\/p>\n<div id=\"attachment_330\" style=\"width: 475px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/meToolsMenu.png\" rel=\"attachment wp-att-330\"><img aria-describedby=\"caption-attachment-330\" decoding=\"async\" loading=\"lazy\" class=\"size-full wp-image-330\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/meToolsMenu.png\" alt=\"Figure 2: MARC Tools Tools Menu\" width=\"465\" height=\"361\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/meToolsMenu.png 465w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/meToolsMenu-300x233.png 300w\" sizes=\"(max-width: 465px) 100vw, 465px\" \/><\/a><p id=\"caption-attachment-330\" class=\"wp-caption-text\">Figure 2: MARC Tools Tools Menu<\/p><\/div>\n<p>[table]<a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\"><img decoding=\"async\" loading=\"lazy\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\" alt=\"tip\" width=\"85\" height=\"75\" \/><\/a>\u00a0[attr style=&#8221;width:90px&#8221;], &#8220;Access to most of these tools can also be found from the Main MarcEdit Window under either the Tools menu or Add-ins menu. \u00a0Also, many tools like the Join, Split, and Merge tools can be added to the MarcEdit home screen through the preferences.&#8221;[\/table]<\/p>\n<p>While many of these functions will be discussed in later chapters, a couple of items are important to highlight.<\/p>\n<ul>\n<li><em>Edit XML Function List:\u00a0<\/em> Users can edit or modify how MarcEdit&#8217;s XML Transformations work by making changes to a specific XSLT&#8217;s configuration values. \u00a0These values are set by editing the XML Function List options. \u00a0This option is also how users add or delete XML functions from the application.<\/li>\n<li><em>Character Conversion Tools: \u00a0<\/em>Given the internationalize of Library metadata &#8212; MarcEdit provides a tool specifically to move data from local charactersets into UTF8 or MARC8 and then back into a local characterset. \u00a0The tool provides access to the most common charactersets used by the MarcEdit community, but users can select from any characterset supported by their operating system.<\/li>\n<li><em>MARCValidator<\/em>: \u00a0The MARCValidator serves a number of roles within the MarcEdit application. \u00a0While the tool does provide a Rules file that will enable a user to &#8220;validate&#8221; their record against AACR2 assumptions &#8212; for the purpose of the MARC Tools window &#8212; the MARCValidator provides a method for testing the structural validity of a particular set of records and isolating invalid data for later processing.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h3>Processing MARC Data<\/h3>\n<p>A lot of people come to MarcEdit with a set of file data, and a need to get this data into a format that can be edited before loading it into their local library information system. \u00a0Essentially, this is what the MARC Tools function does. \u00a0It exposes to the user MarcEdit&#8217;s MARCEngine functionality, allowing users to &#8220;break&#8221; their binary MARC data into a more user friendly mnemonic format that can then be edited in MarcEdit&#8217;s MarcEditor or in any other text editing tool like Notepad+ or UltraEdit.<\/p>\n<h4>Mnemonic Format<\/h4>\n<p>The mnemonic format MarcEdit utilizes is very specific. \u00a0Within the format, some characters are reserved (primarily the &#8220;$&#8221; which stands in for the delimiter character) and some characters have special meaning when placed at the front of lines. \u00a0Here&#8217;s a list of the current rules that govern MarcEdit&#8217;s mnemonic format:<\/p>\n<ol>\n<li>New lines always start with an &#8220;=&#8221; sign. \u00a0For example: =245 \u00a0\\\\$aThis is a title.<\/li>\n<li>Fields use the following format: ={fieldnumber}{2 blank spaces}{ind0-9}. \u00a0Number of indicators is defined within the MARC leader. \u00a0The most important values in this mnemonic string are the equal sign, which designates a new field, and the two blanks between the field value and the first indicator (or the start of control data).<\/li>\n<li>Control field format (fields between 000-009): ={field}{2 blank spaces}[start of control data]<\/li>\n<li>Variable field format (fields between 010-999; aaa-ZZZ): ={field}{2 blank spaces}{ind0-9}[variable data with delimiters]<\/li>\n<li>Comments can be embedded in the mnemonic file format by using a pound sign at the beginning of a line: i.e.: #this is a comment.<\/li>\n<li>New lines designate the end of a field.<\/li>\n<li>Blank line indicates the end of a record<\/li>\n<li>All records must have a Leader designated in field =LDR or =000.<\/li>\n<li>The following values are reserved by the mnemonic format: &#8220;$&#8221;, &#8220;{&#8220;, &#8220;}&#8221;. \u00a0These require the use of mnemonics when using these as literal values: {dollar} = &#8220;$&#8221;, {lcub} = &#8220;{&#8220;, {rcub} = &#8220;}&#8221;<\/li>\n<li>MARC records have field and record limits (9,999 bytes for fields, 99,999 bytes for records). \u00a0The mnemonic format does not enforce these limits while editing, but when compiling back to MARC, the tool will truncate data if a record exceeds the field or record length limits.<\/li>\n<\/ol>\n<p><strong>Mnemonic Record Example:<\/strong><\/p>\n<pre>=LDR 05658cam 2200949 a 4500 \r\n=001 ocm70844414\\ \r\n=007 cr\\||||||||||| \r\n=008 060807s2006\\\\\\\\maua\\\\\\\\of\\\\\\\\001\\0\\eng\\c \r\n020 \\\\$a1597490768 \r\n=072 \\7$aCOM$x053000$2bisacsh \r\n=082 04$a005.8\/068$222 \r\n=049 \\\\$aTFWW \r\n=100 1\\$aSnedaker, Susan. \r\n=245 10$aSyngress IT security project management handbook$h[electronic resource] \/$cSusan Snedaker ; Russ Rogers, technical editor. \r\n=246 30$aIT security project management handbook \r\n=260 \\\\$aRockland, MA :$bSyngress Pub.,$c{copy}2006. \r\n=300 \\\\$a1 online resource (xxvi, 612 pages) :$billustrations \r\n=336 \\\\$atext$btxt$2rdacontent \r\n=337 \\\\$acomputer$bc$2rdamedia \r\n=338 \\\\$aonline resource$bcr$2rdacarrier \r\n=500 \\\\$aIncludes index. \r\n=650 \\0$aComputer security$xManagement$vHandbooks, manuals, etc. \r\n=776 08$iPrint version:$aSnedaker, Susan.$tSyngress IT security project management handbook.$dRockland, MA : Syngress, c2006$z1597490768$z9781597490764$w(OCoLC)72763213 \r\n\r\n<\/pre>\n<h3>Breaking MARC Records<\/h3>\n<p>To &#8220;break&#8221; a MARC record into MarcEdit&#8217;s mnemonic format for editing, select the MarcBreaker option, and then reference the file to be processed in the Input TextBox and the Save File in the Output Textbox. \u00a0By default, MarcEdit associates .mrc file extensions with the MarcBreaker and .mrk file extensions with the MarcEditor. \u00a0When selecting the input and output files, the tool will default to looking for a .mrc file for input and creating a .mrk file as the output. \u00a0These are the extensions MarcEdit has registered with the program, but users are free to use whatever extension that would like to represent their data.<!--nextpage--><\/p>\n<p>[table]<a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\"><img decoding=\"async\" loading=\"lazy\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/tip.png\" alt=\"tip\" width=\"85\" height=\"75\" \/><\/a>\u00a0[attr style=&#8221;width:90px&#8221;], &#8220;A common question that comes up related to MarcEdit is what file extensions does the program support. \u00a0Vendors and ILS systems output MARC Data using a wide range of file extensions ranging from .mrc, .txt, .out, .dat..and many more. \u00a0From MarcEdit&#8217;s perspective, file extensions are meaningless. \u00a0The are used as a convenience function to allow the program to make guesses as to what action the user may want to perform. \u00a0However, if you have a MARC file in a file with the extension of .marcunicorns &#8212; MarcEdit will happily process it. \u00a0You just need to change the file filter in the file selection box from .mrc to all files.&#8221;[\/table]<\/p>\n<p>After selecting the files for processing, then select Execute. \u00a0The program would provide a number of records processed in the Results Box below.<\/p>\n<div id=\"attachment_337\" style=\"width: 807px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/metoolsprocesseddata.png\" rel=\"attachment wp-att-337\"><img aria-describedby=\"caption-attachment-337\" decoding=\"async\" loading=\"lazy\" class=\"wp-image-337 size-full\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/metoolsprocesseddata.png\" alt=\"Figure 3: MarcBreaker\" width=\"797\" height=\"742\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/metoolsprocesseddata.png 797w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/metoolsprocesseddata-300x279.png 300w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/metoolsprocesseddata-768x715.png 768w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/metoolsprocesseddata-624x581.png 624w\" sizes=\"(max-width: 797px) 100vw, 797px\" \/><\/a><p id=\"caption-attachment-337\" class=\"wp-caption-text\">Figure 3: MarcBreaker<\/p><\/div>\n<h3>Remaking Records<\/h3>\n<p>After editing a mnemonic file, the data will need to be compiled back into MARC before the data will be usable by most library systems. \u00a0To do this, you repeat the process for breaking the record, with the following changes:<\/p>\n<ol>\n<li>Select the MarcMaker tool<\/li>\n<li>Input File should be set as the mnemonic file to be processed.<\/li>\n<li>Output File is the MARC file to be generated<\/li>\n<\/ol>\n<p>Once these are set, click the execute button, and like the MarcBreaker &#8212; the tool will generate a results message noting the number of records processed.<\/p>\n<h3>Handling Invalid Data<\/h3>\n<p>With all the data libraries get from publishers, content providers, and other sources, one is bound to get some data that just isn&#8217;t structurally valid. \u00a0This data can usually cause significant loading issues for staff when trying to import data files into an ILS system. \u00a0In MarcEdit, the tool provides two methods for process MARC data:<\/p>\n<ol>\n<li>strict MARC processing algorithm<\/li>\n<li>loose MARC processing algorithm<\/li>\n<\/ol>\n<p>By default, the tool utilizes the strict process algorithm to handle MARC data. \u00a0This processor will only work if the data is structurally correct. \u00a0When the tool encounters a record that isn&#8217;t valid &#8212; it falls back to the second algorithm and attempts to &#8220;heal&#8221; the record. \u00a0When this occurs, the tool will note that structural data errors were present in the record set, and print the Results Message in <span style=\"color: #ff0000;\">*red*<\/span>. \u00a0When this occurs, it is recommended that users utilize the MARCValidator to identify the type of error found in the record, and then take appropriate action (which could be nothing [i.e., MarcEdit healed it], to excluding the offending data for later processing).<\/p>\n<div id=\"attachment_338\" style=\"width: 807px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/metoolsinvaliddata.png\" rel=\"attachment wp-att-338\"><img aria-describedby=\"caption-attachment-338\" decoding=\"async\" loading=\"lazy\" class=\"wp-image-338 size-full\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/metoolsinvaliddata.png\" alt=\"Figure 4: Invalid Record Data\" width=\"797\" height=\"742\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/metoolsinvaliddata.png 797w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/metoolsinvaliddata-300x279.png 300w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/metoolsinvaliddata-768x715.png 768w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/metoolsinvaliddata-624x581.png 624w\" sizes=\"(max-width: 797px) 100vw, 797px\" \/><\/a><p id=\"caption-attachment-338\" class=\"wp-caption-text\">Figure 4: Invalid Record Data<\/p><\/div>\n<h4>Using the MARCValidator<\/h4>\n<p>If an invalid record has been noted in a MARC Tools process (as in Figure 4), open the MARCValidator.<\/p>\n<div id=\"attachment_339\" style=\"width: 527px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/marcvalidator_invalid_records.png\" rel=\"attachment wp-att-339\"><img aria-describedby=\"caption-attachment-339\" decoding=\"async\" loading=\"lazy\" class=\"size-full wp-image-339\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/marcvalidator_invalid_records.png\" alt=\"Figure 5: MARCValidator\" width=\"517\" height=\"256\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/marcvalidator_invalid_records.png 517w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/marcvalidator_invalid_records-300x149.png 300w\" sizes=\"(max-width: 517px) 100vw, 517px\" \/><\/a><p id=\"caption-attachment-339\" class=\"wp-caption-text\">Figure 5: MARCValidator<\/p><\/div>\n<p><!--nextpage--><\/p>\n<p>The MARCValidator has 3 options:<\/p>\n<ol>\n<li><em>Validate Record (Default):<\/em> \u00a0This validates the data of the record utilizing the referenced Rules file.<\/li>\n<li><em>Identify Invalid Records:<\/em> \u00a0This identifies structurally invalid records in either MarcEdit&#8217;s mnemonic file format or in the MARC binary format.<\/li>\n<li><em>Remove Invalid Records: \u00a0<\/em>This will remove the offending data and place it in a .bad file in the same directory as the Source file.<\/li>\n<\/ol>\n<p>To identify why the MARC Tools program flagged a record set as having structurally invalid data, select the file to be tested and then select Identify Invalid Records option. \u00a0When processed, you&#8217;ll receive a set of results like Figure 6.<\/p>\n<div id=\"attachment_340\" style=\"width: 452px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/bad_recordsw.png\" rel=\"attachment wp-att-340\"><img aria-describedby=\"caption-attachment-340\" decoding=\"async\" loading=\"lazy\" class=\"size-full wp-image-340\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/bad_recordsw.png\" alt=\"Figure 6: Identifying Invalid Records\" width=\"442\" height=\"350\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/bad_recordsw.png 442w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2016\/01\/bad_recordsw-300x238.png 300w\" sizes=\"(max-width: 442px) 100vw, 442px\" \/><\/a><p id=\"caption-attachment-340\" class=\"wp-caption-text\">Figure 6: Identifying Invalid Records<\/p><\/div>\n<p>In Figure 6, we see that Record 1 was identified as having an error, and error was determined to be a record length error. \u00a0MarcEdit&#8217;s healing function can correct most of these types of structural errors &#8212; so a user may assume that the data was fixed correctly, or extract this record for processing later.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In this Chapter: Getting started with MARC Tools Where do I find things? Processing MARC Data Handling Invalid Data &nbsp; Getting Started One of MarcEdit&#8217;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 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":9,"menu_order":0,"comment_status":"open","ping_status":"open","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/pages\/293"}],"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=293"}],"version-history":[{"count":13,"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/pages\/293\/revisions"}],"predecessor-version":[{"id":543,"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/pages\/293\/revisions\/543"}],"up":[{"embeddable":true,"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/pages\/9"}],"wp:attachment":[{"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/media?parent=293"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}