Remediate Critical Paratexts
¶ Prior Reading
Deprecate this File
¶ Rationale
Critical paratexts come to us via one of two paths:
The following instructions are primarily written for remediators who are working
on critical paratexts that have come to us via the first path, but will also be helpful
to remediators dealing with new submissions.
Already-published DRE, ISE, and QME critical paratexts were prepared in (or moved
to) the ISEʼs XWiki platform. Joey Takeda converted them to TEI as a batch in 2018 and saved them to
the LEMDO repository. We work on the remediations as time permits and as demand dictates.
You can view these paratexts on the old staticized DRE, ISE, and QME sites, for as
long as those sites continue to work.
Editors who are in the active phase of preparing their edition will sometimes send
us .docx or .pdf files containing their critical paratexts. In these cases, we are
either discharging legacy obligations incurred by the ISE or being paid by the editor
and/or anthology to encode their texts for them.
¶ Suggested Workflow
You can take the following remediation steps immediately, even if none of the other
files in the edition have been remediated:
Give Credit in the Metadata
Update Document Status: In Progress
Replace Quotation Marks
Replace Straight Apostrophes
Tidy
<div>
xml:idsAdd
<p>
xml:idsTag Italics
Add Ellipsis Characters
After the other files in the edition have been remediated, you can proceed to the
following steps:
Link to Modern Text
Link to Bibliography
Update Document Status: Proofing
¶ Practice: Give Credit in the Metadata
Add a
<respStmt>
element for the LEMDO team in the TEI Header (
<teiHeader>
) of the document. See also Encode Responsibility Statements.Record your particular contributions to the remediation of the edition by adding
<change>
elements under the
<revisionDesc>
. Some RAs who have done additional work on an edition have a respStmt for Remediating Editor.The LEMDO Director and/or anthology lead will let you know if your contributions to the edition have moved into the remit of
Remediating Editor.
Note: LEMDO Director Janelle Jenstad is responsible for liaising with the editor and/or
anthology lead to ensure that the rest of the metadata in the
<teiHeader>
is correct. However, if you notice anything that is obviously missing or problematic,
leave an XML comment.¶ Practice: Update Document Status: In Progress
Each time you begin remediating a new document, you must change its status to reflect
this. To change the status of a critical paratext you are remediating, do the following:
Change the value of
@status
on
<revisionDesc>
to "IML-TEI_INP"
.Add a new
<change>
element as a child of
<revisionDesc>
.Write the substantive change in the text node (i.e. “Began remediating document”).
Add a
@who
, a
@when
, and a
@status
attribute to the
<change>
element.Add the prefix pers: followed by your xml:id to the
@who
attribute.Add the date you began the remediation to the
@when
attribute.For example:
<revisionDesc status="IML-TEI_INP">
<change when="2022-05-18" who="pers:XMLID">began remediating document.</change>
</revisionDesc>
<change when="2022-05-18" who="pers:XMLID">began remediating document.</change>
</revisionDesc>
¶ Replace Quotation Marks with Appropriate Tags
Remove quotation marks and replace them with appropriate tags:
<quote>
,
<soCalled>
,
<mentioned>
, or
<q>
. For practice, see Introduction to Quotations, Terms, Expressions, Glosses, Emphasis, and Foreign Languages.
¶ Practice: Replace Straight Apostrophes with Curly Apostrophes
Convert straight apostrophes to curly apostrophes. The quickest way to do this is
through a find-and-replace:
Insert one curly apostrophe. For options on how to do this, see
Practice: Insert a Right Curly Apostrophe.
Copy that curly apostrophe.
Open Oxygenʼs Find/Replace box by typing
Ctrl+F
.Type a straight apostrophe into the
Findspace.
Paste a curly apostrophe into the
Replace withspace.
Click
Find Allto see all instances of straight apostrophes in your file.
Click
Replace Allto replace all instances of straight apostrophes with curly apostrophes.
If you are remediating a new submission, it may be quicker to do a find-and-replace
for straight apostrophe in the .docx file before you copy it into your XML file.
¶ Tidy and Add xml:ids
Tidy the xml:ids of the
<div>
elements. For practice, see Create IDs for Document Divisions.
Give the paragraphs xml:ids following the example of the first numbered paragraph.
For practice, see
Deprecate this File.
¶ Practice: Tag Italics
Anything that the author had italicized has been wrapped in a
<hi>
element with a
@rendition
attribute and the value "rnd:italic"
. Use contextual clues to figure out why the original text was italicized and tag
it appropriately. Add
<title>
elements with the
@level
value of "m"
(if the italics mark a title) or appropriate tagging if the italics mean something
else (like a foreign word). See Encode Titlesand
Encode Foreign Languages.
¶ Practice: Add Ellipsis Characters
Convert three spaced dots to the ellipsis character (if they are in the source) or
<gap reason="sampling">
if the editor is omitting material to keep things short. See Practice: Insert an Ellipsis Character.
¶ Practice: Link to Modern Text
Once the modern text has been remediated, you can turn the editorʼs TLN references
into pointers that point to anchors in the modern text.
To point to entire acts, scenes, or speeches, see
Special Case: Linking to Canonical References.
To point to specific words or passages of text, you will need to:
Add anchors around the passages in the modern text. If the modern text already has
anchors in the right place (added when the annotations and/or collations were pinned
to the modern text), use the pre-existing anchors. See Place Anchors in the Source Document.
Create pointers in the critical paratext and point them to the anchors you just made.
See How to Encode Pointer Links.
See also
Create Anchors.
¶ Practice: Link to Bibliography
Once the edition bibliography has been added to
BIBL1
and the edition bibliography has been created (see Remediate Bibliographies if the task falls to you), you can tag the editorʼs parenthetical citations so that
they become pop-up references when the edition is rendered. See Bibliography Entries.
If the editor cites productions that have been added to
PROD1
, follow the procedure for linking to PROD1.xml entries. See Production Entries.Note that these productions will also need to be added to the edition bibligraphy if they have not already been added.
¶ Practice: Update Document Status: Proofing
When you have completed your work, change the document status. Follow these steps:
Change the value of
@status
on
<revisionDesc>
to "IML-TEI_proofing"
.Add a new
<change>
element as a child of
<revisionDesc>
.Write the substantive change in the text node (i.e.
Finished remediating document).
Add a
@who
, a
@when
, and a
@status
attribute to the
<change>
element.Add the prefix pers: followed by your xml:id to the
@who
attribute.Add the date you finished the remediation to the
@when
attribute.Prosopography
Janelle Jenstad
Janelle Jenstad is a Professor of English at the University of
Victoria, Director of The Map
of Early Modern London, and Director of Linked Early Modern Drama
Online. With Jennifer Roberts-Smith and Mark Kaethler, she
co-edited Shakespeare’s Language in Digital Media: Old
Words, New Tools (Routledge). She has edited John Stow’s
A Survey of London (1598 text) for MoEML
and is currently editing The Merchant of Venice
(with Stephen Wittek) and Heywood’s 2 If You Know Not
Me You Know Nobody for DRE. Her articles have appeared in
Digital Humanities Quarterly, Elizabethan Theatre, Early Modern
Literary Studies, Shakespeare
Bulletin, Renaissance and
Reformation, and The Journal of Medieval
and Early Modern Studies. She contributed chapters to Approaches to Teaching Othello (MLA); Teaching Early Modern Literature from the Archives
(MLA); Institutional Culture in Early Modern
England (Brill); Shakespeare, Language, and
the Stage (Arden); Performing Maternity in
Early Modern England (Ashgate); New
Directions in the Geohumanities (Routledge); Early Modern Studies and the Digital Turn (Iter);
Placing Names: Enriching and Integrating
Gazetteers (Indiana); Making Things and
Drawing Boundaries (Minnesota); Rethinking
Shakespeare Source Study: Audiences, Authors, and Digital
Technologies (Routledge); and Civic
Performance: Pageantry and Entertainments in Early Modern
London (Routledge). For more details, see janellejenstad.com.
Joey Takeda
Joey Takeda is LEMDO’s Consulting Programmer and Designer, a role he
assumed in 2020 after three years as the Lead Developer on
LEMDO.
Martin Holmes
Martin Holmes has worked as a developer in the
UVicʼs Humanities Computing and Media Centre for
over two decades, and has been involved with dozens
of Digital Humanities projects. He has served on
the TEI Technical Council and as Managing Editor of
the Journal of the TEI. He took over from Joey Takeda as
lead developer on LEMDO in 2020. He is a collaborator on
the SSHRC Partnership Grant led by Janelle Jenstad.
Navarra Houldin
Project manager 2022–present. Textual remediator 2021–present. Navarra Houldin (they/them)
completed their BA in History and Spanish at the University of Victoria in 2022. During
their degree, they worked as a teaching assistant with the University of Victoriaʼs
Department of Hispanic and Italian Studies. Their primary research was on gender and
sexuality in early modern Europe and Latin America.
Rylyn Christensen
Rylyn Christensen is an English major at the University of Victoria.
Tracey El Hajj
Junior Programmer 2019–2020. Research Associate 2020–2021. Tracey received her PhD
from the Department of English at the University of Victoria in the field of Science
and Technology Studies. Her research focuses on the algorhythmics of networked communications. She was a 2019–2020 President’s Fellow in Research-Enriched
Teaching at UVic, where she taught an advanced course on
Artificial Intelligence and Everyday Life.Tracey was also a member of the Map of Early Modern London team, between 2018 and 2021. Between 2020 and 2021, she was a fellow in residence at the Praxis Studio for Comparative Media Studies, where she investigated the relationships between artificial intelligence, creativity, health, and justice. As of July 2021, Tracey has moved into the alt-ac world for a term position, while also teaching in the English Department at the University of Victoria.
Orgography
LEMDO Team (LEMD1)
The LEMDO Team is based at the University of Victoria and normally comprises the project
director, the lead developer, project manager, junior developers(s), remediators,
encoders, and remediating editors.
Metadata
Authority title | Remediate Critical Paratexts |
Type of text | Documentation |
Short title | |
Publisher | University of Victoria on the Linked Early Modern Drama Online Platform |
Series | Linked Early Modern Drama Online |
Source |
TEI Customization created by Martin Holmes, Joey Takeda, and Janelle Jenstad; documentation written by members of the LEMDO Team
|
Editorial declaration | n/a |
Edition | Released with Linked Early Modern Drama Online 1.0 |
Encoding description | Encoded in TEI P5 according to the LEMDO Customization and Encoding Guidelines |
Document status | prgGenerated |
Funder(s) | Social Sciences and Humanities Research Council of Canada |
License/availability | This file is licensed under a CC BY-NC_ND 4.0 license, which means that it is freely downloadable without permission under the following conditions: (1) credit must be given to the author and LEMDO in any subsequent use of the files and/or data; (2) the content cannot be adapted or repurposed (except in quotations for the purposes of academic review and citation); and (3) commercial uses are not permitted without the knowledge and consent of the editor and LEMDO. This license allows for pedagogical use of the documentation in the classroom. |