This is now a collection point for the Papyrological Publishing Platform (P3). To be found here are the files which are used to produce articles in the journal Pylon.
You asked me to track some of the things I encountered while Xwalking from Pylon 1. Those notes follow below.
In general, my practice with new publications is to create a single file with well-formed XML, and then to Save As, updating the various fields as required for each individual text. For collections of editions like O.Berenike 4, Save As expedites the Xwalk process considerably, since many fields are the same (or at least similar) in each case. Re-editions, by necessity, require that the fields be updated as needed: for DDB files, re-editions are best entered via PE (so that the dummy headers which redirect to/from the previous edition are generated automatically); for HGV, it can be done via GitHub or a traditional editor.
HGV
Check every <idno> as well as the xml:id in <TEI> at document head; the latter includes the TM number.
Hugh’s converter handles <msIdentifier> differently than HGV, employing <repository> with child <idno type="invNo"> instead of <placeName> w/ child <settlement> and both <collection> and <idno type="invNo">. Fixing that would be nice.
Generate a machine-readable date using the tool in SoSOL
Make sure TM Geo and Pleiades links are included within <placeName>
Add SB reference under <listBibl>. At present, we are not entering page numbers, since Pylon does not have them (nor do Pylon editions have a dedicated paragraph number, either)
Add <revisionDesc> with date and user. Comment: Xwalk (or Update) from Pylon.
Add DOI under <div type="figure">
a. I would prefer that figure pointed to the image itself; but in that case, where is the best place for the DOI?
Update <div type="bibliography" subtype="principalEdition"> as needed
a. NB: for re-editions, the old publication info needs to be moved to <div type="bibliography" subtype="otherPublications">
At present, we are not specifying Pylon as the location of a print illustration under <div type="bibliography" subtype="illustrations">. I wonder whether that is wise.
DDB
Check <title>, every <idno>, and <sourceDesc>
Add <revisionDesc> with date and user. Comment: Xwalk (or Update) from Pylon.
For non-Greek texts, update @xml:lang in <div>
After copy/pasting text, remove @xml:id from <lb> and <div>
After copy/pasting text, remove every instance of <note> and its content, required by the UB xslt.
Translation
ddb-hybrid from Hugh’s converter is often the TM number again, instead of a proper hybrid idno
Any instances of @corresp within <milestone> need to be deleted
<sourceDesc> should read The contents of this file were Xwalked from Pylon.
Add <revisionDesc> with date and user. Comment: Xwalk from Pylon x.
You asked me to track some of the things I encountered while Xwalking from Pylon 1. Those notes follow below.
In general, my practice with new publications is to create a single file with well-formed XML, and then to
Save As
, updating the various fields as required for each individual text. For collections of editions likeO.Berenike 4
,Save As
expedites the Xwalk process considerably, since many fields are the same (or at least similar) in each case. Re-editions, by necessity, require that the fields be updated as needed: for DDB files, re-editions are best entered via PE (so that the dummy headers which redirect to/from the previous edition are generated automatically); for HGV, it can be done via GitHub or a traditional editor.HGV
<idno>
as well as thexml:id
in<TEI>
at document head; the latter includes the TM number.<msIdentifier>
differently than HGV, employing<repository>
with child<idno type="invNo">
instead of<placeName>
w/ child<settlement>
and both<collection>
and<idno type="invNo">
. Fixing that would be nice.<placeName>
<listBibl>
. At present, we are not entering page numbers, since Pylon does not have them (nor do Pylon editions have a dedicated paragraph number, either)<revisionDesc>
with date and user. Comment: Xwalk (or Update) from Pylon.<div type="figure">
a. I would prefer that figure pointed to the image itself; but in that case, where is the best place for the DOI?<div type="bibliography" subtype="principalEdition">
as needed a. NB: for re-editions, the old publication info needs to be moved to<div type="bibliography" subtype="otherPublications">
<div type="bibliography" subtype="illustrations">
. I wonder whether that is wise.DDB
<title>
, every<idno>
, and<sourceDesc>
<revisionDesc>
with date and user. Comment: Xwalk (or Update) from Pylon.@xml:lang
in<div>
@xml:id
from<lb>
and<div>
<note>
and its content, required by the UB xslt.Translation
ddb-hybrid
from Hugh’s converter is often the TM number again, instead of a proper hybrid idno@corresp
within<milestone>
need to be deleted<sourceDesc>
should read The contents of this file were Xwalked from Pylon.<revisionDesc>
with date and user. Comment: Xwalk from Pylon x.xml:id="trans1"
from<div>
xml:lang
in<div>
is updated as needed