CINXE.COM

<!doctype html><html lang=en-us><head><meta charset=utf-8><meta charset=utf-8><meta name=viewport content="width=device-width,initial-scale=1,shrink-to-fit=no"><title>Requesting Corrections - ACL Anthology</title> <meta name=generator content="Hugo 0.140.2"><link href=/aclicon.ico rel="shortcut icon" type=image/x-icon><link rel=stylesheet href=/css/main.min.b53e37419139f6302a0be966257012b1d281f3350967383f227f76c0ecaeff80.css media=screen><link rel=stylesheet href=https://use.fontawesome.com/releases/v5.7.2/css/all.css integrity=sha384-fnmOCqbTlWIlj8LyTjo7mOUStjsKC4pOpQbqyi7RrhN7udi9RwhKkMHpvLbHG9Sr crossorigin=anonymous><link rel=stylesheet href=/css/academicons.min.css></head><body><nav class="navbar navbar-expand-sm navbar-light bg-light bg-gradient-light shadow-sm py-0 mb-3 mb-md-4 mb-xl-5"><div id=navbar-container class=container><a class=navbar-brand href=https://aclanthology.org/><img src=https://aclanthology.org/images/acl-logo.svg width=56 alt="ACL Logo"> <span class="d-inline pl-2">ACL Anthology</span> </a><button class=navbar-toggler type=button data-toggle=collapse data-target=#navbarSupportedContent aria-controls=navbarSupportedContent aria-expanded=false aria-label="Toggle navigation"> <span class=navbar-toggler-icon></span></button><div class="collapse navbar-collapse" id=navbarSupportedContent><ul class="navbar-nav flex-grow-1 pr-md-2"><li class=nav-item><a class=nav-link href=/posts/>News<span class=sr-only>(current)</span></a></li><li class=nav-item><a class=nav-link href=/faq/>FAQ<span class=sr-only>(current)</span></a></li><li class=nav-item><a class=nav-link href=/info/corrections/>Corrections<span class=sr-only>(current)</span></a></li><li class=nav-item><a class=nav-link href=/info/contrib/>Submissions<span class=sr-only>(current)</span></a></li><li class=nav-item><a class=nav-link href=https://github.com/acl-org/acl-anthology/><i class="fab fa-github pr-1"></i>Github</a></li></ul><form class="form-inline my-2 my-lg-0 flex-nowrap" action=/search/? method=get><input id=acl-search-box class="form-control mr-sm-2" name=q type=search placeholder=Search... aria-label=Search> <button class="btn btn-outline-primary" type=submit><i class="fas fa-search"></i></button></form></div></div></nav><div id=main-container class=container><main aria-role=main><h2 id=title>Requesting Corrections</h2><p class="lead text-muted">How to submit corrections to the Anthology</p><hr><p class="font-weight-light font-italic text-muted">February 10, 2025</p><h3 id=what-type-of-correction-do-i-need>What type of correction do I need?</h3><p>Our central guiding corrections principle is that <strong>we view the content of PDFs as authoritative</strong>. If you see errors or inconsistencies in the metadata (author list, title, abstract), you need to first check to see if it matches the PDF.</p><p>This view drives three main types of corrections:</p><ul><li><a href=#pdf-corrections><em>PDF corrections</em></a>. The PDF itself can be in error.</li><li><a href=#metadata-corrections><em>Metadata only</em></a>. Information presented in the Anthology may be different from the PDF. Examples include errors in the title, abstract, or author list.</li><li><a href=#author-disambiguation><em>Author disambiguation</em></a>. An author’s papers might be spread across multiple author pages (one person, multiple pages), or a single author page might contain papers from different people (multiple people, one page).</li></ul><p>Below we describe the process for addressing these types of corrections, in order of the frequency we encounter them.</p><h3 id=metadata-corrections>Metadata corrections</h3><p>Corrections to <strong>metadata</strong> do not require changing the PDF. These kinds of corrections bring the information presented in the Anthology in line with the authoritative PDF.</p><p>A request to change paper metadata can be submitted in two ways.</p><ol><li><p>Navigate to the paper’s page in the ACL Anthology (e.g., <a href=https://aclanthology.org/K17-1003/>K17-1003</a>). From there, click the yellow “Fix data” button. This will display a dialog that you can use to correct the title and abstract and fix issues with the author list.</p><p>Submitting this form will create a Github issue with a JSON data block. This will then be validated by Anthology staff, and processed by a semi-automatic bulk corrections script on a weekly basis.</p></li><li><p>If you would like to expedite the process and are familiar with <a href=https://git-scm.com>git</a>, you can make the correction yourself and file a <a href=https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests>pull request (PR)</a>.</p><ul><li>First, locate your file amongst our <a href=https://github.com/acl-org/acl-anthology/tree/master/data/xml>authoritative XML files</a>. The name of your file is the portion of the Anthology ID that comes before the hyphen. As an example, if the Anthology ID of your paper is <code>P19-10171</code>, then the file you will need to edit is <a href=https://github.com/acl-org/acl-anthology/blob/master/data/xml/P19.xml>data/xml/P19.xml</a>; if the Anthology ID of your paper is <code>2021.iwslt-1.28</code>, then the file you will need to edit is <a href=https://github.com/acl-org/acl-anthology/blob/master/data/xml/2021.iwslt.xml>data/xml/2021.iwslt.xml</a>.</li><li>Find your entry in the XML file, and use Github’s edit button to fix it and then to issue a PR against our <code>master</code> branch.</li><li>For larger XML files, you may have to fork the repository first. <a href=https://help.github.com/en/github/managing-files-in-a-repository/editing-files-in-another-users-repository>More information can be found here</a>.</li></ul></li></ol><p>The Anthology team will attend to the correction as we find time. Metadata changes are generally accepted if they are consistent with the PDF, which we take as authoritative. However, please see the following note.</p><p><strong>Note on changes to author metadata</strong></p><p>Because it is beyond our ability to keep track of the many differing policies governing conferences and journals whose proceedings we host, it is therefore up to those groups to ensure that PDF authorship is correct when proceedings are delivered to the Anthology for ingestion.</p><p>We reserve the right to seek permission or corroboration from the associated conference or workshop program chairs in unusual situations, such as removing or adding an author to a PDF revision. In such cases, we will ask authors to arrange for this permission to be conveyed to us, either (ideally) on the corresponding Github issue or via email.</p><h3 id=author-disambiguation>Author disambiguation</h3><p>The Anthology builds author pages based on the string form of names found in paper metadata. These pages are housed under <a href=https://aclanthology.org/people/>https://aclanthology.org/people/</a>, e.g., <a href=https://aclanthology.org/people/aravind-joshi>Aravand Joshi</a>.</p><p>There are two types of author disambiguation:</p><p><strong>One person, multiple author pages</strong>. This situation occurs when a person has multiple papers written under different names. Often, these names are minor variations of each other (e.g., including or excluding a middle initial). Sometimes, this is a simple mistake in the metadata that can be handled using the procedure described above. However, if the metadata for the papers is correct, then we need to manually link the author pages.</p><p><strong>Multiple people, single author page</strong>. In this situation, many different people have published under the same name. An example is <a href=https://aclanthology.org/people/yang-liu>Yang Liu</a>. In this case, we have to manually assign IDs to the papers to create a separate author page, typically using their Ph.D. granting institution (e.g., <a href=https://aclanthology.org/people/y/yang-liu-edinburgh/>Yang Liu of Edinburgh</a>.</p><p>Both situations can be addressed by <a href="https://github.com/acl-org/acl-anthology/issues/new?template=02-name-correction.yml">filing an Author Page request</a>.</p><h3 id=pdf-corrections>PDF corrections</h3><p>Our PDF corrections process loosely follows the <a href=https://www.acm.org/publications/policies/>ACM Publications Policy</a>:</p><ul><li>An <strong>erratum</strong> clarifies errors made in the original scholarly work. Usually these are just short notes, corrective statements, or changes to equations or other problems in the original, which need to be read alongside the original work.</li><li>A <strong>revision</strong> is a versioned replacement of the original scholarly work. This format allows a corrected paper to be read in place of the original scholarly work, and typically does not highlight the original’s errors.</li><li>A <strong>retraction</strong> occurs when serious, unrecoverable errors are discovered, which drastically affect the findings of the original work.</li><li>A <strong>removal</strong> occurs in rare circumstances where serious ethical or legal issues arise, such as plagiarism.</li></ul><p>Please take note of the following points regarding revisions and retractions.</p><ul><li>The original published PDF is not invalidated. The original will still stand as published and cannot be withdrawn, and both will remain available and linked on the website.</li><li>The landing page for the work will indicate the availability of the erratum or revision.</li><li>We cannot currently regenerate the full volumes, which will continue to contain only the original papers.</li><li>We have no control over how downstream consumers of the Anthology, such as search engine, process the changes.</li></ul><h4 id=revisions-and-errata>Revisions and errata</h4><p>For requests to change paper <em>content</em> (either a revision or an erratum), again, please <a href="https://github.com/acl-org/acl-anthology/issues/new?assignees=anthology-assist&labels=correction%2Crevision&template=03-revision-or-errata.yml&title=Paper+Revision%7Breplace+with+Anthology+ID%7D">file a Github issue</a>. <strong>Please note the following</strong>:</p><ul><li>Be sure to attach the revised PDF to the issue.</li><li>For revisions, provide a brief summary of the changes. This summary will be included in the Anthology. Its intended audience is users of the Anthology, and should therefore be written from a neutral, scientific perspective.</li><li>If the metadata also needs to change, please also follow the instructions in the previous section.</li><li>If possible, when generating your revision, it would be good to add the proper proceedings header and footer stamps, as well as the correct page numbering. Unfortunately, we cannot provide any assistance with this task.</li></ul><p>For revisions, the brief summary should allow readers to find the changed parts, but need not be too detailed. Here are some good examples:</p><ul><li><em>A sponsor was added to the Acknowledgments section.</em></li><li><em>Added a footnote to page 8 describing data processing.</em></li><li><em>Corrected a few citations; added Footnote 2 clarifying the baseline calculation; expanded the caption of Table 3; added a paragraph to the Related Works section.</em></li></ul><p>Following these instructions will help us to process corrections more quickly. We will do our best to process revisions or errata within four weeks, but make no guarantees as to the processing time. Submissions not meeting these standards will be rejected, potentially without notice.</p><p>A revision that changes the author list needs permission (see below).</p><h4 id=retractions>Retractions</h4><p>To initiate a retraction, please communicate directly with the Anthology director. Retractions often involve the organizing editors or chairs of the respective journal or conference.</p><p>Retractions result in the following changes in the Anthology:</p><ul><li>The paper is processed as a revision. Each page of the revised PDF is marked with a prominent watermark reading “RETRACTED”.</li><li>The paper’s title and author list are displayed with <del>strikeout text</del> in the volume and event listings.</li><li>The paper’s canonical page contains a prominent notice of the retraction, Its title, author list, and abstract are presented in <del>strikeout text</del>. No bibliographic files are generated, and the paper is not listed in the consolidated Anthology BibTeX file.</li><li>The paper is removed entirely from the listing on the author page.</li></ul><h4 id=removal>Removal</h4><p>Removals are rare events that are undertaken only in the most serious of situations, such as plagiarism or fraud. A paper can be removed at the request of the scientific organization with jurisdiction over the paper. For most papers within the Anthology, this is the <a href=https://www.aclweb.org/>ACL</a>, but any organization with publications in the Anthology (e.g., <a href=https://www.amtaweb.org/>AMTA</a>, <a href=https://lrec-conf.org>LREC</a>) can also request the removal of a paper. The Anthology staff does not adjudicate removal decisions.</p><p>A removal will result in the following changes to the Anthology:</p><ul><li>The paper PDF, along with all revisions and attachments, are removed from the Anthology. (They will, however, be preserved in the Anthology’s private storage.)</li><li>The associated book will either be regenerated or will be edited to remove the offending paper.</li><li>The paper will be removed from all listings, including the volume page, any events pages it is associated with, and the author page.</li><li>The paper’s canonical page will be modified to contain a prominent notice of the removal. Its title and author list will be presented in <del>strikeout text</del>. The abstract, if present, will be removed. No bibliographic files will be generated.</li></ul></main></div><footer class="bg-gradient-light py-2 py-xl-3 mt-3 mt-md-4 mt-xl-5"><div class=container><p class="text-muted small px-1"><span class="float-right mt-2 ml-2"><a rel=license href=http://creativecommons.org/licenses/by/4.0/><img alt="Creative Commons License" style=border-width:0 src=https://i.creativecommons.org/l/by/4.0/88x31.png></a></span> ACL materials are Copyright 漏 1963–2025 ACL; other materials are copyrighted by their respective copyright holders. Materials prior to 2016 here are licensed under the <a href=https://creativecommons.org/licenses/by-nc-sa/3.0/>Creative Commons Attribution-NonCommercial-ShareAlike 3.0 International License</a>. Permission is granted to make copies for the purposes of teaching and research. Materials published in or after 2016 are licensed on a <a href=https://creativecommons.org/licenses/by/4.0/>Creative Commons Attribution 4.0 International License</a>.</p><p class="text-muted small px-1">The ACL Anthology is managed and built by the <a href=/info/credits/>ACL Anthology team</a> of volunteers.</p><p class="text-muted small px-1"><i>Site last built on 15 March 2025 at 19:45 UTC with <a href=https://github.com/acl-org/acl-anthology/tree/71bcfb52d7c256d242d543f046a0941cfcd6de95>commit 71bcfb5</a>.</i></p></div></footer><script src=https://code.jquery.com/jquery-3.3.1.slim.min.js integrity=sha384-q8i/X+965DzO0rT7abK41JStQIAqVgRVzpbzo5smXKp4YfRvH+8abtTE1Pi6jizo crossorigin=anonymous></script><script src=https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.6/umd/popper.min.js integrity=sha384-wHAiFfRlMFy6i5SRaxvfOCifBUQy1xHdJ/yoi7FRNXMRBu5WHdZYu1hA6ZOblgut crossorigin=anonymous></script><script src=https://stackpath.bootstrapcdn.com/bootstrap/4.2.1/js/bootstrap.min.js integrity=sha384-B0UglyR+jN6CkvvICOB2joaf5I4l3gm9GU6Hc1og6Ls7i6U/mkkaduKaBhlAXv9k crossorigin=anonymous></script><script src=https://cdn.jsdelivr.net/npm/sortablejs@1.15.0/Sortable.min.js></script><script>$(function(){$('[data-toggle="tooltip"]').tooltip(),$("#toggle-all-abstracts")&&($("#toggle-all-abstracts").on("click",function(){var e=$("#toggle-all-abstracts");e.attr("disabled",!0),e.attr("data-toggle-state")=="hide"?($(".abstract-collapse").collapse("show"),e.attr("data-toggle-state","show")):($(".abstract-collapse").collapse("hide"),e.attr("data-toggle-state","hide")),e.attr("disabled",!1)}),$("#toggle-all-abstracts").attr("disabled",!1))})</script></body></html>