<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20190208//EN" "https://jats.nlm.nih.gov/publishing/1.2/JATS-journalpublishing1-mathml3.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" article-type="research-article" dtd-version="1.2" xml:lang="en">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">1832</journal-id>
      <journal-title-group>
        <journal-title>Journal of Cultural Analytics</journal-title>
      </journal-title-group>
      <issn pub-type="epub">2371-4549</issn>
      <publisher>
        <publisher-name>Center for Digital Humanities, Princeton University</publisher-name>
      </publisher>
      <self-uri xlink:href="https://culturalanalytics.org/">Website: Journal of Cultural Analytics</self-uri>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">25943</article-id>
      <article-id pub-id-type="doi">10.22148/001c.25943</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Article</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>The Measure of the Archive: The Ro­bustness of Network Analysis in Early Modern Correspondence</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <name>
            <surname>Ryan</surname>
            <given-names>Yann C.</given-names>
          </name>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Ahnert</surname>
            <given-names>Sebastian E.</given-names>
          </name>
        </contrib>
      </contrib-group>
      <pub-date publication-format="electronic" date-type="pub" iso-8601-date="2021-07-21">
        <day>21</day>
        <month>7</month>
        <year>2021</year>
      </pub-date>
      <pub-date publication-format="electronic" date-type="collection" iso-8601-date="2021-12-02">
        <year>2021</year>
      </pub-date>
      <volume>6</volume>
      <issue seq="1">3</issue>
      <issue-title>Articles in 2021</issue-title>
      <elocation-id>25943</elocation-id>
      <history>
        <date date-type="received" iso-8601-date="2020-12-03">
          <day>3</day>
          <month>12</month>
          <year>2020</year>
        </date>
        <date date-type="accepted" iso-8601-date="2021-02-12">
          <day>12</day>
          <month>2</month>
          <year>2021</year>
        </date>
      </history>
      <permissions>
        <license license-type="open-access">
          <ali:license_ref xmlns:ali="http://www.niso.org/schemas/ali/1.0/">
              http://creativecommons.org/licenses/by/4.0
            </ali:license_ref>
          <license-p>
              This is an open access article distributed under the terms of the <ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/4.0">Creative Commons Attribution License (4.0)</ext-link>, which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.
            </license-p>
        </license>
      </permissions>
      <self-uri content-type="pdf" xlink:href="https://culturalanalytics.org/article/25943.pdf"/>
      <self-uri content-type="xml" xlink:href="https://culturalanalytics.org/article/25943.xml"/>
      <self-uri content-type="json" xlink:href="https://culturalanalytics.org/article/25943.json"/>
      <self-uri content-type="html" xlink:href="https://culturalanalytics.org/article/25943"/>
      <abstract>
        <p>Network analysis of historical correspondence can be a fruitful way to address historical research questions, and has been increasingly used in historical studies over the past decade. As with many areas of quantitative humanities research, the reliability of the results are often called into question, given that such approaches require ’hard data’ as input, yet almost inevitably use datasets with partial or missing records. Other disciplines using network analysis have conducted robustness experiments designed to test the impact of data loss or error on their results. In order to test how this missing data might affect our own area of research, we conducted a number of experiments designed to simulate the impact of the kinds of loss often seen in historical correspondence data, including random document loss, missing years, and errors in the disambiguation and de-duplication process. The results show that most network centrality measures maintain robustness until a very large proportion of the data (60% or more) is removed. Some measures showed a linear change in robustness, while others remained high and then fell off sharply. Only one, transitivity (local clustering coefficient) was significantly impacted throughout. We tested a range of data loss scenarios (random single letters, folio books of manuscript letters, catalogues, and entire years) and a range of commonly used network metrics. In addition, we tested the robustness of more complex network analysis results in the literature that combine several network metrics to highlight individuals in the network, and found that the same types of individuals would have likely been highlighted even with 50% random letter loss. Alongside the article is a web application, built using Shiny, which will calculate robustness measures for a user-uploaded network dataset. We conclude that researchers working with similar historical correspondence datasets might be able to consider network analysis results to be robust in most cases, rather than work on the assumption that missing data would lead to very different findings or results.</p>
      </abstract>
      <kwd-group>
        <kwd>historical archives</kwd>
        <kwd>methodology</kwd>
        <kwd>robustness</kwd>
        <kwd>history</kwd>
        <kwd>correspondence data</kwd>
        <kwd>social network analysis</kwd>
      </kwd-group>
    </article-meta>
  </front>
</article>
