CINXE.COM

News & Events | MetaArchive

<!DOCTYPE html> <!--[if IE 7]> <html class="ie ie7" lang="en-US"> <![endif]--> <!--[if IE 8]> <html class="ie ie8" lang="en-US"> <![endif]--> <!--[if !(IE 7) & !(IE 8)]><!--> <html lang="en-US"> <!--<![endif]--> <head> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width"> <title>News &amp; Events | MetaArchive</title> <link rel="profile" href="http://gmpg.org/xfn/11"> <link rel="pingback" href="https://metaarchive.org/xmlrpc.php"> <link rel="icon" type="image/png" href="/favicon.png"> <!--[if lt IE 9]> <script src="https://metaarchive.org/wp-content/themes/connectTheDots/js/html5.js"></script> <![endif]--> <meta name='robots' content='max-image-preview:large' /> <link rel="alternate" type="application/rss+xml" title="MetaArchive &raquo; Feed" href="https://metaarchive.org/feed/" /> <link rel="alternate" type="application/rss+xml" title="MetaArchive &raquo; Comments Feed" href="https://metaarchive.org/comments/feed/" /> <link rel="alternate" type="application/rss+xml" title="MetaArchive &raquo; News &amp; Events Category Feed" href="https://metaarchive.org/category/news-events/feed/" /> <link rel='stylesheet' id='wp-block-library-css' href='https://metaarchive.org/wp-includes/css/dist/block-library/style.min.css?ver=6.6.1' type='text/css' media='all' /> <style id='classic-theme-styles-inline-css' type='text/css'> /*! This file is auto-generated */ .wp-block-button__link{color:#fff;background-color:#32373c;border-radius:9999px;box-shadow:none;text-decoration:none;padding:calc(.667em + 2px) calc(1.333em + 2px);font-size:1.125em}.wp-block-file__button{background:#32373c;color:#fff;text-decoration:none} </style> <style id='global-styles-inline-css' type='text/css'> :root{--wp--preset--aspect-ratio--square: 1;--wp--preset--aspect-ratio--4-3: 4/3;--wp--preset--aspect-ratio--3-4: 3/4;--wp--preset--aspect-ratio--3-2: 3/2;--wp--preset--aspect-ratio--2-3: 2/3;--wp--preset--aspect-ratio--16-9: 16/9;--wp--preset--aspect-ratio--9-16: 9/16;--wp--preset--color--black: #000000;--wp--preset--color--cyan-bluish-gray: #abb8c3;--wp--preset--color--white: #ffffff;--wp--preset--color--pale-pink: #f78da7;--wp--preset--color--vivid-red: #cf2e2e;--wp--preset--color--luminous-vivid-orange: #ff6900;--wp--preset--color--luminous-vivid-amber: #fcb900;--wp--preset--color--light-green-cyan: #7bdcb5;--wp--preset--color--vivid-green-cyan: #00d084;--wp--preset--color--pale-cyan-blue: #8ed1fc;--wp--preset--color--vivid-cyan-blue: #0693e3;--wp--preset--color--vivid-purple: #9b51e0;--wp--preset--gradient--vivid-cyan-blue-to-vivid-purple: linear-gradient(135deg,rgba(6,147,227,1) 0%,rgb(155,81,224) 100%);--wp--preset--gradient--light-green-cyan-to-vivid-green-cyan: linear-gradient(135deg,rgb(122,220,180) 0%,rgb(0,208,130) 100%);--wp--preset--gradient--luminous-vivid-amber-to-luminous-vivid-orange: linear-gradient(135deg,rgba(252,185,0,1) 0%,rgba(255,105,0,1) 100%);--wp--preset--gradient--luminous-vivid-orange-to-vivid-red: linear-gradient(135deg,rgba(255,105,0,1) 0%,rgb(207,46,46) 100%);--wp--preset--gradient--very-light-gray-to-cyan-bluish-gray: linear-gradient(135deg,rgb(238,238,238) 0%,rgb(169,184,195) 100%);--wp--preset--gradient--cool-to-warm-spectrum: linear-gradient(135deg,rgb(74,234,220) 0%,rgb(151,120,209) 20%,rgb(207,42,186) 40%,rgb(238,44,130) 60%,rgb(251,105,98) 80%,rgb(254,248,76) 100%);--wp--preset--gradient--blush-light-purple: linear-gradient(135deg,rgb(255,206,236) 0%,rgb(152,150,240) 100%);--wp--preset--gradient--blush-bordeaux: linear-gradient(135deg,rgb(254,205,165) 0%,rgb(254,45,45) 50%,rgb(107,0,62) 100%);--wp--preset--gradient--luminous-dusk: linear-gradient(135deg,rgb(255,203,112) 0%,rgb(199,81,192) 50%,rgb(65,88,208) 100%);--wp--preset--gradient--pale-ocean: linear-gradient(135deg,rgb(255,245,203) 0%,rgb(182,227,212) 50%,rgb(51,167,181) 100%);--wp--preset--gradient--electric-grass: linear-gradient(135deg,rgb(202,248,128) 0%,rgb(113,206,126) 100%);--wp--preset--gradient--midnight: linear-gradient(135deg,rgb(2,3,129) 0%,rgb(40,116,252) 100%);--wp--preset--font-size--small: 13px;--wp--preset--font-size--medium: 20px;--wp--preset--font-size--large: 36px;--wp--preset--font-size--x-large: 42px;--wp--preset--spacing--20: 0.44rem;--wp--preset--spacing--30: 0.67rem;--wp--preset--spacing--40: 1rem;--wp--preset--spacing--50: 1.5rem;--wp--preset--spacing--60: 2.25rem;--wp--preset--spacing--70: 3.38rem;--wp--preset--spacing--80: 5.06rem;--wp--preset--shadow--natural: 6px 6px 9px rgba(0, 0, 0, 0.2);--wp--preset--shadow--deep: 12px 12px 50px rgba(0, 0, 0, 0.4);--wp--preset--shadow--sharp: 6px 6px 0px rgba(0, 0, 0, 0.2);--wp--preset--shadow--outlined: 6px 6px 0px -3px rgba(255, 255, 255, 1), 6px 6px rgba(0, 0, 0, 1);--wp--preset--shadow--crisp: 6px 6px 0px rgba(0, 0, 0, 1);}:where(.is-layout-flex){gap: 0.5em;}:where(.is-layout-grid){gap: 0.5em;}body .is-layout-flex{display: flex;}.is-layout-flex{flex-wrap: wrap;align-items: center;}.is-layout-flex > :is(*, div){margin: 0;}body .is-layout-grid{display: grid;}.is-layout-grid > :is(*, div){margin: 0;}:where(.wp-block-columns.is-layout-flex){gap: 2em;}:where(.wp-block-columns.is-layout-grid){gap: 2em;}:where(.wp-block-post-template.is-layout-flex){gap: 1.25em;}:where(.wp-block-post-template.is-layout-grid){gap: 1.25em;}.has-black-color{color: var(--wp--preset--color--black) !important;}.has-cyan-bluish-gray-color{color: var(--wp--preset--color--cyan-bluish-gray) !important;}.has-white-color{color: var(--wp--preset--color--white) !important;}.has-pale-pink-color{color: var(--wp--preset--color--pale-pink) !important;}.has-vivid-red-color{color: var(--wp--preset--color--vivid-red) !important;}.has-luminous-vivid-orange-color{color: var(--wp--preset--color--luminous-vivid-orange) !important;}.has-luminous-vivid-amber-color{color: var(--wp--preset--color--luminous-vivid-amber) !important;}.has-light-green-cyan-color{color: var(--wp--preset--color--light-green-cyan) !important;}.has-vivid-green-cyan-color{color: var(--wp--preset--color--vivid-green-cyan) !important;}.has-pale-cyan-blue-color{color: var(--wp--preset--color--pale-cyan-blue) !important;}.has-vivid-cyan-blue-color{color: var(--wp--preset--color--vivid-cyan-blue) !important;}.has-vivid-purple-color{color: var(--wp--preset--color--vivid-purple) !important;}.has-black-background-color{background-color: var(--wp--preset--color--black) !important;}.has-cyan-bluish-gray-background-color{background-color: var(--wp--preset--color--cyan-bluish-gray) !important;}.has-white-background-color{background-color: var(--wp--preset--color--white) !important;}.has-pale-pink-background-color{background-color: var(--wp--preset--color--pale-pink) !important;}.has-vivid-red-background-color{background-color: var(--wp--preset--color--vivid-red) !important;}.has-luminous-vivid-orange-background-color{background-color: var(--wp--preset--color--luminous-vivid-orange) !important;}.has-luminous-vivid-amber-background-color{background-color: var(--wp--preset--color--luminous-vivid-amber) !important;}.has-light-green-cyan-background-color{background-color: var(--wp--preset--color--light-green-cyan) !important;}.has-vivid-green-cyan-background-color{background-color: var(--wp--preset--color--vivid-green-cyan) !important;}.has-pale-cyan-blue-background-color{background-color: var(--wp--preset--color--pale-cyan-blue) !important;}.has-vivid-cyan-blue-background-color{background-color: var(--wp--preset--color--vivid-cyan-blue) !important;}.has-vivid-purple-background-color{background-color: var(--wp--preset--color--vivid-purple) !important;}.has-black-border-color{border-color: var(--wp--preset--color--black) !important;}.has-cyan-bluish-gray-border-color{border-color: var(--wp--preset--color--cyan-bluish-gray) !important;}.has-white-border-color{border-color: var(--wp--preset--color--white) !important;}.has-pale-pink-border-color{border-color: var(--wp--preset--color--pale-pink) !important;}.has-vivid-red-border-color{border-color: var(--wp--preset--color--vivid-red) !important;}.has-luminous-vivid-orange-border-color{border-color: var(--wp--preset--color--luminous-vivid-orange) !important;}.has-luminous-vivid-amber-border-color{border-color: var(--wp--preset--color--luminous-vivid-amber) !important;}.has-light-green-cyan-border-color{border-color: var(--wp--preset--color--light-green-cyan) !important;}.has-vivid-green-cyan-border-color{border-color: var(--wp--preset--color--vivid-green-cyan) !important;}.has-pale-cyan-blue-border-color{border-color: var(--wp--preset--color--pale-cyan-blue) !important;}.has-vivid-cyan-blue-border-color{border-color: var(--wp--preset--color--vivid-cyan-blue) !important;}.has-vivid-purple-border-color{border-color: var(--wp--preset--color--vivid-purple) !important;}.has-vivid-cyan-blue-to-vivid-purple-gradient-background{background: var(--wp--preset--gradient--vivid-cyan-blue-to-vivid-purple) !important;}.has-light-green-cyan-to-vivid-green-cyan-gradient-background{background: var(--wp--preset--gradient--light-green-cyan-to-vivid-green-cyan) !important;}.has-luminous-vivid-amber-to-luminous-vivid-orange-gradient-background{background: var(--wp--preset--gradient--luminous-vivid-amber-to-luminous-vivid-orange) !important;}.has-luminous-vivid-orange-to-vivid-red-gradient-background{background: var(--wp--preset--gradient--luminous-vivid-orange-to-vivid-red) !important;}.has-very-light-gray-to-cyan-bluish-gray-gradient-background{background: var(--wp--preset--gradient--very-light-gray-to-cyan-bluish-gray) !important;}.has-cool-to-warm-spectrum-gradient-background{background: var(--wp--preset--gradient--cool-to-warm-spectrum) !important;}.has-blush-light-purple-gradient-background{background: var(--wp--preset--gradient--blush-light-purple) !important;}.has-blush-bordeaux-gradient-background{background: var(--wp--preset--gradient--blush-bordeaux) !important;}.has-luminous-dusk-gradient-background{background: var(--wp--preset--gradient--luminous-dusk) !important;}.has-pale-ocean-gradient-background{background: var(--wp--preset--gradient--pale-ocean) !important;}.has-electric-grass-gradient-background{background: var(--wp--preset--gradient--electric-grass) !important;}.has-midnight-gradient-background{background: var(--wp--preset--gradient--midnight) !important;}.has-small-font-size{font-size: var(--wp--preset--font-size--small) !important;}.has-medium-font-size{font-size: var(--wp--preset--font-size--medium) !important;}.has-large-font-size{font-size: var(--wp--preset--font-size--large) !important;}.has-x-large-font-size{font-size: var(--wp--preset--font-size--x-large) !important;} :where(.wp-block-post-template.is-layout-flex){gap: 1.25em;}:where(.wp-block-post-template.is-layout-grid){gap: 1.25em;} :where(.wp-block-columns.is-layout-flex){gap: 2em;}:where(.wp-block-columns.is-layout-grid){gap: 2em;} :root :where(.wp-block-pullquote){font-size: 1.5em;line-height: 1.6;} </style> <link rel='stylesheet' id='ctf_styles-css' href='https://metaarchive.org/wp-content/plugins/custom-twitter-feeds/css/ctf-styles.min.css?ver=1.8.4' type='text/css' media='all' /> <link rel='stylesheet' id='jquery-smooth-scroll-css' href='https://metaarchive.org/wp-content/plugins/jquery-smooth-scroll/css/style.css?ver=6.6.1' type='text/css' media='all' /> <link rel='stylesheet' id='twentythirteen-style-css' href='https://metaarchive.org/wp-content/themes/connectTheDots/style.css?ver=2013-07-18' type='text/css' media='all' /> <!--[if lt IE 9]> <link rel='stylesheet' id='twentythirteen-ie-css' href='https://metaarchive.org/wp-content/themes/connectTheDots/css/ie.css?ver=2013-07-18' type='text/css' media='all' /> <![endif]--> <link rel='stylesheet' id='wpdreams-ajaxsearchpro-instances-css' href='https://metaarchive.org/wp-content/uploads/asp_upload/style.instances-ho-is-po-no-da-co-au-ga-se-is.css?ver=1IUU0w' type='text/css' media='all' /> <script type="text/javascript" src="https://metaarchive.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1" id="jquery-core-js"></script> <script type="text/javascript" src="https://metaarchive.org/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1" id="jquery-migrate-js"></script> <link rel="https://api.w.org/" href="https://metaarchive.org/wp-json/" /><link rel="alternate" title="JSON" type="application/json" href="https://metaarchive.org/wp-json/wp/v2/categories/7" /><link rel="EditURI" type="application/rsd+xml" title="RSD" href="https://metaarchive.org/xmlrpc.php?rsd" /> <link rel="preload" href="https://metaarchive.org/wp-content/plugins/ajax-search-pro/css/fonts/icons/icons2.woff2" as="font" crossorigin="anonymous" /> <style> .asp_m{height: 0;} </style> <link rel="icon" href="https://metaarchive.org/wp-content/uploads/2017/06/cropped-MetaArchive_FavIcon_512x512-32x32.png" sizes="32x32" /> <link rel="icon" href="https://metaarchive.org/wp-content/uploads/2017/06/cropped-MetaArchive_FavIcon_512x512-192x192.png" sizes="192x192" /> <link rel="apple-touch-icon" href="https://metaarchive.org/wp-content/uploads/2017/06/cropped-MetaArchive_FavIcon_512x512-180x180.png" /> <meta name="msapplication-TileImage" content="https://metaarchive.org/wp-content/uploads/2017/06/cropped-MetaArchive_FavIcon_512x512-270x270.png" /> <!-- Google Analytics --> <script> window.ga=window.ga||function(){(ga.q=ga.q||[]).push(arguments)};ga.l=+new Date; ga('create', 'UA-11585749-1', 'auto'); ga('send', 'pageview'); </script> <script async src='https://www.google-analytics.com/analytics.js'></script> <!-- End Google Analytics --> </head> <body class="archive category category-news-events category-7 no-avatars"> <div class="rwd-tester"></div> <a id="top"></a> <div id="navbar" class="navbar"> <nav id="site-navigation" class="navigation main-navigation pw" role="navigation"> <button class="menu-toggle">Menu</button> <a class="screen-reader-text skip-link" href="#content" title="Skip to content">Skip to content</a> <div class="menu-main-navigation-container"><ul id="primary-menu" class="nav-menu"><li id="menu-item-35" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-35"><a href="https://metaarchive.org/about/">About Us</a></li> <li id="menu-item-37" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-37"><a href="https://metaarchive.org/how-ddp-works/">How DDP Works</a></li> <li id="menu-item-38" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-38"><a href="https://metaarchive.org/documentation-resources/">Resources</a></li> <li id="menu-item-234" class="menu-item menu-item-type-taxonomy menu-item-object-category current-menu-item menu-item-234"><a href="https://metaarchive.org/category/news-events/" aria-current="page">News &amp; Events</a></li> <li id="menu-item-202" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-202"><a href="https://metaarchive.org/join-us/">Join Us</a></li> </ul></div> </nav><!-- #site-navigation --> </div><!-- #navbar --> <header id="masthead" class="site-header" role="banner"> <a class="home-link" href="https://metaarchive.org/" title="MetaArchive" rel="home">Home</a> </header><!-- #masthead --> <div id="main" class="site-main"> <div id="primary" class="content-area"> <div id="content" class="site-content" role="main"> <div class="page-header"> <h1 class="page-title">News &amp; Events</h1> </div> <div class="content-section"> <article id="post-1287" class="post-1287 post type-post status-publish format-standard hentry category-home-news category-news category-news-events"> <div class="entry-content pw"> <h5>September 17, 2024</h5> <h3>MetaArchive is Sunsetting: Updates and Learnings from a Community in Transition</h3> <p><span style="font-weight: 400;">When we first announced MetaArchive’s major transition in April 2024, we wanted to create spaciousness, ignite conversations and consider every single potential pathway ahead of us: a member institution becoming our fiscal host; a new organization becoming fiscal host; merging wholesale with another PLN; seeking other options; and more. <strong>After weeks of research, consultation, collaborative brainstorming, and synthesis, a final, feasible pathway emerged. MetaArchive Cooperative would sunset, and individual member organizations would either be adopted by other PLNs, or would join together to create new PLNs. </strong></span></p> <p><span style="font-weight: 400;">The notion of sunsetting didn’t come totally out of left field. At the end of its second decade of operations, the Cooperative had formed a Community Research Task Force which met weekly for over a year to research, document, present information, and make recommendations to broader membership, enabling them to make evidence-based decisions regarding MetaArchive’s strategic directions. These recommendations resulted in several major community decisions, including approving MetaArchive’s Operational Reserve policy and sunsetting budget. So, even as we explored various mitigation efforts, the reality of MetaArchive’s known pain points (current state of finances, membership structure and fees, technical maintenance and R&amp;D, outreach &amp; recruitment, staffing vs. sweat equity), meant that the premise of sunsetting had </span><i><span style="font-weight: 400;">always</span></i><span style="font-weight: 400;"> been present; in fact, the outputs of the Community Research Task Force included a sunsetting budget, sunsetting timeline &amp; dissolution of assets plan, merger plan, and fundraising &amp; sustainability plan. Facing the reality of MetaArchive’s long-term sustainability meant taking on responsibility for our next steps—it became the mandate of the Transformation Research Team (TRT), composed of representatives from MetaArchive, Educopia, and the LOCKSS Program, to operationalize the sunsetting process, attending to the nuances of when and how we would initiate the process, and what we would choose prioritize throughout.</span></p> <p><span style="font-weight: 400;">This seemingly logical and practical plan had a heavy emotional component. MetaArchive was the first and longest-running Private LOCKSS Network of its kind, and has been consistently defining what it entails to be a digital preservation network created and hosted by and for memory organizations. Our collective ways of working and underlying values deeply influenced our shared philosophy toward digital preservation, as we constantly sought opportunities for collaboration and shared governance while maintaining concentrated initiatives. However, this approach also resulted in an added complexity for our sunsetting process. </span></p> <h4><span style="font-weight: 400;">Having created such strong, values-driven and trust-based relationships within our network, how would we untangle these connections between members, committees, project partners, and external agencies without causing harm? </span></h4> <p><span style="font-weight: 400;">In answer to that question, the Transition Research Team named our shared goal: a well-coordinated sunsetting that is mindful, efficient, and done with integrity—demonstrating to all digital preservation stakeholders that endings should be handled with the same attention, investment, and care as beginnings.  </span></p> <p><strong>To that end we devoted intense planning and preparation, with a focus on: </strong></p> <ul> <li style="font-weight: 400;" aria-level="1"><strong>Strategizing communications &amp; making space for member input and feedback, </strong></li> <li style="font-weight: 400;" aria-level="1"><strong>Ensuring the continuity of our members’ digital preservation efforts, </strong></li> <li style="font-weight: 400;" aria-level="1"><strong>Attending to transitional needs, </strong></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;"><strong>and aligning the Cooperative’s finances.</strong> </span></li> </ul> <p><span style="font-weight: 400;">Even as our work continues to evolve, we hope that sharing our decisions, learnings, and reflections may be of value to other organizations in the field who may be negotiating with similar transitions.</span></p> <h4><i><span style="font-weight: 400;">Strategizing communications &amp; making space for member input and feedback</span></i><span style="font-weight: 400;"><br /> </span><b>Key Takeaways from MetaArchive Member 1:1s and Office Hours:</b></h4> <p><span style="font-weight: 400;">The TRT deliberated long and hard over the timing and content of our internal and external communications, in order to avoid a situation in which members ended up knowing different amounts of information. Even as we anticipated that members’ would participate in key conversations relevant to their future pathways, we also wanted to ensure that the full context could be shared, and that we received valuable feedback about what aspects of MetaArchive they valued and wanted to retain in their future pathways. To that end, the TRT hosted Member 1:1s to engage with representatives from each member organization to determine their individual contexts, their digital preservation requirements, and potential pathways they might be interested in. Results from these discussions were synthesized and reported back to the MetaArchive community. In parallel, the TRT also hosted office hours in order to provide a space for members to gather between monthly community calls and ask transition-related questions, while encouraging information sharing and collaboration across the membership</span></p> <h3><b>Outcomes:</b></h3> <p><span style="font-weight: 400;">MetaArchive Chair Christine Wiseman says, “The Member 1:1s and Office Hours were critical to ensuring that all members had opportunities to gather information, have their questions answered, and also to provide needed feedback on the process and choices in order to help inform their decision making process.” </span></p> <p><span style="font-weight: 400;">Some key takeaways from the TRT Member 1:1s included the fact that the aspect members valued the most about MetaArchive’s ways of working was the focus on community. Members appreciated that they could support each other through peer learning and workflow development, preferred working as a network of organizations rather than 3rd party vendors, trusted that their data was safe with LOCKSS boxes, and valued MA’s community-owned governance model, that allowed them to be involved in shaping the direction of the network across time. We also unearthed challenges that members had been facing thus far: storage and costs constraints, staffing and capacity, and reliable functionality. This was also a moment for us to gauge the pulse of the field, as we checked in on the values, resourcing, challenges, and solutions informing digital preservation efforts at various institutions.  </span><span style="font-weight: 400;"><br /> </span><span style="font-weight: 400;"><br /> </span><span style="font-weight: 400;">The information and insights that emerged from these conversations went on to inform a LOCKSS-recommended matrix for individual member adoption by other PLNs, as well as the creation of new PLNs.</span></p> <hr /> <h4><i><span style="font-weight: 400;">Ensuring the continuity of our members’ digital preservation efforts<br /> </span></i><b>Cluster calls for individual member adoption by other PLNs/creation of new PLNs:</b></h4> <p><b></b><span style="font-weight: 400;">Based on the member 1:1s and the subsequent LOCKSS-recommended matrix for individual member adoption by other PLNs, the TRT coordinated cluster calls with prospective adopters and adoptees in order to identify the timelines, next steps, and necessary resources to successfully navigate different facets of this transition. The cluster calls brought multiple stakeholders together to discuss next steps, including formal application and approval, migration of data, and technical requirements and processes for connecting new nodes and replicating new content network-wide.</span></p> <h3><b>Outcomes: </b></h3> <p><span style="font-weight: 400;">When it came to deciding on future pathways for our members, all of these evaluations and conversations allowed us to narrow down to two major approaches:</span></p> <ol> <li style="font-weight: 400;" aria-level="1"><b>Near-term: Ensuring that all existing members know where their data will be stored and preserved in 2025.<br /> </b><i><span style="font-weight: 400;">These pathways can be implemented within the designated Transformation time frame.</span></i><span style="font-weight: 400;"><br /> </span><span style="font-weight: 400;">a. Individual members (whose needs map to existing PLN offerings) adopted by different PLNs</span><span style="font-weight: 400;"><br /> </span><span style="font-weight: 400;">b. Individual members (whose needs do not make to existing PLN offerings) evaluate a non-LOCKSS option</span></li> <li style="font-weight: 400;" aria-level="1"><b>Long-term: Addressing the need for more, targeted LOCKSS-based options.<br /> </b><i><span style="font-weight: 400;">These pathways can be discussed but not implemented within the designated Transformation time frame.</span></i><i><span style="font-weight: 400;"><br /> </span></i><span style="font-weight: 400;">a. Some existing members set up smaller PLNs</span><span style="font-weight: 400;"><br /> </span><span style="font-weight: 400;">b. Some existing members set up a PLN with new external partners</span></li> </ol> <p><span style="font-weight: 400;">At the current moment, based on the size, scope and types of data they have in storage, many of our members have been matched for adoption by existing PLNs. Other members with regional affinities have been grouped together to create new PLNs; these new PLNs are at different stages in their journey: some have begun work on new grants, while others require more research and conversations before formalizing their formation. For those members whose needs do not match existing PLN offerings, the TRT is completing some research into short-term LOCKSS-based storage, in order to offer them a stop-gap service until they are able to implement a robust solution. </span><span style="font-weight: 400;">For members that require transitional, stop-gap support from the LOCKSS program, the TRT is seeking to answer key questions around time frames, costs, communication channels, and other considerations, needs, and expectations.</span><span style="font-weight: 400;"><br /> </span></p> <hr /> <h4><i><span style="font-weight: 400;">Attending to transitional needs </span></i><span style="font-weight: 400;"><br /> </span><b>Asset Disposition Mapping, Committee Chair feedback, Transition Support</b></h4> <p><span style="font-weight: 400;">To ensure a smooth transition, the TRT is reviewing MetaArchive assets, including financial, documentation, platforms, technology, and other business documents, to determine retention, archive, and transfer plans for each asset. We’re also coordinating with the Chairs of MetaArchive’s various committees to address how we might support the wind-down of business-as-usual, which includes attending to outstanding tasks, transferring documentation, coordinating a knowledge transfer to other PLNs, and identifying a point of contact for any questions that might arise during the course of the transition. Finally, the TRT has made inquiries regarding a potential repository home for the MetaArchive records/collection.</span></p> <h3><b>Outcomes: </b></h3> <p><span style="font-weight: 400;">These activities</span> <span style="font-weight: 400;">have put a spotlight on the need for the historical documentation of our own memory organization, telling the story of the development and growth of MetaArchive through its partnerships, activities, and initiatives. Since most of our members are staying within the LOCKSS system and either being adopted by other PLNs or starting new PLNs with transitional storage support from the LOCKSS Program, the TRT is focusing on organizational assets, rather than member assets. We’re using conversations with the PLNs in formation to help us understand what materials are needed to help develop governance structures, and trying to pull organizational assets that would be useful. Templates of community developed documents provide a collection of materials that can function as structural guides that other folks can utilize to inform development of documentation and resources for their own context. Throughout, we are considering options and making decisions on the most functional methods for sharing and storing organizational content.</span></p> <hr /> <h4 style="text-align: left;"><b></b><b></b><i><span style="font-weight: 400;">Aligning the Cooperative’s finances<br /> </span></i><b></b><b>Sunsetting Budget and Plan Revision:</b></h4> <p><span style="font-weight: 400;">Building on the long-term budget planning from the CRTF, the TRT revisited the sunsetting budget to ensure there are sufficient funds for a year-long sunset plan to better support member needs. Final SOWs and contractor costs are being incorporated into the sunsetting budget, acknowledging and supporting the human labor from the LOCKSS program, Educopia, and other contractors for transition work. </span></p> <h3><b>Outcomes: </b></h3> <p><span style="font-weight: 400;">We currently have significantly more clarity on the full costs of completing this process. However, with all of our moving parts and emergent information, final numbers around revenue and expenses are still a moving target until the end of the year. If there are remaining funds when the process is completed in 2025, the community determines what they would like Educopia to do with them (e.g., donate remaining funds to a digipres conference scholarship fund).</span></p> <hr /> <p><span style="font-weight: 400;">As we conclude this detailed account of MetaArchive’s sunsetting process, it is clear that the journey has been as nuanced and emotionally charged as it has been methodical. Our focus on thoughtful planning and community engagement has allowed us to address complex challenges while honoring the deep-seated values and relationships that have defined MetaArchive’s legacy. We remain committed to supporting our members through this process and will continue to provide updates and reflections as we move towards the final stages of our transition. As always, we invite you to contact us to address questions and concerns:</span></p> <p><em><span style="font-weight: 400;">Email &lt;</span></em><a href="mailto:ma_trt@educopia.org"><span style="font-weight: 400;">ma_trt@educopia.org</span></a><em><span style="font-weight: 400;">&gt; if you have a question for the Transformation Research Team (which includes representatives from MA membership, Educopia, and the LOCKSS Program)</span></em></p> <p><em><span style="font-weight: 400;">Email MA Leadership Chair, Christine Wiseman at &lt;</span></em><a href="mailto:cwiseman@auctr.edu"><span style="font-weight: 400;">cwiseman@auctr.edu</span></a><em><span style="font-weight: 400;">&gt; or MA Leadership Chair Elect, Reid Boehm at &lt;<a href="mailto:riboehm@purdue.edu">riboehm@purdue.edu</a>&gt; if you have a question specific to MA Leadership</span></em></p> <p><em><span style="font-weight: 400;">Email MA Treasurer and Chair of Outreach &amp; Member Services Committee, Alex Kinneman at &lt;</span></em><a href="mailto:alexk93@vt.edu"><span style="font-weight: 400;">alexk93@vt.edu</span></a><em><span style="font-weight: 400;">&gt;, if you have questions about the MA Operating Budget or information sharing about the Transformation</span></em></p> <p><em><span style="font-weight: 400;">Email Educopia Co-Director &lt;</span></em><a href="mailto:jessica@educopia.org"><span style="font-weight: 400;">jessica@educopia.org</span></a><em><span style="font-weight: 400;">&gt; if you have questions about Educopia’s changes to membership community fiscal hosting criteria or questions about Educopia more broadly.</span></em></p> <p><em><span style="font-weight: 400;">Email MetaArchive’s Interim Community Facilitators, Brandon Locke at &lt;</span></em><a href="mailto:brandon@educopia.org"><span style="font-weight: 400;">b</span><span style="font-weight: 400;">randon@educopia.org</span></a><em><span style="font-weight: 400;">&gt; and Jessica Meyerson at &lt;</span></em><a href="mailto:jessica@educopia.org"><span style="font-weight: 400;">jessica@educopia.org</span></a><em><span style="font-weight: 400;">&gt;</span></em></p> </div><hr /> </article><!-- #post --> <article id="post-1277" class="post-1277 post type-post status-publish format-standard hentry category-home-news category-news category-news-events"> <div class="entry-content pw"> <h5>July 2, 2024</h5> <h3>Quarter 2 Report: MetaArchive Transformation Research Team</h3> <h3><strong>Executive Summary</strong></h3> <p><span style="font-weight: 400;">The Transition Research Team, composed of leadership from the MetaArchive Community and Educopia, and the LOCKSS Program Team began planning and implementing necessary steps for MetaArchive’s sunset, preservation planning for members, and asset disposition. At the end of the 2nd quarter, planning activities and initial information sharing were completed through weekly meetings, one-on-one member interviews, exploration of new pathway options, and internal and external information sharing. MetaArchive is financially on track to meet the 2024 budget, continuing to inform the sunsetting process.</span></p> <h3><strong><br /> Major Activities</strong></h3> <ol> <li><b>Closed the Community Research Task Force (CRTF) in April</b><span style="font-weight: 400;"> to begin planning for MetaArchive’s transformation. For more information on the CRTF see the blog post </span><a href="https://metaarchive.org/metaarchives-community-research-task-force-is-planning-for-the-future-of-the-community/"><span style="font-weight: 400;">MetaArchive’s Community Research Task Force is Planning for the Future of the Community</span></a><span style="font-weight: 400;">.</span></li> <li><b>Instated the Transition Research Team (TRT)</b>, charged with bringing  together the expertise, perspectives, and efforts of all MetaArchive key stakeholder groups to determine clear, feasible merging/migration/sunsetting pathways for MA members so decisions can be made by the members at end of Q3 2024, and those decisions can be implemented beginning in January 2025.</li> <li><b>Identified initial pathways</b> to explore, including a full MetaArchive merger, reforming MetaArchive, and individual member adoptions by other PLNs.</li> <li><b>Hosted Member 1:1s</b> to engage with each member and their representatives to determine individual context, requirements, and potential pathways. Results from these discussions were synthesized and reported back to the MetaArchive community.</li> <li><b>Hosted open Office Hours</b> for members to meet specifically with MetaArchive Leadership Team members to gain member-to-members insights, feedback, and concerns.</li> </ol> <h3><strong><br /> Deliverables</strong></h3> <p><span style="font-weight: 400;">To support open and transparent communication about the processes and decisions from the TRT, we have issued deliverables targeted for member representatives, their supervisors and administrators, and the greater digital preservation and PLN community. </span></p> <h4><i><span style="font-weight: 400;">For Members (internal to MetaArchive Members)</span></i></h4> <ul> <li style="font-weight: 400;" aria-level="1"><a href="https://drive.google.com/drive/folders/1M49I_WkEWNkQIsckd0MVNqvPtyFlWA5v"><span style="font-weight: 400;">Monthly one-pagers post Community Calls</span></a></li> <li style="font-weight: 400;" aria-level="1"><a href="https://drive.google.com/file/d/1_IYE9sh7GtpOSJ1T07hLis7_U6wIr0D7/view?usp=sharing"><span style="font-weight: 400;">Announcement</span></a><span style="font-weight: 400;"> one-pager for supervisors/admin</span></li> <li style="font-weight: 400;" aria-level="1"><a href="https://docs.google.com/presentation/d/1WkDZikXytuGGbqhrdHg9r3s-o3UzKfXlY9-upb--KFw/edit#slide=id.g270ebc6963a_1_24"><span style="font-weight: 400;">1:1 Synthesis</span></a></li> <li style="font-weight: 400;" aria-level="1"><a href="https://docs.google.com/presentation/d/1tuBEB5vn46nxJv6BI8W9GJs-RuyJo46qkrPbuxxC7ns/present?slide=id.g2e55dfcc2f9_0_59"><span style="font-weight: 400;">LOCKSS-recommended Matrix</span></a><span style="font-weight: 400;"> (</span><span style="font-weight: 400;">Potential Adoption/Migration Pathways for Individual Members based on mutual needs and geographic region</span><span style="font-weight: 400;">)</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Anonymous </span><a href="https://forms.gle/f25Pyh22wg5hyE2WA"><span style="font-weight: 400;">Member Feedback Form</span></a></li> </ul> <h4><i><span style="font-weight: 400;">For Community</span></i></h4> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Blog post 1: </span><a href="https://metaarchive.org/metaarchive-leads-PLN-transformation/"><span style="font-weight: 400;">MetaArchive Leads PLN Transformation</span></a><span style="font-weight: 400;"> (April 15, 2024)</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Blog post 2: </span><a href="https://metaarchive.org/metaarchive-cooperative-transformation-frequently-asked-questions/"><span style="font-weight: 400;">Frequently Asked Questions</span></a><span style="font-weight: 400;"> (May 31, 2024)</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Anonymous </span><a href="https://forms.gle/83qSDL3JsbSTLfQb7"><span style="font-weight: 400;">Community Feedback Form</span></a></li> </ul> <h3><strong><br /> 3rd Quarter Goals</strong></h3> <ul> <li><b>Cluster Calls<br /> </b><span style="font-weight: 400;">Based on the member 1:1s and the subsequent LOCKSS-recommended matrix for individual member adoption by other PLNs, the TRT is coordinating cluster calls with prospective adopters and adoptees. These calls will take place in July 2024 and synthesized results will be reported to the community. </span><em><em>Anticipated Completion: August 2024.</em></em></li> <li><b>Customized Content Transfer Plans<br /> </b>The cluster calls will inform the actionable processes and plans for how each member will transfer content out of MetaArchive and to their chosen destination. These plans will be finalized in collaboration with each member and presented to the community. <em>Anticipated Completion: September 10, 2024 Community Call</em>.</li> <li aria-level="1"><b>Asset Disposition Mapping<br /> </b>To ensure smooth transitions, the TRT is reviewing MetaArchive assets, including financial, documentation, platforms, technology, and other business documents, to determine retention, archive, and transfer plans for each asset. <em><em>Anticipated Completion: August 2024.</em></em></li> <li aria-level="1"><b>Sunsetting Budget and Plan Revision<br /> </b>Building on the long-term budget planning from the CRTF, the TRT is revising the sunsetting budget to ensure there are sufficient funds for a year-long sunset plan to better support member needs. <em>Anticipated Completion: August 2024.</em></li> </ul> <p><span style="font-weight: 400;">Additional questions and comments may be directed to the MetaArchive Leadership Team (</span><a href="mailto:ma_leadership@metaarchive.org"><span style="font-weight: 400;">ma_leadership@metaarchive.org</span></a><span style="font-weight: 400;">) or the TRT (</span><a href="mailto:ma_trt@educopia.org"><span style="font-weight: 400;">ma_trt@educopia.org</span></a><span style="font-weight: 400;">).</span><br style="font-weight: 400;" /><br style="font-weight: 400;" /></p> </div><hr /> </article><!-- #post --> <article id="post-1260" class="post-1260 post type-post status-publish format-standard hentry category-home-news category-news category-news-events"> <div class="entry-content pw"> <h5>May 30, 2024</h5> <h3>MetaArchive Cooperative Transformation: Frequently Asked Questions</h3> <h2><span style="font-weight: 400;">General Questions</span></h2> <h4><span style="font-weight: 400;">Context</span></h4> <h5><span style="color: #333399;"><b>1. What’s going on with MetaArchive?</b></span><b><br /> </b></h5> <p><span style="font-weight: 400;">MetaArchive Cooperative is undergoing an administrative and technical transformation, because by the end of 2025, MetaArchive will no longer be hosted by Educopia Institute. </span><span style="font-weight: 400;"><strong>The Cooperative remains intact as a group, and the data held within its networks remains secure.</strong> </span></p> <p><span style="font-weight: 400;">In March 2024, we completed the transfer of the technical infrastructure to the LOCKSS Program. LOCKSS will continue to provide technical support to the network and will be instrumental in the transformation process. The Cooperative is convening a Transformation Research Team to bring together the expertise, perspectives, and efforts of key stakeholder groups to determine clear, feasible pathways for MA members. These pathways might include merging with another LOCKSS network, forming one or more new PLNs with different administrative hosts, or migrating members’ content to a geographically/topically/financially relevant PLN of their choice.<br /> </span></p> <hr /> <h5><span style="color: #333399;"><b>2. Why is Educopia no longer hosting the MetaArchive Cooperative?</b></span></h5> <p><span style="font-weight: 400;">In March 2024, Educopia completed the first year of a 3-year operational funding investment from the Mellon Foundation.</span><span style="font-weight: 400;">You can read more about Educopia’s Mellon-funded capacity building work </span><a href="https://educopia.org/reflections-in-transition-planting-the-seeds-for-renewal/"><span style="font-weight: 400;">here</span></a><span style="font-weight: 400;">. </span><span style="font-weight: 400;">Educopia is now in the process of making data-informed changes to its business model, changes that will both contribute to greater financial sustainability and respond to the lived experience of staff members that have worked part time on one or more member communities at the same time. </span></p> <p><span style="font-weight: 400;"><strong>Beginning January 2025, all member communities hosted by Educopia will have to support 1 Full-time Employee (rather than .5FTE).</strong> The impact of this new criteria is very different for each community, as they all have different trajectories– different foundings, activities, and staffing levels over time. For MetaArchive, this new criteria intersects with changes in the information landscape over the 20 years of the Cooperative’s existence, a dip in its Operational Reserve, and on-going questions regarding sustainability. </span></p> <p><span style="font-weight: 400;">For the benefit of all parties involved, MetaArchive will no longer be hosted by Educopia Institute in 2025. Educopia will work closely with MetaArchive and LOCKSS Program staff in 2024 to map out its next phase, i.e., feasible future pathways, by:</span></p> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Mapping clear pathways for members: Merging with another PLN; Forming one or more new PLNs with a different administrative host; Migrating member content to an existing private LOCKSS network</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Gathering all of MetaArchive’s historical documentation since its inception</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Ensuring ongoing facilitation and coordination network needs are being met in collaboration with membership and LOCKSS Program staff, until Jackson Huang returns in July</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Consultation and project management while participating directly in the Transformation research (until the end of Q3 2024)</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Communications planning and support to Leadership and the Membership &amp; Outreach Committee: Community-wide informational resources as well as public communications</span></li> </ul> <hr /> <h5><span style="color: #333399;"><b>3. What will Educopia focus on next?</b></span></h5> <p><span style="font-weight: 400;">Educopia continues to mature, grow, and change guided by its </span><a href="https://educopia.org/we-have-a-vision-and-a-mission/"><span style="font-weight: 400;">new Vision and Mission Statements</span></a><span style="font-weight: 400;">.</span> With explicit descriptions of fiscal hosting criteria, services, and fees<span style="font-weight: 400;"> coming soon to our website, Educopia will continue to provide fiscal sponsorship to groups and projects focusing on knowledge production, knowledge preservation, and knowledge sharing. We hope to expand our fiscal sponsorship portfolio, centering projects and initiatives that reduce knowledge inequities. Educopia will also continue to grow its consulting portfolio and pursue collaborative research projects that inform field-level understanding in organizational development and cultivation of diverse knowledge communities; collaborative knowledge production and publishing; digital preservation and curation; and community-controlled infrastructure. </span></p> <hr /> <h5><span style="color: #333399;"><b>4. What happened to the IMLS Implementation grant proposal?</b></span></h5> <p><span style="font-weight: 400;">The rationale behind the IMLS Implementation grant proposal was a one-time infusion of capital to cover the cost of a full time Community Facilitator that would work closely with members and the LOCKSS team to improve ingest workflows and the overall usability of the network as a prerequisite to new member recruitment. Additionally, the capital would subsidize service and storage costs associated with LOCKSS Program and Internet Archive partnerships—both of which aimed at lowering the barrier to entry for cultural organizations to participate in the network.</span></p> <p><span style="font-weight: 400;">While the transition was initiated and grant writing continued, MetaArchive lost two additional members, bringing the projected 2024 operational reserve to $14,000 below the target, according to the community’s operational reserve policy.</span></p> <p><span style="font-weight: 400;">After completing numerous detailed financial and member recruitment projections, the Task Force members determined that even with hoped-for grant funding ($250,000 over three years), there was a high probability that MetaArchive would have to sunset at some point during the grant project, due the projected drain of operational reserve funds.</span></p> <p><span style="font-weight: 400;">While the Community Research Task Force named the </span><i><span style="font-weight: 400;">need</span></i><span style="font-weight: 400;"> for 1FTE of central staffing support in 2023, in February 2024, Educopia announced criteria for all member communities to be able to support 1FTE by 2025. This requirement, combined with the dip in operational reserve, initiated the Transformation process. </span></p> <hr /> <h5><span style="color: #333399;"><b>5. Will MetaArchive still be an Educopia Community?</b></span></h5> <p><span style="font-weight: 400;">Once members have been provided with all possible pathways (no later than the end of Q3 2024) so they can make an informed decision, implementation of said member decisions will begin by or before January 2025. Once all members have transitioned their data to their chosen digital preservation pathway, MetaArchive will no longer be affiliated with Educopia. </span></p> <h4><span style="font-weight: 400;">The Community Research Task Force</span></h4> <h5><span style="color: #333399;"><b>1. What happened to the Community Research Task Force (CRTF)?</b></span></h5> <p>At the end of its second decade of operations, the Cooperative formed a Community Research Task Force with the intention of going beyond business-as-usual to “do things differently to get the long term success we are all working towards”. Convening weekly for over a year, the Task Force researched, documented, presented information, and made recommendations to broader membership, enabling them to make evidence-based decisions regarding MetaArchive’s strategic directions.</p> <p>Starting April 10th, the Community Research Task Force wound down, as it had completed its original charge. This group was reformed as the Transformation Research Team, composed of Educopia staff, Stanford/LOCKSS Program staff, and MetaArchive Community members.</p> <h4>The Transformation Research Team</h4> <h5><b><span style="color: #333399;">1. What is the <span style="caret-color: #333399;">Transformation</span> Research Team (TRT)?</span></b></h5> <p>MetaArchive convened a Transformation Research Team to bring together the expertise, perspectives, and efforts of key stakeholder groups to determine clear, feasible pathways for MA members. The TRT is composed of Educopia staff (Brandon Locke, Jessica Meyerson, Aloma Antao, Jackson Huang), Stanford/LOCKSS Program staff (Clay Miller, Thib Guicherd-Callin, Snowden Becker), and MetaArchive Community members (Christine Wiseman, Reid Boehm, Hannah Pryor, Alex Kinneman, Zach Vowell, Shanna Smith). The charge of this Research Team will include:</p> <ul> <li>Calls with PLNs on governance, costs, and potential partnerships</li> <li>Mapping out cache-to-cache migration, including pathways, timelines, and costs</li> <li>Calls and member office hours with members that may want to create a new PLN, providing pathways, timelines, and costs</li> <li>Creating a clear migration plan and timeline for members that may want to migrate their content to an existing PLN or alternative bit-level digital preservation service in 2025</li> <li>Providing all possible pathways to members no later than the end of Q3 2024 so they can make an informed decision</li> <li>Implementation of member decisions begins January 2025</li> </ul> <p>&nbsp;</p> <h2><span style="font-weight: 400;">Future Pathways</span></h2> <h4><span style="font-weight: 400;">Options</span></h4> <h5><span style="color: #333399;"><b>1. What are my options as a member?</b></span><b><br /> </b></h5> <p>The options available to members are a work-in-progress. As the work of the Transformation Research Team progresses (mapping MA members&#8217; needs and their constraints to available LOCKSS alternatives, and documenting the timeline and resourcing needed to implement each option presented during the April 9th Community Call), we are narrowing the options and specifying the actions involved to implement them. Currently:</p> <p>Off the table (as of 5/20/2024) due to variables including constraints of capacity and the timeframe for transformation:<br /> A. Merging as a whole with an existing PLN<br /> B. Reforming as a new PLN with a new admin host</p> <p>Options that can be implemented within the specified timeframe for MA’s Transformation:<br /> A. Some MA members are adopted by other LOCKSS PLNs<br /> B. Some MA members identify a non-LOCKSS solution (If there are members that choose a non-LOCKSS-based solution and they currently have data stored in LOCKSS nodes hosted by other members, there will be technical assistance provided to ensure the relocation of all preserved content). The TRT is also going to compile a decisionmaking resource for members to evaluate non-LOCKSS digital preservation solutions.</p> <p>Options that may take longer than the specified timeframe for MA’s Transformation*:<br /> A. MA splits into smaller networks [different admin host, different monetary/billing aspects, based on geography, common content needs, or ingest size (e.g., 100TB v. 1TB)]<br /> B. Some MA members establish a new PLN among themselves and/or with partners not currently in MA</p> <p>*While these options may take longer than the specified timeframe for MA’s Transformation, the TRT still plans to undertake research and documentation activities that will serve members who may want to pursue these longer-term options after MetaArchive’s Transformation is complete.</p> <hr /> <h5><span style="color: #333399;"><b>2. How much input and agency will the member institutions have to define and select options?</b></span><b><br /> </b></h5> <p>MA leadership, Educopia, and LOCKSS (TRT members) hold context regarding which options will be possible with available capacity in the specific timeframe for the Transformation. Given this, the TRT will provide a clear presentation of which options we think would best serve each member given their particular digital preservation needs (based on member 1:1s and follow-ups with individual members), thus enabling member organizations to make informed decisions. All members will ultimately determine for themselves whether the LOCKSS solutions recommended to them are the solution they want to pursue.</p> <hr /> <h5><span style="color: #333399;"><b>3. What if my institution cannot find an option that works?</b></span><b><br /> </b></h5> <p>In addition to matching current members’ digital preservation needs to existing or new LOCKSS-based solutions, the TRT is also going to compile a decisionmaking resource for members to evaluate non-LOCKSS digital preservation solutions. All members will ultimately determine for themselves whether the LOCKSS solutions recommended to them are the solution they want to pursue. There are likely to be one or more members that do not have a clear match with a current LOCKSS solution. Those members will have to determine whether they want to select a non-LOCKSS digital preservation solution, or to pause preservation activities until they select a new solution.</p> <p>If there are members that choose a non-LOCKSS-based solution and they currently have data stored in LOCKSS nodes hosted by other members, there will be technical assistance provided to ensure the relocation of all preserved content.</p> <hr /> <h5><span style="color: #333399;"><b>4. When will we have a clearer picture of plans and options for 2025?</b></span><b><br /> </b></h5> <p>While members of the TRT will follow up with individual members and smaller groups of MA members that share the same digital preservation needs in order to gather additional information between now and September, the goal is for all MA members to have a clear picture of their plans for 2025 by the September Community Call.</p> <p>&nbsp;</p> <h2><span style="font-weight: 400;">For Members</span></h2> <h4><span style="font-weight: 400;">Invoicing &amp; Contracts</span></h4> <h5><span style="color: #333399;"><b>1. How will I be billed for 2024? And will fees change?</b></span><b><br /> </b></h5> <p>Invoicing will continue on your institution’s normal billing cycle.<br /> All invoices from now until the end of 2024 will be the same amount as your previous invoice.</p> <hr /> <h5><span style="color: #333399;"><b>2. What about 2025?</b></span><b><br /> </b></h5> <p>Invoices in 2025 will be prorated so that you’ll only be paying through Dec 31, 2025.<br /> We will send storage invoices in early 2025 (for 2024 storage) and late 2025 (for 2025 storage).</p> <hr /> <h5><span style="color: #333399;"><b>3. Why does MetaArchive encourage members to renew for 1 year??</b></span><b><br /> </b></h5> <ul> <li>The Transformation Process was triggered once MA dipped below the sunsetting budget reflected in the community-approved Operational Reserve Policy. The Operational Reserve Policy was approved and put in place in 2023 in anticipation of a potential sunsetting of the network at that time. While MA’s projected Operational Reserve at the end of 2024 is below the sunsetting budget, those funds are required to resource the Transformation and to pay for ongoing network services in the meantime (assuming members renew their membership agreement and pay their invoices through 2025).</li> <li>The truth is that we do not know with certainty what the full costs of completing this process will be. In addition to the normal operating budget items like staff and overhead, we anticipate a number of unknown, one-time costs associated with the Transformation.</li> <li><strong>Thus, it’s crucial that we continue to have revenue in 2025 for the Transformation to be successful</strong> (appropriately resourced, well documented, thoughtfully implemented). If there are remaining funds when the process is completed in 2025, the community determines what they would like Educopia to do (e.g., transfer funds to new fiscal host; or donate remaining funds to a digipres conference scholarship fund).</li> </ul> <hr /> <h5><span style="color: #333399;"><b>4. Who do I contact with billing and invoicing questions?</b></span><b><br /> </b></h5> <p><span style="font-weight: 400;">Please feel free to contact either of MetaArchive’s Interim Community Facilitators:<br /> </span><span style="font-weight: 400;">Brandon Locke &lt;</span><span style="font-weight: 400; color: #0000ff;">brandon@educopia.org</span><span style="font-weight: 400;">&gt;<br /> </span><span style="font-weight: 400;">Jessica Meyerson &lt;</span><span style="font-weight: 400; color: #0000ff;">jessica@educopia.org</span><span style="font-weight: 400;">&gt; </span></p> <hr /> <h5><span style="color: #333399;"><b>5. Will ingests continue in 2024 and/or 2025?</b></span><b><br /> </b></h5> <p>Ingests will be on pause during Q2 of 2024. For Q3-Q4, members with functioning workflows and regular content ingests into MetaArchive may choose to continue ingests as usual. Members with broken plug-ins, older content, or other workflow issues may choose to focus on AU quality control and ideal packaging workflows. Upon their return in July, MA Community Facilitator Jackson Huang will work closely with each member to identify appropriate next steps for their specific needs.</p> <p>Ingesting more content in the network, and storing one copy on the Stanford node, could help to ensure smoother cache-to-cache migration for members that are likely to move forward with a LOCKSS-based solution. However, if some members think they are likely to move ahead with a non-LOCKSS-based solution, it may not make sense to ingest additional content into the network.</p> <h4><span style="font-weight: 400;">Committees</span></h4> <h5><span style="color: #333399;"><b>1. I’m on a MetaArchive committee. How will this affect our work?</b></span><b><br /> </b></h5> <p>Committee work continues in 2024 as planned. Some of the activities described in the 2024 committee action plans have been re-oriented to support the Transformation process.</p> <hr /> <h5><span style="color: #333399;"><b>2. Who is my liaison to the TRT?</b></span><b><br /> </b></h5> <p>Alex Kinnaman is TRT liaison to the Outreach and Member Services Committee<br /> Zach Vowell is the TRT liaison to the Technical Committee<br /> Shanna Smith is the TRT liaison to the Documentation Committee<br /> Christine Wiseman and Reid Boehm are liaisons to the Leadership Committee</p> <h4><span style="font-weight: 400;">Ongoing Support</span></h4> <h5><span style="color: #333399;"><b>1. Where do I go if I have questions?</b></span><b><br /> </b></h5> <p>Members have several resources for addressing their questions and concerns:</p> <ul> <li>Email &lt;<span style="color: #0000ff;">ma_trt@educopia.org</span>&gt; If you have a question for the Transformation Research Team (which includes representatives from MA membership, Educopia, and the LOCKSS Program)</li> <li>Email MA Leadership Chair, Christine Wiseman at &lt;<span style="color: #0000ff;">cwiseman@auctr.edu</span>&gt; or MA Leadership Chair Elect, Reid Boehm at &lt;<span style="color: #0000ff;">riboehm@purdue.edu</span>&gt; if you have a question specific to MA Leadership</li> <li>Email MA Treasurer and Chair of Outreach &amp; Member Services Committee, Alex Kinneman at &lt;<span style="color: #0000ff;">alexk93@vt.edu</span>&gt;, if you have questions about the MA Operating Budget or information sharing about the Transformation</li> <li>Email Educopia Co-Director &lt;<span style="color: #0000ff;">jessica@educopia.org</span>&gt; if you have questions about Educopia’s changes to membership community fiscal hosting criteria or questions about Educopia more broadly.</li> <li>Email MetaArchive’s Interim Community Facilitators, Brandon Locke at &lt;<span style="color: #0000ff;">brandon@educopia.org</span>&gt;and Jessica Meyerson at &lt;<span style="color: #0000ff;">jessica@educopia.org</span>&gt;</li> </ul> <hr /> <h5><span style="color: #333399;"><b>2. What technical support will I have?</b></span><b><br /> </b></h5> <p>The LOCKSS team and the Technical Committee are available to provide technical support throughout the Transformation process. When Jackson Huang, MetaArchive’s Community Facilitator, returns in July 2024, they will also be available to provide hands-on technical support to members.</p> <p>Technical support from the LOCKSS Program staff may include node maintenance, AU quality control, transfer of content into a node and/or out to the Stanford node, migrating a node from the MetaArchive network to a different LOCKSS network, and more.</p> <p>The LOCKSS technical support team can be contacted by emailing &lt;<span style="color: #0000ff;">lockss-support@lockss.org</span>&gt;</p> <p>The MetaArchive Technical Committee can be contacted by emailing &lt;<span style="color: #0000ff;">ma_technical@metaarchive.org</span>&gt;.</p> <hr /> <h5><span style="color: #333399;"><b>3. Will Educopia still be involved in the process for any chosen option?</b></span><b><br /> </b></h5> <p>Yes, Educopia will be part of the process for members’ chosen options. The role Educopia plays in the process will depend on the option that each member selects.</p> <p>As the fiscal host for MetaArchive since 2006, Educopia will work with membership to determine an archival repository for MetaArchive’s organizational records &#8211; the transfer of records to an archival repository would only take place after the Transformation process is completed in 2025. Educopia will also be involved in the disbursement or transfer of any funds remaining in the MetaArchive account after the Transformation process is completed.</p> <h4><span style="font-weight: 400;">Communication &amp; Feedback Mechanisms</span></h4> <h5><span style="color: #333399;"><b>1. How will the community be updated about progress made?</b></span><b><br /> </b></h5> <p>There are several channels for information about MetaArchive’s Transformation process:</p> <ul> <li>Monthly Community Calls</li> <li>Member 1-pagers</li> <li>The MetaArchive Blog</li> <li>MA Member Office Hours</li> </ul> <hr /> <h5><span style="color: #333399;"><b>2. Where do I go if I have feedback?</b></span><b><br /> </b></h5> <ul> <li>Email &lt;<span style="color: #0000ff;">ma_trt@educopia.org</span>&gt; ff you have feedback for the Transformation Research Team (which includes representatives from MA membership, Educopia, and the LOCKSS Program)</li> <li>Email MA Leadership Chair, Christine Wiseman at &lt;<span style="color: #0000ff;">cwiseman@auctr.edu</span>&gt; or MA Leadership Chair Elect, Reid Boehm at &lt;<span style="color: #0000ff;">riboehm@purdue.edu</span>&gt; if you have a feedback specific to MA Leadership</li> <li>Email Chair of Outreach &amp; Member Services Committee, Alex Kinneman at &lt;alexk93@vt.edu&gt;, if you have feedback about member communications</li> <li>Email Educopia Co-Director &lt;<span style="color: #0000ff;">jessica@educopia.org</span>&gt; if you have feedback about Educopia’s changes to membership community fiscal hosting criteria or for Educopia more broadly.</li> <li>Email MetaArchive’s Interim Community Facilitators, Brandon Locke at &lt;<span style="color: #0000ff;">brandon@educopia.org</span>&gt;and Jessica Meyerson at &lt;<span style="color: #0000ff;">jessica@educopia.org</span>&gt; if you have feedback about ongoing scheduling, coordination, and facilitation of the network.</li> </ul> <p>&nbsp;</p> <h2><span style="font-weight: 400;">For the Field</span></h2> <h4><span style="font-weight: 400;">Impact</span></h4> <h5><span style="color: #333399;"><b>1. How might this impact other PLNs?</b></span><b><br /> </b></h5> <p>Other PLNs may be directly impacted by the transformation in the following ways:</p> <ul> <li>Other PLNs may bring one or more of the current MA members on board as new members of their network.This will require migrating the data that is currently preserved in MA’s network and integrating it into the new network, a fairly straightforward process. For networks with similar structures for membership and storage fees, the net difference may be minimal for migrating MA members, and a modest gain for the other PLNs that bring them on board (which may also gain additional geographic and administrative diversity with new members).</li> <li>If new PLNs arise as a result of the MA transformation, this may represent some opportunities for recruitment of new members to multiple PLNs (for example, a newly created regional network might offer pricing incentives for members that also are, or become, members of the GLN, CLOCKSS, USDocs, etc.)</li> <li>Other PLNs may also be indirectly impacted in one or more ways. For instance, the factors that contributed to MA’s changing status may also affect similar communities, which is why MetaArchive is committed to regular community and public reporting on this transformation in the hopes that this documentation will serve as a valuable contribution to the ongoing evolution of the digital preservation services landscape.</li> </ul> </div><hr /> </article><!-- #post --> <article id="post-1230" class="post-1230 post type-post status-publish format-standard hentry category-home-news category-news category-news-events"> <div class="entry-content pw"> <h5>April 15, 2024</h5> <h3>MetaArchive Leads PLN Transformation</h3> <h3><strong>In Summary:</strong></h3> <h3><span style="font-weight: 400;">In 2025, MetaArchive will experience a major transition. No longer hosted by Educopia Institute beyond the coming year, the Cooperative will work with Educopia and LOCKSS to navigate administrative and technical transformation—a new phase for the long running PLN.</span></h3> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">MetaArchive Cooperative is undergoing an<strong> administrative and technical transformation, </strong></span><span style="font-weight: 400;">because by the end of 2025, MetaArchive will <strong>no longer be hosted by Educopia Institute.</strong></span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">In March 2024, we completed the <strong>transfer of the technical infrastructure to the LOCKSS Program.</strong> LOCKSS will continue to provide technical support to the network and will be instrumental in the transformation process.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The Cooperative remains intact as a group, and the data held within its networks remains secure. </span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The Cooperative is convening a <strong>Transformation Research Team</strong> to bring together the expertise, perspectives, and efforts of key stakeholder groups to determine clear, feasible pathways for MA members.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Emergent strategies and lessons learned during MetaArchive’s evaluation and evidence-based decision making processes <strong>will be shared transparently with the broader PLN community</strong>, so that they may serve as a learning resource for peer organizations striving for sustainable digital preservation through community collaboration.</span></li> </ul> <p><span style="font-weight: 400;">Founded in 2004, the MetaArchive Cooperative has been consistently defining what it entails to be a digital preservation network created and hosted by and for memory organizations. As a member-governed cooperative, it has also been discovering and documenting what it takes to <em>sustain</em> a decentralized, risk-mitigating digital preservation storage network. </span></p> <p>A lot has changed in the 20 years of MetaArchive’s existence—in the broader economic environment, in the knowledge landscape and digital preservation field, and within the Cooperative itself. As a result, the Cooperative is facing challenges to sustainability that necessitate a change for the network from its current form.</p> <p>Now that the network has dipped below the draft sunsetting budget outlined in its Operational Reserve Policy(1), MetaArchive will work closely with Educopia and LOCKSS Program staff in 2024 to map out its next phase, i.e., feasible future pathways. These pathways might include merging with another LOCKSS network, forming one or more new PLNs with different administrative hosts, or migrating members&#8217; content to a geographically/topically/financially relevant PLN of their choice.</p> <p><strong>Just as MetaArchive was the first and longest running Private LOCKSS Network, it will continue to build on its legacy of field-level leadership in the digital preservation space by completing an intentional and well-coordinated transformation that is mindful, efficient, and done with integrity—demonstrating to all digital preservation stakeholders that endings should be handled with the same attention, investment, and care as beginnings.  </strong></p> <h6><img fetchpriority="high" decoding="async" class="alignnone wp-image-1242 size-full" src="https://metaarchive.org/wp-content/uploads/2024/04/MA-Timeline-4.png" alt="" width="2988" height="1664" srcset="https://metaarchive.org/wp-content/uploads/2024/04/MA-Timeline-4.png 2988w, https://metaarchive.org/wp-content/uploads/2024/04/MA-Timeline-4-300x167.png 300w, https://metaarchive.org/wp-content/uploads/2024/04/MA-Timeline-4-600x334.png 600w, https://metaarchive.org/wp-content/uploads/2024/04/MA-Timeline-4-220x123.png 220w, https://metaarchive.org/wp-content/uploads/2024/04/MA-Timeline-4-768x428.png 768w, https://metaarchive.org/wp-content/uploads/2024/04/MA-Timeline-4-1536x855.png 1536w, https://metaarchive.org/wp-content/uploads/2024/04/MA-Timeline-4-2048x1141.png 2048w" sizes="(max-width: 2988px) 100vw, 2988px" /><br /> Links to mitigation strategies: <a href="https://metaarchive.org/announcing-the-supernode-pilot-project/">SuperNode Pilot Project</a>, <a href="https://educopia.org/metaarchive-case-study-apr20/">Change for Continuing Impact</a>, <a href="https://metaarchive.org/metaarchive-concludes-project-mycelium/">Project Mycelium</a>, Launching <a href="https://metaarchive.org/metaarchive-fall-update-new-opportunities-new-challenges/">CRTF and LOCKSS Transition</a></h6> <h3><b>Considerations and Conclusions: </b><b>Recent Mitigation Efforts 

