Commit Changes to the LEMDO Repository

Rationale

When you make changes to files in your local copy of the LEMDO repository, you must also send them back to the centralized Subversion repository by committing. This allows you to see your changes on the LEMDO development site and ensures that all versions of your file are saved. You must commit at the end of every work session and should also commit regularly during long work sessions. There are three steps to committing: 1) Validating your files in Oxygen, 2) Checking the status of your local copy, and 3) Using the SVN command to commit your files to the central LEMDO repository. This documentation will explain the practice for each step.

Practice: Validate Your Files in Oxygen

Before committing any files to the central LEMDO repository, you must validate and save them in Oxygen. To validate your file, click on the button that resembles a piece of paper with a checkmark on it at the top of your Oxygen window:

                           Oxygen validation button
If your file is valid, you will see a green square followed by the message Validation successful at the bottom of your Oxygen window.

                           Oxygen message with a green square to the left reads: Validation successful
If your file is valid, you may now save your file and move on to checking the status of your local copy.
If your file is invalid, you will see a red square followed by an error message at the bottom of your Oxygen window. Follow the steps given at the bottom of the window and then validate your file again. For more detailed instructions on validating files, go to Validate Files.

Practice: Check the Status of Your Local Copy

At any point, you can check the status of your local copy compared to the centralized repository. When you check the status of your local copy, you are checking to see if your local files differ from the files in the repository. This is useful for a few reasons:
You can check that you have made changes in the files that you expected to and not in those that you had not expected to.
You can see the pathway to the lowest level of the repo before the file that you have changed. You should change directory down that pathway into the lowest level before you commit.
To check the status of your local copy, type svn status and then press the Enter/Return key. You will see a list of files that you have made changes in preceded by the path to get to those files from your current location. If you have made changes in files, you will also see the following characters on the left side of your command line window:
Character Meaning
M Modified: You have modified the following file in some way.
? You have created a new file, but you have not yet run the svn add command to add it to the repo.
A Added: You have created a new file and you have queued it up to be added to the repo by running the svn add command.
D Deleted: You have removed a file and queued it up to be deleted from the repo.

Practice: Commit

Once you have checked the status of your local copy, you are ready to commit your files to the centralized LEMDO repository.
We give people write privileges to commit only to the portfolios that they are expected to work on. You will likely have been given permissions to commit only to your editionʼs directory and lower. This means that you must navigate to at least your edition directory level (e.g., data/texts/FV for Famous Victories of Henry V) before you commit. Best practice is to commit from the lowest level before the file that you have made changes in, as doing this ensures that you commit only what you mean to (e.g., data/texts/FV/main to commit the file data/texts/FV/main/emdFV_M.xml). To navigate down the folder tree, use the Terminal command cd followed by a space and then the pathway to the directory that you are navigating to (e.g., cd data/texts/FV/main) and then press the Enter/Return key.
Once you are in the lowest directory, you will commit your file. Type the command svn commit -m followed by a space and a brief message about what you did in the file. For example, if you had numbered all of the speeches in emdFV_Q1, you might put svn commit -m "numbered speeches". If you are committing just one file, it is unnecessary to specify the file in your message. If you are committing multiple files at once, it is helpful to specify what you did in which file.
If SVN asks you for a password, check that the username is your NetLink ID (not your computer username). If it is not, press Enter/Return and then, when prompted, type in your NetLink ID. Once the username is your NetLink ID, type your NetLink password.
If your commit is successful, you will see a message reading Committed revision followed by the new revision number.

                           White text on black background reads: C:\Users\katel\lemdo greater-than angle bracket svn commit -m double quotation mark Added entry to BIBL1 and proofread content in lemdo_bornDigital double quotation mark / Sending data\BIBL1.xml / Sending data\documentation\lemdo_bornDigital.xml / Transmitting file data ..done / Committing transaction... Committed revision 6459. / C:\Users\katel\lemdo greater-than angle bracket
If the commit fails and you are uncertain why, email lemdo@uvic.ca for support.

Step-by-Step: Commit

Validate and save your file in Oxygen. Your file must be valid before you commit.
In Terminal, run svn status from the lemdo level.
Navigate to the lowest level before your file using the command cd (change directory). E.g., cd data/texts/FV/main.
Use the command svn commit -m "message about what you did", replacing the text in the quotation marks with a short message about what changes you made in your file.

Special Case: Committing Only Some Files

If you have made changes in several files in a single portfolio and only want to commit certain ones, follow these steps:
Validate and save your file in Oxygen.
In Terminal, run svn status from the lemdo level.
Navigate to the lowest level before your file using the command cd (change directory).
Type svn commit followed by a space, the full name of the file(s) that you wish to commit (including the file extension, which will normally by .xml) followed by a space, -m and then a brief message about the changes that you made in each file. If you are committing more than one file, seperate each file with a single space. E.g., svn commit emdFV_GenIntro.xml emdPerfIntro.xml -m "added xml:ids in emdFV_GenIntro, numbered paragraphs in emdPerfIntro".

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.

Glossary

Portfolio
“A directory (i.e., folder) in the LEMDO repository containing all the files for an edition. The name of each portfolio is the abbreviation for the edition, such as AYL for As You Like It.”
svn commit
“A Terminal command used to push any local-copy changed files to the LEMDO repository.”
write privileges
“the ability to commit new and revised files to the repository”

Metadata