Release Process and Timelines

This page is designed for Anthology Leads (the Coordinating Editors of the NISE, DRE, or MoMS anthologies; the General Editors of the QME, EMEE, DRD, EMDP, and Douai anthologies).

Rationale

Having a clear understanding of the release process and reasonable expectations for the amount of time that each step of the process takes can make the release process go more smoothly and run on schedule. This documentation is designed to give you an overview of the anticipated process and timeline for an anthology release based on the LEMDO teamʼs publication experiences. We recommend consulting it as you plan your anthologyʼs release.
Note that the size of your release will impact the amount of time that the run-up to release takes; a smaller release will take less time than a larger release. You must notify the LEMDO Team at least two calendar months ahead of your desired release date. The feasibility of your release will depend on other tasks in the LEMDO Teamʼs workflow. The precise release date and time will depend on our developersʼ availability.

Practice: Determine Files to be Published

Before you can plan what needs to be done to ensure that your files are ready to be published, determine which files and editions you will include in your release. These should be files and editions that are either already complete or that are near completion and have people working on them. You should be in communication with your editors so that you can anticipate when they will be finished work on their editions.
LEMDO recommends doing fairly small releases, especially for your anthologyʼs first release. By publishing only a few editions at a time, you will reduce the amount of work that your anthology needs to do and the amount of time that it takes to complete that work during the release process.
Your anthology will include only the editions that you select to be published by including them in your anthologyʼs TEI Corpus file (the file in your anthology portfolio with an @xml:id value identical to your anthology ID; e.g., moms.xml). Only files that have a value of "published" on the @status attribute of their <revisionDesc> can be published.
Once you have determined the files that you want to publish, let the LEMDO Team know that you would like to prepare for a website release. Let us know at least two months in advance of when you would like to publish.

Practice: Pre-Release

Minimum Two Months Ahead of Release Date

Notify the LEMDO Team of your desired release date and which editions you intend to include.
Determine which files you are going to publish in your upcoming release.
Finalize content in the files you are going to publish: enter revisions arising from the peer-review process, check citations and references, and ensure that you have made all the links you want to make.
Call for updated bios from contributors, if necessary.

One Month Ahead of Release Date

Create a pre-freeze progress chart that lists all the files you are publishing or updating in this release. Having this chart will help you to determine a timeline for your freeze and ensure that you do not miss any required tasks. People often notice errors and omissions during this stage; anticipate that it will take a full month to complete your pre-freeze tasks. For more information on pre-freeze tasks (including creating a pre-freeze progress chart), see Before an Anthology Freeze.
Proofread pages.
Standardize metadata across all pages.
Write release notes.
Let the LEMDO Director know when you are close to being ready to freeze your anthology. The LEMDO team can then support you to plan a timeline for the freeze. It is important that your team knows when the freeze will be and what it entails to ensure that they understand that they can add no new content during the freeze and that they complete their pre-freeze tasks on time. For more information on freezes, see Freeze.

One Week Ahead of Release: Freeze Tasks

When you are nearly finished with your pre-freeze tasks, you create a final release progress chart. Share it with your team after you have completed all of your pre-freeze tasks. These tasks include:
Check the metadata for each Web page.
Proofread to correct any glaring errors.
Click every link on each Web page.
Change the status of each page to "published".
For more information about the tasks to be done during the freeze and on creating your final release progress chart, see Freeze.
The LEMDO director will announce the freeze when you have finished your pre-freeze tasks. There should be no new content added or major revisions made from this point on.
This stage typically takes about a week. We prefer to publish early in the week (on Mondays when possible) to ensure that we are able to give the release our full and unrushed attention. To allow your team a full week for the freeze period, plan to freeze your anthology at the end of a work week and to complete your final release tasks at the end of the following week.

One Day Ahead of Release

The LEMDO team will take over once you have completed your final release tasks during the freeze. We will do a final check to ensure that your anthology is ready to be published, then we will publish your beta site.
There are sometimes final corrections to be made in this stage. You can anticipate that it will take about a day to release your site. We prefer to publish early in the week; please plan to be done your final release tasks by Monday morning of the week that you wish to publish your anthology.

Practice: Evaluate Your Release

(One month)
LEMDO will do a release evaluation and report after your anthology has been published. Your role in this stage of the release process is to respond to release questionnaires that the LEMDO Project Manager emails you. The Project Manager will incorporate all team membersʼ questionnaire responses into the our release report. All questionnaire responses will be anonymous. This in turn allows us to evaluate what went well during the release process, and what we can improve on in future releases. The LEMDO Project Manager will send you the final release report when it is complete.
Anticipate that it will take about one month for you to receive the release report after your anthology has been released. For more information about the publication and evaluation of your anthology, see Publish and Evaluate Your Anthology Release.

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.

Mahayla Galliford

Research assistant, remediator, encoder, 2021–present. Mahayla Galliford is a fourth-year student in the English Honours and Humanities Scholars programs at the University of Victoria. She researches early modern drama and her Jamie Cassels Undergraduate Research Award project focused on approaches to encoding early modern stage directions.

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.

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