Skip to main content Accessibility help
×
Hostname: page-component-7b7567c8c-tnzcf Total loading time: 0 Render date: 2026-11-14T06:18:51.005Z Has data issue: false hasContentIssue false

Where to Next?

Published online by Cambridge University Press:  20 October 2026

Get access

Summary

AS I READ Joanna Drucker and others posit new, fantastic ways digital humanities could, or should, be approaching visualization, I was struck by just how difficult it is to make these ideas a reality. Scholars imagine forms of visualization that capture nuance and are interactive in ways that align with the “values” of the humanities rather than “co-opting” methods from the sciences but have no easy way to enact those imaginings with the current technical tools available to them. At times, criticism of visualization in digital humanities, even from practitioners of visualization, feels naive in its failure to acknowledge the current state of visualization tools. Of course, imagining what might be possible in the future drives innovation and development of new tools, but such software development requires skills not already in the wheelhouse of most humanities researchers.

While it is possible to do network analysis without any programming skills at all, the process of data capture and transformation is made much easier by the ability to script. As an undergraduate studying computer science, I first came to digital humanities with more skills in the digital and spent the latter half of my undergraduate and all my graduate education skilling-up in the humanities aspects. But traditional computer science education is by no means the only, best, or even most common path for digital humanists to gain programming skills to aid their work. Websites like CodeCademy offer free lessons in languages common for DH work, like Python and R, and the journal The Programming Historian publishes free online tutorials for common digital history tasks and tools.

Even using with tools like Gephi and OpenRefine at one’s disposal, an aspiring network analyzer will find their work greatly eased by a little bit of scripting power. But it still is not easy: the work of capturing and transforming data is still labour-intensive—tedious, “mechanical,” and important work that can be difficult to have recognized by traditional academic structures.

Information

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure no-reply@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×