Copyright held by
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Further details of licences are available from our
Licences page. For more
information, contact the project director,
Provider: University of Victoria
Database: The Map of Early Modern London
Content: text/plain; charset="utf-8"
TY - ELEC
A1 - Holmes, Martin
A1 - Landels-Gruenewald, Tye
A1 - Butt, Cameron
ED - Jenstad, Janelle
T1 - Access Files from the Subversion Repository
T2 - The Map of Early Modern London
PY - 2020
DA - 2020/06/26
CY - Victoria
PB - University of Victoria
LA - English
UR - https://mapoflondon.uvic.ca/subversion.htm
UR - https://mapoflondon.uvic.ca/xml/standalone/subversion.xml
ER -
RT Web Page
SR Electronic(1)
A1 Holmes, Martin
A1 Landels-Gruenewald, Tye
A1 Butt, Cameron
A6 Jenstad, Janelle
T1 Access Files from the Subversion Repository
T2 The Map of Early Modern London
WP 2020
FD 2020/06/26
RD 2020/06/26
PP Victoria
PB University of Victoria
LA English
OL English
LK https://mapoflondon.uvic.ca/subversion.htm
The Julian calendar, in use in the British Empire until September 1752. This calendar is used for dates where the date of the beginning of the year is ambigious.
The Julian calendar with the calendar year regularized to beginning on 1 January.
The Julian calendar with the calendar year beginning on 25 March. This was the calendar used in the British Empire until September 1752.
The Gregorian calendar, used in the British Empire from September 1752. Sometimes
referred to as
The Anno Mundi (year of the world
) calendar is based on the supposed date of the
creation of the world, which is calculated from Biblical sources. At least two different
creation dates are in common use. See Anno Mundi (Wikipedia).
Regnal dates are given as the number of years into the reign of a particular monarch.
Our practice is to tag such dates with
Junior Programmer, 2018-present. Tracey is a PhD candidate in the English Department at the University of Victoria. Her research focuses on Critical Technical Practice, more specifically Algorhythmics. She is interested in how technologies communicate without humans, affecting social and cultural environments in complex ways.
Programmer, 2018-present. Junior Programmer, 2015-2017. Research Assistant, 2014-2017. Joey Takeda was a graduate student at the University of British Columbia in the Department of English (Science and Technology research stream). He completed his BA honours in English (with a minor in Women’s Studies) at the University of Victoria in 2016. His primary research interests included diasporic and indigenous Canadian and American literature, critical theory, cultural studies, and the digital humanities.
Data Manager, 2015-2016. Research Assistant, 2013-2015. Tye completed his undergraduate honours degree in English at the University of Victoria in 2015.
Research Assistant, 2012–2013. Cameron Butt completed his undergraduate honours degree in English at the University of Victoria in 2013. He minored in French and has a keen interest in Shakespeare, film, media studies, popular culture, and the geohumanities.
Research Assistant, 2012-2014.
Director of Pedagogy and Outreach, 2015–present. Associate Project Director, 2015–present. Assistant Project Director, 2013-2014. MoEML Research Fellow, 2013. Kim McLean-Fiander comes to
Janelle Jenstad is Associate Professor of English at the University of Victoria, Director of
Programmer at the University of Victoria Humanities Computing and Media Centre (HCMC). Martin ported the MOL project from its original PHP incarnation to a pure eXist database implementation in the fall of 2011. Since then, he has been lead programmer on the project and has also been responsible for maintaining the project schemas. He was a co-applicant on MoEML’s 2012 SSHRC Insight Grant.
Most
mol:
prefix and accessed through the web application
with their id + .xml
.
The molagas prefix points to the shape representation of a location on
Links to page-images in the Chadwyck-Healey
Links to page-images in the
The mdt (
The mdtlist (
_subcategories, meaning all subcategories of the category.
The molgls (
This molvariant prefix is used on
This molajax prefix is used on
The molstow prefix is used on
Our editorial and encoding practices are documented in detail in the Praxis section of our website.
s/heand
his/herto
theyand
theirrespectively.
This manual explains how to share files using a subversion (SVN) repository. For a summary of commonly used commands, see Commands
.
All of
To access data from the repository, use an SVN command-line client. This method
may seem old-fashioned, but it is an easy process that remains consistent across
different platforms (Windows, Mac, etc.). It also allows experienced users to
run functions like svn log
to see a list of all the changes made to
the repository.
This manual provides instructions for Linux, Windows and Mac users. See also tips and tricks for using SVN.
At HCMC, SVN is already installed on Linux. Editors working from their own computers will need to install SVN from the repositories of their own distribution.
First, create a directory for
mkdir london
and pressing
the return key.home
directory to the london
directory by typing cd
london
and pressing the return key.svn
checkout https://hcmc.uvic.ca/svn/london/db/data .
and pressing the return key. Make sure to include the s
in
https
and the space + period at the end (after
data
).The command line entries should look like this:
All the
There is now a complete copy of
Since multiple editors will be adding, updating, and sometimes deleting
svn
update
into the command line and pressing the return key.
In this example, a change has been made: a new file has been added
(this is indicated by the A
next to it; updated files are
indicated with a U
and deleted files with a
D
). Note that the revision number is incremented every time a
commit is made; this repository is at revision number 1043, so 1043 commits
have been made.
Permissions are required to commit files to SVN. To obtain permission,
contact the
When changes are made to local files, they will need to be committed
(uploaded) to the repository with the commit
command:
london
directory (see above), type
svn commit
and press the return key.Updated broken ref links in
data/info/website_structure.xml
. Then press Ctrl + O to
create a file name for the revision in the repository, followed by
the return key. Then press Ctrl + X to exit the text editor.
The system has committed the changes and the revision number is now
76.
To add a new file to the repository, make sure the file is valid and follows
In the london
directory, type svn add
, then a
space, and then the file name. For instance, a file called
test.xml
located in the info
folder should
appear as follows:
The command line responds by echoing the folder and file name with an
A
in front of it.
Now commit the change to the server (see above); nothing is sent to the repository without an
svn commit
:
The command line will confirm that the revision has been committed.
Use caution when deleting files from SVN: deleted files can be recovered, but
recovering files is a time-consuming process. To delete a file, type
svn delete
, then a space, then the file name (in this
example, info/test.xml
):
Note that this process also deletes the local copy of the file.
Obtain a command-line client from CollabNet. Registration is required to download the program, but there is no cost. Make sure to download the correct version; there are versions for 32-bit and 64-bit Windows. Once the program is downloaded, install it by double-clicking the downloaded installer and following its instructions.
Next, open a command window (terminal) by clicking the start menu and typing
cmd
into the search box and pressing return. This action
should bring up a terminal window:
The terminal window opens in the home folder (C:\Users\[username] on Windows 7). Save
london
: mkdir london
into the
command line and then pressing the return key.home
directory to the
london
directory by typing cd london
followed by the return key.svn checkout
https://hcmc.uvic.ca/svn/london/db/data .
followed by the return key. Make sure to include the s
in https
and the space + period at the end (after
data
).All the
There is now a complete copy of
C:Users/[username]/london
): Since multiple editors will be adding, updating, and sometimes deleting
svn
update
into the command line and pressing the return key.
In this example, a change has been made: a new file has been added (it
has A
next to it; updated files are indicated with a
U
and deleted files with a D
). Note that
the revision number has changed to 18.
Permissions are required to commit files to SVN. To obtain permission,
contact the
When changes are made to a file, they will need to be committed (uploaded) to
the repository with the commit
command:
svn commit
followed by a space and -m
for message.
For example, if updates were made to the file
data/info/website_structure.xml
, commit them by typing the
following:
svn commit -m "Added copyright info to the header of
website_structure.xml."
If SVN asks you for a password, give your netlink password (the first
time your password is given, it may fail since SVN defaults to the user name
on your local computer first; in that case, SVN will also ask for a user
name—use your netlink user name). Once SVN confirms that you have rights to
commit to the respository, it will upload the changes:
The system has committed the changes and the revision number is now
19.
To add a new file to the repository, make sure the file is valid and follows
In the london
directory (see above), type svn
add
, then a space, and then the file name. For instance, a file
called test.xml
located in the info
folder should
appear as follows:
The command line responds by echoing the folder and filename with an
A
in front of it.
Now commit the change to the server (see above); nothing is sent to the server without an svn
commit
:
The command line will confirm that the revision has been
committed.
Use caution when deleting files from SVN: deleted files can be recovered but
recovering files is a time-consuming process. To delete a file, type
svn delete
, then a space, then the file name (in this
example, info/test.xml).
Then commit the change (see
above). Note that this process also deletes the local copy of the file.
Mountain Lion and Mavericks users can access
Though earlier Mac operating systems include subversion command tools by
default, Mountain Lion and Mavericks do not. To test whether your operating system has
these commands installed, follow these instructions:
To install the subversion command tools, you will need to do the
following:
terminal
by
clicking the magnifying glass in the menu bar or by typing
Command + Space. Once terminal is selected, press return
key.Terminal
from the Utilities folder
in Applications.svn checkout
and press the return key. If
terminal responds that there are Not enough arguments
provided
, the subversion commands are already installed
and you may proceed to the next section. If terminal responds that the command is
not recognized, you will need to install them.
Once you have made sure that your operating system has the necessary command line tools, you can check out
First, create a directory for the files and check them out:
Once you’ve completed these steps, the mkdir london
and pressing
return.london
directory by typing cd
london
and pressing return.svn checkout
https://hcmc.uvic.ca/svn/london/db/data .
and
pressing return. Make sure to include the s
in
https
and the space + period at the end (after
data
). You may wish to copy-paste the command from
these instructions to avoid typos.
Updating local files will be exactly the same for Mountain Lion, Mavericks and Linux users alike. Please see the Linux instructions above.
Committing changes to files will svn commit
. Instead, you
will need to include the log message on one line as follows: svn
commit -m "[short description of your changes]"
(See Linux instructions above).
Adding and deleting files will be the same for Mountain Lion and Mavericks users as it is for Linux users (See Linux instructions on adding files and instructions on deleting files), with the exception that after committing the files, the log message needs to be entered on the same line (see above).
This section includes a few terminal commands that may speed up your work with the subversion repository.
When creating a new file for the project, even if it is just a word-processor
file with notes in it, remember to give it a descriptive file name, and do
not use punctuation or spaces in the file name. SVN can handle such
characters in file and folder names, but files with these types of names can
cause problems. For example, instead of Fred’s notes on
Stow.odt
, use Fred_notes_on_Stow.odt
.
When creating a new file, first save it in the correct SVN folder and then
enter svn add [the filename]
to tell SVN that it should be
managing the file. For instance, when creating a file in the documentation
folder, first enter svn add
documentation/Fred_notes_on_Stow.odt
. The command line should
respond with A (bin) documentation/Fred_notes_on_Stow.odt
,
meaning that SVN has accepted the file. Finally, the file needs to be
committed with the command svn commit -m "[Short description of your
changes]"
. Ex. svn commit -m "Added a file to documentation
with my notes on Stow"
.
It may sometimes be necessary to add multiple formats of the same file; this
is particularly applicable for image files. Suppose that the following image
files exist: facsimile_agas.png
,
facsimile_agas.svg
, and facsimile_agas.gif
.
Upload all three files at the same time by entering svn add
db/site/images/facsimile_agas.*
into the commmand line. The
asterix symbol in this command means .png
file, the .svg
file, and the
.gif
file together. Thus, this command will trigger the
following response:
svn add db/site/images/facsimile_agas.*
A (bin) db/site/images/facsimile_agas.png
A db/site/images/facsimile_agas.svgz
A db/site/images/facsimile_agas.gif
Finally, these file need to be committed with the command svn commit -m
"Added new image of the Agas map in three formats."
Before moving a file in SVN, make sure everyone who might have uncommitted changes to file being moved has committed their changes. Once you have done this, use the following command template in Terminal: svn mv [Insert current file url.] [Insert desired file url.]
This template assumes that you are in the correct data directory (i.e., that you have used Terminal to navigate to the folder that contains your
london). As the template indicates, the
svn mv
command consists of three parts: the preface svn mv, the file’s current url (i.e., where the file is located now), and the file’s desired url (i.e., where you want the file to be located).
Suppose that you want to move praxis.xml from its current location in the how_to
folder to the info
folder. The file’s current url is how_to/praxis.xml
. In this hypothetical scenario, the file’s desired url is info/praxis.xml
. To move the file, type the following command into Terminal: svn mv how_to/praxis.xml info/praxis.xml
. SVN will respond by deleting the original file (in this example, how_to/praxis.xml
) and adding a new one (in this example, info/praxis.xml
). A dialogue that looks something like the following should occur in your Terminal window:
Finally, commit your change using the svn commit
command. Once you commit your change, any team member who updates their SVN files will see that the original file has been deleted and that a new version of the file has been added in the specified location.
Commands must be typed precisely at the command line with the correct
capitalization. For example, MyFile.odt
is a different file
from myfile.odt
. However, the command line has a few helpful
shortcuts. To automatically complete a command, press tab after entering the
first two or three characters of a file name (enough to distinguish it from
any other file in the folder). For example, typesvn add doc
,
then press tab. The command line should then complete the folder name:
svn add documentation/
. Then add Fre
:
svn add documentation/Fre
and press tab. The command line
should complete the rest of the filename: svn add
documentation/Fred_notes_on_Stow.odt
.
When working at the command line, it may sometimes be necessary to repeat the
last command, or the last command with a small variation. It is possible to
use the arrow keys on the keyboard to recall previous commands. For example,
enter svn add documentation/Fred_notes_on_Stow.odt
svn commit -m "Added a file to documentation with my notes on
Stow."
then press the svn commit -m "Added a file to documentation with my
notes on Stow."
and Press the svn add
documentation/Fred_notes_on_Stow.odt
. Use the
It frequently happens that new files are created and subsequently forgotten
before being added to SVN. To find out what files have been modified in the
current session, enter svn status
. The command line will then
return a list of file names. For example:
svn status
M db/site/css/global.css
? db/site/images/facsimile_page.svg
? db/site/images/facsimile_page.png
In the above list, the question mark symbol precedes file names that are not currently being managed by SVN. These files, should they be relevant to MoEML, need to be added and commited to SVN.
Finally, in the above list, M
preceeds file names that
have been modified in the current session but not commited to SVN. These
files need to be commited to SVN.
The svn log
command makes it possible to read SVN logs from
recent commits, thereby enabling users to track each other’s work. To use
this command, first enter svn log -l 20
. (The character after
the dash is a lowercase L and the succeeding number tells SVN how many logs
to return.) In this example, SVN is being asked to return the most recent 20
entries; it is possible, however, to ask for more or less entries.To see the
very latest log entry, enter svn log -r HEAD
. To see the log
entry for a specific revision, enter the number of the revision after -r.
For example, svn log -r 1259
will return revision number
1259.
The command line will respond to these commands with a log entry or a series of log entries that look(s) like this:
r1259 | jenstad | 2013-05-06 16:31:33 -0700 (Mon, 06 May 2013) |
1
line Added a new file for Editorial practices for mayoral shows
editorial_practices_mayoral.xml in info.
Each individual log entry corresponds with a commit submitted to SVN. A log
entry provides the revision number, the person who did the commit, the exact
date and time of the commit, and the comment they provided. The information
provided by log entries can be very helpful when attempting to solve
mistakes and errors. For example, it is possible to see the exact changes that
were made between one revision and another in a particular file. Simply
enter svn diff -r
followed by the range of revisions (x:y) and
the file name. For example, svn diff -r 1276:1279 PERS1.xml
will return log entries for revisions to PERS1.xml numbered 1276 through to
1279.
The following is a table of common commands used when working with SVN. Each command should be followed by pressing the Enter/Return key (⏎).
For further information about how to use Subversion, consult Collins-Sussman, Fitzpatrick, and Pilato (2008).