This repository contains data produced by and used to run the Papyri.info website. For the code which runs Papyri.info, see the papyri/navigator repository and the sosol/sosol repository (used for the Papyrological Editor). For some more project background, see the Papyri.info about page, the DDbDP background page, or The Son of Suda On-Line (2013). Papyri.info is maintained by the Duke Collaboratory for Classics Computing (DC3).
As Integrating Digital Papyrology implies, this repository brings together several different data sources from a variety of projects, which is reflected at the top level of the file hierarchy:
APD- Texts from the Arabic Papyrology Database in EpiDoc XMLAPIS- Metadata for the Advanced Papyrological Information System (APIS) in EpiDoc XMLBiblio- Bibliographic data for the Bibliographie Papyrologique (BP)DCLP- Texts from the Digital Corpus of Literary Papyri in EpiDoc XMLDDB_EpiDoc_XML- Texts from the Duke Data Bank of Documentary Papyri (DDbDP) in EpiDoc XMLHGV_meta_EpiDoc- Metadata from the Heidelberger Gesamtverzeichnis der Griechischen Papyrusurkunden Ägyptens (HGV) in EpiDoc XMLHGV_metadata- Upstream HGV FileMaker dataHGV_trans_EpiDoc- Translations from the HGV in EpiDoc XMLRDF- Collection metadata from Papyri.info in RDF XMLValidation- Dependencies for XML validation (see.github/workflows/xml-validation.yml)
Automated XML validation for this repository is available as a GitHub Action.
As the Papyrological Editor on Papyri.info uses Git for its data backend, data in this repository is updated frequently via that user interface. The Papyrological Editor uses its own Git repository which is synchronized bidirectionally on an hourly basis with this public-facing repository.
As a result of this, it is suggested that you use the Papyrological Editor for changes which are primarily to text, metadata, or translations at the level of individual documents. The reason for this is that the Papyrological Editor already incorporates workflows for editorial review by the editorial boards which oversee each individual project component.
For advanced users familiar with Git and XML wishing to make batch changes which affect a large number of files, it may be preferable to use a Pull Request instead. We will review these on a case-by-case basis. You can also contact us at dcthree@duke.edu in order to coordinate this sort of work if you are unsure if we are likely to be able to incorporate your changes or submissions.
We also use this repository's GitHub Issues to keep track of ongoing issues with the data. Feel free to give us feedback about this repository there as well.
This data is made available under a Creative Commons Attribution 3.0 License, with copyright and attribution to the respective projects.