diff --git a/about.md b/about.md index f4d92ad..d85f38a 100644 --- a/about.md +++ b/about.md @@ -1,9 +1,17 @@ -**About papyri.info** +# About papyri.info -**Prototype**: Under leadership of Roger Bagnall and with funding from the [Andrew W. Mellon Foundation](http://www.mellon.org/) and the [National Endowment for the Humanities](http://www.neh.gov/), in 2006/07, [Columbia University Libraries](http://library.columbia.edu/) 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 [TEI](http://www.tei-c.org/index.xml) [EpiDoc](http://sourceforge.net/p/epidoc/wiki/Home/) 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 [NYU's Institute for the Study of the Ancient World](http://isaw.nyu.edu/), which was the seat of production until July 2013. +## Prototype -**Release**: In 2010 the new [papyri.info](http://papyri.info) was released to production (see [J. Sosin's presentation](http://www.stoa.org/archives/1263) to the 26th Intl Papyrological Congress), featuring the new PE and a completely redesigned PN. +Under leadership of Roger Bagnall and with funding from the [Andrew W. Mellon Foundation](http://www.mellon.org/) and the [National Endowment for the Humanities](http://www.neh.gov/), in 2006/07, [Columbia University Libraries](http://library.columbia.edu/) 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 [TEI](http://www.tei-c.org/index.xml) [EpiDoc](http://sourceforge.net/p/epidoc/wiki/Home/) 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 [NYU's Institute for the Study of the Ancient World](http://isaw.nyu.edu/), which was the seat of production until July 2013. -**Stewardship**: In July 2013 the [Duke University Libraries](http://library.duke.edu/), again with the generous support of the Mellon Foundation, launched the [Duke Collaboratory for Classics Computing](http://blogs.library.duke.edu/dcthree/) (DC3), a digital classics unit embedded in the Libraries. A core part of their mission is the maintenance and enhancement of the [papyri.info](http://papyri.info) toolset and community. +## Release -**Moving Parts**: See the [top level data flow](https://github.com/papyri/documentation/blob/master/system_level/TopLevelDataFlow.md). The PN supports browse and faceted search of the constellation of papyri.info resources. It relies on an RDF triple store ([Apache Jena](http://jena.apache.org/)) to manage the relationships between documents from different sources and [Apache Solr](http://lucene.apache.org/solr/) 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 [Suda On Line](http://www.stoa.org/sol) project and our colleague [Ross Scaife](http://en.wikipedia.org/wiki/Ross_Scaife). +In 2010 the new [papyri.info](http://papyri.info) was released to production (see [J. Sosin's presentation](http://www.stoa.org/archives/1263) to the 26th Intl Papyrological Congress), featuring the new PE and a completely redesigned PN. + +## Stewardship + +In July 2013 the [Duke University Libraries](http://library.duke.edu/), again with the generous support of the Mellon Foundation, launched the [Duke Collaboratory for Classics Computing](http://blogs.library.duke.edu/dcthree/) (DC3), a digital classics unit embedded in the Libraries. A core part of their mission is the maintenance and enhancement of the [papyri.info](http://papyri.info) toolset and community. + +## Moving Parts + +See the [top level data flow](https://github.com/papyri/documentation/blob/master/system_level/TopLevelDataFlow.md). The PN supports browse and faceted search of the constellation of papyri.info resources. It relies on an RDF triple store ([Apache Jena](http://jena.apache.org/)) to manage the relationships between documents from different sources and [Apache Solr](http://lucene.apache.org/solr/) 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 [Suda On Line](http://www.stoa.org/sol) project and our colleague [Ross Scaife](http://en.wikipedia.org/wiki/Ross_Scaife). diff --git a/apis.md b/apis.md index 10333e4..a8f8c79 100644 --- a/apis.md +++ b/apis.md @@ -1,6 +1,8 @@ +# About APIS + **The Advanced Papyrological Information System** (APIS) was planned, starting in 1995, by Roger Bagnall, [†Traianos Gagos](https://record.umich.edu/articles/a1143-obituaries/), and [†John Oates](http://today.duke.edu/2006/06/oatesobit.html), representing Columbia University, the University of Michigan, and Duke University. Berkeley, Princeton, and Yale joined the effort soon after. The project was launched in 1996/7 with support from the National Endowment for the Humanities (NEH) and the six original institutions. The goal was to create a collections-based repository of information about and images of papyrological materials (e.g., papyri, ostraca, wooden tablets, etc.) located in collections around the world; it was envisaged as a first stage in creating a comprehensive papyrological working environment online. A total of six NEH grants, along with institutional support, foundation grants, and private donations, sustained the development of APIS through 2013. At present it includes twelve full member institutions along with another fifteen collections that have contributed data, including some archaeological field projects. Its founding vision was more completely realized when it was systematically linked to the other resources in the Papyrological Navigator through the Integrating Digital Papyrology project, in several phases, supported by the Andrew W. Mellon Foundation and directed by Joshua Sosin. APIS contains physical descriptions, provenance, dating, and bibliographic information about these papyri and other written materials, as well as digital images and English translations of many of these texts. For many there is also information about the acquisition history of the objects. APIS includes both published and unpublished material in all languages. Generally, much more detailed information is available about the published texts. Unpublished papyri have often not yet been fully transcribed, and the information available is sometimes very basic. If you need more information about a papyrus, you should contact the appropriate person at the owning institution. Active development and hosting of the APIS technical infrastructure was carried out at a number of APIS partner institutions over the period 1996-2013, principally Columbia University, the University of Michigan and New York University. As of 1 July 2013, the host and steward of canonical APIS data is papyri.info, which is served by the DC3 and Duke University Libraries. -The collections module, with a metadata record editor, of papyri.info is now open to all institutions, whether or not they are APIS members. Collections of any size may contribute catalog records, images, texts, translations, and metadata to papyri.info directly, once they establish an authorized editorial structure. Interested collections should contact dcthree AT duke DOT edu. +The collections module, with a metadata record editor, of papyri.info is now open to all institutions, whether or not they are APIS members. Collections of any size may contribute catalog records, images, texts, translations, and metadata to papyri.info directly, once they establish an authorized editorial structure. Interested collections should contact dcthree AT duke DOT edu. \ No newline at end of file diff --git a/checklist.md b/checklist.md index 9111381..4de19f3 100644 --- a/checklist.md +++ b/checklist.md @@ -1,5 +1,7 @@ # Checklist of Editions of Greek, Latin, Demotic, and Coptic Papyri, Ostraca, and Tablets -##### Founding Editors: John F. Oates and William H. Willis +
Founding Editors: John F. Oates and William H. Willis
+ +--- This new instance of the Checklist is a work in progress. Most of the data already supersede those of the [previous site](http://library.duke.edu/rubenstein/scriptorium/papyrus/texts/clist.html). Previous print and online editions were curated by a board of Editors, founded by the late Professors John F. Oates and William H. Willis. This latest carries forward the spirit of openness and collaboration that they championed. Abbreviations are arrived at after discussion by a variety of stakeholders, including Joshua D. Sosin (Duke), Rodney Ast (Heidelberg), Roger S. Bagnall (NYU), James M.S. Cowey (Heidelberg), Mark Depauw (Leuven), Alain Delattre (Brussels), Robert L. Maxwell (BYU), Paul Heilporn (Strasbourg), volume editors, and others, sometimes including the wider papyrological community (via [papylist](http://lists.hum.ku.dk/cgi-bin/mailman/listinfo/papy)). The quickest way to initiate discussion of updates and abbreviations is to write the papylist, or any one of the individuals named above. Editors are strongly urged to let us know when new volumes are published. Links to digitized volumes available online have been made by Ryan Baumann (Duke), with the help of [a list](https://www.college-de-france.fr/media/culture-ecrite-antiquite-papyrologie-byzantine/UPL1136838564638901641_Checklist_avec_url_des_pdf__9XII17_.pdf) made by Loreleï Vanderheyden and Jean-Luc Fournet. @@ -33,7 +35,7 @@ This new instance of the Checklist is a work in progress. Most of the data alrea * VIII, Spätptolemäische Papyri aus amtlichen Büros des Herakleopolites, ed. W. Schubart and D. Schäfer. 1933. Nos. 1730—1890. [MF 1.8; rp. CG]〚eight drachmas, = 8 drachmas,〛〚eight drachmas, = 8 drachmas,〛<del>eight drachmas, = 8 drachmas,</del>To indicate translation of text, which was deleted in the original, use double square brackets: 〚...〛.
div - SimpleRecto<T=.en<D=.r <=text=>=D>=T><div xml:lang="en" type="translation" xml:space="preserve"><div n="r" type="textpart"><p>text</p></div></div>
+Take care to enter your translation in the correct div. When entering a translation of an existing Greek text, SoSOL creates the divs for users. So if there is both a recto and a verso (or similar divisions such as columns), the translation windows already provides the appropriate subdivisions of the text.
[...][...]<gap reason='lost' extent='unknown' unit='character'/>Lacuna on papyrus. Use of square brackets to indicate partially missing words (e.g. part[ially]) is strongly discouraged.
......<gap reason='illegible' extent='unknown' unit='character'/>Three dots indicate a break in the translation. Reasons include: untranslatable words or parts of words, presence of mere vestiges, or considerable repetition in the text such that it is not worth full translation.
+Raised line number((11))<milestone unit='line' n='11'/>To indicate the line of the original documentary text. Indication of every line number is strongly discouraged. Instead, mark every 4th or 5th line (if any), starting with ((1)). Let ease of reading be your guide.
rend='break'Raised line number, starting on new line(((33)))<milestone unit='line' n='33' rend='break'/>To indicate the line number of a new 'paragraph' or 'section' of the translation. For example, in a list of contract summaries you might start each new section with a new line: ((1)) ... (((5))) ... (((9))), etc.
In italics in parentheses/*Top right sideways*/<note>Top right sideways</note>To indicate an authorial note in a translation. Use sparingly.
+Contents of tag with mouseover definition<unwatered land=abrochos><term target='abrochos'>unwatered land</term>To insert a link to the (in progress) glossary. Suppose you are translating the Greek word ἄβροχος and want to link to the glossary entry. From the translation window mouse over 'Helpers', select 'Terms'; find the desired term in the glossary, click on the red transcription of the Greek word. This will insert into your translation window a sample-filled tag: <place word="" here="abrochos">.
Then, depending on what you want to appear in your translation, enter as follows:
+ <unwatered land=abrochos>
+
Whatever you enter on the left will appear in the translation; in any case when you mouse over that word in the PN, it will display a pop-up with the definition of abrochos.
langContents of tag with mouseover definition<vir egregius~la=hokratistos><term target='hokratistos' xml:lang='la'>vir egregius</term>To indicate (1) Latin equivalent or (2) translitteration (rather than translation proper)
+
+ (1) <vir egregius~la=hokratistos>
+ (2) <epistrategos-grc-Latn=epistrategos>
+