{"id":37,"date":"2013-05-25T07:02:24","date_gmt":"2013-05-25T07:02:24","guid":{"rendered":"http:\/\/marcedit.reeset.net\/learning_marcedit\/?page_id=37"},"modified":"2016-04-14T20:38:07","modified_gmt":"2016-04-14T20:38:07","slug":"chapter-1-getting-to-know-marcedit","status":"publish","type":"page","link":"https:\/\/marcedit.reeset.net\/learning_marcedit\/welcome-to-marcedit\/chapter-1-getting-to-know-marcedit\/","title":{"rendered":"Chapter 1: Getting to Know MarcEdit"},"content":{"rendered":"<h1>In this Chapter:<\/h1>\n<ul>\n<li><strong><span style=\"line-height: 13px;\">Where it all started<\/span><\/strong><\/li>\n<li><strong>MarcEdit through the years<\/strong><\/li>\n<li><strong>Looking to the future<\/strong><\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h2>Where it all started<\/h2>\n<p>I would like to be able to say that the development and release of MarcEdit was part of a grand master plan to equip technical services librarians with the tools necessary to manipulate their institution&#8217;s metadata. \u00a0That would be a good story, but it isn&#8217;t mine. \u00a0Like many undergraduate students at the University of Oregon, I held a work-study position in the university library system, specifically the Maps and Aerial Photography (MAP) Library. \u00a0It was there that I was first introduced to concepts like MARC, OCLC, and AACR2. \u00a0While at the University of Oregon, the MAP Library functioned more as a departmental library for the Geography Department &#8212; it was part of the library system, but the close ties to the department and the distance from the main library allowed the Library and its staff to work largely independent of the main library system. It was during my tenure at the MAP Library that then Head of the MAP Library, Peter Stark, began instructing me on historical cartographic cataloging. \u00a0For years, Mr. Stark was cataloging the historical cartographic collections into the catalog, but OCLC&#8217;s Passport\u00a0was a pain point, and we were interesting in knowing if there was a better way.<\/p>\n<p>While I had no background in libraries, I did come to the MAP Library with a background in computers. \u00a0At the time, working on a cataloging record required using OCLC&#8217;s Passport for Windows. \u00a0This program looked like a telnet screen, and essentially functioned as a specialized telnet client. \u00a0We&#8217;d\u00a0toss some information into this telnet program and out would come a neatly formatted binary file that we would magically load into the Library&#8217;s Integrated Library System (ILS). \u00a0I&#8217;ve always liked to know how things worked, and Passport for Windows was no exception. \u00a0I started spending time working to understand the process. \u00a0The resulting output was a set of tools that would allow me to build reports of MARC records so I could better understand what information was embedded in a record. \u00a0It certainly wasn&#8217;t much, but this work began a life-long exploration of how library metadata moves and interacts with other systems, and served as the precursor to MarcEdit&#8217;s initial coding libraries.<\/p>\n<p>After graduating from the University of Oregon, I took a cataloging\u00a0position at Oregon State University (OREStateU). \u00a0This would be the first time that I worked with other catalogers in a formal technical services environment. \u00a0It was also the first time I found out how wonderfully nuts folks in technical services can be. \u00a0Shortly after starting at OREStateU Libraries, the Technical Services Department met to discuss it&#8217;s next big project. OREStateU Libraries had\u00a0been utilizing a process to change SuDoc numbers into the Library of Congress Classification system\u00a0and by and large, this process was working reliably. \u00a0But like all automated processes, there had been exceptions, and over a period of time those exceptions had grown into a problem representing\u00a0nearly 100,000 records\u00a0given incorrect classifications. \u00a0On the tables were reams and reams of printed out spreadsheets, each containing the incorrect and correct classification numbers. \u00a0The project was presented as a 3-5 year effort and would involve everyone taking a range of records and making manual changes. \u00a0Given the staff in the Libraries, it worked out to ~15,000 records per person.<\/p>\n<p>I, on the other hand, was starting to rethink my decision of working in libraries.<\/p>\n<p><!--nextpage--><\/p>\n<p>To complete the project, OREStateU Libraries has identified and collected the records that needed to be updated and an electronic copy identifying each of the changes to be made in Excel. \u00a0Given the very narrow nature of the problem, I thought that maybe I could provide a more efficient path to completing the project. \u00a0Using what I&#8217;d learned as a student, I developed a core set of code libraries that I could use in applications like Visual Basic or the Visual Basic Application macro language embedded in Excel. \u00a0Working from within Excel, I was able to develop a proof of concept macro that could take a file containing the problem records and modify the data based on the information in Excel. \u00a0Working over a couple of days, I tested a random sampling of records needing to be corrected, and when I was finally confident in the process, I approached Kyle Banerjee to talk about my plan.<\/p>\n<p>Having Kyle at the OREStateU Libraries at the time that I was starting out really became the catalyst for the work that I would do in the future. \u00a0Kyle was and is a kindred spirit. \u00a0He loved to experiment and actively looked for opportunities to utilize new and emerging technology in the library. \u00a0He was also the first librarian that I&#8217;d ever met that actively was learning how to write code and had no problems breaking as much stuff as he fixed. \u00a0He was also a bit of a troublemaker at times, and I have to admit, I often appreciated and adopted his mantra of asking for forgiveness rather than permission. \u00a0Working with Kyle, I demonstrated the process I&#8217;d developed to correct the records. \u00a0And after a little back and forth, I&#8217;d completed the project over a couple of hours. \u00a0It was at the completion of that work, that Kyle started nudging me to consider developing the project further to make this type of functionality easily available to the larger library community. \u00a0Over a couple of months, I would develop a wireframe for the application and then worked with Kyle to test my assumptions and make sure that the tools could be generalized to a larger audience. \u00a0Fortunately, Kyle was an excellent beta tester because he didn&#8217;t mind if something accidentally went wrong. \u00a0As my guinea pig, I think I rendered Kyle&#8217;s PC unusable more than a couple of times but he stuck with it, and the final product ended up being MarcEdit 1.0.<\/p>\n<p>I can honestly say, that had it not been for Kyle&#8217;s encouragement, MarcEdit never would have became a tool for public consumption and I likely wouldn&#8217;t be in libraries today. \u00a0He really was the right person at the right time for me &#8212; helping to change my perceptions of what libraries and librarians did, and pushed me to move outside of my comfort-zone to start asking my own research questions and building my own research agenda. Kyle became one of my biggest cheerleaders and supporters. \u00a0I&#8217;d often hear him telling people that MarcEdit was the &#8220;greatest thing since sliced bread&#8221; and he pushed me to continue developing the program. \u00a0He helped me build connections in the field with other catalogers and ultimately, when I decided to go back to school for my MLS &#8212; he kept me sane during the process.<\/p>\n<h3><\/h3>\n<h2>MarcEdit through the years<\/h2>\n<p>I&#8217;ve been working on MarcEdit in some capacity for seventeen years and during that time, the program has gone through a number of significant revisions. \u00a0At a source code level, MarcEdit originated as a program written in a combination of Assembly and Visual Basic. \u00a0All of the code libraries where written Assembly, and all the user interface components and programmers API were developed or exposed using Visual Basic. \u00a0Around 2004, to accommodate the increasing usage of UTF-8 data, I did a 100% rewrite of the MarcEdit code-base, migrating the application into the C# programming language. \u00a0The drivers behind this decision really revolved around a desire to provide MarcEdit on multiple platforms, and both a Microsoft sponsored and open source sponsored implementation of the C# language were available. \u00a0What&#8217;s more, I had hoped that by porting the code to a higher level language, I could open up some of the MarcEdit code-base and potentially, look at opening up the entire MarcEdit code-base. For the most part, this has been what has occurred. \u00a0While I haven&#8217;t made the decision to open up the entire MarcEdit code-base as of yet, I have released the code for many of the tools and libraries that make up the application.<!--nextpage--><\/p>\n<p><strong>MarcEdit 1.0<\/strong><\/p>\n<p>In terms of the MarcEdit user interface, the program has changed significantly. \u00a0Since MarcEdit was originally developed as a set of coding libraries and tools, MarcEdit 1.0 really focused on providing a graphical interface to those tools and functions.<\/p>\n<div id=\"attachment_39\" style=\"width: 447px\" class=\"wp-caption alignleft\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/startup1.jpg\"><img aria-describedby=\"caption-attachment-39\" decoding=\"async\" loading=\"lazy\" class=\"size-full wp-image-39 \" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/startup1.jpg\" alt=\"MarcEdit 1.0\" width=\"437\" height=\"258\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/startup1.jpg 437w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/startup1-300x177.jpg 300w\" sizes=\"(max-width: 437px) 100vw, 437px\" \/><\/a><p id=\"caption-attachment-39\" class=\"wp-caption-text\">Figure 1: MarcEdit 1.0 Startup Screen<\/p><\/div>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>In Figure 1 above, you can see the original MarcEdit startup screen. \u00a0Early versions of MarcEdit essentially exposed the functionality of the MARCEngine, the underlying coding libraries used to process MARC data. \u00a0What&#8217;s more, the program interface was largely influenced by the Library of Congress&#8217;s MARCBreakr\/MARCMakr [ref]http:\/\/www.loc.gov\/marc\/makrbrkr.html#download[\/ref] and the way the tool separated specific operations. \u00a0Looking back, the tool lacks many of the functions that make MarcEdit useful within today&#8217;s metadata environment. \u00a0In 2000, when the first public version of MarcEdit was released, few catalogers had the ability to directly manipulate MARC data once it was loaded into OCLC or their organization&#8217;s ILS. \u00a0Records management was largely taken out of the hands of the catalogers and moved into library information technology units where tools like MARC PERL could be utilized to build scripts that could edit batches of records. \u00a0MarcEdit represented the first concerted effort to provide a graphical, free MARC editing client to the cataloging community.<\/p>\n<div id=\"attachment_41\" style=\"width: 654px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/startup2_thumb.jpg\"><img aria-describedby=\"caption-attachment-41\" decoding=\"async\" loading=\"lazy\" class=\"size-full wp-image-41 \" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/startup2_thumb.jpg\" alt=\"MarcBreaker\" width=\"644\" height=\"338\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/startup2_thumb.jpg 644w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/startup2_thumb-300x157.jpg 300w\" sizes=\"(max-width: 644px) 100vw, 644px\" \/><\/a><p id=\"caption-attachment-41\" class=\"wp-caption-text\">Figure 2: MarcBreaker<\/p><\/div>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<div id=\"attachment_42\" style=\"width: 654px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/startup3_thumb.jpg\"><img aria-describedby=\"caption-attachment-42\" decoding=\"async\" loading=\"lazy\" class=\"size-full wp-image-42 \" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/startup3_thumb.jpg\" alt=\"\" width=\"644\" height=\"297\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/startup3_thumb.jpg 644w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/startup3_thumb-300x138.jpg 300w\" sizes=\"(max-width: 644px) 100vw, 644px\" \/><\/a><p id=\"caption-attachment-42\" class=\"wp-caption-text\">Figure 3: MarcMaker<span style=\"font-size: 13px; line-height: 19px;\">\u00a0<\/span><\/p><\/div>\n<p>&nbsp;<\/p>\n<p>Figure 2 and 3 illustrate the MarcBreaker and MarcMaker windows. Early on, you can see that MarcEdit started to introduce this idea of editing records visually inline as part of the breaking and making process. \u00a0In Figure 2, there is an option to edit records once a file was processed. Likewise, in Figure 3, there is an option to open an edit window (Figure 4 below). \u00a0These edit windows were the early precursors to MarcEdit&#8217;s MarcEditor &#8212; a specialized notepad for editing MARC records. \u00a0The other thing I&#8217;d like to highlight\u00a0is the option in Figure 2 called Quick Break. Early on in the development process, I found it necessary to start investigating different methods for handling invalid MARC data provided by vendors. \u00a0This early version of MarcEdit provided users a toggle so that they could switch between a breaking algorithm that strictly followed the MARC specification, or a permissive breaking algorithm that made a number of assumptions about a record&#8217;s format in order to over come structural errors in the records. Today, this functionality still exists in MarcEdit, though the process has become much more advanced and is done automatically for the user.<\/p>\n<div id=\"attachment_45\" style=\"width: 520px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/editor_thumb.jpg\"><img aria-describedby=\"caption-attachment-45\" decoding=\"async\" loading=\"lazy\" class=\"size-full wp-image-45\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/editor_thumb.jpg\" alt=\"Figure 4: MarcEditor\" width=\"510\" height=\"484\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/editor_thumb.jpg 510w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/editor_thumb-300x284.jpg 300w\" sizes=\"(max-width: 510px) 100vw, 510px\" \/><\/a><p id=\"caption-attachment-45\" class=\"wp-caption-text\">Figure 4: MarcEditor<\/p><\/div>\n<p>&nbsp;<\/p>\n<h3>MarcEdit 3.0<\/h3>\n<p>MarcEdit 3.0 represented the first major change to the MarcEdit interface. \u00a0This was the version that introduced a full fledged MarcEditor, attempted to address the growing problems of diacritics between varying flavors of MARC, and began looking at how non-MARC data like delimited text could be integrated into MARC data. \u00a0This version also represented the point in which MarcEdit became more mainstream. \u00a0Up until this point, the application was largely used by a handful of people at OREStateU, a few folks in the Pacific Northwest, and the people Kyle Banerjee ran into and convinced to give it a try. \u00a0Around MarcEdit 3.0 was the first time I started hearing people talk about the application at conferences and in presentations, and the first time I saw it show up in an article discussing automating metadata workflows.<!--nextpage--><\/p>\n<div id=\"attachment_46\" style=\"width: 569px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/startup11.jpg\"><img aria-describedby=\"caption-attachment-46\" decoding=\"async\" loading=\"lazy\" class=\"size-full wp-image-46\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/startup11.jpg\" alt=\"Figure 5: MarcEdit 3.0 Startup\" width=\"559\" height=\"344\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/startup11.jpg 559w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/startup11-300x184.jpg 300w\" sizes=\"(max-width: 559px) 100vw, 559px\" \/><\/a><p id=\"caption-attachment-46\" class=\"wp-caption-text\">Figure 5: MarcEdit 3.0 Startup<\/p><\/div>\n<div id=\"attachment_47\" style=\"width: 654px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/meStartup_thumb.jpg\"><img aria-describedby=\"caption-attachment-47\" decoding=\"async\" loading=\"lazy\" class=\"size-full wp-image-47\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/meStartup_thumb.jpg\" alt=\"Figure 6: MarcEdit 3.0 MarcEditor\" width=\"644\" height=\"387\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/meStartup_thumb.jpg 644w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/meStartup_thumb-300x180.jpg 300w\" sizes=\"(max-width: 644px) 100vw, 644px\" \/><\/a><p id=\"caption-attachment-47\" class=\"wp-caption-text\">Figure 6: MarcEdit 3.0 MarcEditor<\/p><\/div>\n<p>Figure 6 shows the first version of the MarcEditor, which appears in MarcEdit 3.0. \u00a0The MarcEditor introduced for the first time, this idea of a specialized notepad environment designed around the manipulation of MARC records. \u00a0While previous version of MarcEdit included an edit window for quick edits, the MarcEdit took this a step further, by allowing users to load very large record sets and then globally make modifications uses a specialized set of editing tools designed around the MARC field\/subfield structure. \u00a0What&#8217;s more, by developing these tools around the universal MARC structure, rather than MARC21, the editor was able to be used with any flavor of MARC, making the application available to international users as well.<\/p>\n<p>&nbsp;<\/p>\n<h3>MarcEdit 5+<\/h3>\n<p>The current version of MarcEdit is a feature rich metadata client. \u00a0Unlike previous versions that focused solely on MARC data, the current version of MarcEdit introduces the ability to process various flavors of XML data, delimited data, and MARC data. \u00a0In addition to function related to the editing of metadata, the program includes tools to capture existing records, providing an OAI records harvester, a Z39.50 client, and functionality to directly integrate the application with Connexion and various ILS systems. \u00a0For information about the various tools and functions found in the current version of MarcEdit, please see the table of contents.<\/p>\n<p><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/marcedit5_9startup.png\"><img decoding=\"async\" loading=\"lazy\" class=\"alignnone size-full wp-image-273\" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/marcedit5_9startup.png\" alt=\"MarcEdit 5.9 Start-Up\" width=\"482\" height=\"444\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/marcedit5_9startup.png 482w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/marcedit5_9startup-300x276.png 300w\" sizes=\"(max-width: 482px) 100vw, 482px\" \/><\/a><\/p>\n<p>Figure 7: MarcEdit 5+ Startup<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<div id=\"attachment_49\" style=\"width: 778px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/marceditor5.png\"><img aria-describedby=\"caption-attachment-49\" decoding=\"async\" loading=\"lazy\" class=\" wp-image-49 \" src=\"http:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/marceditor5.png\" alt=\"Figure 8: MarcEdit 5+ MarcEditor\" width=\"768\" height=\"722\" srcset=\"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/marceditor5.png 960w, https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-content\/uploads\/2013\/05\/marceditor5-300x281.png 300w\" sizes=\"(max-width: 768px) 100vw, 768px\" \/><\/a><p id=\"caption-attachment-49\" class=\"wp-caption-text\">Figure 8: MarcEdit 5+ MarcEditor<\/p><\/div>\n<p>&nbsp;<\/p>\n<h2>Looking to the Future<\/h2>\n<p>Libraries currently find themselves in a volatile metadata environment. \u00a0Nearly every conference focused on technical services or metadata processing includes a number of sessions relating to how we deal with change, or addressing the migration from AACR2 encoded data to the new RDA [ref]Resource Description and Access,\u00a0http:\/\/access.rdatoolkit.org\/[\/ref] encoding standard. On the horizon there is the Library of Congress&#8217;s Bibframe [ref]Bibframe Initiative,\u00a0http:\/\/bibframe.org\/[\/ref] that seeks to replace the MARC format with a new bibliographic framework that takes advantage of current technology and data models. How these changes shake out will certainly affect MarcEdit.<\/p>\n<p>I&#8217;m trying to take a pragmatic approach to how MarcEdit addresses the many new metadata initiatives moving through the library community. \u00a0In 2013, MarcEdit introduced the RDA Helper, a tool designed to help libraries automatically migrate AACR2 data into RDA, or take existing RDA records encoding under previous versions of the standard, and move them up to the current encoding standard. \u00a0The tool has been designed to be a stop gap to help libraries and librarians trying to manage multiple data formats a simple process for converting records cataloged using AACR2 rules. \u00a0Because MarcEdit is utilized by many content vendors to generate their MARC records, this tool can also be used to enable content providers a straightforward migration path for their bibliographic records.<!--nextpage--><\/p>\n<p>In 2014, MarcEdit introduced MARCNext. \u00a0This toolset allows catalogers the opportunity to experiment with BibFrame and semantic web concepts. \u00a0These tools will likely provide the framework for many of the new enhancements that make their way into the MarcEdit application, and hopefully provide a method for catalogers to engage in the rich discussions happening within the larger BibFrame communities.<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In this Chapter: Where it all started MarcEdit through the years Looking to the future &nbsp; Where it all started I would like to be able to say that the development and release of MarcEdit was part of a grand master plan to equip technical services librarians with the tools necessary to manipulate their institution&#8217;s [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":23,"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\/37"}],"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=37"}],"version-history":[{"count":15,"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/pages\/37\/revisions"}],"predecessor-version":[{"id":472,"href":"https:\/\/marcedit.reeset.net\/learning_marcedit\/wp-json\/wp\/v2\/pages\/37\/revisions\/472"}],"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=37"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}