Papyri.info

<!DOCTYPE html> <html lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> <title>Papyri.info</title> <link rel="stylesheet" href="/css/yui/reset-fonts-grids.css" type="text/css" media="screen" title="no title" charset="utf-8"> <link rel="stylesheet" href="/css/master.css" type="text/css" media="screen" title="no title" charset="utf-8"> <link rel="stylesheet" href="/css/custom-theme/jquery-ui-1.14.1.min.css" type="text/css" media="screen" title="no title" charset="utf-8"> <link rel="stylesheet" href="/css/custom-theme/jquery-ui-dul-theme-shim.css" type="text/css" media="screen" title="no title" charset="utf-8"> <script src="/js/jquery-3.7.1.min.js" type="text/javascript" charset="utf-8"></script> <script src="/js/jquery-ui-1.14.1.min.js" type="text/javascript" charset="utf-8"></script> <script src="/js/init.js" type="text/javascript" charset="utf-8"></script> <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', '34']); 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> </head> <body onload="init()"> <div id="d"> <div id="hd"> <h1>Papyri.info</h1> <h2 id="login"><a href="/editor/user/signin">sign in</a></h2> </div> <div id="bd"> <div class="nav">  <form method="get" accept-charset="utf-8"> <ul class="nav"> <li>Browse: </li> <li> <a href="/browse/ddbdp/">DDbDP</a> </li> <li> <a href="/browse/hgv/">HGV</a> </li> <li> <a href="/browse/apis/">APIS</a> </li> <li> <a href="/browse/dclp/">DCLP</a> </li> <li> <a href="/authors">Authors</a> </li> <li class="dialog" id="tm" title="TM Number" ><div id="tmc">TM#: <input type="text" name="tmid" id="tmid" onclick="this.setAttribute('value','');this.focus();" size="10"/> <input onclick="window.location='/trismegistos/'+jQuery('#tmid').prop('value');" type="button" name="tmgo" id="tmgo" value=" > " /></div> </li> <li>or Search:</li> <li> <a href="/search">Data</a> </li> <li> <a href="/bibliosearch">Bibliography</a> </li> </ul> </form> </div> <div id="main"> <div class="content"> <div class="markdown"> <p><strong>About papyri.info</strong></p> <p><strong>Prototype</strong>: Under leadership of Roger Bagnall and with funding from the <a href="http://www.mellon.org/">Andrew W. Mellon Foundation</a> and the <a href="http://www.neh.gov/">National Endowment for the Humanities</a>, in 2006/07, <a href="http://library.columbia.edu/">Columbia University Libraries</a> developed specifications for a 'Papyrological Navigator,' (PN) in order to demonstrate that multiple digital papyrological resources could be co-displayed in a scholarly web resource. In the following year a prototype PN was released. In 2007/08, with further support from the Mellon Foundation, a Duke-led team launched 'Integrating Digital Papyrology', whose three phases ran through 2012. The goals were to migrate the DDbDP from SGML to <a href="http://www.tei-c.org/index.xml">TEI</a> <a href="http://sourceforge.net/p/epidoc/wiki/Home/">EpiDoc</a> XML, and from betacode to Unicode; to map DDbDP texts and HGV metadata to corresponding APIS images and catalog records, and to convert both HGV and APIS data to EpiDoc; to enhance the Papyrological Navigator; to create a version controlled, transparent and auditable, multi-author, web-based, real-time, tag-lite, editing environment, which--in tandem with a new editorial infrastructure--would allow the entire community of papyrologists to take editorial control of core disciplinary data. In 2009 the new PN and Papyrological Editor (PE) were moved to <a href="http://isaw.nyu.edu/">NYU's Institute for the Study of the Ancient World</a>, which was the seat of production until July 2013.</p> <p><strong>Release</strong>: In 2010 the new <a href="http://papyri.info">papyri.info</a> was released to production (see <a href="http://www.stoa.org/archives/1263">J. Sosin's presentation</a> to the 26th Intl Papyrological Congress), featuring the new PE and a completely redesigned PN.</p> <p><strong>Stewardship</strong>: In July 2013 the <a href="http://library.duke.edu/">Duke University Libraries</a>, again with the generous support of the Mellon Foundation, launched the <a href="http://blogs.library.duke.edu/dcthree/">Duke Collaboratory for Classics Computing</a> (DC3), a digital classics unit embedded in the Libraries. A core part of their mission is the maintenance and enhancement of the <a href="http://papyri.info">papyri.info</a> toolset and community.</p> <p><strong>Moving Parts</strong>: See the <a href="https://github.com/papyri/documentation/blob/master/system_level/TopLevelDataFlow.md">top level data flow</a>. The PN supports browse and faceted search of the constellation of papyri.info resources. It relies on an RDF triple store (<a href="http://jena.apache.org/">Apache Jena</a>) to manage the relationships between documents from different sources and <a href="http://lucene.apache.org/solr/">Apache Solr</a> for its search and faceting capabilities. The PE (1) allows users to add new or change existing 'publications' in the PN, edit the EpiDoc, either via database-style form (for APIS, HGV, BP) or proxy EpiDoc syntax called Leiden+ (for DDbDP), (2) enables submission of all such edits to peer review, which may result in commission of such to the canonical repository, and (3) provides transparent version-control (via git) of all such edits, system-wide. This bundle of services is referred to as Son of Suda on Line (SoSOL), in homage to the <a href="http://www.stoa.org/sol">Suda On Line</a> project and our colleague <a href="http://en.wikipedia.org/wiki/Ross_Scaife">Ross Scaife</a>.</p> </div> </div> </div> </div> <div id="footer"> <div id="footer-left-col"> <div id="secondary-nav"> <ul class="nav"> <li><a href="/" title="Project Home">Home</a></li> <li><a href="/docs/help" title="Site help">Help</a></li>     <li><a href="http://digitalpapyrology.blogspot.com/" title="Digital Papyrology">Blog</a></li> <li><a href="/docs/resources" title="Papyrological tools and resources">Resources</a></li> <li><a href="/feedback.html" title="Feeback">Feedback</a></li> <li><a href="http://epidoc.sourceforge.net/" title="EpiDoc Home">About EpiDoc</a></li> </ul> </div> <div class="spacer"></div> </div> <div id="footer-right-col"> <p>Produced by</p> <p><a href="http://blogs.library.duke.edu/dcthree/">The Duke Collaboratory for Classics Computing</a> <br/>& the <a href="http://www.nyu.edu/isaw/">Institute for the Study of the Ancient World</a></p> <div id="about-nav"> <ul class="nav"> <li><a href="http://www.ulb.ac.be/philo/cpeg/bp.htm" title="Bibliographie Papyrologique Home">BP</a></li> <li><a href="http://www.trismegistos.org/" title="Trismegistos Home">Trismegistos</a></li> <li><a href="http://www.rzuser.uni-heidelberg.de/%7Egv0/" title="Heidelberger Gesamtverzeichnis der Griechischen Papyrusurkunden 脛gyptens - Home ">HGV</a></li> <li><a href="/docs/ddbdp" title="Duke Databank of Documentary Papyri - Home">DDbDP</a></li> <li><a href="/docs/apis">APIS</a></li> <li class="last-child"><a href="/docs/about" title="Papyri.info">Papyri.info</a></li> </ul> <h3 id="about-hdr">About:</h3> </div> </div> <div class="spacer"></div> </div> </div> <script type="text/javascript" charset="utf-8"> const buttonOptions = { classes: { "ui-button": "ui-corner-all ui-state-default" } }; $("#searchbutton").button(buttonOptions); $("#editorbutton").button(buttonOptions); </script> </body> </html>

CINXE.COM

Papyri.info