<?xml version="1.0"?>
<oembed><version>1.0</version><provider_name>Bitstreams: The Digital Collections Blog</provider_name><provider_url>https://blogs.library.duke.edu/bitstreams</provider_url><author_name>Sean Aery</author_name><author_url>https://blogs.library.duke.edu/bitstreams/author/seanaeryduke-edu/</author_url><title>Implementing ArcLight: A Reflection - Bitstreams: The Digital Collections Blog</title><type>rich</type><width>600</width><height>338</height><html>&lt;blockquote class="wp-embedded-content" data-secret="XwtdhJdUXS"&gt;&lt;a href="https://blogs.library.duke.edu/bitstreams/2020/11/20/implementing-arclight-a-reflection/"&gt;Implementing ArcLight: A Reflection&lt;/a&gt;&lt;/blockquote&gt;&lt;iframe sandbox="allow-scripts" security="restricted" src="https://blogs.library.duke.edu/bitstreams/2020/11/20/implementing-arclight-a-reflection/embed/#?secret=XwtdhJdUXS" width="600" height="338" title="&#x201C;Implementing ArcLight: A Reflection&#x201D; &#x2014; Bitstreams: The Digital Collections Blog" data-secret="XwtdhJdUXS" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" class="wp-embedded-content"&gt;&lt;/iframe&gt;&lt;script&gt;
/*! This file is auto-generated */
!function(d,l){"use strict";l.querySelector&amp;&amp;d.addEventListener&amp;&amp;"undefined"!=typeof URL&amp;&amp;(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&amp;&amp;!/[^a-zA-Z0-9]/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll('iframe[data-secret="'+t.secret+'"]'),o=l.querySelectorAll('blockquote[data-secret="'+t.secret+'"]'),c=new RegExp("^https?:$","i"),i=0;i&lt;o.length;i++)o[i].style.display="none";for(i=0;i&lt;a.length;i++)s=a[i],e.source===s.contentWindow&amp;&amp;(s.removeAttribute("style"),"height"===t.message?(1e3&lt;(r=parseInt(t.value,10))?r=1e3:~~r&lt;200&amp;&amp;(r=200),s.height=r):"link"===t.message&amp;&amp;(r=new URL(s.getAttribute("src")),n=new URL(t.value),c.test(n.protocol))&amp;&amp;n.host===r.host&amp;&amp;l.activeElement===s&amp;&amp;(d.top.location.href=t.value))}},d.addEventListener("message",d.wp.receiveEmbedMessage,!1),l.addEventListener("DOMContentLoaded",function(){for(var e,t,s=l.querySelectorAll("iframe.wp-embedded-content"),r=0;r&lt;s.length;r++)(t=(e=s[r]).getAttribute("data-secret"))||(t=Math.random().toString(36).substring(2,12),e.src+="#?secret="+t,e.setAttribute("data-secret",t)),e.contentWindow.postMessage({message:"ready",secret:t},"*")},!1)))}(window,document);
//# sourceURL=https://blogs.library.duke.edu/bitstreams/wp-includes/js/wp-embed.min.js
&lt;/script&gt;
</html><thumbnail_url>https://blogs.library.duke.edu/bitstreams/files/2020/11/arclight-for-blog.jpg</thumbnail_url><thumbnail_width>1036</thumbnail_width><thumbnail_height>574</thumbnail_height><description>Around this time last year, I wrote about our ambitious plans to implement ArcLight software for archival discovery and access at Duke in 2020. While this year has certainly laid waste to so many good intentions, our team persisted through the cacophony undeterred, and&#x2014;I&#x2019;m proud to report&#x2014;still hit our mark of going live on July &hellip; Continue reading &rarr;</description></oembed>
