I have had the pleasure over the last several months of transcribing Bills of Mortality for the Death by Numbers team, and what initially most surprised me is the amount of interpretation my role requires. Just because the bills are what historians would describe as “primary sources,” transcribing them is more complicated than just copying them word-for-word. While it helps that the original bills are in English, I still routinely run into textual issues that require me to pause and think carefully and critically about how to approach the text.

As Death by Numbers has evolved and developed, there have been some slight changes to our workflow, which caused us to reconsider how to work through and present our data. One of those shifts came about because we set up our workflows using early 18th century bills as a model, before shifting to work with the bills from the mid and late 17th century. As a team, we quickly realized that the older bills were falling apart and had more missing information than the bills produced later.

Figure 1. Bills of Mortality Workflow. Once items are added to DataScribe and the datasets are ready for transcription, the transcription workflow begins. The project owner can assign users one of two roles: reviewer or transcriber. Reviewers can edit all records and items, regardless of the item’s status. For Bills of Mortality, Reviewers include the staff members on the project and our Digital History Research Assistants. Transcribers can only edit records and items which are locked to them.

So you want to start transcribing data from historical documents? The task seems easy! However, there are quite a few issues that can pop up which can create problems for other parts of the project. Below are some of the expected errors our transcribers on Death By Numbers frequently run into and some tips on how to handle them. The job may sound intimidating with all the potential pitfalls, but we have suggested solutions from all the tips and tricks our team has picked up over the past few months.