</b></h3> <p><span style="font-weight: 400;"><br /> At the end of its second decade of operations, the Cooperative formed a Community Research Task Force with the intention of going beyond business-as-usual to “do things differently to get the long term success we are all working towards”. Convening weekly for over a year, the Task Force<a href="https://metaarchive.org/metaarchives-community-research-task-force-is-planning-for-the-future-of-the-community/"> researched, documented, presented information, and made recommendations</a> to broader membership, enabling them to make evidence-based decisions regarding MetaArchive’s strategic directions. These recommendations resulted in several major community decisions:<br /> </span></p> <ul> <li><span style="font-weight: 400;">Approving the Operational Reserve policy and sunsetting budget</span></li> <li><span style="font-weight: 400;">Voting to remain an independent network while pursuing a partnership for technical infrastructure support</span></li> <li><span style="font-weight: 400;"><span style="font-weight: 400;">Voted to partner with the LOCKSS Program at Stanford, transitioning much of the network’s technical infrastructure to Stanford</span></span></li> </ul> <p>In a joint statement from CRTF members Christine Wiseman, Reid Boehm, Shanna Smith, Zach Vowell, and Alex Kinnaman earlier this week:</p> <h4>“The work undertaken by the CRTF (May 2023 &#8211; April 2024) resulted in a clearer understanding of specific areas of technical improvement, peer network contingency planning, and the unique positioning of MetaArchive in the broader digital preservation landscape. Our changing partnership with Educopia and subsequent infrastructure changes coupled with our new collaboration with the LOCKSS Program illuminated the need for change, guiding MetaArchive into a period of transformation.”</h4> <p><img decoding="async" class="alignnone wp-image-1243 size-full" src="https://metaarchive.org/wp-content/uploads/2024/04/MA-Mitigation-Efforts-larger-font-3-1.png" alt="" width="5476" height="5848" srcset="https://metaarchive.org/wp-content/uploads/2024/04/MA-Mitigation-Efforts-larger-font-3-1.png 5476w, https://metaarchive.org/wp-content/uploads/2024/04/MA-Mitigation-Efforts-larger-font-3-1-281x300.png 281w, https://metaarchive.org/wp-content/uploads/2024/04/MA-Mitigation-Efforts-larger-font-3-1-562x600.png 562w, https://metaarchive.org/wp-content/uploads/2024/04/MA-Mitigation-Efforts-larger-font-3-1-206x220.png 206w, https://metaarchive.org/wp-content/uploads/2024/04/MA-Mitigation-Efforts-larger-font-3-1-768x820.png 768w, https://metaarchive.org/wp-content/uploads/2024/04/MA-Mitigation-Efforts-larger-font-3-1-1438x1536.png 1438w, https://metaarchive.org/wp-content/uploads/2024/04/MA-Mitigation-Efforts-larger-font-3-1-1918x2048.png 1918w" sizes="(max-width: 5476px) 100vw, 5476px" /></p> <h3><b><br /> Planning a Deliberative Transformation: </b><b><br /> </b><b>Appropriately Resourced, Well Documented, Thoughtfully Implemented</b></h3> <p><span style="font-weight: 400;"><br /> The technical transition to the LOCKSS Program has involved an important investment of staff and member time, as it is essential to ensure the success of any merger or migration of member content. While the migration to LOCKSS begins to address MetaArchive&#8217;s technical needs, the partnership has also underscored the need for specific technical improvements that needed to support a sustainable, functioning digital preservation infrastructure, including a streamlined ingest process, community staging alternative for members, consistent processes for cache upgrades, cache monitoring and recovery, AU quality control, and AU reporting and clean-up.</span></p> <h4>&#8220;The fact that, over the last six months, the transition of MetaArchive technical services to the LOCKSS Program contributed to the acceleration of a need for MetaArchive to restructure, is a feature, not a bug,&#8221; Thib Guicherd-Callin, Program Manager of the LOCKSS Program, said on Monday. &#8220;Taking stock of MetaArchive&#8217;s collective needs and interpolating them with the digital preservation landscape at individual MetaArchive institutions richly informs the future partnerships that will emerge as MetaArchive goes through a transformation 20 years in the making.&#8221;</h4> <h3><b><br /> Next Steps</b></h3> <p>Starting April 10th, the Community Research Task Force will wind down, as it has completed its original charge. This group will reform as a <strong>Transformation Research Team</strong> composed of Educopia staff, Stanford/LOCKSS Program staff, and MetaArchive Community members. The charge of this Research Team will include:</p> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;"><strong>Calls with PLNs</strong> on governance, costs, and potential partnerships</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Mapping out <strong>cache-to-cache migration</strong>, including pathways, timelines, and costs</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Calls with members that may want to create<strong> a new PLN</strong>, providing pathways, timelines, and costs</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Creating a <strong>clear migration plan and timeline</strong> for members that may want to migrate their content to an existing PLN or alternative bit-level digital preservation service in 2025 </span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Providing all possible pathways to members <strong>no later than the end of Q3 2024</strong> so they can make an informed decision</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Implementation of member decisions begins <strong>January 2025</strong> </span></li> </ul> <p><span style="text-decoration: underline;"><span style="font-weight: 400;">Roles and responsibilities for members of the Transformation Research Team are as follows:</span></span></p> <p><span style="font-weight: 400;"><strong>1. Community Members</strong></span><i><span style="font-weight: 400;"> (Christine Wiseman, Reid Boehm, Hannah Pryor, Alex Kinneman, Zach Vowell, Shanna Smith)</span></i></p> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Ensuring that member needs are being met and questions are being answered</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Holding member “office hours” every other week (starting May) to discuss questions as they arise </span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Working closely with Educopia and LOCKSS Program staff on clear pathways for members:</span> <ul> <li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Merging with another PLN</span></li> <li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Forming one or more new PLNs with a different administrative host</span></li> <li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Migrating member content to an existing private LOCKSS network</span></li> </ul> </li> </ul> <p><span style="font-weight: 400;"><strong>2. Educopia Staff</strong> </span><i><span style="font-weight: 400;">(Brandon Locke, Jessica Meyerson, Aloma Antao, Jackson Huang)</span></i></p> <ul> <li aria-level="1">Gathering all of MetaArchive&#8217;s historical documentation since its inception</li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Ensuring ongoing facilitation and coordination network needs are being met in collaboration with membership and LOCKSS Program staff, until Jackson Huang returns in July</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Now–end of Q3: Consultation and project management while participating directly in the Transformation research  </span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Communications planning and support to Leadership and the Membership &amp; Outreach Committee: Community-wide informational resources as well as public communications</span></li> </ul> <p><strong>3. LOCKSS Program Staff </strong><i><span style="font-weight: 400;">(Clay Miller, Thib Guicherd-Callin, Snowden Becker)</span></i></p> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Participating in research on clear pathways for members:</span> <ul> <li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Merging with another PLN</span></li> <li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Forming one or more new PLNs with a different administrative host</span></li> <li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Migrating member content to an existing private LOCKSS network</span></li> </ul> </li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Guidance and advice on technical aspects of the Transformation</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Ongoing 1:1 member technical support for those who are:</span> <ul> <li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Testing their ingest workflows</span></li> <li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Completing server upgrades to prevent cache losses</span></li> <li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Engaged in AU troubleshooting and migration</span></li> <li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Performing assessment and clean-up of existing content for quality control and ease of migration</span></li> </ul> </li> </ul> <p><span style="font-weight: 400;">If you have questions regarding this transformation, you can reach the MetaArchive Transformation Research Team at <span style="color: #0000ff;">ma_trt@educopia.org</span></span><span style="font-weight: 400;">, or you can submit anonymized questions to <span style="color: #0000ff;"><a style="color: #0000ff;" href="https://docs.google.com/forms/d/1mEA9dxIzMRKgD_MUQjOluIHEu5PTjYLMSzn1PP2sifU/edit">this form</a></span>. All members of the Transformation Research team will be notified when new questions are submitted, and these questions will be addressed to the best of our ability in monthly MetaArchive Community Calls. </span></p> <p>Responses to relevant questions may also be added to an evolving FAQ, which will be hosted on the MetaArchive website. These FAQs will serve both as a reference for members of our network, as well as a learning resource for peer organizations in the field. The Transformation Research Team is committed to regular community and public reporting on this transformation in the hopes that this documentation will serve as a valuable contribution to the ongoing evolution of the digital preservation services landscape.</p> <hr /> <p><span style="font-weight: 400;">(1) </span><span style="font-weight: 400;">MetaArchive’s operational reserve policy is based on looking at current annual expenditures combined with projected one-time costs to facilitate a deliberative and graceful transformation (be that merging with another network or migrating individual member content to other services of their choosing).</span></p> </div><hr /> </article><!-- #post --> <article id="post-1213" class="post-1213 post type-post status-publish format-standard hentry category-home-news category-news category-news-events"> <div class="entry-content pw"> <h5>December 12, 2023</h5> <h3>Celebrating the MetaArchive Technical Team</h3> <p><span style="font-weight: 400;">MetaArchive is a distributed digital preservation system, relying on members to host caches, volunteer time and energy to committee work, and exchange knowledge within and outside of the Community. However, a common pain point felt by many digital preservationists is a lack of technical support dedicated to preservation infrastructure long-term. MetaArchive provides a low-barrier entry to digital preservation because we have robust technical support through our contracted staff members Bill Robbins, Kurt Nordstrom, and Chris Helms, and through LOCKSS Support Engineer Clay Miller.</span></p> <p><span style="font-weight: 400;">MetaArchive has been lucky to have had dedicated staff members who have supported our infrastructure since 2008, and as our </span><a href="https://metaarchive.org/metaarchive-fall-update-new-opportunities-new-challenges/"><span style="font-weight: 400;">infrastructure shifts to LOCKSS</span></a><span style="font-weight: 400;"> and we transition our technical support to the LOCKSS Program team, we wanted to take the opportunity to celebrate and thank our Technical Team for their work. Their contributions have been substantial and essential to MetaArchive functionality and we cannot express our gratitude enough.</span></p> <p><span style="font-weight: 400;">The Technical Team members have been integral to how MetaArchive functions, ensured smooth transitions, and provided quick IT support.  Some of their essential activities included cache management, Conspectus management, research and development support, Amazon Web Service (AWS) management, and bridging support between MetaArchive and LOCKSS.</span></p> <p><b>Cache Management</b><span style="font-weight: 400;">: Our members host the caches that create our distributed digital preservation network. The Technical Team leads the ongoing maintenance of caches and provides technical support to local IT teams and members. They oversee cache replacements and manage cache recovery during rare, but inevitable, cache failures and are key to getting the network performing optimally. The Technical Team is central to all cache management and we heavily rely on them on the operational side of the cache server and LOCKSS maintenance.</span></p> <p><b>Conspectus</b><span style="font-weight: 400;">: Conspectus is the MetaArchive’s web-based collection management tool and the first point of entry for ingest into the network. The Conspectus maintains the metadata and preservation status information of preserved (or to be preserved) collections of member institutions and offers an easy to use interface, so that members can create, update, and maintain their collections and the collection descriptions of their archives. </span><span style="font-weight: 400;"> All members depend on  the Conspectus, and the Technical Team ensures that it is up and running and manages all debugging and technical support for it .</span></p> <p><b>Supporting Research &amp; Development</b><span style="font-weight: 400;">: The MetaArchive community has been engaged in ongoing research and development to improve services for our members, many of which are supported. Recent projects include the </span><a href="https://metaarchive.org/announcing-the-supernode-pilot-project/"><span style="font-weight: 400;">SuperNode Pilot Project</span></a><span style="font-weight: 400;"> and </span><a href="https://scholarsphere.psu.edu/resources/00b7cec7-61b9-4647-9094-956c8e12e3d1"><span style="font-weight: 400;">evaluating our current LOCKSS infrastructure</span></a><span style="font-weight: 400;">.</span></p> <p><b>AWS Integration</b><span style="font-weight: 400;">: MetaArchive integrated AWS EC2 Cloud storage in 2010 as a backup system in a cloud environment to serve as a single location for the cache manager, title database, and central plugin repository. Since then, as more members transition to using AWS S3 and EC2 for their organization’s storage solution, the Technical Team has facilitated the integration of more AWS-accessible features.</span></p> <p><b>LOCKSS Support</b><span style="font-weight: 400;">: As a Private LOCKSS Network, MetaArchive works collaboratively with LOCKSS technical support to maintain smooth integrations and cache support for MetaArchive members.</span></p> <p><span style="font-weight: 400;">We also want to take the opportunity to highlight the individual work of the Technical Team to acknowledge the depth and importance of their expertise.</span></p> <p><b>Bill Robbins</b><span style="font-weight: 400;"> has been at MetaArchive since 2008, working closely with Educopia leadership. His role began as a Systems Administrator for MetaArchive and has taken on additional areas of support as needed, particularly as our cache expert. Initially, his work focused on coordinating Archival Unit (AU) ingest into the MetaArchive repository. He has written documentation for the LOCKSS interface that is still used as the official guidance for the LOCKSS GUI. His role transitioned to Network Support on a part-time basis for the last few years and he rejoined the Technical Committee to assist with the LOCKSS 2.0 investigation. Bill has performed everything from writing shell scripts for server maintenance to presenting his work in collaboration with MetaArchive. He contributed to “Chapter 7: Cache and Network Administration for PLNs&#8221; in </span><a href="https://metaarchive.org/wp-content/uploads/2017/03/A_Guide_to_Distributed_Digital_Preservation_0.pdf"><span style="font-weight: 400;">A Guide to Digital Preservation</span></a><span style="font-weight: 400;"> (2010) Edited by Katherine Skinner &amp; Matt Schultz, presented at Designing Storage Architecture hosted by the Library of Congress in 2009 on </span><a href="https://digitalpreservation.gov/meetings/documents/othermeetings/1-4_Robbins-METAARCHIVE.pdf"><span style="font-weight: 400;">MetaArchive &amp; Cloud Computing</span></a><span style="font-weight: 400;">, and joined the Technical Committee in our 2020 </span><a href="https://scholarsphere.psu.edu/resources/00b7cec7-61b9-4647-9094-956c8e12e3d1"><span style="font-weight: 400;">MetaArchive LOCKSS Evaluation</span></a><span style="font-weight: 400;">.</span></p> <p><span style="font-weight: 400;">Bill currently serves as the Lead System Engineer at the Georgia Tech Research Institute.</span></p> <p><b>Kurt Nordstrom</b><span style="font-weight: 400;"> has been with MetaArchive since 2015 and is the expert on the MetaArchive user interface Conspectus. Conspectus is a central tool for the network and operations, allowing members to manage collection-level metadata and monitor preservation statuses. Kurt led the ongoing maintenance of the front and back ends of Conspectus. He has maintained Conspectus diligently, migrating it from Ruby to Django Python, serving as a backstop and administrator as needed, and perpetually debugging. </span></p> <p><span style="font-weight: 400;">Kurt currently serves as a Software Developer at Index Data.</span></p> <p><b>Chris Helms</b><span style="font-weight: 400;"> has been with MetaArchive since 2012. He became the general Systems Administrator and led all AWS infrastructure initiatives, including provisioning AWS, server setup, writing shell scripts for the administrative server, and consultation. Recently, Chris implemented our new Private LOCKSS Network dashboard to stand it up in AWS and manage the keys for our ingest plugins in the network. Chris is the bridge between our Technical Team and the Transition Team during the </span><a href="https://metaarchive.org/metaarchive-fall-update-new-opportunities-new-challenges/"><span style="font-weight: 400;">MetaArchive’s transition to LOCKSS infrastructure</span></a><span style="font-weight: 400;"> and is the point person for facilitating that transition on the MetaArchive side.</span></p> <p><span style="font-weight: 400;">Chris has been at the Georgia Tech Library in various IT roles and currently serves as the Manager of Network Services. </span></p> <p><b>Clay Miller</b><span style="font-weight: 400;"> has been key technical support for MetaArchive since 2011. As a Support Engineer for the LOCKSS Project at Stanford University, he has been integral in keeping MetaArchive up and running. He has made himself available to MetaArchive members for direct, one-on-one support for everything LOCKSS, such as cache-hosting configuration, cache server replacements, Linux upgrades on cache servers, AU rebalancing across cache server filesystems, cache recovery; ingest issues diagnosis, and locating the right documentation for any LOCKSS-related question. Clay will continue to be an ongoing resource for the MetaArchive.</span></p> <p><span style="font-weight: 400;">Clay currently serves as a Support Engineer for LOCKSS at Stanford University.</span></p> <p>&nbsp;</p> </div><hr /> </article><!-- #post --> <article id="post-1204" class="post-1204 post type-post status-publish format-standard hentry category-home-news category-news category-news-events"> <div class="entry-content pw"> <h5>November 3, 2023</h5> <h3>Announcing the 2024 MetaArchive Leadership Team Candidates</h3> <p>The MetaArchive Cooperative is pleased to announce the candidates for the 2024 Leadership Team election. Details about each position can be found in our <a href="https://metaarchive.org/wp-content/uploads/2021/06/2021_ma_governance_procedures.pdf" target="_blank" rel="noopener">Governance Procedures</a>.</p> <p>Elections will be held from November 6th, 2023 to November 29th, 2023.</p> <p>Elected Leadership Team members will take office on January 1st, 2024.</p> <p>The voting representative for each Institutional and Collaborative member will receive a ballot via email on November 13th.</p> <hr /> <h3>Reid Boehm</h3> <p>Research Data Systems Manager, Purdue University Libraries</p> <p><strong>Running for: Chair-Elect</strong></p> <h4>Candidate Statement</h4> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="4252035"> <div class="freebirdFormviewerViewItemsTextTextItemContainer"> <div class="freebirdFormviewerViewItemsTextLongText freebirdFormviewerViewItemsTextDisabledText freebirdThemedInput">Working as the Research data systems manager at Purdue University Libraries and managing Purdue University Research Repository is in many ways my dream job because it allows me to work with both the human and technical elements of research data stewardship and with a repository held in high regard within the research data management community. Every day I learn more from researchers, my colleagues, and in the process of developing and sustaining campus partnerships. My doctoral degree is in information science and ever since I’ve worked in academic libraries supporting researchers and working with research data repositories. My background is in research data management, curation, and repositories, starting with an internship at a NASA archive center and a post-doc at Notre Dame Libraries. I enjoy collaborative research on data services and repository related issues. In the past year and a half, since coming to Purdue and getting involved with the collaborative as a member and in working with the Community Research Task Force I am learning multitudes in the realm of preservation, and in a broader extent how a distributed network made up of diverse institutions can sustain and support each other and their system in the face of changes and challenges. I enjoy working with the collaborative, and would like to contribute as a member of leadership to be a part of the effort to support and sustain a valuable network that plays a major role for so many in this field.</div> </div> </div> </div> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="628391191"> <div class="freebirdFormviewerViewItemsItemItemHeader"> <div class="freebirdFormviewerViewItemsItemItemTitleDescContainer"> <div class="freebirdFormviewerViewFormContent"> <div class="freebirdFormviewerViewItemList" role="list"> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="628391191"> <div class="freebirdFormviewerViewItemsTextTextItemContainer"> <div> <hr /> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> <h3>Alex Kinnaman</h3> <p>Digital Preservation Coordinator, Virginia Tech</p> <p><strong>Running for: Treasurer</strong></p> <h4>Candidate Statement</h4> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="4252035"> <div class="freebirdFormviewerViewItemsTextTextItemContainer"> <div class="freebirdFormviewerViewItemsTextLongText freebirdFormviewerViewItemsTextDisabledText freebirdThemedInput"> <p>My work at Virginia Tech is largely policy writing, collaborating on developing and implementing preservation workflows, and consulting with my colleagues on preservation needs. My research interests are in repository certification metrics, digital preservation documentation, and the preservation of 3D objects and Digital Humanities projects.</p> <p>I am running for the Treasurer position on the Leadership Team. I have served as the MetaArchive Treasurer for almost two years as we investigated changes to our financial health and transitioned our budget structure. I believe that given our current time of transition and changing budget priorities, I can provide context and recent historical knowledge to the way our budget is managed. I also serve as co-chair for the Outreach &amp; Membership Services Committee, and have been with the Outreach folks since 2020, and previously served at the Leadership Team Secretary. I look forward to the opportunity to serve and to helping support the forward-movement of MetaArchive. Thank you for your time and consideration.</p> </div> <div> <div class="freebirdFormviewerViewFormContent"> <div class="freebirdFormviewerViewItemList" role="list"> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="628391191"> <div class="freebirdFormviewerViewItemsTextTextItemContainer"> <div> <hr /> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> <h3>Hannah Pryor</h3> <p>Archivist for University Records and Records Manager, University of Louisville</p> <p><strong>Running for: Secretary</strong></p> <h4>Candidate Statement</h4> <p>Hannah Pryor seeks reelection to the role of the MetaArchive Leadership Team’s Secretary. She is an archives and records management professional with 8+ years of experience in state government and higher education. She currently works at the University of Louisville as their Archivist for University Records and Records Manager and often manages born-digital and digitized university records. She is also a member of the Outreach and Membership Services Committee.</p> </div><hr /> </article><!-- #post --> <article id="post-1197" class="post-1197 post type-post status-publish format-standard hentry category-home-news category-news category-news-events"> <div class="entry-content pw"> <h5>October 10, 2023</h5> <h3>MetaArchive Concludes Project Mycelium</h3> <p><span style="font-weight: 400;">In February 2022, </span><a href="https://metaarchive.org/MetaArchive-Explores-Next-Generation-Digital-Preservation-Solutions/"><span style="font-weight: 400;">MetaArchive announced</span></a><span style="font-weight: 400;"> a research and development project to create a next-generation distributed digital preservation solution that later became known as Project Mycelium. The project was a multi-phase effort to leverage commercial-sector infrastructure advancements to simplify digital preservation and increase sustainability. Phase 1 focused on documenting requirements and conceptualizing the design, it was completed in Fall 2022.</span></p> <p><span style="font-weight: 400;">MetaArchive worked with </span><a href="https://www.keepertech.com/"><span style="font-weight: 400;">Keeper Technology</span></a><span style="font-weight: 400;"> to complete Phase 1 activities that include an environmental scan, </span><a href="https://airtable.com/appbZKYWN5lvfd3Fx/shrLYUokNlIjcZVYh"><span style="font-weight: 400;">prioritization and justification</span></a><span style="font-weight: 400;"> of </span><a href="https://osf.io/sjc6u/"><span style="font-weight: 400;">digital preservation storage criteria</span></a><span style="font-weight: 400;">, user surveys and interviews, and a </span><a href="https://docs.google.com/document/d/1qDo9goWJrl5ikzucoDjR9NiVonFct4Tk/edit?usp=sharing&amp;ouid=117725276507144719292&amp;rtpof=true&amp;sd=true"><span style="font-weight: 400;">design document for a next-generation digital preservation architecture</span></a><span style="font-weight: 400;">. We used multiple strategies to seek feedback from the digital preservation community including posting to digital preservation related mailing lists, presenting a </span><a href="https://doi.org/10.17605/OSF.IO/V9UB8"><span style="font-weight: 400;">paper at iPRES 2022</span></a><span style="font-weight: 400;">, and a </span><a href="https://www.digitalpreservation.gov/meetings/DSA2023/loc_dsa2023_website_0201_heinleTallman_projectMycelium_2022-03.pdf"><span style="font-weight: 400;">presentation at Library of Congress Designing Storage Architectures 2023</span></a><span style="font-weight: 400;">; each time a link to the design document was shared, encouraging people add comments and suggestions. Pricing estimates for initial development and ongoing maintenance showed that MetaArchive would need to find partners to continue to phases 2 (proof-of-concept) and 3 (production service).</span></p> <p><span style="font-weight: 400;">At the same time that we engaged the community on our design document, MetaArchive </span><a href="https://metaarchive.org/MetaArchives-Community-Research-Task-Force-is-Planning-for-the-Future-of-the-Community/"><span style="font-weight: 400;">launched the Community Research Task Force</span></a><span style="font-weight: 400;"> to assess the organization&#8217;s financial health, engage in contingency planning, and present options to the membership for remediating technical debt. While the Task Force is continuing some of its work, a result of the process was a decision to strengthen our relationship with LOCKSS and contract with them to perform essential technical operations, including the creation of an anchor node that will hold a copy of all AUs in the network. </span></p> <p><span style="font-weight: 400;">This change was needed to maintain the viability of our network in the short- and medium-terms. It does not limit MetaArchive’s ability to resume technical operations in the future or to pursue other preservation technologies. However, it does mean that now is not the right time for us to continue working on Project Mycelium. We had a lot of fun and learned much during the process and it helped us to solidify our shared understanding and formed a consensus around digital preservation requirements. We hope the artifacts from this project may be helpful to other digital preservation networks and community members. Thank you to everyone who read or commented on the design document, attended our conference sessions, or participated in the process.</span></p> </div><hr /> </article><!-- #post --> <article id="post-1192" class="post-1192 post type-post status-publish format-standard hentry category-home-news category-news category-news-events"> <div class="entry-content pw"> <h5>October 6, 2023</h5> <h3>MetaArchive Fall Update: New Opportunities, New Challenges</h3> <p><span style="font-weight: 400;">The MetaArchive Cooperative is excited to announce that we are partnering with the LOCKSS Program at Stanford University to improve our central administrative infrastructure through increased engagement with the LOCKSS community. This decision was reached through the work of the MetaArchive Community Research Task Force,open communication with the LOCKSS Program team, and an informed MetaArchive community vote. The Cooperative will continue to operate as an Educopia Institute community while contracting out technical support to the LOCKSS Program. </span></p> <p><span style="font-weight: 400;">We are grateful to the LOCKSS Program team for their generosity, openness, and active collaboration during this transition and look forward to working closely with them to improve the MetaArchive Collaborative.</span></p> <h3><b>Community Research Task Force</b></h3> <p><span style="font-weight: 400;">As a member-owned, distributed digital preservation network, MetaArchive is continuously investigating strategies to improve technical capabilities, membership support, and community-based decision-making all while remaining grounded in our </span><a href="https://metaarchive.org/about/"><span style="font-weight: 400;">Mission, Vision, and Values Statement</span></a><span style="font-weight: 400;">. To fulfill this mission, the MetaArchive Community Research Task Force spent the first and second quarter of 2023 addressing the cooperative’s  existing technical debt, improving contingency planning capabilities, and lowering the barrier of entry for participation. For more detailed information on the work of the task force, see the June 7, 2023 blog post, </span><a href="https://metaarchive.org/metaarchives-community-research-task-force-is-planning-for-the-future-of-the-community/"><span style="font-weight: 400;">“MetaArchive’s Community Research Task Force is Planning for the Future of the Community.”</span></a></p> <p><span style="font-weight: 400;">Reviewing the current status and further sustainability of the cooperative required a critical eye and a commitment to transparency. Specifically, the task force reviewed all aspects of the cooperative which needed improvement. The approach was one of hard realism rather than aspiration, encouraging the community to assess its known pain points, both in the immediate and in the long-term. Initially, the task force focused on improving contingency planning, developing two new procedural governance documents, the MetaArchive Contingency Plan for Sunsetting and the MetaArchive Operating Reserve policy, as well as the creation of a prospective operations budget. With contingency infrastructure in place, strategies to achieve the prospective operations budget resulted in several paths for the collaborative to move forward. </span></p> <p><span style="font-weight: 400;">The task force for the second quarter of 2023 brought three proposals to the community for consideration:</span></p> <ol> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Partnership with the LOCKSS Program, to continue our current technical infrastructure with increased technical support and less overhead.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Staying independent and focusing on fundraising to hire additional staff for increased support.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Initiate sunset in January 2024 which would provide the membership, and the digital preservation community, a generous transition period.</span></li> </ol> <p><span style="font-weight: 400;">These proposals considered the financial sustainability of the Cooperative, the obstacles and benefits each option provided the membership and the digital preservation community, and areas of possible development for the Cooperative. The proposals were reviewed by the Leadership Team, presented to the Cooperative prior to the annual member meeting for discussion, and provided  a communication plan, with feedback opportunities, via email. The Leadership Team released a ballot to the community in July 2023 and the final decision was option 1, partnership with the LOCKSS Program.  </span></p> <h3><b>Transition &amp; Impact</b></h3> <p><span style="font-weight: 400;">MetaArchive has been using the LOCKSS digital preservation software since its founding in 2004, which makes transitioning technical support to the LOCKSS Program mutually beneficial. During the planning process, the LOCKSS Program team generously proposed a number of modular support scenarios for partnering with MetaArchive. These scenarios are designed with the opportunity to be decoupled in the future if more independence is desirable and achievable. The LOCKSS Program’s Support team is well-positioned to advise MetaArchive on mitigating risk from node turnover and provide assistance as MetaArchive addresses existing technical debt and migrates to LOCKSS 2.0. LOCKSS Program staff will be able to provide user support during business hours, increasing service responsiveness and reliability. As one of the longest-running LOCKSS networks, MetaArchive’s experiences will help the LOCKSS user community better understand the support needs of mature digital preservation collaboratives  that rely on member contributions and decentralized infrastructure. </span></p> <p><span style="font-weight: 400;">The Cooperative is invested in </span><a href="https://metaarchive.org/about/"><span style="font-weight: 400;">our values</span></a><span style="font-weight: 400;"> and chose a path forward that is consistent with our collaborative, community-focused mission. MetaArchive and its members will continue to be active contributors to the global community of open-source preservation tools and their users, not passive consumers of  proprietary preservation products. As structured, the partnership with the LOCKSS Program effectively brings MetaArchive closer to needed support and services, and increases communication between the LOCKSS Program and the network about technical needs that might be shared with the rest of the LOCKSS user community. The LOCKSS Program has always had a stake in MetaArchive&#8217;s success and sustainability. This partnership is an affirmation of the values both entities hold in common, as well as the ways in which effective digital preservation demands adaptation to changing technology and institutional capacities over the long term. A transition team composed of members from the LOCKSS Program team, MetaArchive Leadership Team and Technical Committee, and Educopia was formed in August 2023. Their charge is to document and facilitate the transition of MetaArchive systems and technical support services to the LOCKSS Program team at Stanford by November 2023. </span></p> <p><span style="font-weight: 400;">In the short term, the partnership with the LOCKSS Program provides immediate cost savings that allows the Cooperative more breathing room to develop sustainability plans and pursue external funding. There is also an immediate increase in technical and software implementation support during regular business hours. Looking further out, the technical support transition frees up staff and volunteers to focus on community management and governance support, including strategies for external funding. The long-term impact is a more sustainable, robust, and continuously member-driven distributed digital preservation community with a greater capacity to serve its members and adapt to the changes inherent in the digital humanities.</span></p> </div><hr /> </article><!-- #post --> <article id="post-1156" class="post-1156 post type-post status-publish format-standard hentry category-home-news category-news category-news-events"> <div class="entry-content pw"> <h5>June 7, 2023</h5> <h3>MetaArchive’s Community Research Task Force is Planning for the Future of the Community</h3> <p>The MetaArchive Cooperative broke ground in community-based digital preservation when it was founded in 2004. Over its first decade, it grew to be one of the first international, member-owned, distributed digital preservation networks. Other digital preservation organizations, particularly in the community of <a href="https://www.lockss.org/">LOCKSS</a> networks, were able to learn from MetaArchive and refine on its <a href="https://metaarchive.org/wp-content/uploads/2017/03/A_Guide_to_Distributed_Digital_Preservation_0.pdf">early implementations of LOCKSS and community governance model</a>.</p> <p>Now at the end of its second decade, MetaArchive is still dedicated to community-driven digital preservation. MetaArchive offers unique value to its members, as one of the only examples of an independent member-owned cooperative that supports decentralized, risk-mitigating digital preservation storage. As a cooperative, MetaArchive thrives on the investments that its members make to the organization. These investments, however, have become increasingly difficult for MetaArchive members to sustain over time. As IT infrastructure in academia and cultural heritage organizations is overwhelmingly outsourced to the cloud, maintaining an on-premise node for a network like MetaArchive starts to be seen as a “boutique” service that is untenable for some of our members. This shifting IT landscape has also made it difficult for current and prospective members to advocate internally for membership in an organization like MetaArchive, because the value of distributed, decentralized digital preservation storage may not be well-understood. These shifts obscure the fact that MetaArchive, as a long-standing consortial effort between academic and cultural heritage organizations, is uniquely positioned to provide responsible stewardship for digital materials and advance digital preservation work across the field.</p> <p>The digital stewardship commitments made by MetaArchive operate on an inherently longer timescale and look to a fundamentally different set of impact measures than other kinds of digital work. Knowing this helps us define our success by our ability to build capacity for our collective action initiatives, anticipate change, adapt our ways of working, and think strategically about resourcing. This definition of success for community-driven digital preservation guides the current work of the <em><strong>Community Research Task Force</strong></em>. The task force’s primary objective is to research, document, and present information about the current state of the community, and to make an evidence-based recommendation to broader membership regarding MetaArchive’s strategic directions.</p> <p>In this current change process, MetaArchive is grounded in its core mission of engaging in sustainable digital preservation through community collaboration, while operating with the knowledge that we cannot expect a different result by trying the same things. We have to do things differently to get the long term success we are all working towards. In this case, doing things differently means:</p> <h3>Addressing the costs of existing technical debt</h3> <p>In the first quarter of 2023, we have created an ideal operations budget, intended to move MetaArchive out of an austerity mindset and into a more sustainable resourcing model. In the second quarter of 2023, we are researching and proposing different fundraising strategies to the membership that may help us reach these goals.</p> <h3>Improving the ability of the cooperative to plan for contingencies</h3> <p>In the first quarter of 2023, we created and updated several procedural governance documents, including an operating reserve policy and a contingency plan for sunsetting the network. During this process, we spoke to a number of other digital preservation networks about their own practices for succession and contingency planning. We are also exploring partnerships with other networks and services, as well as a strategic reassessment of our infrastructure, that will make MetaArchive more resilient to change.</p> <h3>Identifying the service capabilities that need to be developed in order to meaningfully lower the barrier to entry for participation in the network</h3> <p>In the second quarter of 2023, we are engaging in one-on-one conversations with all members, gathering information about current barriers to participation in the network. We have identified both ingest and reporting functionalities as major areas for improvement, and we are working in partnership with the LOCKSS team at Stanford to identify areas for improvement and support between MetaArchive and LOCKSS. Another area of focus for this work is revisiting our pricing model, in order to make sure that MetaArchive is lowering financial barriers where possible in order to foster an equitable approach to digital preservation.</p> <p>We recognize that MetaArchive’s future not only impacts our own members, but also our strategic partners, stakeholders, and the broader digital preservation community. The success of community-driven digital preservation rests on a framework of transparency and deep collaboration, and we are moving through this process in that spirit. If you have any questions about this work and MetaArchive’s future directions, please contact the Leadership Team at <a href="mailto:ma_leadership@metaarchive.org">ma_leadership@metaarchive.org</a>.</p> <p><strong>MetaArchive Community Research Task Force (May &#8211; July 2023)</strong></p> <p>Reid Boehm<br /> Brandon Locke<br /> Shanna Smith<br /> Zach Vowell<br /> Hannah Wang<br /> Christine Wiseman</p> <p><em>Thank you to the previous members of the MetaArchive Community Research Task Force (January &#8211; April 2023) for all of their work and leadership:</em></p> <p>Alex Kinnaman<br /> Jessica Meyerson<br /> Nathan Tallman</p> </div><hr /> </article><!-- #post --> <article id="post-1105" class="post-1105 post type-post status-publish format-standard hentry category-home-news category-news category-news-events"> <div class="entry-content pw"> <h5>November 28, 2022</h5> <h3>Announcing the 2023 MetaArchive Leadership Team Candidates</h3> <p>The MetaArchive Cooperative is pleased to announce the candidates for the 2023 Leadership Team election. Details about each position can be found in our <a href="https://metaarchive.org/wp-content/uploads/2021/06/2021_ma_governance_procedures.pdf" target="_blank" rel="noopener">Governance Procedures</a>.</p> <p>Elections will be held from November 28th, 2022 to December 9th, 2022.</p> <p>Elected Leadership Team members will take office on January 1st, 2023.</p> <p>The voting representative for each Institutional and Collaborative member will receive a ballot via email on November 28th.</p> <hr /> <h3>Shanna Smith</h3> <p>Collection Information Specialist, Isabella Stewart Gardner Museum</p> <p><strong>Running for: Chair</strong></p> <h4>Candidate Statement</h4> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="4252035"> <div class="freebirdFormviewerViewItemsTextTextItemContainer"> <div class="freebirdFormviewerViewItemsTextLongText freebirdFormviewerViewItemsTextDisabledText freebirdThemedInput">Shanna Smith is the Collection Information Specialist at the Isabella Stewart Gardner Museum (ISGM). Since starting at ISGM in 2020, she has gradually become more involved in the MetaArchive Cooperative. She currently serves as the secretary of the Leadership Team and co-chair of the Membership Services Committee. She looks forward to 2023 and the opportunity to continue to contribute to and serve the MetaArchive community.</div> </div> </div> </div> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="628391191"> <div class="freebirdFormviewerViewItemsItemItemHeader"> <div class="freebirdFormviewerViewItemsItemItemTitleDescContainer"> <div class="freebirdFormviewerViewFormContent"> <div class="freebirdFormviewerViewItemList" role="list"> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="628391191"> <div class="freebirdFormviewerViewItemsTextTextItemContainer"> <div> <hr /> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> <h3>Christine Wiseman</h3> <p>Head of the Digital Services Department, AUC Woodruff Library</p> <p><strong>Running for: Chair-Elect</strong></p> <h4>Candidate Statement</h4> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="4252035"> <div class="freebirdFormviewerViewItemsTextTextItemContainer"> <div class="freebirdFormviewerViewItemsTextLongText freebirdFormviewerViewItemsTextDisabledText freebirdThemedInput"> <p>As Head of the Digital Services Department at the AUC Woodruff Library, she serves as the primary liaison and technical support for the HBCU Library Alliance’s membership in the MetaArchive Cooperative. She has really enjoyed her role serving as a liaison to the Alliance, hosting the LOCKSS server, and advocating for the preservation and access of collections from HBCUs. Recently, there is escalating interest among HBCU Library Alliance members in expanding the breadth and depth of their digital presence, and Christine looks forward to integrating digital preservation into that effort. Involvement in the MetaArchive Cooperative has provided the AUC Woodruff Library staff with opportunities to contribute to the profession in enriching ways including serving on committees and working groups. They have expanded their expertise and knowledge around digital preservation practices and broadened their network of professional contacts. Membership in MetaArchive has tangentially connected them with high profile grant projects including the Library Publishing Coalition Workflows Project and the OssArcFlow (Born Digital Archival Workflows) Documentation Project.</p> <p>Christine has gained much professionally from her involvement in MetaArchive during her tenure at AUC. As the cooperative finds itself at a pivotal moment of change, she hopes she can contribute to the vision and forward progression as the MetaArchive Cooperative approaches two decades of providing community based digital preservation.</p> </div> <div> <div class="freebirdFormviewerViewFormContent"> <div class="freebirdFormviewerViewItemList" role="list"> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="628391191"> <div class="freebirdFormviewerViewItemsTextTextItemContainer"> <div> <hr /> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> <h3>Hannah Pryor</h3> <p>Archivist for University Records and Records Manager, University of Louisville</p> <p><strong>Running for: Secretary</strong></p> <h4>Candidate Statement</h4> <p>Hannah Pryor is an archives and records management professional with 7+ years of experience in state government and higher education. She currently works at the University of Louisville as their Archivist for University Records and Records Manager and often works with born-digital and digitized university records. She has previously served as recording secretary for the Oklahoma Archivists Association and the board of commissioners for a state agency. Currently a member of the Membership Services Committee, she would love the opportunity to get more involved and use her organizational skills to serve MetaArchive.</p> </div><hr /> </article><!-- #post --> <article id="post-1086" class="post-1086 post type-post status-publish format-standard hentry category-news category-news-events"> <div class="entry-content pw"> <h5>February 1, 2022</h5> <h3>MetaArchive Explores Next-Generation Digital Preservation Solutions</h3> <p>The MetaArchive Cooperative has begun a multi-phase research and development project to create a modern distributed digital preservation system. The primary goal is to leverage technical infrastructure advancements in the commercial sector to simplify digital preservation systems and make them more sustainable. These advancements include software defined storage, self-healing file systems, and functions-as-a-service. MetaArchive Technical Committee co-chair Nathan Tallman recently had a <a href="https://doi.org/10.6017/ital.v40i4.13355" target="_blank" rel="noopener">journal article published that explores these concepts further</a>.</p> <p>MetaArchive is partnering with <a href="https://www.keepertech.com/" target="_blank" rel="noopener">Keeper Technology</a> (KeeperTech) on this project. KeeperTech, based in Virginia, has deep expertise in building modern, secure, and integral data storage and processing solutions for corporations and government agencies. This multi-phase project has exit ramps for either partner at the conclusion of each phase, when specific proposals for the next phase will be developed and approved.</p> <p>Phase 1 of this project, estimated to take between 2-3 months, will be a collaborative exploration and definition of functional requirements for a distributed digital preservation system. Phase 2 will build on these requirements with KeeperTech developing a prototype system. Phase 3 will consider options for production deployment and implementation alongside <a href="https://www.lockss.org/" target="_blank" rel="noopener">LOCKSS</a>, long used by MetaArchive to achieve bit-level digital preservation. All three phases will occur alongside the day-to-day operations and maintenance on the MetaArchive network.</p> <p>MetaArchive and KeeperTech kicked off Phase 1 in earnest in January 2022. Community Facilitator Hannah Wang and Technical Committee co-chair Nathan Tallman have recently met with the KeeperTech team to share demonstrations of LOCKSS and Conspectus (MetaArchive’s tool for creating archival units in LOCKSS). Bonnie Gordon, from MetaArchive member Rockefeller Archive Center, also presented <a href="https://www.archivematica.org/en/" target="_blank" rel="noopener">Archivematica</a> and discussed digital preservation workflows. Soon, KeeperTech will engage the Cooperative with a questionnaire and focus groups to identify current functional requirements of the community. MetaArchive has already provided several inputs into this process to KeeperTech including prioritized, ranked, and justified criteria for digital preservation storage using the <a href="https://osf.io/sjc6u/" target="_blank" rel="noopener">Digital Preservation Storage Criteria</a>; a SWOT analysis of LOCKSS; and <a href="https://educopia.org/ossarcflow/" target="_blank" rel="noopener">OSSArcFlow</a> workflow analysis diagrams.</p> <p>MetaArchive is excited to engage in this important work to advance the digital preservation community. Functional requirements and software code from the project will be openly-licensed and shared with the community for feedback at the end of each phase. We look forward to being able to share the first outputs.</p> </div><hr /> </article><!-- #post --> <article id="post-1081" class="post-1081 post type-post status-publish format-standard hentry category-news category-news-events"> <div class="entry-content pw"> <h5>November 15, 2021</h5> <h3>Announcing the MetaArchive 2021 Leadership Team Candidates</h3> <p>The MetaArchive Cooperative is pleased to announce the candidates for the 2021 Leadership Team election. Details about each position can be found in our <a href="https://metaarchive.org/wp-content/uploads/2021/06/2021_ma_governance_procedures.pdf" target="_blank" rel="noopener">Governance Procedures</a>.</p> <p>Elections will be held from November 22nd, 2021 to December 10th, 2021.</p> <p>Elected Leadership Team members will take office on January 1st, 2022.</p> <p>The voting representative for each Institutional and Collaborative member will receive a ballot via email on November 22nd.</p> <hr /> <h3>Bonnie Gordon</h3> <p>Rockefeller Archive Center</p> <p><strong>Running for: Chair-Elect</strong></p> <h4>Biography</h4> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="4252035"> <div class="freebirdFormviewerViewItemsTextTextItemContainer"> <div class="freebirdFormviewerViewItemsTextLongText freebirdFormviewerViewItemsTextDisabledText freebirdThemedInput">Bonnie Gordon is a Digital Archivist at the Rockefeller Archive Center, where she focuses on digital preservation, born digital records, and training around technology. Previously, she worked at the Tamiment Library and Robert F. Wagner Labor Archives at New York University. She received her M.A. in Archives and Public History from New York University and her B.A. in History from Purchase College, SUNY.</div> </div> </div> </div> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="628391191"> <div class="freebirdFormviewerViewItemsItemItemHeader"> <div class="freebirdFormviewerViewItemsItemItemTitleDescContainer"> <h4 class="freebirdFormviewerViewItemsItemItemTitleContainer">Election Statement</h4> <div class="freebirdFormviewerViewFormContent"> <div class="freebirdFormviewerViewItemList" role="list"> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="628391191"> <div class="freebirdFormviewerViewItemsTextTextItemContainer"> <div class="freebirdFormviewerViewItemsTextLongText freebirdFormviewerViewItemsTextDisabledText freebirdThemedInput">I have been actively involved in many open source communities, including other communities housed by Educopia. I think open source communities and infrastructure are vital for sustainable digital preservation, and therefore I am looking forward to the opportunity to take an active role in leading the MetaArchive Cooperative&#8217;s efforts. I am also excited to bring the perspective of the Rockefeller Archive Center, an independent archives and research center. While longtime members of the Cooperative, we had paused while we solidified our digital preservation policies and digital infrastructure. As we ramp back up, I hope to help advance the MetaArchive community&#8217;s goals.</div> <div> <hr /> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> <h3>Alex Kinnaman</h3> <p>Virginia Tech</p> <p><strong>Running for: Treasurer</strong></p> <h4>Biography</h4> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="4252035"> <div class="freebirdFormviewerViewItemsTextTextItemContainer"> <div class="freebirdFormviewerViewItemsTextLongText freebirdFormviewerViewItemsTextDisabledText freebirdThemedInput">I joined the Virginia Tech University Libraries as the Digital Preservation Coordinator in 2017. I have a Bachelor’s in English from the University of Nebraska-Lincoln and an MSLIS from the University of Illinois at Urbana-Champaign. My work at Virginia Tech is largely policy writing, collaborating on developing and implementing preservation workflows, and consulting with my colleagues on preservation needs. My research interests are in repository certification metrics, digital preservation documentation, and the preservation of 3D objects and Digital Humanities projects. We are currently in the process of responding to a CoreTrustSeal application for our Digital Libraries Platform. I reside in Blacksburg, VA, I enjoy reading, running, and all things spooky, and my cats Finn and Opal who can’t wait to talk to people on my video calls!</div> <h4 class="freebirdFormviewerViewItemsTextLongText freebirdFormviewerViewItemsTextDisabledText freebirdThemedInput">Election Statement</h4> <div> <div class="freebirdFormviewerViewFormContent"> <div class="freebirdFormviewerViewItemList" role="list"> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="628391191"> <div class="freebirdFormviewerViewItemsTextTextItemContainer"> <div class="freebirdFormviewerViewItemsTextLongText freebirdFormviewerViewItemsTextDisabledText freebirdThemedInput">I am running for the Treasurer position. Last fall I was elected into the position of Secretary on the Leadership Team, which has given me a higher-level experience in the MetaArchive Cooperative. I have also served as the co-chair for the Outreach Committee since fall 2020 and work with many fantastic committee members to increase engagement and reach in the digipres community. I believe that serving as Treasurer will be an excellent opportunity for me to engage further with MetaArchive and help make decisions that will further progress our community, as well as an opportunity for personal growth. I look forward to serving and to helping support the forward-movement of MetaArchive. Thank you for your time and consideration.</div> <div> <hr /> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> <h3>Shanna Smith</h3> <p>Isabella Stewart Gardner Museum</p> <p><strong>Running for: Secretary</strong></p> <h4>Biography</h4> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="4252035"> <div class="freebirdFormviewerViewItemsTextTextItemContainer"> <div class="freebirdFormviewerViewItemsTextLongText freebirdFormviewerViewItemsTextDisabledText freebirdThemedInput">Shanna Smith is the Collection Information Specialist at the Isabella Stewart Gardner Museum in Boston and the current co-chair of the Membership Services Committee. She holds a MLIS from Simmons University and has worked in libraries, universities, and museums.</div> </div> </div> </div> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="628391191"> <div class="freebirdFormviewerViewItemsItemItemHeader"> <h4 class="freebirdFormviewerViewItemsItemItemTitleContainer">Election Statement</h4> <div> <div class="freebirdFormviewerViewFormContent"> <div class="freebirdFormviewerViewItemList" role="list"> <div class="freebirdFormviewerViewNumberedItemContainer" role="listitem"> <div class="freebirdFormviewerViewItemsItemItem freebirdFormviewerViewItemsTextTextItem" data-item-id="628391191"> <div class="freebirdFormviewerViewItemsTextTextItemContainer"> <div class="freebirdFormviewerViewItemsTextLongText freebirdFormviewerViewItemsTextDisabledText freebirdThemedInput">I am excited by the opportunity to serve in the Secretary Position for the Leadership Team. As co-chair of the Membership Services Committee I&#8217;m familiar with the importance of recording and distributing minutes form all Leadership Team Meetings. I am humbled by the nomination and if elected I look forward to share my unique institutional experience and support MetaArchive community in this position in the coming year.</div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div><hr /> </article><!-- #post --> <article id="post-1069" class="post-1069 post type-post status-publish format-standard hentry category-news category-news-events"> <div class="entry-content pw"> <h5>July 27, 2021</h5> <h3>MetaArchive&#8217;s New Mission, Vision, and Values</h3> <p>The MetaArchive Cooperative is pleased to introduce the community to MetaArchive’s newly revised <a href="https://metaarchive.org/about/">Mission, Vision, and Values Statement</a>.</p> <p>MetaArchive Mission: “To engage in sustainable digital preservation through community collaboration.”</p> <p>MetaArchive Vision: “Preserving the past, harnessing the present, preparing for the future”</p> <p>Revising and developing our Mission and Vision began in 2019 as part of the <a href="https://educopia.org/metaarchive-case-study-apr20/" target="_blank" rel="noopener">Changing for Continued Impact (CFCI)</a> series. We wanted to ensure that what the MetaArchive stands for and abides by is reflected in our Mission and Vision statements and to revisit our values as a community. This discussion took an entire session of the CFCI process where all members were given time to brainstorm in a shared document and generate a list of potential options for both the Mission and Vision statements. Small groups were assigned to workshop the lists to finalize a few options individually and report back to the community. The end of CFCI did not bring any final decisions as we had so many moving parts coming together at that point. Recently the Leadership Team revisited the previous notes to explore options and continue workshopping. After narrowing down the options, the Leadership Team presented them to the community for feedback.</p> <p>Our new Values Statement is an updated version of our previous Operational Principles that better reflects our revised Mission and Vision statements:</p> <ul> <li>Encourage and support the long-term preservation of digital content;</li> <li>Promote a cooperative, robust, and decentralized approach to digital preservation;</li> <li>Encourage archives, libraries, research institutes, museums, and other such organizations to build their own preservation infrastructures and knowledge rather than outsourcing this core service to external vendors;</li> <li>Encourage the growth of distributed digital preservation networks for preserving copies of replicated content in secure, distributed locations over time;</li> <li>Maintain a minimal overhead and straightforward mechanisms for collaboration;</li> <li>Administer services that have wide applicability to a range of organizations and digital content;</li> <li>Utilize and create open standards and systems;</li> <li>Ensure that digital materials are stored and maintained in migratable formats and data structures;</li> <li>Promote and support high standards for preservation metadata capture;</li> <li>Undertake research and development projects to advance digital preservation best practices</li> </ul> <p>In addition to these values, we support and adhere to the <a href="https://dpscollaborative.org/shared-values_en.html" target="_blank" rel="noopener">Digital Preservation Declaration of Shared Values</a>.</p> <p>MetaArchive looks forward to upholding our new guiding statements and supporting our community. If you have any questions please contact Community Facilitator Hannah Wang at <a href="mailto:hannah.wang@educopia.org">hannah.wang@educopia.org</a>.</p> </div><hr /> </article><!-- #post --> <article id="post-1050" class="post-1050 post type-post status-publish format-standard hentry category-news category-news-events category-uncategorized"> <div class="entry-content pw"> <h5>June 17, 2021</h5> <h3>MetaArchive Announces New Membership Levels</h3> <p>The MetaArchive Cooperative is very happy to announce that we are now welcoming new and returning members under our new membership levels! These new levels and terms signal exciting changes for the Cooperative.</p> <p>These changes were driven by the MetaArchive members during and after the Changing for Continued Impact (CFCI) Series, a program of intensive evaluations of both our organizational model and our technical approaches to distributed digital preservation. For more information about the outcomes of CFCI, see the <a href="https://educopia.org/making-community-spaces-safer-on-being-transformational/">blog post</a> written by Matt Schultz, former MetaArchive Community Facilitator.</p> <p>The new membership levels were authored by two long-time members of the Cooperative, Rachel Howard from the University of Louisville and Deanna Ulvestad from the Greene County Public Library in Ohio, and unanimously approved by the MetaArchive Steering Committee on December 14, 2020.</p> <p>So what has changed?</p> <h3>Simplified Membership Levels</h3> <p>Here is the nitty gritty of what has actually changed with the membership options offered by MetaArchive:</p> <table> <tbody> <tr> <th>Pre-2021</th> <th>2021 and beyond</th> </tr> <tr> <td><strong>Sustaining Members</strong>: Single organizations that provided leadership for the Cooperative and engaged in preservation activities.</p> <p>Annual fee: $5,500 (+ technology fee, if applicable)</p> <p><strong>Preservation Members</strong>: Single organizations that engaged in preservation activities.</p> <p>Annual fee: $3,000 (+ technology fee, if applicable)</td> <td><strong>Institutional Members</strong>: Single organizations that provide leadership for the Cooperative and engage in preservation activities.</p> <p>Annual fee: $4,000</td> </tr> <tr> <td><strong>Collaborative Members</strong>: Groups of institutions (often consortia) that engaged in preservation activities.</p> <p>Annual fee: $2,500 + $100/member (+ technology fee, if applicable)</td> <td><strong>Collaborative Members</strong>: Groups of institutions (often consortia) that provide leadership for the Cooperative and engage in preservation activities.</p> <p>Annual fee: $4,000 + $100/member</td> </tr> <tr> <td></td> <td><strong>Individual Members</strong>: Individual practitioners who can now join the Cooperative for free in order to learn about and participate in the community</p> <p>Annual fee: None</td> </tr> </tbody> </table> <p>Each Institutional and Collaborative member designates one Voting Representative, and anyone from an Institutional or Collaborative member organization is eligible to serve in a leadership position.</p> <p>As an incentive for new organizations joining the MetaArchive Cooperative under these terms, we are offering 50% off your first year of membership!</p> <h3>NEW! Storage Rewards</h3> <p>MetaArchive members are given the option to host a LOCKSS cache at their organization. LOCKSS caches are the backbone of the MetaArchive Technical Network &#8211; content is geographically distributed across multiple caches, which automatically check in with each other to verify that the content remains complete and identical over time.</p> <p>In past years, members who have opted not to host LOCKSS caches have paid a $1,000 technology fee instead. With the new membership terms, we have flipped that structure: <strong>instead of charging members who do not host caches, we are rewarding members who do host caches.</strong> This is in recognition of the time, labor, and money that is involved in setting up and maintaining a LOCKSS cache.</p> <p>Under the new storage rewards system, members who host a LOCKSS cache receive 10% of contributed storage volume free. This means that, if you provide 48 TB of storage volume through your LOCKSS cache, you will be able to ingest and store 4.8 TB of digital content in the network for free. Any storage used beyond that 10% will be subject to annual storage fees (as of 2021, $0.50/GB/year).</p> <h3>NEW! Individual Memberships</h3> <p>We are most excited to start implementing the Individual Membership option. In the past, if an individual left their MetaArchive member organization, or if their organization left the Cooperative, there was no way for those practitioners to continue to engage in MetaArchive. This community is tight-knit and filled with exciting voices in the field &#8211; it is a loss to say goodbye to any of those people!</p> <p><strong>These new Individual Memberships allow practitioners to join the Cooperative for free.</strong> This opens the door not only to former members, but also to any practitioners without a MetaArchive affiliation who are interested in learning about distributed digital preservation and engaging with this community. Individual Members cannot make use of the MetaArchive Technical Network for the preservation of digital collections, and they do not have voting rights in the Cooperative. Individual members can, however, attend meetings, serve on committees, and engage with other members in peer mentoring programs.</p> <p>We have already begun welcoming new Individual Members to the Cooperative, and we are excited to spread the word! Reach out to Hannah Wang, MetaArchive Community Facilitator, at <a href="mailto:hannah.wang@educopia.org">hannah.wang@educopia.org</a> if you are interested in joining as an Individual Member.</p> <h3>Learn More</h3> <p>Head over to <a href="https://metaarchive.org/join-us/">Join Us</a> to learn more about our membership options. If you are ready to take the plunge and talk to someone about membership, get in touch with Hannah Wang, Community Facilitator, at <a href="mailto:hannah.wang@educopia.org">hannah.wang@educopia.org</a>.</p> </div><hr /> </article><!-- #post --> <article id="post-950" class="post-950 post type-post status-publish format-standard hentry category-news-events tag-member-profile"> <div class="entry-content pw"> <h5>May 28, 2020</h5> <h3>MetaArchive Member Profile: Oregon State University Libraries</h3> <h3 class="wp-block-heading">By: Michael Boock, Associate Professor/Scholarly Communication Librarian</h3> <figure class="wp-block-image"><img decoding="async" src="https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_BlogBanner_June25-1.png" alt="MetaArchive Member Profiles" class="wp-image-852"/></figure> <h3 class="wp-block-heading">Tell us a bit about the digital preservation program at your organization?<br></h3> <p>Oregon State University Libraries has been firmly committed to the long term preservation of the scholarship of the university and its unique digital assets as far back as 2008 when Terry Reese was appointed to an endowed position with responsibilities for building the digital preservation infrastructure of the Libraries. During his tenure, the Libraries began using LOCKSS for preserving journal content and joined the MetaArchive Cooperative as a sustaining member.&nbsp; Our digital preservation operations were vastly improved after 2012 with the hire of <a href="https://mediaarea.net/blog/2017/11/06/interview-with-brian-e-davis-oregon-state-university">Brian Davis as Digital Production Unit Head</a> , who developed format-specific identification, validation, characterization, and fixity checking of digitized content. The Libraries further committed to digital preservation in a 2012-2017 strategic plan that called for the creation of a “robust and flexible digital preservation and curation infrastructure” and “a long-term preservation system for university scholarship and digital collections developed and curated by OSU Libraries and Press.” <br></p> <h3 class="wp-block-heading">Looking ahead, what are you excited about, or what&#8217;s on the horizon for your program?</h3> <p>Brian and I presented a report to library leadership in 2017 that described the current state of the library’s digital preservation efforts and recommended <a href="https://ir.library.oregonstate.edu/concern/technical_reports/73666904w">next steps for preserving the Libraries digital objects</a>. Emblematic of how quickly things are changing in the digital preservation space, many of the report recommendations have shifted over the last couple of years, but I am thrilled to say that some of the recommendations, in particular upgrading the library’s backup and storage systems to include monthly and incremental daily backups and the increased use of Archivematica for processing digital objects before repository ingest. </p> <div class="wp-block-image"><figure class="aligncenter"><img decoding="async" width="600" height="300" src="https://metaarchive.org/wp-content/uploads/2020/05/Copy-of-MetaArchive_MemberProfile_Oregon_Twitter-1-600x300.png" alt="MetaArchive Member Profile: Oregon State University Libraries. Aside from our use of MetaArchive to preserve substantial amounts of our most important digital content, I value MetaArchive for its community of experts. It is immensely valuable to be able to learn from leaders in our field." class="wp-image-953" srcset="https://metaarchive.org/wp-content/uploads/2020/05/Copy-of-MetaArchive_MemberProfile_Oregon_Twitter-1-600x300.png 600w, https://metaarchive.org/wp-content/uploads/2020/05/Copy-of-MetaArchive_MemberProfile_Oregon_Twitter-1-220x110.png 220w, https://metaarchive.org/wp-content/uploads/2020/05/Copy-of-MetaArchive_MemberProfile_Oregon_Twitter-1-300x150.png 300w, https://metaarchive.org/wp-content/uploads/2020/05/Copy-of-MetaArchive_MemberProfile_Oregon_Twitter-1-768x384.png 768w, https://metaarchive.org/wp-content/uploads/2020/05/Copy-of-MetaArchive_MemberProfile_Oregon_Twitter-1.png 1024w" sizes="(max-width: 600px) 100vw, 600px" /><figcaption><em>&#8221; Aside from our use of MetaArchive to preserve substantial amounts of our most important digital content, I value MetaArchive for its community of experts. It is immensely valuable to be able to learn from leaders in our field.</em><br>Pictured, Top Row, L-R: Michael Boock, Associate Professor/Scholarly Communication Librarian; Brian Davis, Digital Production Unit Supervisor. Bottom Row, L-R: Hui Zhang, Associate Professor/Digital Services Librarian; Margaret Mellinger, Associate Professor/Director, Emerging Technologies and Services</figcaption></figure></div> <h3 class="wp-block-heading">Tell us a bit about your local workflow. How has the MetaArchive preservation storage service been incorporated?</h3> <p>As noted, for digitized objects, a breadth of preservation work is done to ensure content validation and fixity for digitized objects. The master, preservation-level files are then moved onto ZFS storage systems via a BagIt protocol. For born-digital scholarship housed in the Samvera/Fedora based ScholarsArchive@OSU institutional repository, file integrity using a checksum tool is checked as part of file ingestion. Dr. Hui Zhang, digital services librarian, uses a script that traverses the hierarchy of repository objects in the institutional repository to locate and export binary files with the RDF metadata from specific repository collections. The generated BAGs are then moved to temporary Amazon Web Services storage for MetaArchive harvesting.<br></p> <h3 class="wp-block-heading"><strong>What types of digital collections are you focusing on for preservation in MetaArchive? What will preserving those collections for the long-term mean for their users or your institution? How are some of those collections used now?</strong></h3> <p>The Libraries first used MetaArchive to replicate the university’s corpus of Electronic Theses and Dissertations. Theses and dissertations represent the breadth of significant research and scholarship conducted at the university over its entire history, and also serve as an important historical record of the OSU research and teaching interests. MetaArchive is also used to replicate all of the University’s Extension and Experiment Station Communication Publications (EESC). As noted in this editorial from the Corvallis Gazette-Times, published after the EESC collection of over 6,000 technical reports were digitized and made available in the IR, many of the same issues that were important to Oregon residents 100 years ago continue to be important today. Preserving this content with MetaArchive’s robust Private LOCKSS network helps to ensure that it will be available to citizens today and long into the future. </p> <div class="wp-block-image"><figure class="aligncenter"><img loading="lazy" decoding="async" width="600" height="286" src="https://metaarchive.org/wp-content/uploads/2020/05/Gazette-Times-600x286.jpg" alt="An Editorial from the Corvallis Gazette-Times: After 100 years, Extension still valuable. " class="wp-image-954" srcset="https://metaarchive.org/wp-content/uploads/2020/05/Gazette-Times-600x286.jpg 600w, https://metaarchive.org/wp-content/uploads/2020/05/Gazette-Times-220x105.jpg 220w, https://metaarchive.org/wp-content/uploads/2020/05/Gazette-Times-300x143.jpg 300w, https://metaarchive.org/wp-content/uploads/2020/05/Gazette-Times-768x366.jpg 768w, https://metaarchive.org/wp-content/uploads/2020/05/Gazette-Times.jpg 1600w" sizes="(max-width: 600px) 100vw, 600px" /><figcaption><em> <br> Editorial from the Corvallis Gazette-Times, published after the EESC collection of over 6,000 technical reports were digitized and made available in the IR, noted that many of the same issues that were important to Oregon residents 100 years ago continue to be important today.</em> </figcaption></figure></div> <h3 class="wp-block-heading">Tell us about your experience in participating in the MetaArchive community. How has it influenced you or your work? </h3> <p>I have personally served as OSU’s representative on the MetaArchive Steering Team since 2015 and as this year’s Chair of the Steering Team.&nbsp; When I joined the Steering Team five years ago, I had a strong interest in digital preservation, but I had very little idea about how to do it. As noted above, OSU Libraries has invested in staff and resources to improve digital preservation operations, but this work should not be done in a vacuum. Aside from our use of MetaArchive to preserve substantial amounts of our most important digital content, I value MetaArchive for its community of experts. It is immensely valuable to be able to learn from leaders in our field such as Katherine Skinner, Matt Schultz, and Sam Meister (former MetaArchive Community Manager), and to learn from colleagues from a variety of different library and museum types about their preservation work.</p> <h3 class="wp-block-heading"><strong>Tell us a bit about your experience participating in the <em>Changing for Continued Impact Series</em>? What have been some of your key takeaways from the series thus far?</strong></h3> <p>As Katherine Skinner (Executive Director of Educopia) noted to members last year, MetaArchive, as the world’s longest tenured distributed digital preservation solution in the world, has been in place and operating within the same technology base and governance structure since its inception. As part of this Series, our community has had an opportunity to hear from experts in the field about alternative technological approaches. It has been invaluable to me to learn from experts in the field, and MetaArchive’s own experts like Nathan Tallman (Penn State) and Zach Vowell (Cal State Poly), that there are alternative solutions that are ripe for further exploration by the community. Another key takeaway for me is that MetaArchive will remain viable as a preservation network only so long as we are prepared to transition to meet the needs of the community. Fortunately, the transparency of the network and its governance structure helps to ensure that the community’s needs will continue to be met. </p> <p><em>Editorial note: “Since late 2019 the MetaArchive community has been undergoing a series of intensive evaluations of both their organizational model as well as their technical approaches to distributed digital preservation (DDP). This is the Changing for Continued Impact (CFCI) Series, a facilitated framework led by Educopia that engages the MetaArchive members in a series of focused-discussions and work-sessions. This generative and co-creative process got underway in earnest this past Fall 2019, and will continue through Spring 2020 leading up to the next Annual MetaArchive Membership Meeting.&#8221; </em><br></p> </div><hr /> </article><!-- #post --> <article id="post-940" class="post-940 post type-post status-publish format-standard hentry category-news-events tag-member-profile"> <div class="entry-content pw"> <h5>April 15, 2020</h5> <h3>MetaArchive Member Profile: Virginia Tech University Libraries</h3> <h3 class="wp-block-heading">By: Alex Kinnaman, Digital Preservation Coordinator, and Nathan Hall, Director of Digital Imaging and Preservation</h3> <figure class="wp-block-image"><img decoding="async" src="https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_BlogBanner_June25-1.png" alt="MetaArchive Member Profiles" class="wp-image-852"/></figure> <h3 class="wp-block-heading">Tell us a bit about the digital preservation program at your organization?<br></h3> <p>Virginia Tech University Libraries was a founding member of the MetaArchive Cooperative and has hosted a LOCKSS cache since 2007. Our preservation system has evolved since then, including the addition of a second distributed digital preservation service with APTrust, the hiring of two digital preservation faculty members in 2017, and the ongoing development of a preservation-centric Digital Library Platform. The preservation system is managed by the Director of Digital Imaging and Preservation Services, the Digital Preservation Coordinator, and the Digital Preservation Technologist, and it is implemented by the Digital Library Development team in the Library. This group is responsible for developing and maintaining policies, overseeing workflows, and collaborating with our content producers. We are currently working on our Digital Preservation Program Priorities and Deliverables, outlining policies, services, and automations to be integrated with our new platform in development.<br></p> <h3 class="wp-block-heading">Looking ahead, what are you excited about, or what&#8217;s on the horizon for your program?</h3> <p>We have recently received a grant to digitize the Virginia Tech Insect Collection in 3D using photogrammetry in collaboration with the Entomology Department. 3D objects are complex and dynamic objects that present a preservation challenge, and we are investigating how our preservation workflow for these objects will differ from workflows for simpler objects. We are also developing a more robust Digital Humanities support system in the Libraries and are collaborating with VT Publishing to develop preservation levels for the variety of DH projects we hope to host. Ultimately, we are excited to have an automated preservation system built into the Digital Library Platform that communicates directly with MetaArchive.</p> <div class="wp-block-image"><figure class="aligncenter"><img loading="lazy" decoding="async" width="576" height="360" src="https://metaarchive.org/wp-content/uploads/2020/04/MetaArchive_MemberProfile_VirginiaTech_Carousel-1.png" alt="MetaArchive is integral to our preservation system, particularly since the MetaArchive network is where we store or most unique and valuable content. " class="wp-image-943" srcset="https://metaarchive.org/wp-content/uploads/2020/04/MetaArchive_MemberProfile_VirginiaTech_Carousel-1.png 576w, https://metaarchive.org/wp-content/uploads/2020/04/MetaArchive_MemberProfile_VirginiaTech_Carousel-1-220x138.png 220w, https://metaarchive.org/wp-content/uploads/2020/04/MetaArchive_MemberProfile_VirginiaTech_Carousel-1-300x188.png 300w" sizes="(max-width: 576px) 100vw, 576px" /><figcaption><em>MetaArchive is integral to our preservation system, particularly since the MetaArchive network is where we store or most unique and valuable content. </em><br>L-R: Nathan Hall, Director of Digital Imaging and Preservation;&nbsp;Alex&nbsp;Kinnaman, Digital Preservation Coordinator; and Luke Menzies, Digital Preservation Technologist </figcaption></figure></div> <h3 class="wp-block-heading">Tell us a bit about your local workflow. How has the MetaArchive preservation storage service been incorporated?</h3> <p>Our current workflows are under revision as our new Digital Library Platform is in its beta form. In the past we performed our MetaArchive ingests manually; we are working on a MetaArchive Automation Service to better streamline our preservation system. MetaArchive currently holds all of our digitized bound theses and dissertations prior to 2017. While we have not ingested content into MetaArchive during our preservation system development, we have maintained an active role in hosting our cache and staying active within the community. <br></p> <h3 class="wp-block-heading">Tell us about your experience in participating in the MetaArchive community. How has it influenced you or your work? </h3> <p>Virginia Tech University Libraries has been an active member in MetaArchive since 2004, both as a cache host and in the community, including Steering Committee participation, and committee participation. The Change for Continued Impact Series has enabled us to engage more in the community and offer feedback. We have often relied on this community for advice or discussion in making our preservation decisions. MetaArchive is integral to our preservation system, particularly since the MetaArchive network is where we store our most unique and valuable content.</p> <h3 class="wp-block-heading"><strong>Tell us a bit about your experience participating in the <em>Changing for Continued Impact Series</em>? What have been some of your key takeaways from the series thus far?</strong></h3> <p>We have been active in the Changed for Continued Impact Series, and appreciate the expanded interest in community needs and comprehensive engagement. One of the most valuable outcomes thus far has been the MetaArchive-LOCKSS Sustainability Evaluations provided by Penn State and Cal Poly, as they are in line with our needs at Virginia Tech as we develop an automated system.</p> <p><em>Editorial note: “Since late 2019 the MetaArchive community has been undergoing a series of intensive evaluations of both their organizational model as well as their technical approaches to distributed digital preservation (DDP). This is the Changing for Continued Impact (CFCI) Series, a facilitated framework led by Educopia that engages the MetaArchive members in a series of focused-discussions and work-sessions. This generative and co-creative process got underway in earnest this past Fall 2019, and will continue through Spring 2020 leading up to the next Annual MetaArchive Membership Meeting.&#8221; </em><br></p> </div><hr /> </article><!-- #post --> <article id="post-933" class="post-933 post type-post status-publish format-standard hentry category-news category-news-events tag-member-profile"> <div class="entry-content pw"> <h5>March 25, 2020</h5> <h3>MetaArchive Member Profile: University of Louisville Archives &#038; Special Collections</h3> <h3 class="wp-block-heading">By: Kyna Herzinger, Archivist for Record Management, and Rachel Howard, Digital Initiatives Librarian</h3> <figure class="wp-block-image"><img decoding="async" src="https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_BlogBanner_June25-1.png" alt="MetaArchive Member Profiles" class="wp-image-852"/></figure> <h3 class="wp-block-heading">Tell us a bit about the digital preservation program at your organization?<br></h3> <p>Our colleague, Rare Books Curator Delinda Buie, happened to be in the right place at the right time when Martin Halbert and others discussed applying for an NDIIPP (National Digital Information Infrastructure and Preservation Program) grant to explore distributed digital preservation at an ARL (Association of Research Libraries) meeting in 2003. At the time, UofL did not have a formal digitization program, but the Special Collections department, in which Delinda worked, had been doing <em>ad hoc</em> digitization for customer orders and exhibits for several years. The successful NDIIPP grant evolved into the MetaArchive Cooperative, and locally led to the creation of the Digital Initiatives program, in which Rachel Howard has served since 2006 and has overseen Digital Collections of cultural heritage materials and an institutional repository of university scholarship. UofL’s digital preservation efforts focused on digitized images and oral histories. In 2017, after Kyna Herzinger had joined the team, UofL took steps to develop a framework for a digital preservation program, drafting policies, exploring tools, and documenting workflows.&nbsp; At that time, UofL’s digital preservation expanded to include born-digital university records, oral histories, and community collections.<br></p> <h3 class="wp-block-heading">Looking ahead, what are you excited about, or what&#8217;s on the horizon for your program?</h3> <p>In terms of content, we are looking forward to preserving our electronic theses and dissertations, which are currently backed up in the cloud. We plan to establish a workflow to have them harvested into the MetaArchive network. In terms of maturing our overall program, we have identified two areas of focus. Having no single position that is responsible for handling born-digital content, we are still ensuring that our curators can accession and process their own born-digital collections.&nbsp; This means fine-tuning workflows. We are also starting to shift focus toward improving access to born-digital content, both in terms of discovery and researcher support.</p> <div class="wp-block-image"><figure class="aligncenter"><img loading="lazy" decoding="async" width="576" height="360" src="https://metaarchive.org/wp-content/uploads/2020/03/MetaArchive_MemberProfile_Louisville_Carousel.png" alt="" class="wp-image-934" srcset="https://metaarchive.org/wp-content/uploads/2020/03/MetaArchive_MemberProfile_Louisville_Carousel.png 576w, https://metaarchive.org/wp-content/uploads/2020/03/MetaArchive_MemberProfile_Louisville_Carousel-220x138.png 220w, https://metaarchive.org/wp-content/uploads/2020/03/MetaArchive_MemberProfile_Louisville_Carousel-300x188.png 300w" sizes="(max-width: 576px) 100vw, 576px" /><figcaption>&#8220;We both enjoy knowing a welcoming community of people who are engaged in similar work and are always willing to share advice or lend an ear. As we assess the resources at our disposal, we are especially cognizant of the role that MetaArchive plays as our most robust storage option. It provides what we could not have done ourselves: secure, distributed, bit-level preservation.&#8221;<br><em>In photo, L-R: Rachel Howard, Kyna Herzinger</em></figcaption></figure></div> <h3 class="wp-block-heading">Tell us a bit about your local workflow. How has the MetaArchive preservation storage service been incorporated?</h3> <p>For digitized content, after creating master and access files and metadata and launching a digital collection to the public, Rachel would copy master files and an XML file of the metadata to a staging server and organize them into archival units (AUs) of acceptable size for ingest into the MetaArchive network. The size of those AUs grew over time as we tested network capabilities, so that, for example, our yearbooks, whose master files ballooned to as much as 50 GB per yearbook, could each be treated as a single AU, thus requiring less “data wrangling”. She would then create a manifest page and (as was required in the early days) plugin, document the locations of those files and the AUs in the MetaArchive Conspectus database, and then work with MetaArchive partners to test and then ingest the collection into the preservation storage network.&nbsp;<br></p> <p>Now, with born-digital content, we use the BagIt profile specification, and recently participated in the MetaArchive’s SuperNode Pilot project, testing Bagit + OwnCloud and Exactly + SFTP to ingest content into the network.<br></p> <h3 class="wp-block-heading">Tell us about your experience in participating in the MetaArchive community. How has it influenced you or your work? </h3> <p>We both enjoy knowing a welcoming community of people who are engaged in similar work and are always willing to share advice or lend an ear. Working together with this group has also provided us with&nbsp; opportunities for research and professional leadership/ service at an international level. As we assess the resources at our disposal, we are especially cognizant of the role that the MetaArchive plays as our most robust storage option.&nbsp; It provides what we could not have done ourselves: secure, distributed, bit-level preservation. </p> <h3 class="wp-block-heading"><strong>Tell us a bit about your experience participating in the <em>Changing for Continued Impact Series</em>? What have been some of your key takeaways from the series thus far?</strong></h3> <p>It has been reenergizing to connect in a more focused way with the partners as we talk about the past, present, and future of the Cooperative. The series has provided reassurance that growing pains are normal, that challenges are opportunities for growth, and that it is better to be proactive about change than to wait until circumstances demand an immediate reaction.We appreciate being part of a community in which we have a say in its future. </p> <p><em>Editorial note: “Since late 2019 the MetaArchive community has been undergoing a series of intensive evaluations of both their organizational model as well as their technical approaches to distributed digital preservation (DDP). This is the Changing for Continued Impact (CFCI) Series, a facilitated framework led by Educopia that engages the MetaArchive members in a series of focused-discussions and work-sessions. This generative and co-creative process got underway in earnest this past Fall 2019, and will continue through Spring 2020 leading up to the next Annual MetaArchive Membership Meeting.&#8221; </em><br></p> </div><hr /> </article><!-- #post --> <article id="post-924" class="post-924 post type-post status-publish format-standard hentry category-news category-news-events tag-member-profile"> <div class="entry-content pw"> <h5>February 3, 2020</h5> <h3>MetaArchive Member Profile: Indianapolis Public Library</h3> <h3 class="wp-block-heading">By: William Knauth, Indianapolis Marion County Public Library, Digital Indy</h3> <figure class="wp-block-image"><img decoding="async" src="https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_BlogBanner_June25-1.png" alt="MetaArchive Member Profiles" class="wp-image-852"/></figure> <h3 class="wp-block-heading">Tell us a bit about the digital preservation program at your organization?<br></h3> <p>The Digital Indy project has been a member of InDiPres since 2017, previous to this there had been concerns about the integrity and longevity of the digital archival collections being created by the project and an analysis found that the level of preservation and cost associated with InDiPres was the best available. The primary work of preparing and transferring digital collections to the InDiPres server is done as part of the role of the Metadata Specialist, as well as communication with the InDiPres and MetaArchive groups. I regularly attend and participate at meetings of these organizations and report back developments to the team at the library. As far as goals and visions for our involvement with this project I would be very pleased if we are able to preserve 100% of our large digital collections in the MetaArchive network by 2021. I would also like to see the ongoing Supernode efforts materialize into an efficient streamlined ingest system that would attract new members to InDiPres and MetaArchive.</p> <h3 class="wp-block-heading">Looking ahead, what are you excited about, or what&#8217;s on the horizon for your program?</h3> <p>We are presently working on getting more of our collections data ingested into MetaArchive as well as setting up firm and effective workflows for sending data to the InDiPres staging server after some technical issues have placed this on hold. I am excited to see how this will be made more efficient by some of the projects being worked on at MetaArchive. </p> <div class="wp-block-image"><figure class="aligncenter"><img loading="lazy" decoding="async" width="600" height="300" src="https://metaarchive.org/wp-content/uploads/2020/01/MetaArchive_MemberProfile_InDiPres_Twitter-600x300.png" alt="MetaArchive Member Profile: Indianapolis Public Library" class="wp-image-926" srcset="https://metaarchive.org/wp-content/uploads/2020/01/MetaArchive_MemberProfile_InDiPres_Twitter-600x300.png 600w, https://metaarchive.org/wp-content/uploads/2020/01/MetaArchive_MemberProfile_InDiPres_Twitter-220x110.png 220w, https://metaarchive.org/wp-content/uploads/2020/01/MetaArchive_MemberProfile_InDiPres_Twitter-300x150.png 300w, https://metaarchive.org/wp-content/uploads/2020/01/MetaArchive_MemberProfile_InDiPres_Twitter-768x384.png 768w, https://metaarchive.org/wp-content/uploads/2020/01/MetaArchive_MemberProfile_InDiPres_Twitter.png 1024w" sizes="(max-width: 600px) 100vw, 600px" /><figcaption>&#8220;We are presently working on getting more of our collections data ingested into MetaArchive as well as setting up firm and effective workflows for sending data to the InDiPres staging server after some technical issues have placed this on hold. I am excited to see how this will be made more efficient by some of hte projects being worked on at MetaArchive.&#8221;<br><br><em>Pictured, L-R: William Knauth, Victoria Duncan, Beth Franklin, and Meaghan Fukunaga</em> <em>(formerly of InDiPres)</em></figcaption></figure></div> <h3 class="wp-block-heading">Tell us a bit about your local workflow. How has the MetaArchive preservation storage service been incorporated?</h3> <p>Our team has not had to significantly alter the established workflows in the initial areas of organizing and describing collections. The current standards we use are sufficiently robust as to create results that are effective for preservation purposes. We have had to make some additions to the workflows for successful ingest. This has involved processing collections through data integrity programs like Bagger and Exactly, setting up online transfer protocols, and creating documentation for preservation status of collections.</p> <h3 class="wp-block-heading">Tell us about your experience in participating in the MetaArchive community. How has it influenced you or your work? </h3> <p>I have had a positive experience meeting and working with the MetaArchive community in the several years of my involvement with the organization. I have found the membership to be very informed about both their own digital preservation situation and the state of this field of expertise in general. It has been useful and beneficial to have a group of individuals facing similar challenges to share ideas and solutions with. </p> </div><hr /> </article><!-- #post --> <article id="post-836" class="post-836 post type-post status-publish format-standard hentry category-news category-news-events tag-member-profile"> <div class="entry-content pw"> <h5>January 14, 2020</h5> <h3>MetaArchive Member Profile: Purdue University</h3> <h3 class="wp-block-heading">By: Sandi Caldrone and Michael Witt</h3> <figure class="wp-block-image"><img decoding="async" src="https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_BlogBanner_June25-1.png" alt="MetaArchive Member Profiles" class="wp-image-852"/></figure> <h3 class="wp-block-heading">Tell us a bit about the digital preservation program at your organization?<br></h3> <p>The <a rel="noreferrer noopener" aria-label="Purdue University Research Repository (opens in a new tab)" href="https://purr.purdue.edu/" target="_blank">Purdue University Research Repository</a>, also known as PURR (insert cat joke here), is one of a couple of Purdue University Libraries and School of Information Studies repositories which utilize MetaArchive for preservation storage. PURR is a university core research facility provided by the Libraries, the Office of the Executive Vice President for Research and Partnerships, and Information Technology at Purdue. It provides an online, collaborative working space, data sharing, and publication platform for Purdue researchers and their collaborators. PURR also provides preservation support for published datasets and the MetaArchive Cooperative is a huge part of that preservation support. </p> <h3 class="wp-block-heading">Looking ahead, what are you excited about, or what&#8217;s on the horizon for your program?</h3> <p>We&#8217;ve recently started to talk with faculty members who create virtual reality (VR) environments and objects as part of their research. VR preservation is an exciting and challenging new area for us and we are looking into how our platform and preservation workflows can support the preservation of VR objects and what new features or support we might need to develop down the road. </p> <div class="wp-block-image"><figure class="aligncenter"><img loading="lazy" decoding="async" width="1024" height="512" src="https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_Purdue_Twitter_June25-1.png" alt="" class="wp-image-889" srcset="https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_Purdue_Twitter_June25-1.png 1024w, https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_Purdue_Twitter_June25-1-220x110.png 220w, https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_Purdue_Twitter_June25-1-300x150.png 300w, https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_Purdue_Twitter_June25-1-768x384.png 768w, https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_Purdue_Twitter_June25-1-600x300.png 600w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption>&#8220;We’ve recently started to talk with faculty members who create virtual reality (VR) environments and objects as part of their research. VR preservation is an exciting and challenging new area for us and we are looking into how our platform and preservation workflows can support VR preservation and what new features we might need to develop down the road.&#8221; <br><br>Pictured back row L-R: Standa Pejša, Carly Dearborn, Matthew Kroll, Michael Witt. Front row L-R: Clair Stirm, Anthony Fuentes, Sandi Caldrone, and Yanqun Kuang.</figcaption></figure></div> <h3 class="wp-block-heading">Tell us a bit about your local workflow. How has the MetaArchive preservation storage service been incorporated?</h3> <p>We were lucky to have been still developing PURR when the Libraries joined the MetaArchive Cooperative and were able to develop our preservation infrastructure with a <a href="https://metaarchive.org/how-ddp-works/" target="_blank" rel="noreferrer noopener" aria-label="distributed model (opens in a new tab)">distributed model</a> in mind. We use BagIt bags to package our datasets and metadata for preservation. <br><br>We also regularly try to think through a &#8220;fire drill&#8221; scenario—what would we do if we experience partial loss of content in our repository? This has proven to be a great way for us to interrogate the construction of our archival units and determine if we have embedded the necessary metadata to rebuild our local repository from our backups in MetaArchive. </p> <h3 class="wp-block-heading">Tell us about your experience in participating in the MetaArchive community. How has it influenced you or your work? </h3> <p>Digital Preservation is hard work, and MetaArchive has a demonstrated track record of success with the biggest challenges of digital preservation, which aren&#8217;t related to storage or technology, but governance and sustainability. It is so valuable to have a built-in community to troubleshoot the various issues that arise in digital processing, preservation planning, and everything in between. The MetaArchive Cooperative represents a mature solution and community—it isn&#8217;t a flash in the pan. </p> </div><hr /> </article><!-- #post --> <article id="post-883" class="post-883 post type-post status-publish format-standard hentry category-news-events tag-member-profile"> <div class="entry-content pw"> <h5>December 19, 2019</h5> <h3>MetaArchive Member Profile: Atlanta University Center Robert W. Woodruff Library</h3> <h3 class="wp-block-heading">By: Josh Hogan on behalf of the Historically Black Colleges and University Library Alliance (HBCU LA)</h3> <figure class="wp-block-image"><img decoding="async" src="https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_BlogBanner_June25-1.png" alt="MetaArchive Member Profiles" class="wp-image-852"/></figure> <h3 class="wp-block-heading">Tell us a bit about the digital preservation program at your organization?<br></h3> <p>Since 2010, the <a href="https://www.auctr.edu/" target="_blank" rel="noreferrer noopener" aria-label="Atlanta University Center (AUC) Woodruff Library (opens in a new tab)">Atlanta University Center (AUC) Woodruff Library</a> has served as the technical lead and host of the LOCKSS server on behalf of the HBCU Library Alliance’s membership in the MetaArchive Cooperative.&nbsp; Digital preservation at the AUC Woodruff Library is implemented by the Digital Preservation Working Group (DPWG), a collaborative team with members from the Archives Research Center, the Digital Services Department, Records Management, and the IT Department.&nbsp; The DPWG is responsible for identifying, acquiring, and providing the means to preserve and ensure ongoing access to selected digital assets and associated metadata in accordance with AUC Woodruff Library’s collection development policies. For the past three years, we have pursued a three-year plan to develop our policies, workflows, and priorities.<br></p> <h3 class="wp-block-heading">Looking ahead, what are you excited about, or what&#8217;s on the horizon for your program?</h3> <p>We are excited about recently completing a revision of our digital collection development policy, providing clarity to our collecting areas related to born digital materials. We are also pleased to have wrapped up our first three-year plan, completing all of our goals for the period. We are eager to tackle the development of the new three-year plan in the coming months with an eye toward taking the program to the next level. </p> <div class="wp-block-image"><figure class="aligncenter"><img loading="lazy" decoding="async" width="1024" height="512" src="https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_AUCWoodruff_Twitter_final.png" alt="Member Profile: Atlanta University Center Woodruff Library. &quot;We are excited about recently completing a revision of our digital collection development policy, providing clarity to our collecting areas related to born digital materials. We are also pleased to have wrapped up our first three-year plan, completing all of the goals for the period. We're eager to tackle the development of the new three-year plan in the coming months with an eye toward taking the program to the next level.&quot; Photograph of Cliff Landis, Jessica Leming, Robert Fallen, Josh Hogan, Alex Dade, Aletha Carter, Suteera Apichatabutra, Christine Wiseman." class="wp-image-892" srcset="https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_AUCWoodruff_Twitter_final.png 1024w, https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_AUCWoodruff_Twitter_final-220x110.png 220w, https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_AUCWoodruff_Twitter_final-300x150.png 300w, https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_AUCWoodruff_Twitter_final-768x384.png 768w, https://metaarchive.org/wp-content/uploads/2019/12/MetaArchive_MemberProfile_AUCWoodruff_Twitter_final-600x300.png 600w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption><em>&#8220;We are excited about recently completing a revision of our digital collection development policy, providing clarity to our collecting areas related to born digital materials. We are also pleased to have wrapped up our first three-year plan, completing all of the goals for the period. We&#8217;re eager to tackle the development of the new three-year plan in the coming months with an eye toward taking the program to the next level.&#8221; </em><br><br><em>Pictured back row L-R: Cliff Landis, Jessica Leming, Robert Fallen, Josh Hogan. Front row L-R: Alex Dade, Aletha Carter, Suteera Apichatabutra, Christine Wiseman</em></figcaption></figure></div> <h3 class="wp-block-heading">Tell us a bit about your local workflow. How has the MetaArchive preservation storage service been incorporated?</h3> <p>Our local workflow identifies three broad categories of material to be preserved: born digital archival material, digitized archival material, and born digital institutional photographs and records. In addition to these categories, there are two tiers related to the priority of preserving the object or collection. The first tier objects are those of the highest priority, and these will be the ones that we will seek to ingest into robust preservation networks such as MetaArchive. Second tier objects and collections will be preserved in at least two different geographical areas and stored on Amazon Glacier. </p> <h3 class="wp-block-heading">Tell us about your experience in participating in the MetaArchive community. How has it influenced you or your work? </h3> <p>The AUC Woodruff Library has long participated in MetaArchive as a member of the HBCU Library Alliance. Most of the material we have ingested has been digitized copies of the founding documentation of the participating HBCUs, and we have been the host site of that initiative since 2008. <br><br>We recently participated in the SuperNode Pilot Project, playing the role of one of the ingesting institutions. This participation helped us ingest a significant portion of the digital material that we have identified as tier one, and it helped us evaluate the use of Exactly and OwnCloud as tools for use in our program. We hope that feedback provided to MetaArchive Steering Committee will be useful in determining the future path of this intiative that could reduce barriers to digital preservation for smaller institutions. </p> </div><hr /> </article><!-- #post --> <nav class="navigation paging-navigation" role="navigation"> <h1 class="screen-reader-text">Posts navigation</h1> <div class="nav-links"> <div class="nav-previous"><a href="https://metaarchive.org/category/news-events/page/2/" ><span class="meta-nav">&larr;</span> Older posts</a></div> </div><!-- .nav-links --> </nav><!-- .navigation --> </div> </div><!-- #content --> </div><!-- #primary --> <div class="story-section"><div class="pw"> <div class="post-box post-329" > <h2><p>The collections we ingest into MetaArchive largely include born-digital objects and digitized copies of audio/visual recordings, and these kinds of collections are at risk for all sorts of loss and damage. MetaArchive provides a trusted way to preserve these at-risk digital collections in a long-term fashion. The trust stems from the fact that MetaArchive is composed of peer, cultural heritage institutions that are on the same wavelength, and that we have a voice on the way the organization is run. This all gives us peace of mind.</p> </h2> <p> ~&nbsp;Zach Vowell, <em>California Polytechnic State University</em></p> </div> <a href="https://metaarchive.org/join-us/">Join MetaArchive Today &raquo;</a> <div class="cb"></div> </div></div> </div><!-- #main --> <footer id="colophon" class="site-footer" role="contentinfo"> <div class="social-network"> <a class="icon-email" href="/contact/" target="_blank">Contact Us</a> </div> <div class="cb"></div> <!--hilary was here 10/17--> <div class="footer-search"><div class="asp_w_container"> <div class='asp_w asp_m asp_m_2 asp_m_2_1 wpdreams_asp_sc wpdreams_asp_sc-2 ajaxsearchpro asp_main_container asp_non_compact' data-id="2" data-name="Sitewide/Footer Imported" data-instance="1" id='ajaxsearchpro2_1'> <div class="probox"> <div class='promagnifier' tabindex="101"> <div class='asp_text_button hiddend'> Search </div> <div class='innericon'> <svg xmlns="http://www.w3.org/2000/svg" width="22" height="22" viewBox="0 0 512 512"><path d="M460.355 421.59l-106.51-106.512c20.04-27.553 31.884-61.437 31.884-98.037C385.73 124.935 310.792 50 218.685 50c-92.106 0-167.04 74.934-167.04 167.04 0 92.107 74.935 167.042 167.04 167.042 34.912 0 67.352-10.773 94.184-29.158L419.945 462l40.41-40.41zM100.63 217.04c0-65.095 52.96-118.055 118.056-118.055 65.098 0 118.057 52.96 118.057 118.056 0 65.097-52.96 118.057-118.057 118.057-65.096 0-118.055-52.96-118.055-118.056z"/></svg> </div> <div class="asp_clear"></div> </div> <div class='prosettings' style='display:none;' data-opened=0> <div class='innericon'> <svg xmlns="http://www.w3.org/2000/svg" width="22" height="22" viewBox="0 0 512 512"><polygon transform="rotate(90 256 256)" points="142.332,104.886 197.48,50 402.5,256 197.48,462 142.332,407.113 292.727,256"/></svg> </div> </div> <div class='proinput'> <form action='#' autocomplete="off" aria-label="Search form 2"> <input type='search' class='orig' tabindex="100" placeholder='Search website...' name='phrase' value='' aria-label="Search input 2" autocomplete="off"/> <input type='text' class='autocomplete' name='phrase' value='' aria-label="Search autocomplete, ignore please" aria-hidden="true" autocomplete="off" disabled/> <input type='submit' aria-hidden="true" aria-label="Hidden button" style='width:0; height: 0; visibility: hidden;'> </form> </div> <div class='proloading'> <div class="asp_loader"> <div class="asp_loader-inner asp_simple-circle"> </div> </div> </div> <div class='proclose'> <svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="512px" height="512px" viewBox="0 0 512 512" enable-background="new 0 0 512 512" xml:space="preserve"> <polygon points="438.393,374.595 319.757,255.977 438.378,137.348 374.595,73.607 255.995,192.225 137.375,73.622 73.607,137.352 192.246,255.983 73.622,374.625 137.352,438.393 256.002,319.734 374.652,438.378 "/> </svg> </div> </div> </div> <div class='asp_data_container' style="display:none !important;"> <div class="asp_init_data" style="display:none !important;" id="asp_init_id_2_1" data-asp-id="2" data-asp-instance="1" data-aspdata="ew0KICAgICAgICAiaG9tZXVybCI6ICJodHRwczovL21ldGFhcmNoaXZlLm9yZy8iLA0KICAgIAkiaXNfcmVzdWx0c19wYWdlIjogMCwNCiAgICAicmVzdWx0c3R5cGUiOiAidmVydGljYWwiLA0KICAgICJyZXN1bHRzcG9zaXRpb24iOiAiaG92ZXIiLA0KICAgICJyZXN1bHRzU25hcFRvIjogImxlZnQiLA0KICAgICJyZXN1bHRzIjogew0KICAgICAgICAid2lkdGgiOiAiYXV0byIsDQogICAgICAgICJ3aWR0aF90YWJsZXQiOiAiYXV0byIsDQogICAgICAgICJ3aWR0aF9waG9uZSI6ICJhdXRvIg0KICAgIH0sDQogICAgIml0ZW1zY291bnQiOiA0LA0KICAgICJjaGFyY291bnQiOiAgNCwNCiAgICAiaGlnaGxpZ2h0IjogMCwNCiAgICAiaGlnaGxpZ2h0V2hvbGV3b3JkcyI6IDEsDQogICAgInNpbmdsZUhpZ2hsaWdodCI6IDAsDQogICAgInNjcm9sbFRvUmVzdWx0cyI6IHsNCiAgICAgICAgImVuYWJsZWQiOiAwLA0KICAgICAgICAib2Zmc2V0IjogMCAgICB9LA0KICAgICJhdXRvY29tcGxldGUiOiB7DQogICAgICAgICJlbmFibGVkIjogMSwNCgkJInRyaWdnZXJfY2hhcmNvdW50IjogMCwNCiAgICAgICAgImdvb2dsZU9ubHkiOiAwLA0KICAgICAgICAibGFuZyI6ICJlbiIsDQogICAgICAgICJtb2JpbGUiOiAxICAgIH0sDQogICAgInRyaWdnZXIiOiB7DQogICAgICAgICJkZWxheSI6IDMwMCwNCiAgICAgICAgImF1dG9jb21wbGV0ZV9kZWxheSI6IDMxMCwNCiAgICAgICAgImZhY2V0IjogMCwNCiAgICAgICAgInR5cGUiOiAwLA0KICAgICAgICAiY2xpY2siOiAicmVzdWx0c19wYWdlIiwNCiAgICAgICAgImNsaWNrX2xvY2F0aW9uIjogInNhbWUiLA0KICAgICAgICAicmV0dXJuIjogInJlc3VsdHNfcGFnZSIsDQogICAgICAgICJyZXR1cm5fbG9jYXRpb24iOiAic2FtZSIsDQogICAgICAgICJyZWRpcmVjdF91cmwiOiAiP3M9e3BocmFzZX0iLA0KICAgICAgICAiZWxlbWVudG9yX3VybCI6ICJodHRwczovL21ldGFhcmNoaXZlLm9yZy8/YXNwX2xzPXtwaHJhc2V9Ig0KICAgIH0sDQogICAgIm92ZXJyaWRld3BkZWZhdWx0IjogMSwNCiAgICAib3ZlcnJpZGVfbWV0aG9kIjogInBvc3QiLA0KICAgICJzZXR0aW5ncyI6IHsNCiAgICAgICAgImhpZGVDaGlsZHJlbiI6IDAgICAgfSwNCiAgICAic2V0dGluZ3NpbWFnZXBvcyI6ICJyaWdodCIsDQogICAgInNldHRpbmdzVmlzaWJsZSI6IDAsDQogICAgInNldHRpbmdzSGlkZU9uUmVzIjogMCwNCiAgICAicHJlc2NvbnRhaW5lcmhlaWdodCI6ICI0MDBweCIsDQogICAgImNsb3NlT25Eb2NDbGljayI6IDEsDQogICAgImZvY3VzT25QYWdlbG9hZCI6IDAsDQogICAgImlzb3RvcGljIjogew0KICAgICAgICAiaXRlbVdpZHRoIjogIjIwMHB4IiwNCiAgICAgICAgIml0ZW1XaWR0aFRhYmxldCI6ICIyMDBweCIsDQogICAgICAgICJpdGVtV2lkdGhQaG9uZSI6ICIyMDBweCIsDQogICAgICAgICJpdGVtSGVpZ2h0IjogIjIwMHB4IiwNCiAgICAgICAgIml0ZW1IZWlnaHRUYWJsZXQiOiAiMjAwcHgiLA0KICAgICAgICAiaXRlbUhlaWdodFBob25lIjogIjIwMHB4IiwNCiAgICAgICAgInBhZ2luYXRpb24iOiAxLA0KICAgICAgICAicm93cyI6IDIsDQogICAgICAgICJndXR0ZXIiOiA1LA0KICAgICAgICAic2hvd092ZXJsYXkiOiAxLA0KICAgICAgICAiYmx1ck92ZXJsYXkiOiAxLA0KICAgICAgICAiaGlkZUNvbnRlbnQiOiAxICAgIH0sDQogICAgImxvYWRlckxvY2F0aW9uIjogImF1dG8iLA0KICAgICJzaG93X21vcmUiOiB7DQogICAgICAgICJlbmFibGVkIjogMCwNCiAgICAgICAgInVybCI6ICI/cz17cGhyYXNlfSIsDQogICAgICAgICJlbGVtZW50b3JfdXJsIjogImh0dHBzOi8vbWV0YWFyY2hpdmUub3JnLz9hc3BfbHM9e3BocmFzZX0iLA0KICAgICAgICAiYWN0aW9uIjogImFqYXgiLA0KICAgICAgICAibG9jYXRpb24iOiAic2FtZSIsDQogICAgICAgICJpbmZpbml0ZSI6IDEgICAgfSwNCiAgICAibW9iaWxlIjogew0KICAgICAgICAidHJpZ2dlcl9vbl90eXBlIjogMSwNCiAgICAgICAgImNsaWNrX2FjdGlvbiI6ICJyZXN1bHRzX3BhZ2UiLA0KICAgICAgICAicmV0dXJuX2FjdGlvbiI6ICJyZXN1bHRzX3BhZ2UiLA0KICAgICAgICAiY2xpY2tfYWN0aW9uX2xvY2F0aW9uIjogInNhbWUiLA0KICAgICAgICAicmV0dXJuX2FjdGlvbl9sb2NhdGlvbiI6ICJzYW1lIiwNCiAgICAgICAgInJlZGlyZWN0X3VybCI6ICI/cz17cGhyYXNlfSIsDQogICAgICAgICJlbGVtZW50b3JfdXJsIjogImh0dHBzOi8vbWV0YWFyY2hpdmUub3JnLz9hc3BfbHM9e3BocmFzZX0iLA0KICAgICAgICAibWVudV9zZWxlY3RvciI6ICIjbWVudS10b2dnbGUiLA0KICAgICAgICAiaGlkZV9rZXlib2FyZCI6IDAsDQogICAgICAgICJmb3JjZV9yZXNfaG92ZXIiOiAwLA0KICAgICAgICAiZm9yY2Vfc2V0dF9ob3ZlciI6IDAsDQogICAgICAgICJmb3JjZV9zZXR0X3N0YXRlIjogIm5vbmUiDQogICAgfSwNCiAgICAiY29tcGFjdCI6IHsNCiAgICAgICAgImVuYWJsZWQiOiAwLA0KICAgICAgICAiZm9jdXMiOiAxLA0KICAgICAgICAid2lkdGgiOiAiMTAwJSIsDQogICAgICAgICJ3aWR0aF90YWJsZXQiOiAiNDgwcHgiLA0KICAgICAgICAid2lkdGhfcGhvbmUiOiAiMzIwcHgiLA0KICAgICAgICAiY2xvc2VPbk1hZ25pZmllciI6IDEsDQogICAgICAgICJjbG9zZU9uRG9jdW1lbnQiOiAwLA0KICAgICAgICAicG9zaXRpb24iOiAic3RhdGljIiwNCiAgICAgICAgIm92ZXJsYXkiOiAwICAgIH0sDQogICAgInNiIjogew0KICAgICAgICAicmVkaXJlY3RfYWN0aW9uIjogImFqYXhfc2VhcmNoIiwNCiAgICAgICAgInJlZGlyZWN0X2xvY2F0aW9uIjogInNhbWUiLA0KICAgICAgICAicmVkaXJlY3RfdXJsIjogIj9zPXtwaHJhc2V9IiwNCiAgICAgICAgImVsZW1lbnRvcl91cmwiOiAiaHR0cHM6Ly9tZXRhYXJjaGl2ZS5vcmcvP2FzcF9scz17cGhyYXNlfSINCiAgICB9LA0KICAgICJyYiI6IHsNCiAgICAgICAgImFjdGlvbiI6ICJub3RoaW5nIg0KICAgIH0sDQogICAgImFuaW1hdGlvbnMiOiB7DQogICAgICAgICJwYyI6IHsNCiAgICAgICAgICAgICJzZXR0aW5ncyI6IHsNCiAgICAgICAgICAgICAgICAiYW5pbSIgOiAiZmFkZWRyb3AiLA0KICAgICAgICAgICAgICAgICJkdXIiICA6IDMwMCAgICAgICAgICAgIH0sDQogICAgICAgICAgICAicmVzdWx0cyIgOiB7DQogICAgICAgICAgICAgICAgImFuaW0iIDogImZhZGVkcm9wIiwNCiAgICAgICAgICAgICAgICAiZHVyIiAgOiAzMDAgICAgICAgICAgICB9LA0KICAgICAgICAgICAgIml0ZW1zIiA6ICJmYWRlSW5Eb3duIg0KICAgICAgICB9LA0KICAgICAgICAibW9iIjogew0KICAgICAgICAgICAgInNldHRpbmdzIjogew0KICAgICAgICAgICAgICAgICJhbmltIiA6ICJmYWRlZHJvcCIsDQogICAgICAgICAgICAgICAgImR1ciIgIDogMzAwICAgICAgICAgICAgfSwNCiAgICAgICAgICAgICJyZXN1bHRzIiA6IHsNCiAgICAgICAgICAgICAgICAiYW5pbSIgOiAiZmFkZWRyb3AiLA0KICAgICAgICAgICAgICAgICJkdXIiICA6IDMwMCAgICAgICAgICAgIH0sDQogICAgICAgICAgICAiaXRlbXMiIDogInZvaWRhbmltIg0KICAgICAgICB9DQogICAgfSwNCiAgICAic2VsZWN0MiI6IHsNCiAgICAgICAgIm5vcmVzIjogIk5vIHJlc3VsdHMgbWF0Y2giDQogICAgfSwNCiAgICAiZGV0ZWN0VmlzaWJpbGl0eSIgOiAwLA0KICAgICJhdXRvcCI6IHsNCiAgICAgICAgInN0YXRlIjogImRpc2FibGVkIiwNCiAgICAgICAgInBocmFzZSI6ICIiLA0KICAgICAgICAiY291bnQiOiAxMCAgICB9LA0KICAgICJyZXNQYWdlIjogew0KICAgICAgICAidXNlQWpheCI6IDAsDQogICAgICAgICJzZWxlY3RvciI6ICIjbWFpbiIsDQogICAgICAgICJ0cmlnZ2VyX3R5cGUiOiAxLA0KICAgICAgICAidHJpZ2dlcl9mYWNldCI6IDEsDQogICAgICAgICJ0cmlnZ2VyX21hZ25pZmllciI6IDAsDQogICAgICAgICJ0cmlnZ2VyX3JldHVybiI6IDAgICAgfSwNCiAgICAiZnNzX2xheW91dCI6ICJjb2x1bW4iLA0KICAgICJzY3JvbGxCYXIiOiB7DQogICAgICAgICJ2ZXJ0aWNhbCI6IHsNCiAgICAgICAgICAgICJhdXRvSGlkZSI6IDEgICAgICAgIH0sDQogICAgICAgICJob3Jpem9udGFsIjogew0KICAgICAgICAgICAgImVuYWJsZWQiOiAxLA0KICAgICAgICAgICAgImF1dG9IaWRlIjogMSAgICAgICAgfSwNCiAgICAgICAgInNldHRpbmdzIjogew0KICAgICAgICAgICAgImF1dG9IaWRlIjogMCAgICAgICAgfQ0KICAgIH0sDQoJImRpdmkiOiB7DQoJCSJib2R5Y29tbWVyY2UiOiAwCX0sDQogICAgInByZXZlbnRCb2R5U2Nyb2xsIjogMCwNCiAgICAic3RhdGlzdGljcyI6IDB9DQo="></div> <div class='asp_hidden_data' style="display:none !important;"> <div class='asp_item_overlay'> <div class='asp_item_inner'> <svg xmlns="http://www.w3.org/2000/svg" width="22" height="22" viewBox="0 0 512 512"><path d="M448.225 394.243l-85.387-85.385c16.55-26.08 26.146-56.986 26.146-90.094 0-92.99-75.652-168.64-168.643-168.64-92.988 0-168.64 75.65-168.64 168.64s75.65 168.64 168.64 168.64c31.466 0 60.94-8.67 86.176-23.734l86.14 86.142c36.755 36.754 92.355-18.783 55.57-55.57zm-344.233-175.48c0-64.155 52.192-116.35 116.35-116.35s116.353 52.194 116.353 116.35S284.5 335.117 220.342 335.117s-116.35-52.196-116.35-116.352zm34.463-30.26c34.057-78.9 148.668-69.75 170.248 12.863-43.482-51.037-119.984-56.532-170.248-12.862z"/></svg> </div> </div> </div> </div> <div id='__original__ajaxsearchprores2_1' class='asp_w asp_r asp_r_2 asp_r_2_1 vertical ajaxsearchpro wpdreams_asp_sc wpdreams_asp_sc-2' data-id="2" data-instance="1"> <div class="results"> <div class="resdrg"> </div> </div> <div class="asp_res_loader hiddend"> <div class="asp_loader"> <div class="asp_loader-inner asp_simple-circle"> </div> </div> </div> </div> <div id='__original__ajaxsearchprosettings2_1' class="asp_w asp_ss asp_ss_2 asp_s asp_s_2 asp_s_2_1 wpdreams_asp_sc wpdreams_asp_sc-2 ajaxsearchpro searchsettings" data-id="2" data-instance="1"> <form name='options' class="asp-fss-column" autocomplete = 'off'> <input type="hidden" style="display:none;" name="current_page_id" value="1287"> <input type='hidden' name='qtranslate_lang' style="display:none;" value='0'/> <input type="hidden" name="filters_changed" style="display:none;" value="0"> <input type="hidden" name="filters_initial" style="display:none;" value="1"> <fieldset class="asp_filter_generic asp_filter_id_1 asp_filter_n_0"> <legend>Generic filters</legend> <div class="asp_option"> <div class="asp_option_inner"> <input type="checkbox" value="exact" id="set_exact2_1" aria-label="Exact matches only" name="asp_gen[]" /> <label aria-hidden="true" for="set_exact2_1"> Hidden label </label> </div> <div class="asp_option_label"> Exact matches only </div> </div> <div class="asp_option"> <div class="asp_option_inner"> <input type="checkbox" value="title" id="set_title2_1" data-origvalue="1" aria-label="Search in title" name="asp_gen[]" checked="checked"/> <label aria-hidden="true" for="set_title2_1"> Hidden label </label> </div> <div class="asp_option_label"> Search in title </div> </div> <div class="asp_option"> <div class="asp_option_inner"> <input type="checkbox" value="content" id="set_content2_1" data-origvalue="1" aria-label="Search in content" name="asp_gen[]" checked="checked"/> <label aria-hidden="true" for="set_content2_1"> Hidden label </label> </div> <div class="asp_option_label"> Search in content </div> </div> <div class="asp_option"> <div class="asp_option_inner"> <input type="checkbox" value="excerpt" id="set_excerpt2_1" aria-label="Search in excerpt" name="asp_gen[]" /> <label aria-hidden="true" for="set_excerpt2_1"> Hidden label </label> </div> <div class="asp_option_label"> Search in excerpt </div> </div> </fieldset> <input type="checkbox" style="display: none !important;" value="post" aria-label="Hidden label" aria-hidden="true" id="2_1customset_2_1100" name="customset[]" checked="checked"/> <input type="checkbox" style="display: none !important;" value="page" aria-label="Hidden label" aria-hidden="true" id="2_1customset_2_1101" name="customset[]" checked="checked"/> <input type="checkbox" style="display: none !important;" value="calendar" aria-label="Hidden label" aria-hidden="true" id="2_1customset_2_1102" name="customset[]" checked="checked"/> <input type="checkbox" style="display: none !important;" value="acf" aria-label="Hidden label" aria-hidden="true" id="2_1customset_2_1103" name="customset[]" checked="checked"/> <div style="clear:both;"></div> </form> </div> </div> </div> <div class="site-info"> &copy; <script type="text/javascript"> var theDate=new Date() document.write(theDate.getFullYear()) </script> <a href="https://educopia.org/">Educopia Institute</a> | 1230 Peachtree Street, Suite 1900 | Atlanta, GA 30309 | (470)&nbsp207-8384 </div><!-- .site-info --> </footer><!-- #colophon --> <a id="scroll-to-top" href="#" title="Scroll to Top">Top</a> <div class='asp_hidden_data' id="asp_hidden_data" style="display: none !important;"> <svg style="position:absolute" height="0" width="0"> <filter id="aspblur"> <feGaussianBlur in="SourceGraphic" stdDeviation="4"/> </filter> </svg> <svg style="position:absolute" height="0" width="0"> <filter id="no_aspblur"></filter> </svg> </div> <script type="text/javascript" src="https://metaarchive.org/wp-content/plugins/jquery-smooth-scroll/js/script.min.js?ver=6.6.1" id="jquery-smooth-scroll-js"></script> <script type="text/javascript" src="https://metaarchive.org/wp-content/themes/connectTheDots/js/functions.js?ver=20160717" id="twentythirteen-script-js"></script> <script type="text/javascript" id="wd-asp-ajaxsearchpro-js-before"> /* <![CDATA[ */ window.ASP = typeof window.ASP !== 'undefined' ? window.ASP : {}; window.ASP.wp_rocket_exception = "DOMContentLoaded"; window.ASP.ajaxurl = "https:\/\/metaarchive.org\/wp-admin\/admin-ajax.php"; window.ASP.backend_ajaxurl = "https:\/\/metaarchive.org\/wp-admin\/admin-ajax.php"; window.ASP.js_scope = "jQuery"; window.ASP.asp_url = "https:\/\/metaarchive.org\/wp-content\/plugins\/ajax-search-pro\/"; window.ASP.upload_url = "https:\/\/metaarchive.org\/wp-content\/uploads\/asp_upload\/"; window.ASP.css_basic_url = "https:\/\/metaarchive.org\/wp-content\/uploads\/asp_upload\/style.basic-ho-is-po-no-da-co-au-ga-se-is.css"; window.ASP.detect_ajax = 0; window.ASP.media_query = "1IUU0w"; window.ASP.version = 5024; window.ASP.pageHTML = ""; window.ASP.additional_scripts = []; window.ASP.script_async_load = false; window.ASP.scrollbar = true; window.ASP.css_async = false; window.ASP.js_retain_popstate = 0; window.ASP.highlight = {"enabled":false,"data":[]}; window.ASP.debug = false; window.ASP.instances = {}; window.ASP.analytics = {"method":0,"tracking_id":"","string":"?ajax_search={asp_term}","event":{"focus":{"active":1,"action":"focus","category":"ASP {search_id} | {search_name}","label":"Input focus","value":"1"},"search_start":{"active":0,"action":"search_start","category":"ASP {search_id} | {search_name}","label":"Phrase: {phrase}","value":"1"},"search_end":{"active":1,"action":"search_end","category":"ASP {search_id} | {search_name}","label":"{phrase} | {results_count}","value":"1"},"magnifier":{"active":1,"action":"magnifier","category":"ASP {search_id} | {search_name}","label":"Magnifier clicked","value":"1"},"return":{"active":1,"action":"return","category":"ASP {search_id} | {search_name}","label":"Return button pressed","value":"1"},"try_this":{"active":1,"action":"try_this","category":"ASP {search_id} | {search_name}","label":"Try this click | {phrase}","value":"1"},"facet_change":{"active":0,"action":"facet_change","category":"ASP {search_id} | {search_name}","label":"{option_label} | {option_value}","value":"1"},"result_click":{"active":1,"action":"result_click","category":"ASP {search_id} | {search_name}","label":"{result_title} | {result_url}","value":"1"}}}; /* ]]> */ </script> <script type="text/javascript" src="https://metaarchive.org/wp-content/plugins/ajax-search-pro/js/legacy/min/jquery.ajaxsearchpro-sb.min.js?ver=1IUU0w" id="wd-asp-ajaxsearchpro-js"></script> </body> </html>

Pages: 1 2 3 4 5 6 7 8 9 10