CINXE.COM

May 2015 - Duke Collaboratory for Classics Computing (DC3)

<!DOCTYPE html> <!--[if IE 7]> <html class="ie ie7" lang="en-US"> <![endif]--> <!--[if !(IE 7) | !(IE 8) ]><!--> <html lang="en-US"> <!--<![endif]--> <head> <meta charset="UTF-8"> <meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests"> <meta name="viewport" content="width=device-width"> <title>May 2015 - Duke Collaboratory for Classics Computing (DC3)</title> <link rel="profile" href="//gmpg.org/xfn/11"> <link rel="pingback" href="https://blogs.library.duke.edu/dcthree/xmlrpc.php"> <!--[if lt IE 9]> <script src="https://blogs.library.duke.edu/dcthree/wp-content/themes/twentyfourteen/js/html5.js"></script> <![endif]--> <meta name='robots' content='noindex, follow' /> <style>img:is([sizes="auto" i], [sizes^="auto," i]) { contain-intrinsic-size: 3000px 1500px }</style> <!-- This site is optimized with the Yoast SEO plugin v24.6 - https://yoast.com/wordpress/plugins/seo/ --> <meta property="og:locale" content="en_US" /> <meta property="og:type" content="website" /> <meta property="og:title" content="May 2015 - Duke Collaboratory for Classics Computing (DC3)" /> <meta property="og:url" content="https://blogs.library.duke.edu/dcthree/2015/05/" /> <meta property="og:site_name" content="Duke Collaboratory for Classics Computing (DC3)" /> <meta name="twitter:card" content="summary_large_image" /> <script type="application/ld+json" class="yoast-schema-graph">{"@context":"https://schema.org","@graph":[{"@type":"CollectionPage","@id":"https://blogs.library.duke.edu/dcthree/2015/05/","url":"https://blogs.library.duke.edu/dcthree/2015/05/","name":"May 2015 - Duke Collaboratory for Classics Computing (DC3)","isPartOf":{"@id":"https://blogs.library.duke.edu/dcthree/#website"},"breadcrumb":{"@id":"https://blogs.library.duke.edu/dcthree/2015/05/#breadcrumb"},"inLanguage":"en-US"},{"@type":"BreadcrumbList","@id":"https://blogs.library.duke.edu/dcthree/2015/05/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://blogs.library.duke.edu/dcthree/"},{"@type":"ListItem","position":2,"name":"Archives for May 2015"}]},{"@type":"WebSite","@id":"https://blogs.library.duke.edu/dcthree/#website","url":"https://blogs.library.duke.edu/dcthree/","name":"Duke Collaboratory for Classics Computing (DC3)","description":"a collection of parts flying in loose formation","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://blogs.library.duke.edu/dcthree/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"}]}</script> <!-- / Yoast SEO plugin. --> <link rel="alternate" type="application/rss+xml" title="Duke Collaboratory for Classics Computing (DC3) &raquo; Feed" href="https://blogs.library.duke.edu/dcthree/feed/" /> <link rel="alternate" type="application/rss+xml" title="Duke Collaboratory for Classics Computing (DC3) &raquo; Comments Feed" href="https://blogs.library.duke.edu/dcthree/comments/feed/" /> <script> window._wpemojiSettings = {"baseUrl":"https:\/\/s.w.org\/images\/core\/emoji\/15.0.3\/72x72\/","ext":".png","svgUrl":"https:\/\/s.w.org\/images\/core\/emoji\/15.0.3\/svg\/","svgExt":".svg","source":{"concatemoji":"https:\/\/blogs.library.duke.edu\/dcthree\/wp-includes\/js\/wp-emoji-release.min.js?ver=6.7.2"}}; /*! This file is auto-generated */ !function(i,n){var o,s,e;function c(e){try{var t={supportTests:e,timestamp:(new Date).valueOf()};sessionStorage.setItem(o,JSON.stringify(t))}catch(e){}}function p(e,t,n){e.clearRect(0,0,e.canvas.width,e.canvas.height),e.fillText(t,0,0);var t=new Uint32Array(e.getImageData(0,0,e.canvas.width,e.canvas.height).data),r=(e.clearRect(0,0,e.canvas.width,e.canvas.height),e.fillText(n,0,0),new Uint32Array(e.getImageData(0,0,e.canvas.width,e.canvas.height).data));return t.every(function(e,t){return e===r[t]})}function u(e,t,n){switch(t){case"flag":return n(e,"\ud83c\udff3\ufe0f\u200d\u26a7\ufe0f","\ud83c\udff3\ufe0f\u200b\u26a7\ufe0f")?!1:!n(e,"\ud83c\uddfa\ud83c\uddf3","\ud83c\uddfa\u200b\ud83c\uddf3")&&!n(e,"\ud83c\udff4\udb40\udc67\udb40\udc62\udb40\udc65\udb40\udc6e\udb40\udc67\udb40\udc7f","\ud83c\udff4\u200b\udb40\udc67\u200b\udb40\udc62\u200b\udb40\udc65\u200b\udb40\udc6e\u200b\udb40\udc67\u200b\udb40\udc7f");case"emoji":return!n(e,"\ud83d\udc26\u200d\u2b1b","\ud83d\udc26\u200b\u2b1b")}return!1}function f(e,t,n){var r="undefined"!=typeof WorkerGlobalScope&&self instanceof WorkerGlobalScope?new OffscreenCanvas(300,150):i.createElement("canvas"),a=r.getContext("2d",{willReadFrequently:!0}),o=(a.textBaseline="top",a.font="600 32px Arial",{});return e.forEach(function(e){o[e]=t(a,e,n)}),o}function t(e){var t=i.createElement("script");t.src=e,t.defer=!0,i.head.appendChild(t)}"undefined"!=typeof Promise&&(o="wpEmojiSettingsSupports",s=["flag","emoji"],n.supports={everything:!0,everythingExceptFlag:!0},e=new Promise(function(e){i.addEventListener("DOMContentLoaded",e,{once:!0})}),new Promise(function(t){var n=function(){try{var e=JSON.parse(sessionStorage.getItem(o));if("object"==typeof e&&"number"==typeof e.timestamp&&(new Date).valueOf()<e.timestamp+604800&&"object"==typeof e.supportTests)return e.supportTests}catch(e){}return null}();if(!n){if("undefined"!=typeof Worker&&"undefined"!=typeof OffscreenCanvas&&"undefined"!=typeof URL&&URL.createObjectURL&&"undefined"!=typeof Blob)try{var e="postMessage("+f.toString()+"("+[JSON.stringify(s),u.toString(),p.toString()].join(",")+"));",r=new Blob([e],{type:"text/javascript"}),a=new Worker(URL.createObjectURL(r),{name:"wpTestEmojiSupports"});return void(a.onmessage=function(e){c(n=e.data),a.terminate(),t(n)})}catch(e){}c(n=f(s,u,p))}t(n)}).then(function(e){for(var t in e)n.supports[t]=e[t],n.supports.everything=n.supports.everything&&n.supports[t],"flag"!==t&&(n.supports.everythingExceptFlag=n.supports.everythingExceptFlag&&n.supports[t]);n.supports.everythingExceptFlag=n.supports.everythingExceptFlag&&!n.supports.flag,n.DOMReady=!1,n.readyCallback=function(){n.DOMReady=!0}}).then(function(){return e}).then(function(){var e;n.supports.everything||(n.readyCallback(),(e=n.source||{}).concatemoji?t(e.concatemoji):e.wpemoji&&e.twemoji&&(t(e.twemoji),t(e.wpemoji)))}))}((window,document),window._wpemojiSettings); </script> <style id='wp-emoji-styles-inline-css'> img.wp-smiley, img.emoji { display: inline !important; border: none !important; box-shadow: none !important; height: 1em !important; width: 1em !important; margin: 0 0.07em !important; vertical-align: -0.1em !important; background: none !important; padding: 0 !important; } </style> <link rel='stylesheet' id='twentyfourteen-lato-css' href='https://blogs.library.duke.edu/dcthree/wp-content/themes/twentyfourteen/fonts/font-lato.css?ver=20230328' media='all' /> <link rel='stylesheet' id='genericons-css' href='https://blogs.library.duke.edu/dcthree/wp-content/themes/twentyfourteen/genericons/genericons.css?ver=3.0.3' media='all' /> <link rel='stylesheet' id='twentyfourteen-style-css' href='https://blogs.library.duke.edu/dcthree/wp-content/themes/dul-2014/style.css?ver=20241112' media='all' /> <link rel='stylesheet' id='twentyfourteen-block-style-css' href='https://blogs.library.duke.edu/dcthree/wp-content/themes/twentyfourteen/css/blocks.css?ver=20240708' media='all' /> <!--[if lt IE 9]> <link rel='stylesheet' id='twentyfourteen-ie-css' href='https://blogs.library.duke.edu/dcthree/wp-content/themes/twentyfourteen/css/ie.css?ver=20140711' media='all' /> <![endif]--> <style id='akismet-widget-style-inline-css'> .a-stats { --akismet-color-mid-green: #357b49; --akismet-color-white: #fff; --akismet-color-light-grey: #f6f7f7; max-width: 350px; width: auto; } .a-stats * { all: unset; box-sizing: border-box; } .a-stats strong { font-weight: 600; } .a-stats a.a-stats__link, .a-stats a.a-stats__link:visited, .a-stats a.a-stats__link:active { background: var(--akismet-color-mid-green); border: none; box-shadow: none; border-radius: 8px; color: var(--akismet-color-white); cursor: pointer; display: block; font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', 'Roboto', 'Oxygen-Sans', 'Ubuntu', 'Cantarell', 'Helvetica Neue', sans-serif; font-weight: 500; padding: 12px; text-align: center; text-decoration: none; transition: all 0.2s ease; } /* Extra specificity to deal with TwentyTwentyOne focus style */ .widget .a-stats a.a-stats__link:focus { background: var(--akismet-color-mid-green); color: var(--akismet-color-white); text-decoration: none; } .a-stats a.a-stats__link:hover { filter: brightness(110%); box-shadow: 0 4px 12px rgba(0, 0, 0, 0.06), 0 0 2px rgba(0, 0, 0, 0.16); } .a-stats .count { color: var(--akismet-color-white); display: block; font-size: 1.5em; line-height: 1.4; padding: 0 13px; white-space: nowrap; } </style> <script src="https://blogs.library.duke.edu/dcthree/wp-includes/js/jquery/jquery.min.js?ver=3.7.1" id="jquery-core-js"></script> <script src="https://blogs.library.duke.edu/dcthree/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1" id="jquery-migrate-js"></script> <script src="https://blogs.library.duke.edu/dcthree/wp-content/themes/twentyfourteen/js/functions.js?ver=20230526" id="twentyfourteen-script-js" defer data-wp-strategy="defer"></script> <link rel="https://api.w.org/" href="https://blogs.library.duke.edu/dcthree/wp-json/" /><link rel="EditURI" type="application/rsd+xml" title="RSD" href="https://blogs.library.duke.edu/dcthree/xmlrpc.php?rsd" /> <meta name="generator" content="WordPress 6.7.2" /> <link href='//fonts.googleapis.com/css?family=Libre+Baskerville:400,700,400italic' rel='stylesheet' type='text/css'> <!-- Matomo --> <script> var _paq = window._paq = window._paq || []; _paq.push(['trackPageView']); _paq.push(['enableLinkTracking']); (function() { var u="//analytics.lib.duke.edu/"; _paq.push(['setTrackerUrl', u+'matomo.php']); _paq.push(['setSiteId', '28']); var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0]; g.async=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s); })(); </script> <!-- End Matomo Code --> </head> <body class="archive date wp-embed-responsive group-blog header-image list-view full-width"> <div id="page" class="hfeed site"> <div id="site-header"> <a href="https://blogs.library.duke.edu/dcthree/" rel="home"> <img alt="Duke Collaboratory for Classics Computing (DC3)" src="https://blogs.library.duke.edu/dcthree/files/2014/11/dc3.jpg" width="1260" height="200" alt=""> </a> </div> <div id="library_logo"><a href="//library.duke.edu" title="Duke University Libraries"><img src="/wp-content/themes/dul-2014/images/library_logo_transparent.png" alt="Duke University Libraries" border="0"></a></div> <nav id="primary-navigation" class="site-navigation primary-navigation" role="navigation"> <button class="menu-toggle">Primary Menu</button> <a class="screen-reader-text skip-link" href="#content">Skip to content</a> <div class="menu-main-container"><ul id="menu-main" class="nav-menu"><li id="menu-item-235" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-235"><a href="https://blogs.library.duke.edu/dcthree/partners/">Partners</a></li> <li id="menu-item-236" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-236"><a href="https://blogs.library.duke.edu/dcthree/people/">People</a></li> <li id="menu-item-237" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-237"><a href="https://blogs.library.duke.edu/dcthree/projects/">Projects</a></li> </ul></div> </nav> <div id="main" class="site-main"> <section id="primary" class="content-area"> <div id="content" class="site-content" role="main"> <header class="page-header"> <h1 class="page-title"> Monthly Archives: May 2015 </h1> </header><!-- .page-header --> <article id="post-256" class="post-256 post type-post status-publish format-standard hentry category-uncategorized"> <header class="entry-header"> <div class="entry-meta"> <span class="cat-links"><a href="https://blogs.library.duke.edu/dcthree/category/uncategorized/" rel="category tag">Uncategorized</a></span> </div> <h1 class="entry-title"><a href="https://blogs.library.duke.edu/dcthree/2015/05/26/harpokration-on-line/" rel="bookmark">Harpokration On Line</a></h1> <div class="entry-meta"> <span class="entry-date"><a href="https://blogs.library.duke.edu/dcthree/2015/05/26/harpokration-on-line/" rel="bookmark"><time class="entry-date" datetime="2015-05-26T14:44:33-05:00">May 26, 2015</time></a></span> <span class="byline"><span class="author vcard"><a class="url fn n" href="https://blogs.library.duke.edu/dcthree/author/jds15duke-edu/" rel="author">Joshua Sosin</a></span></span> <span class="comments-link"><a href="https://blogs.library.duke.edu/dcthree/2015/05/26/harpokration-on-line/#comments">3 Comments</a></span> </div><!-- .entry-meta --> </header><!-- .entry-header --> <div class="entry-content"> <span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.title=Harpokration+On+Line&amp;rft.aulast=Sosin&amp;rft.aufirst=Joshua&amp;rft.subject=Uncategorized&amp;rft.source=Duke+Collaboratory+for+Classics+Computing+%28DC3%29&amp;rft.date=2015-05-26&amp;rft.type=blogPost&amp;rft.format=text&amp;rft.identifier=https://blogs.library.duke.edu/dcthree/2015/05/26/harpokration-on-line/&amp;rft.language=English"></span> <p>About a year ago the Suda On Line [<a href="http://www.stoa.org/sol">http://www.stoa.org/sol</a>] passed an amazing milestone: all entries translated. This was an exciting moment, and one that resonated here at Duke: SOL was an inspiration for the Papyrological Editor (<a href="http://papyri.info">papyri.info</a>), much of whose internals we call SoSOL, &#8220;<a href="http://wiki.digitalclassicist.org/SoSOL">Son of Suda On Line</a>.&#8221;</p> <p>Around that time I was starting to get interested in Harpokration&#8217;s lexicon, mainly for the light that it shed on Athenian law. But before long I was in deep. As Fall set in, John Paul Aldrup-MacDonald, Mackenzie Zalin, and I decided it would be a fun service to translate Harpokration. We began to meet every couple weeks over lunch, took our time, learned from each other, did not rush. At some point we figured we ought to release a few hundred entries to the web and see whether anyone else wanted to join us, in a spirit similar to that which has driven SOL.</p> <p>I guess we had a little too much fun: by spring we had amassed draft translations of all but a few entries. Our colleague <a href="https://ryanfb.github.io/">Ryan Baumann</a> was kind enough to whip up a lightweight tool to support crowd translation.</p> <p>So, here we are; if you would like to join us,</p> <ol> <li>go to <a href="http://cite-harpokration.appspot.com">http://cite-harpokration.appspot.com</a>, click on the link to &#8216;authorize&#8217;; use your google address<br /> <a href="https://blogs.library.duke.edu/dcthree/files/2015/05/CITE-authorization.png"><img fetchpriority="high" decoding="async" class="alignnone size-medium wp-image-257" src="https://blogs.library.duke.edu/dcthree/files/2015/05/CITE-authorization-300x195.png" alt="CITE-authorization" width="300" height="195" srcset="https://blogs.library.duke.edu/dcthree/files/2015/05/CITE-authorization-300x195.png 300w, https://blogs.library.duke.edu/dcthree/files/2015/05/CITE-authorization.png 974w" sizes="(max-width: 300px) 100vw, 300px" /></a></li> <li>close that window and go to <a href="http://dcthree.github.io/harpokration">http://dcthree.github.io/harpokration</a> (authentication can be a little fussy; so, let us know if you encounter problems: <a href="mailto:dcthree@duke.edu">dcthree@duke.edu</a>)</li> <li>find an entry that you would like to translate (either newly or in order to correct mistakes that we have made)</li> <li>click on &#8220;Add translation for urn.cts:greekLit …&#8221; above the entry<br /> <a href="https://blogs.library.duke.edu/dcthree/files/2015/05/agoranomoiTranslated.png"><img decoding="async" class="alignnone size-medium wp-image-258" src="https://blogs.library.duke.edu/dcthree/files/2015/05/agoranomoiTranslated-300x193.png" alt="agoranomoiTranslated" width="300" height="193" srcset="https://blogs.library.duke.edu/dcthree/files/2015/05/agoranomoiTranslated-300x193.png 300w, https://blogs.library.duke.edu/dcthree/files/2015/05/agoranomoiTranslated.png 705w" sizes="(max-width: 300px) 100vw, 300px" /></a></li> <li>This will open a form in which you may enter a translation and any (plain text) notes that you would like to leave for others.<br /> <a href="https://blogs.library.duke.edu/dcthree/files/2015/05/agoranomoiEditor.png"><img decoding="async" class="alignnone size-medium wp-image-259" src="https://blogs.library.duke.edu/dcthree/files/2015/05/agoranomoiEditor-300x186.png" alt="agoranomoiEditor" width="300" height="186" srcset="https://blogs.library.duke.edu/dcthree/files/2015/05/agoranomoiEditor-300x186.png 300w, https://blogs.library.duke.edu/dcthree/files/2015/05/agoranomoiEditor.png 975w" sizes="(max-width: 300px) 100vw, 300px" /></a></li> <li>Translate, click &#8220;Submit,&#8221; move on.</li> <li>We have been adding pointers to corresponding Suda entries; this is not yet a feature of the translation form. We may add it later. If/when we do, you will enter simply, e.g., &#8220;alpha,302&#8221;.</li> </ol> <p>This is meant to be simple, fast, lightweight; both tool and translations are <b>works in progress</b>. Thus,</p> <ul> <li>There is no peer-review in the formal and narrow sense of gate-keeping and quality control; just low barrier-to-entry, collegial, collaborative, translation. There is no fine-grained version control. We do not curate translations. We have no editorial board. Rather, we concatenate multiple attributed versions. If you notice that we have gotten a word or phrase wrong, you cannot merely change that word or phrase, but if you click on &#8220;Add a new version of translation urn:cite:dc3&#8230;&#8221; the form will open with the &#8220;Translation&#8221; field already populated with the version that you would like to correct. Make your changes, click Submit. The whole will be attributed to you, but anyone will be able to see that you have only changed a few words. It isn&#8217;t fancy, but it is easy and fast.</li> <li>You will see tags in some of the Greek entries (indicating authors, works, citations, references, Pleiades IDs). This markup is not exhaustive and may contain errors;  some day we may do something with it. At the moment, we don&#8217;t.</li> <li>About our translations. These are <b>drafts</b>, a first step toward something better and more complete. You will find errors, perhaps many, perhaps serious. If you see something wrong, please feel free to fix it. We have tried to reflect the grammar and style of the work as literally as possible. This sometimes results in a bit of chop and awkwardness. If in places this seems to come at the expense of clarity, please feel free to fix it. At this stage, we make little claim to nuance. There may be more (or less) to Harpokration&#8217;s use of verb tense (esp. the imperfect), or verbs of citation/attribution (μνημονεύει, λέγει, φησί, διείλεκται, vel sim.) than we have surfaced; or to the value of δέ (sometimes &#8216;and&#8217;, sometimes &#8216;but&#8217;), and so on. If you see clumsiness, please feel free to fix it (or to email us, in case of global problems).</li> <li>The Greek is from Dindorf&#8217;s 1853 edition, generously shared by the <a href="http://stephanus.tlg.uci.edu/index.php">TLG</a>. Where Keaney&#8217;s 1991 edition is clearly superior, such that a translation should follow it, we indicate as much. To digitize Keaney and then weigh its merits against Dindorf was out of scope.</li> </ul> <p>We have now pushed draft translations of the first hundred entries. Please feel free to add, to correct, to improve. If you have a google account, you are good to go. For our part, we plan to push a new batch of drafts each week over the course of the summer&#8211;maybe 20, maybe 50, maybe 100 per week, depending on how things go.</p> <p>If this succeeds, who knows what comes next. A more robust, production-oriented site supporting crowd-translation of ancient lexica, scholia, and scholarship would certainly be a great thing to have and to build and to contribute to.</p> <p>In the meantime, feel free to pitch in.</p> <p>Josh Sosin (<a href="mailto:joshua.sosin@duke.edu">joshua.sosin@duke.edu</a>)<br /> John P. Aldrup-MacDonald (<a href="mailto:john.smith.macdonald@duke.edu">john.smith.macdonald@duke.edu</a>)<br /> Mackenzie Zalin (<a href="mailto:mack.zalin@duke.edu">mack.zalin@duke.edu</a>)</p> </div><!-- .entry-content --> </article><!-- #post-256 --> </div><!-- #content --> </section><!-- #primary --> <div id="secondary"> <h2 class="site-description">a collection of parts flying in loose formation</h2> <div id="primary-sidebar" class="primary-sidebar widget-area" role="complementary"> <aside id="text-2" class="widget widget_text"><h1 class="widget-title">About</h1> <div class="textwidget">The Duke Collaboratory for Classics Computing, the DC3, is a no-nonsense, interdisciplinary, results-oriented research group devoted to the creation and care of standards, services, and tooling for digital classics and beyond. We aim to be flexible, durable, and to leverage the strengths of our many partnerships so as to be a collection of parts flying in loose formation. Like the plane. <p> <p>The DC3 manages papyri.info data and tooling, experiments in the development of new complementary resources, and engages in teaching and outreach at Duke and beyond.</div> </aside><aside id="search-3" class="widget widget_search"><h1 class="widget-title">Search the DC3 Blog</h1><form role="search" method="get" class="search-form" action="https://blogs.library.duke.edu/dcthree/"> <label> <span class="screen-reader-text">Search for:</span> <input type="search" class="search-field" placeholder="Search &hellip;" value="" name="s" /> </label> <input type="submit" class="search-submit" value="Search" /> </form></aside> <aside id="recent-posts-2" class="widget widget_recent_entries"> <h1 class="widget-title">Recent Posts</h1><nav aria-label="Recent Posts"> <ul> <li> <a href="https://blogs.library.duke.edu/dcthree/2018/01/10/digital-servius/">Digital Servius</a> <span class="post-date">January 10, 2018</span> </li> <li> <a href="https://blogs.library.duke.edu/dcthree/2016/08/04/theres-new-whale-town/">There&#8217;s a new whale in town</a> <span class="post-date">August 4, 2016</span> </li> <li> <a href="https://blogs.library.duke.edu/dcthree/2016/02/04/harpokration-done-but-not-even-almost/">Harpokration, done but not even almost.</a> <span class="post-date">February 4, 2016</span> </li> <li> <a href="https://blogs.library.duke.edu/dcthree/2015/05/26/harpokration-on-line/">Harpokration On Line</a> <span class="post-date">May 26, 2015</span> </li> <li> <a href="https://blogs.library.duke.edu/dcthree/2015/04/02/text-of-shifting-frontiers-in-the-digital-humanities/">Text of “Shifting Frontiers in the Digital Humanities”</a> <span class="post-date">April 2, 2015</span> </li> </ul> </nav></aside><aside id="archives-3" class="widget widget_archive"><h1 class="widget-title">Archives</h1><nav aria-label="Archives"> <ul> <li><a href='https://blogs.library.duke.edu/dcthree/2018/01/'>January 2018</a></li> <li><a href='https://blogs.library.duke.edu/dcthree/2016/08/'>August 2016</a></li> <li><a href='https://blogs.library.duke.edu/dcthree/2016/02/'>February 2016</a></li> <li><a href='https://blogs.library.duke.edu/dcthree/2015/05/' aria-current="page">May 2015</a></li> <li><a href='https://blogs.library.duke.edu/dcthree/2015/04/'>April 2015</a></li> <li><a href='https://blogs.library.duke.edu/dcthree/2015/03/'>March 2015</a></li> <li><a href='https://blogs.library.duke.edu/dcthree/2014/09/'>September 2014</a></li> <li><a href='https://blogs.library.duke.edu/dcthree/2014/08/'>August 2014</a></li> <li><a href='https://blogs.library.duke.edu/dcthree/2014/02/'>February 2014</a></li> <li><a href='https://blogs.library.duke.edu/dcthree/2013/12/'>December 2013</a></li> <li><a href='https://blogs.library.duke.edu/dcthree/2013/11/'>November 2013</a></li> <li><a href='https://blogs.library.duke.edu/dcthree/2013/08/'>August 2013</a></li> <li><a href='https://blogs.library.duke.edu/dcthree/2013/07/'>July 2013</a></li> <li><a href='https://blogs.library.duke.edu/dcthree/2013/06/'>June 2013</a></li> </ul> </nav></aside> </div><!-- #primary-sidebar --> </div><!-- #secondary --> </div><!-- #main --> <footer id="colophon" class="site-footer" role="contentinfo"> <div class="site-info"> <a href="https://blogs.library.duke.edu/dcthree/" rel="home">Duke Collaboratory for Classics Computing (DC3)</a> </div><!-- .site-info --> </footer><!-- #colophon --> </div><!-- #page --> </body> </html>

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