CINXE.COM
Information for Editors | IEEE Information Theory Society
<!DOCTYPE html> <html lang="en" dir="ltr"> <head> <meta charset="utf-8" /> <script async src="https://www.googletagmanager.com/gtag/js?id=UA-7402386-1"></script> <script>window.dataLayer = window.dataLayer || [];function gtag(){dataLayer.push(arguments)};gtag("js", new Date());gtag("set", "developer_id.dMDhkMT", true);gtag("config", "UA-7402386-1", {"groups":"default","anonymize_ip":true,"page_placeholder":"PLACEHOLDER_page_path"});</script> <meta name="Generator" content="Drupal 9 (https://www.drupal.org)" /> <meta name="MobileOptimized" content="width" /> <meta name="HandheldFriendly" content="true" /> <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no" /> <style>div#sliding-popup, div#sliding-popup .eu-cookie-withdraw-banner, .eu-cookie-withdraw-tab {background: #000000} div#sliding-popup.eu-cookie-withdraw-wrapper { background: transparent; } #sliding-popup h1, #sliding-popup h2, #sliding-popup h3, #sliding-popup p, #sliding-popup label, #sliding-popup div, .eu-cookie-compliance-more-button, .eu-cookie-compliance-secondary-button, .eu-cookie-withdraw-tab { color: #ffffff;} .eu-cookie-withdraw-tab { border-color: #ffffff;}</style> <meta http-equiv="x-ua-compatible" content="ie=edge" /> <link rel="icon" href="/themes/custom/itsoc/images/IT_Fav.ico" type="image/vnd.microsoft.icon" /> <link rel="canonical" href="https://www.itsoc.org/page/information-editors" /> <link rel="shortlink" href="https://www.itsoc.org/node/37229" /> <script>window.a2a_config=window.a2a_config||{};a2a_config.callbacks=[];a2a_config.overlays=[];a2a_config.templates={};a2a_config.icon_color = "#fff,#7F8AAD";</script> <title>Information for Editors | IEEE Information Theory Society</title> <link rel="stylesheet" media="all" href="/sites/default/files/css/css_sY2rm151rYmCkOMVKDfD2re4bFUyyRMJD4ONfnxG-VY.css" /> <link rel="stylesheet" media="all" href="//cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/css/all.min.css" /> <link rel="stylesheet" media="all" href="/sites/default/files/css/css_PquxatLmFK3933sBjjZDZZzQo5M9hiY3HR_yCDsF-T0.css" /> <link rel="stylesheet" media="all" href="/sites/default/files/css/css_GpEn-FmviTzOuZj65etw_EMZ31FSCzyTLozK1tE3Qfo.css" /> <link href="https://fonts.googleapis.com/css2?family=Source+Serif+Pro:wght@300;400;600;700&display=swap" rel="stylesheet"> <link href="https://fonts.googleapis.com/css2?family=Open+Sans:wght@300;400;600;700;800&display=swap" rel="stylesheet"> <link rel="apple-touch-icon" href="/apple-favicon.png"> </head> <body class="layout-no-sidebars page-node-37229 not-logged-in path-node node--type-landing-page"> <a href="#main-content" class="visually-hidden focusable skip-link"> Skip to main content </a> <div class="dialog-off-canvas-main-canvas" data-off-canvas-main-canvas> <div id="page-wrapper" class="microsite-page-wrap"> <div id="page"> <header id="header" class="header micro-sites-header" role="banner" aria-label="Site header"> <div class="top--header"> <div class="container-fluid"> <div class="header-container"> <section class="row region region-secondary-menu"> <nav role="navigation" aria-labelledby="block-itsoc-microsite-secondarymenu--2-menu" id="block-itsoc-microsite-secondarymenu--2" class="block block-menu navigation menu--secondary-menu"> <h2 class="visually-hidden" id="block-itsoc-microsite-secondarymenu--2-menu">Secondary Menu</h2> <ul class="clearfix nav"> <li class="nav-item"> <a href="https://www.ieee.org/" title="IEEE Homepage" class="nav-link nav-link-https--wwwieeeorg-">IEEE Home</a> </li> <li class="nav-item"> <a href="https://ieeexplore.ieee.org/" title="IEEExplore" class="nav-link nav-link-https--ieeexploreieeeorg-">IEEE Xplore Digital Library</a> </li> <li class="nav-item"> <a href="http://standards.ieee.org/" title="IEEE Standards" class="nav-link nav-link-http--standardsieeeorg-">IEEE Standards</a> </li> <li class="nav-item"> <a href="http://spectrum.ieee.org/" title="IEEE Spectrum" class="nav-link nav-link-http--spectrumieeeorg-">IEEE Spectrum</a> </li> <li class="nav-item"> <a href="https://www.ieee.org/sitemap.html" title="More sites" class="nav-link nav-link-https--wwwieeeorg-sitemaphtml">More Sites</a> </li> </ul> </nav> <div class="search-block-form block block-search block-search-form-block" data-drupal-selector="search-block-form-4" id="block-itsoc-microsite-searchform--2" role="search"> <div class="content container-inline"> <div class="content container-inline"> <form action="/itsoc-search" method="get" id="search-block-form--4" accept-charset="UTF-8" class="search-form search-block-form form-row"> <div class="js-form-item js-form-type-search form-type-search js-form-item-search-api-fulltext form-item-search-api-fulltext form-no-label mb-3"> <label for="edit-search-api-fulltext--4" class="visually-hidden">Search</label> <input title="Enter the terms you wish to search for." data-drupal-selector="edit-search-api-fulltext" type="search" id="edit-search-api-fulltext--4" name="search_api_fulltext" value="" size="15" maxlength="128" class="form-search form-control" placeholder="Search" /> </div> <div data-drupal-selector="edit-actions" class="form-actions js-form-wrapper form-wrapper mb-3" id="edit-actions--4"><input data-drupal-selector="edit-submit" type="submit" id="edit-submit--4" value="Search" class="button js-form-submit form-submit btn btn-primary form-control" /> </div> </form> </div> </div> </div> <nav role="navigation" aria-labelledby="block-itsoc-microsite-account-menu--2-menu" id="block-itsoc-microsite-account-menu--2" class="block block-menu navigation menu--account"> <h2 class="visually-hidden" id="block-itsoc-microsite-account-menu--2-menu">User account menu</h2> <div class="clearfix nav"> <a href="/saml_login" class="nav-link nav-link--saml-login">Sign in</a> </div> </nav> </section> </div> </div> </div> <div class="header--inner"> <div class="container-fluid"> <div class="header-container"> <div class="logo--section align-top"> <a href="/it-trans" title="Home" rel="home" class="navbar-brand"> <img src="https://www.itsoc.org/sites/default/files/2021-06/IT%20Soc%20Microsite%20logo%20300%20x%20350.002_1.jpeg" alt="Home" class="micro--site--logo img-fluid d-inline-block" /> </a> </div> <div class="hamburger-icon"><span class="icon-menu-search"></span></div> <div class="menu--section"> <nav class="navbar justify-content-end d-none d-lg-flex" id="navbar-top"> </nav> <nav class="navbar navbar-expand-xl px-0" id="navbar-main"> <div class="navbar-collapse justify-content-end" id="CollapsingNavbar"> <div class="microsite--menu--right"> <div class="search-block-form block block-search block-search-form-block" data-drupal-selector="search-block-form-2" id="block-itsoc-microsite-search" role="search"> <h2>Search</h2> <div class="content container-inline"> <div class="content container-inline"> <form action="/itsoc-search" method="get" id="search-block-form--2" accept-charset="UTF-8" class="search-form search-block-form form-row"> <div class="js-form-item js-form-type-search form-type-search js-form-item-search-api-fulltext form-item-search-api-fulltext form-no-label mb-3"> <label for="edit-search-api-fulltext--2" class="visually-hidden">Search</label> <input title="Enter the terms you wish to search for." data-drupal-selector="edit-search-api-fulltext" type="search" id="edit-search-api-fulltext--2" name="search_api_fulltext" value="" size="15" maxlength="128" class="form-search form-control" placeholder="Search" /> </div> <div data-drupal-selector="edit-actions" class="form-actions js-form-wrapper form-wrapper mb-3" id="edit-actions--2"><input data-drupal-selector="edit-submit" type="submit" id="edit-submit--2" value="Search" class="button js-form-submit form-submit btn btn-primary form-control" /> </div> </form> </div> </div> </div> <div class="header--logos d-none d-lg-flex"> <div class="search-block-form block block-search block-search-form-block" data-drupal-selector="search-block-form-3" id="block-searchform" role="search"> <div class="content container-inline"> <div class="content container-inline"> <form action="/itsoc-search" method="get" id="search-block-form--3" accept-charset="UTF-8" class="search-form search-block-form form-row"> <div class="js-form-item js-form-type-search form-type-search js-form-item-search-api-fulltext form-item-search-api-fulltext form-no-label mb-3"> <label for="edit-search-api-fulltext--3" class="visually-hidden">Search</label> <input title="Enter the terms you wish to search for." data-drupal-selector="edit-search-api-fulltext" type="search" id="edit-search-api-fulltext--3" name="search_api_fulltext" value="" size="15" maxlength="128" class="form-search form-control" placeholder="Search" /> </div> <div data-drupal-selector="edit-actions" class="form-actions js-form-wrapper form-wrapper mb-3" id="edit-actions--3"><input data-drupal-selector="edit-submit" type="submit" id="edit-submit--3" value="Search" class="button js-form-submit form-submit btn btn-primary form-control" /> </div> </form> </div> </div> </div> <div class="ieee-logo pl-3"> <a href="https://www.ieee.org" target="_blank"> <img src="/themes/custom/itsoc/images/ieee.png" alt="IEEE Logo" /> </a> </div> <div class="ieee-logo microsite-logo pl-3"> <a href="https://www.itsoc.org" target="_blank"> <img src="/themes/custom/itsoc/images/logo-microsite.png" alt="ITSOC Logo"/> </a> </div> </div> </div> <div class="d-lg-none"> <div class="row justify-content-end"> <div class="secondary--menu"> <section class="row region region-secondary-menu"> <nav role="navigation" aria-labelledby="block-itsoc-microsite-secondarymenu--2-menu" id="block-itsoc-microsite-secondarymenu--2" class="block block-menu navigation menu--secondary-menu"> <h2 class="visually-hidden" id="block-itsoc-microsite-secondarymenu--2-menu">Secondary Menu</h2> <ul class="clearfix nav"> <li class="nav-item"> <a href="https://www.ieee.org/" title="IEEE Homepage" class="nav-link nav-link-https--wwwieeeorg-">IEEE Home</a> </li> <li class="nav-item"> <a href="https://ieeexplore.ieee.org/" title="IEEExplore" class="nav-link nav-link-https--ieeexploreieeeorg-">IEEE Xplore Digital Library</a> </li> <li class="nav-item"> <a href="http://standards.ieee.org/" title="IEEE Standards" class="nav-link nav-link-http--standardsieeeorg-">IEEE Standards</a> </li> <li class="nav-item"> <a href="http://spectrum.ieee.org/" title="IEEE Spectrum" class="nav-link nav-link-http--spectrumieeeorg-">IEEE Spectrum</a> </li> <li class="nav-item"> <a href="https://www.ieee.org/sitemap.html" title="More sites" class="nav-link nav-link-https--wwwieeeorg-sitemaphtml">More Sites</a> </li> </ul> </nav> <div class="search-block-form block block-search block-search-form-block" data-drupal-selector="search-block-form-4" id="block-itsoc-microsite-searchform--2" role="search"> <div class="content container-inline"> <div class="content container-inline"> <form action="/itsoc-search" method="get" id="search-block-form--4" accept-charset="UTF-8" class="search-form search-block-form form-row"> <div class="js-form-item js-form-type-search form-type-search js-form-item-search-api-fulltext form-item-search-api-fulltext form-no-label mb-3"> <label for="edit-search-api-fulltext--4" class="visually-hidden">Search</label> <input title="Enter the terms you wish to search for." data-drupal-selector="edit-search-api-fulltext" type="search" id="edit-search-api-fulltext--4" name="search_api_fulltext" value="" size="15" maxlength="128" class="form-search form-control" placeholder="Search" /> </div> <div data-drupal-selector="edit-actions" class="form-actions js-form-wrapper form-wrapper mb-3" id="edit-actions--4"><input data-drupal-selector="edit-submit" type="submit" id="edit-submit--4" value="Search" class="button js-form-submit form-submit btn btn-primary form-control" /> </div> </form> </div> </div> </div> <nav role="navigation" aria-labelledby="block-itsoc-microsite-account-menu--2-menu" id="block-itsoc-microsite-account-menu--2" class="block block-menu navigation menu--account"> <h2 class="visually-hidden" id="block-itsoc-microsite-account-menu--2-menu">User account menu</h2> <div class="clearfix nav"> <a href="/saml_login" class="nav-link nav-link--saml-login">Sign in</a> </div> </nav> </section> </div> <div class="header--logos"> <div class="ieee-logo pl-3"> <a href="https://www.ieee.org"> <img src="/themes/custom/itsoc/images/ieee.png" alt="IEEE" /> </a> </div> <div class="ieee-logo microsite-logo pl-3"> <a href="https://www.itsoc.org" target="_blank"> <img src="/themes/custom/itsoc/images/logo-microsite.png" alt="ITSOC Logo"/> </a> </div> </div> </div> </div> </div> </nav> </div> </div> </div> </div> </header> <div class="highlighted"> <aside class="container section clearfix" role="complementary"> <div data-drupal-messages-fallback class="hidden"></div> </aside> </div> <div id="main-wrapper" class="layout-main-wrapper clearfix"> <div id="main" class="container-fluid"> <div class="row row-offcanvas row-offcanvas-left clearfix"> <main class="main-content col order-last" id="content" role="main"> <section class="section"> <a id="main-content" tabindex="-1"></a> <div id="block-itsoc-microsite-breadcrumbs" class="block block-system block-system-breadcrumb-block"> <div class="content container"> <nav role="navigation" aria-label="breadcrumb"> <ol class="breadcrumb"> <li class="breadcrumb-item"> <a href="/it-trans">Home</a> </li> <li class="breadcrumb-item active"> Information for Editors </li> </ol> </nav> </div> </div> <div id="block-itsoc-microsite-content" class="block block-system block-system-main-block"> <div class="content"> <article data-history-node-id="37229" role="article" class="node node--type-landing-page node--promoted node--view-mode-full clearfix"> <header> </header> <div class="node__content clearfix"> <div class="listing--header layout layout--onecol"> <div class="layout__region layout__region--content"> <div class="block block-layout-builder block-field-blocknodelanding-pagetitle"> <div class="content"> <span class="field field--name-title field--type-string field--label-hidden">Information for Editors</span> </div> </div> </div> </div> <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <div class="block block-layout-builder block-field-blocknodelanding-pagebody"> <div class="row mobile--row body--field--block--wrap pt-5 pb-3"> <div class="container"> <div class="content"> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><div class="tex2jax_process"><p>Advice for Associate Editors</p> <p>Thank you for agreeing to serve as an Associate Editor for the <em>IEEE Transactions on Information Theory</em>. While selection as Associate Editor may be seen as a recognition of the high esteem in which you are held by your peers, please note that the position is not merely honorary—there is a lot of work to be done! Our readers are counting upon you to exercise your best judgement, based on your extensive technical expertise, to assist authors in improving the quality of their submitted papers so that the high standard expected of papers published in the <em>Transactions</em> is reached. Your job is a difficult one: you will coordinate the review process for a large number of papers, and for each paper you will be the main point-of-contact for authors, reviewers, the Area Editor and the Editor-in-Chief. The position, though voluntary, is time-consuming: be prepared to spend many hours reading papers, reading emails, chasing reviewers, and writing careful assessments and responses. You can expect to spend about 6 to 8 hours per week on Associate Editorial tasks, though naturally the load will be time-varying, and you will become more efficient as you gain experience.</p> <h2>Generalities</h2> <p>In coordinating the review process for each paper assigned to you by an Area Editor, your main loyalty must be to the <strong>reader</strong> of the <em>Transactions</em>. As noted in the <a href="http://trans-it.ece.umd.edu/reviewer-info.html">Information for Reviewers</a>, the suitability of a paper for publication must be assessed based on three criteria (two of them objective and one subjective), which, loosely speaking, can be phrased as follows: is the paper <strong>new</strong>?; <strong>correct</strong>?; <strong>interesting</strong>?</p> <p>Novelty and correctness are obvious attributes that any newly published paper must possess. Novelty is a measure of the <em>results</em> and <em>ideas</em> of the paper: a paper can be considered novel if it contains a new result (even if the result flows from the application of well-known techniques) or if it contains a new idea (even if the idea merely reveals a simpler way to understand an old result).</p> <p>The third question—is the paper interesting?—requires judgement and familiarity with the community served by the <em>Transactions</em>. The question might also be phrased as “does it matter?” or “will it make a difference?” or “is it useful?” Of course this is a subjective criterion (after all, what is interesting to one person may not be interesting to another); what is intended by this question is whether or not the paper, if published, will serve the needs of the readership of the <em>Transactions</em>. The information for authors states that</p> <blockquote>“novelty alone does not assure publication; the significance of a paper and its usefulness to this <em>Transactions</em>' readership will also be assessed.”</blockquote> <p>For example, a paper with new and correct results that are, however, purely of mathematical interest, without any engineering provenance or significance, may be deemed outside the scope of this <em>Transactions</em>, and the authors re-directed to a suitable Mathematics journal. On the other hand, a paper that advances a well-recognized mathematical problem initially motivated by Information Theory and studied by members of our community, would certainly be deemed interesting.</p> <p> </p> <p>When a paper does satisfy the three central criteria, a final measure that must be assessed is that of <strong>length</strong>: is the length of the paper commensurate with the contribution that it makes? The <em>Transactions</em> imposes no page limits, and papers can range in length from 2 or 3 pages to more than 20. Short well-focused papers that make an important point briefly are certainly acceptable, and should not be lengthened unnecessarily. Authors should be discouraged from padding their papers by adding superfluous examples or excessively many simulation plots.</p> <p>As an Associate Editor, you also have specific responsibilities towards the <strong>authors</strong>. You must strive to:</p> <ul><li>provide unbiased feedback in a timely manner, giving comments and making decisions that are supported by a suitable rationale;</li> <li>respond promptly and politely to author queries;</li> <li>avoid personal comments or criticism;</li> <li>maintain confidentiality of the content of the paper, and avoid using confidential information for your own purposes or for the advantage of others.</li> </ul><p>While fairness is of paramount concern in dealing with authors, please do note the emphasis on timeliness and civility: a lack of responsiveness, or providing responses which are curt or perfunctory, invariably lead to author complaints to the EiC, who must then intervene. The cumulative load of such interventions detracts unnecessarily from useful EiC functions.</p> <p> </p> <p>In interacting with <strong>reviewers</strong>, you have a duty to:</p> <ul><li>preserve the anonymity of the reviewers;</li> <li>preserve the integrity of the review process by communicating the reviewers' comments to the authors without editing them;</li> <li>refrain from always asking a particular reviewer to provide comments on papers from a particular group of authors.</li> </ul><p>Associate Editors also have specific responsibilities towards the <strong>Editor-in-Chief</strong> and <strong>Area Editors</strong>. AEs must:</p> <ul><li>alert the Area Editor and EiC promptly about possible conflicts of interest;</li> <li>notify the Area Editor and EiC promptly if circumstances arise that make it impossible to complete the handling of the paper in a timely manner;</li> <li>inform the Area Editor and EiC of any festering disagreement with authors;</li> <li>notify the Area Editor and EiC promptly with any ethical concerns.</li> </ul><p> </p> <h2>Specifics</h2> <p>As of 2021, the <em>IEEE Transactions on Information Theory</em> receives approximately 100 submissions per month. Submissions occur online via the <a href="https://mc.manuscriptcentral.com/t-it">ScholarOne Manuscripts</a> (S1M) web site. A small number of submissions are out-of-scope, and will be rejected immediately by the Area Editor (RE). Taking into account the subject of the paper and the current load of each AE, the remaining papers are assigned by the RE to an Associate Editor for handling. Each AE will end up being assigned about 2 to 3 papers per month, though these numbers may fluctuate from month to month and may be larger near the beginning of your term. You may occasionally be assigned a paper that is not directly within your main area of expertise, but usually not so far away that you are not able to identify appropriate referees for the paper. If it happens that you are assigned a paper that you cannot or wish not to handle, please alert the RE immediately so that the paper can be re-assigned promptly.</p> <h3>The Paper is Assigned</h3> <p>You will be notified by an email from the Area Editor, sent via S1M, whenever a paper is assigned to you. Each paper is assigned a unique identifier of the form IT-YY-NNNN[.Rr], where YY identifies the year of submission, NNNN is a number that increments by one for each manuscript received, and [.Rr] is a suffix, not present on the original submission, that identifies the<em> revision </em>number, i.e., .R1 for the first <em>revision</em>, .R2 for the second <em>revision</em>, and so on. Normally <em>all</em> steps of the paper-handling process, including all official correspondence with the authors and with reviewers, should be conducted via S1M. Each action (assignment to an AE, inviting a reviewer, sending an email, changing the status of a paper) is carefully recorded by S1M in the audit trail associated with the paper. This audit trail is accessible, for the papers assigned to you, through your S1M Associate Editor Center. Please note that email communications made outside of the S1M system can always be added to the official record by “cutting-and-pasting”; if needed, the Transactions Administrative Assistant can assist with this.</p> <p>Although the paper-assignment letters are derived from a standard template (and all look much the same) please read each one carefully, as often the RE will have included possible comments on the quality or contribution the paper, or will have included suggestions for possible reviewers. (Should you accidentally delete the email, don't worry: you can always recover it from the audit trail.)</p> <h3>First Reading</h3> <p>When a paper is assigned, after carefully noting any comments from the Area Editor in the assignment letter, your first step is to read through the paper. In this initial scan of the paper, you should not attempt to read the paper carefully for correctness, but just read it to get a sense of the scope of the results. You should examine the list of references to see which previous papers are being cited. The journals and conferences cited serve as an indicator of the readership that the paper addresses and as a measure of the degree to which the paper fits the <em>Transactions</em> (or, possibly, a different journal). You should also check to see whether the authors have included a cover letter or any other supplementary material, and read through this material, if present. Although cover letters are not always present, it is expected that authors will provide such a letter in case the paper is a<em> revision </em>of a previous submission. Indeed, inclusion of such a letter is <strong>mandatory</strong> if the paper is a<em> resubmission </em>of one previously rejected by the <em>Transactions</em>. Such a letter should indicate, in detail, the manner of <em>revision</em>, or, in the latter case, how the issues that led to the rejection of the previous manuscript have been addressed. In the case of <em>resubmission</em>, failure to include such a letter can be the sole reason for immediate rejection, and in some circumstances might even lead to a publication ban.</p> <p>After your initial reading of the paper, you may decide to take one of three actions:</p> <ul><li>Inform the Area Editor that you are unable to handle the paper because of a conflict of interest, or because the paper is too far outside the domain of your expertise.</li> <li>Initiate an <strong>“immediate rejection (IR)</strong>”, because the paper clearly does not meet the high standards of the <em>Transactions</em> (for example, it could be poorly written, out-of-scope, unlikely to interest the <em>Transactions</em>' readership, or present a trivial or well-known result). More on immediate rejections <a href="http://trans-it.ece.umd.edu/ae-info.html#FASTREJ">below</a>.</li> <li>Send the paper out for review. This is the normal course of action.</li> </ul><h3>Immediate Rejections</h3> <p>The <a href="https://www.ieee.org/documents/opsmanual.pdf">IEEE Publication Services and Products Board Operations Manual</a> states, in Section 8.8.2.A.3, that an article may be “prescreened,” i.e., immediately rejected, when the authors have (a) not followed IEEE guidelines for style, (b) have not adhered to IEEE policies, (c) have submitted an incomprehensible article, (d) have submitted an article whose subject and contents do not meet the scope of the journal, or (e) have submitted an article that does not meet the minimum criterion for technical substance established for the periodical. Rejection under criterion (e) requires concurrence of the EiC and at least two other members of the editorial board. Thus, under these rules, an immediate rejection under criterion (e) can occur with the concurrence of three individuals: for the <em>IT Transactions</em>, these could be: (i) two Area Editors and the EiC, (ii) the Area Editor, and the AE handling the paper (if one has been assigned), and the EiC.</p> <p>If the second route is followed for the immediate rejection, the AE carefully reads the paper, and writes a thorough draft rationale explaining the reasons for rejection. The AE sends the draft rationale to both the EiC and the Area Editor for comments and concurrence. The EiC and Area Editor also read the paper and provide comments on the rationale. Only when all three individuals agree that indeed a immediate rejection is appropriate, can the paper then be rejected without sending it out for further review. <strong>The rejection letter to the authors can only come from the Area Editor or the EiC</strong>; the AE workspace on ScholarOne does not provide the option for immediate rejection. Should there be disagreement about the immediate rejection decision, the paper must be sent out for review following the usual procedures.</p> <p>Immediate rejections should normally be executed within 10 business days of receiving the paper assignment.</p> <h3>Inviting Reviewers</h3> <p>Apart from communicating editorial decisions, reviewer selection is probably the most important task of an Associate Editor. A misstep here will lead to delays, frustration, and author complaints. It is therefore advisable to think carefully about whom to invite. The ideal reviewer is probably somebody currently active in the given area, who is up to date on recent developments, and who will read the paper in depth, providing detailed suggestions for improvement. It is often useful to invite a mixture of senior and junior referees. Senior reviewers are able to provide broad perspectives and insight and often can make helpful connections to related areas. More junior referees, particularly those who are actively working on the topic, will be able to provide detailed comments about the contributions of the paper. Outstanding senior doctoral students working on a given topic can and should be selected as reviewers, but it would be unwise to rely solely on student reviewers for any given paper. Many potential reviewers will already have a history of reviewing for the <em>Transactions</em>; through S1M, AEs can see which papers each reviewer has reviewed in the past, which can be helpful to get a sense of the reviewer's load and responsiveness.</p> <p>The <a href="https://www.ieee.org/documents/opsmanual.pdf">IEEE Publication Services and Products Board Operations Manual</a> states, in Section 8.8.2.A.4, that for all scientific articles submitted (excluding those that are prescreened), the AE shall select at least two referees who are competent and have experience in the area of the subject matter of the article. Thus, a <strong>minimum</strong> of two independent reviews are required for each article. Usually, though, three (and, in rare cases, four) reviews are obtained.</p> <p>The process of reviewer selection in S1M is quite straightforward. There are three stages: <strong>select</strong> (create a list of reviewers whom you would like to invite), <strong>invite</strong> (actually send out letters of invitation), and <strong>assign</strong> (the reviewer is assigned to the paper only upon the reviewers' agreement to take on the review; this happens automatically). You will find papers in their various states in the “Associate Editor Lists” section of your AE Center: the dashboard will provide summary numbers of how many papers have a certain status.</p> <p>Ordinarily, AEs should refrain from soliciting “informal reviews”; all reviews for a paper should follow the formal procedure outlined above. Occasionally, however, it may be useful to <em>supplement</em> the formal reviews with a quick and informal expert review targeting a specific aspect of the paper, or providing a broad perspective, particularly if such viewpoints are lacking in the formal reviews. Some reviewers will not respond quickly to requests, in which case some follow-up may be needed. Three business days is a normal period to allow for a response. If a reviewer who agreed to volunteer their time is no longer available or responsive, please feel free to reach out to a new reviewer.</p> <p>Reviewer assignments (i.e., the complete select, invite, and assign process for at least three reviewers) should normally be completed within 10 business days of receiving the paper.</p> <h3>Awaiting Reviewer Scores</h3> <p>Reviewers are normally asked to submit their comments within 60 (calendar) days in which to carry out a first review. Some reviewers will ask for a longer period of time; if the request is reasonable, please grant it. Otherwise, please invite a different reviewer instead.</p> <p>S1M will automatically send reminders to reviewers on your behalf (three days before the reminder, S1M will inform you of this, and you have the option not to send the reminder). Despite such reminders, you will certainly encounter situations where some reviewers have not uploaded a review prior to the deadline; in this case the paper will enter the “Overdue Reviewer Scores” status. Although a brief grace period can probably be granted, you should certainly follow up with the reviewers if you have not heard back from them within five business days of the missed review deadline. If the reviewer does not communicate, promptly invite another reviewer or move on to making an editorial decision. Should the promised review materialize eventually, it can be forwarded to the author at a later date. If you receive a perfunctory review, you might ask the reviewer to provide more detailed comments on a particular aspect of the paper, or simply invite yet another reviewer. Occasionally, you may need to call in a favor for a quick review from a trusted colleague, or, as a last resort, after consulting with the RE and EiC, assign the paper to yourself. Ordinarily, reviews are passed unedited to the authors; however, in rare cases—for example if you find that the review contains inflammatory language—you may wish to ask the reviewer to amend the review.</p> <h3>Making Decisions</h3> <p>Associated with each paper on S1M is a selectable value “# reviews required to make decision”: once this number of reviews has been received, the paper enters the “Awaiting AE Decision” status. Should you give up on waiting for a long-promised review, you may decrease this value, but ideally it should not drop below 2. You should strive to make an editorial decision within five business days of receiving the last review.</p> <p>When handling a paper, <strong>you</strong> are the executive; the role of the reviewers is solely advisory. In particular, the editorial process is <strong>not</strong> democratic; reviewers do not get votes. <strong>You</strong> must weigh the input you receive, as you see fit, to arrive at an appropriate editorial decision. You should refrain from becoming a relay in a channel between the authors and reviewers, and you should not necessarily feel compelled to align yourself with the majority opinion.</p> <p>Note that it will be impossible to read each paper under your purview at the same depth as a reviewer—you simply won't have enough time. Thus, to a certain extent you must rely on reviewers whose opinion you trust. You should certainly read the paper carefully enough to be able to defend your eventual decision, particularly in cases where there are conflicting reviews. You may find that you have concerns about a paper that are not reflected in any of the reviews; you can and should express these concerns in your decision letter.</p> <p>Remember that your first loyalty is to the reader of the <em>Transactions</em>, and that a paper can be accepted only if it is <strong>new</strong>, <strong>correct</strong>, and <strong>interesting</strong>. Your role is not that of a goal-keeper (keeping the ball out of the net), but rather that of a judge who decides whether the paper has achieved the high standard expected of papers published in the <em>IEEE Transactions on Information Theory</em>. Think of yourself as a curator (from Latin, <em>curare</em>, meaning “to take care”) of papers that will be archived in perpetuity, and strive to include papers in the archive only when they have something to add to the developing record of the field.</p> <p>For each paper, you must arrive at an editorial decision: either accept, reject, or revise-and-<em>resubmit</em>. As an experienced author, you are well acquainted with the type of decision letter that is most effective. You should not simply repeat the comments of the reviewers, as the authors can read these for themselves. Always be polite. A thoughtful decision letter, like a thorough review, will be seen by the authors as helpful (even in cases when the paper is rejected). If appropriate, feel free to commend—in the decision letter itself—one or more of the reviewers for a job well done.</p> <p>Writing letters that accept a paper is generally easy; the authors will certainly be happy. Rejections are more difficult. When communicating a rejection decision, please take the time to write a convincing rationale, expressed politely, but firmly. If the paper is to be rejected, reject it thoroughly. If you have doubts about the decision, or simply wish to have feedback on a draft letter, feel free to consult the Area Editor and the EiC.</p> <p>In many cases, you will need to write a letter requesting a<em> revision </em>of the paper. Do so only if you genuinely believe that the paper can eventually be<em> revised </em>to a publishable state. If not, the paper should be rejected right away. You can remind the authors that they are always free to<em> resubmit </em>a rejected paper if they are able to address the concerns that were raised in the review. Request a<em> revision </em>only if the required changes are relatively minor and do not entail a material transformation of technical content; else, a new submission is warranted. Always remind the authors to include a detailed cover letter with any<em> revision </em>or <em>resubmission</em>.</p> <p>If indeed there is good evidence that the paper can be published after a relatively minor <em>revision</em>, please give the authors clear and concrete advice as to what you expect to see. If you seek a reduction in length, give <em>specific</em> advice as to which particular sections can be reduced, and how. While the authors are, necessarily, the primary audience of a decision letter, consider writing it also for your own future reference, so that it provides a convenient record for what needs to be checked in a subsequent <em>revision</em>. You should keep in mind that the EiC will also read the decision letter, and may occasionally comment.</p> <p>In most cases, if a paper is returned after a relatively minor <em>revision</em>, and <strong>you</strong> are satisfied that the authors have addressed the concerns of the reviewers, you do <strong>not</strong> need to send the paper out for another round of reviews. Send the paper out for subsequent rounds of review only if there remains doubt as to the acceptability of the paper.</p> <p>Sometimes you may wish to give the authors an opportunity to rebut the comments of a reviewer. Revise-and-<em>resubmit</em> is the usual mechanism for this. Please be clear and unambiguous about key concerns that should be addressed. The authors have the option to withdraw the paper should they be unable to address the given concern.</p> <h3>The Final Manuscript</h3> <p>At the time of accepting a paper, feel free to provide the authors with concrete advice for how they might improve the non-technical aspects of the paper. For example:</p> <ul><li>Ask the authors to update references to available published versions of papers cited (and not just earlier preprint or arXiv versions)</li> <li>Double-check the paper for English usage</li> <li>Give specific advice, if needed, for improving the quality of figures or figure captions</li> </ul><p>When the authors return the final manuscript, examine it to ensure that the authors have not made major (unreviewed) amendments. If all looks fine, you will need to complete a Checklist, and enter the paper into the publication queue. If you deem a paper to be of potentially award-winning quality (even if it is too “fresh” to judge impact), please record this in the AE Checklist with a paragraph or two explaining your reasons, and then notify the EiC and Area Editor of your action. Such assessments are valuable for identifying deserving papers later for appropriate recognition.</p> <p>The final checking stage should normally be completed within 3 business days after the final manuscript is uploaded by the authors.</p> <h2>Communicating with Authors</h2> <p>It is preferable that communication between the AEs and the authors be done through the ScholarOne workspace or directly via email. If the author/s call you or request a phone or video conference call to discuss the decision, please decline. All communication with the authors should be recorded in an email trail or on ScholarOne. If the authors are unhappy with your decision, you may let them know that they can submit an official appeal to the Editor-in-Chief. </p> <h2>Last Words of Advice</h2> <p>The job of an Associate Editor is a difficult and lonely one. Feel free to call upon the Editor-in-Chief and Area Editor when you have need of advice or encouragement. Feel free to push back when you feel that new papers to handle have been arriving too quickly. Advise the Area Editor immediately when circumstances arise that may affect your ability to handle papers (if absolutely needed, you may request a brief—one or two month—respite from receiving new submissions). Finally, take courage; the <em>Transactions</em> reader is depending upon you!</p> <h2>Links</h2> <p> </p> <ul><li>An S1M <a href="http://mchelp.manuscriptcentral.com/gethelpnow/tutorials/Editor.pdf">Editor User Guide</a> is available, but most features of the system should be quite self-explanatory.</li> <li>The <a href="https://www.ieee.org/documents/opsmanual.pdf">IEEE PSPB Operations Manual</a></li> <li><a href="http://trans-it.ece.umd.edu/TIT-FinalSubmissions.pdf">LaTeX Advice for Authors Preparing Final Manuscripts</a>. Feel free to point authors here.</li> </ul></div></div> </div> </div> </div> </div> </div> </div> </div> </article> </div> </div> </section> </main> </div> </div> </div> <footer class="pt-5 px-4 px-lg-5 site-footer"> <div class="container"> <div class="site-footer__top clearfix"> <div class="footer--first py-4"> <section class="row region region-footer-first"> <nav role="navigation" aria-labelledby="block-itsoc-microsite-footer-menu" id="block-itsoc-microsite-footer" class="block block-menu navigation menu--footer"> <h2 class="visually-hidden" id="block-itsoc-microsite-footer-menu">Footer menu</h2> <ul class="clearfix nav navbar-nav"> <li class="nav-item"> <a href="/" class="nav-link nav-link--" data-drupal-link-system-path="<front>">Home</a> </li> <li class="nav-item"> <a href="/form/contact" class="nav-link nav-link--form-contact" data-drupal-link-system-path="webform/contact">Contact</a> </li> <li class="nav-item"> <a href="https://www.ieee.org/accessibility-statement.html" title="Accessibility statement" class="nav-link nav-link-https--wwwieeeorg-accessibility-statementhtml">Accessibility</a> </li> <li class="nav-item"> <a href="https://www.ieee.org/about/corporate/governance/p9-26.html" title="Nondiscrimination Policy" class="nav-link nav-link-https--wwwieeeorg-about-corporate-governance-p9-26html">Nondiscrimination Policy</a> </li> <li class="nav-item"> <a href="https://www.ieee.org/security-privacy.html" title="IEEE Privacy Policy" class="nav-link nav-link-https--wwwieeeorg-security-privacyhtml">IEEE Privacy Policy</a> </li> <li class="nav-item"> <a href="/help" class="nav-link nav-link--help" data-drupal-link-system-path="node/33720">Help</a> </li> </ul> </nav> </section> </div> <div class="footer--second"> <section class="row region region-footer-second"> <div id="block-itsoc-microsite-socialmedialinks" class="block-social-media-links block block-social-media-links-block"> <div class="content"> <ul class="social-media-links--platforms platforms inline horizontal"> <li> <a class="social-media-link-icon--twitter" href="https://www.twitter.com/itsoc" > <span class='fab fa-twitter fa-lg'></span> </a> </li> <li> <a class="social-media-link-icon--googleplus" href="https://plus.google.com/itsoc" > <span class='fab fa-google-plus fa-lg'></span> </a> </li> <li> <a class="social-media-link-icon--instagram" href="https://www.instagram.com/itsoc" > <span class='fab fa-instagram fa-lg'></span> </a> </li> <li> <a class="social-media-link-icon--youtube" href="https://www.youtube.com/itsoc" > <span class='fab fa-youtube fa-lg'></span> </a> </li> <li> <a class="social-media-link-icon--facebook" href="https://www.facebook.com/itsoc" > <span class='fab fa-facebook fa-lg'></span> </a> </li> </ul> </div> </div> </section> </div> </div> <div class="site-footer__bottom pt-4"> <section class="row region region-footer-third"> <div id="block-itsoc-microsite-footercopyrights" class="block block-block-content block-block-content196c0c5e-1b10-45e7-bdfd-962bf218b8b1"> <div class="content"> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><div class="tex2jax_process"><div class="copy--rights"> <div>© Copyright 2021 IEEE – All rights reserved. Use of this website signifies your agreement to the IEEE Terms and Conditions.</div> <div>A not-for-profit organization, IEEE is the world’s largest technical professional organization dedicated to advancing technology for the benefit of humanity.</div> </div> </div></div> </div> </div> </section> </div> </div> </footer> </div> </div> </div> <script type="application/json" data-drupal-selector="drupal-settings-json">{"path":{"baseUrl":"\/","scriptPath":null,"pathPrefix":"","currentPath":"node\/37229","currentPathIsAdmin":false,"isFront":false,"currentLanguage":"en"},"pluralDelimiter":"\u0003","suppressDeprecationErrors":true,"ajaxPageState":{"libraries":"addtoany\/addtoany.front,better_local_tasks\/local-tasks,bootstrap_barrio\/breadcrumb,bootstrap_barrio\/global-styling,bootstrap_barrio\/node,eu_cookie_compliance\/eu_cookie_compliance_default,google_analytics\/google_analytics,improved_multi_select\/ims,itsoc\/global-styling,itsoc\/owl-carousel,itsoc_microsite\/it_trans,itsoc_microsite\/microsites,layout_discovery\/onecol,mathjax\/config,mathjax\/setup,mathjax\/source,social_media_links\/fontawesome.component,social_media_links\/social_media_links.theme,system\/base,webform\/webform.dialog","theme":"itsoc_microsite","theme_token":"eZZaQyYcOY1EbOFi7jHkr9MDWo7XuAH0q3D-UXyAxj8"},"ajaxTrustedUrl":{"\/itsoc-search":true},"google_analytics":{"account":"UA-7402386-1","trackOutbound":true,"trackMailto":true,"trackDownload":true,"trackDownloadExtensions":"7z|aac|arc|arj|asf|asx|avi|bin|csv|doc(x|m)?|dot(x|m)?|exe|flv|gif|gz|gzip|hqx|jar|jpe?g|js|mp(2|3|4|e?g)|mov(ie)?|msi|msp|pdf|phps|png|ppt(x|m)?|pot(x|m)?|pps(x|m)?|ppam|sld(x|m)?|thmx|qtm?|ra(m|r)?|sea|sit|tar|tgz|torrent|txt|wav|wma|wmv|wpd|xls(x|m|b)?|xlt(x|m)|xlam|xml|z|zip","trackColorbox":true},"improved_multi_select":{"selectors":["select[multiple]"],"filtertype":"partial","placeholder_text":"","orderable":false,"js_regex":false,"groupresetfilter":false,"remove_required_attr":false,"buttontext_add":"\u003E","buttontext_addall":"\u00bb","buttontext_del":"\u003C","buttontext_delall":"\u00ab","buttontext_moveup":"Move up","buttontext_movedown":"Move down"},"mathjax":{"config_type":1,"config":{"tex2jax":{"inlineMath":[["$","$"],["\\(","\\)"]],"processEscapes":"true"},"showProcessingMessages":"false","messageStyle":"none"}},"webform":{"dialog":{"options":{"narrow":{"title":"Narrow","width":600},"normal":{"title":"Normal","width":800},"wide":{"title":"Wide","width":1000}},"entity_type":"node","entity_id":"37229"}},"eu_cookie_compliance":{"cookie_policy_version":"1.0.0","popup_enabled":true,"popup_agreed_enabled":false,"popup_hide_agreed":false,"popup_clicking_confirmation":false,"popup_scrolling_confirmation":false,"popup_html_info":"\u003Cdiv aria-labelledby=\u0022popup-text\u0022 class=\u0022eu-cookie-compliance-banner eu-cookie-compliance-banner-info eu-cookie-compliance-banner--opt-in\u0022\u003E\n \u003Cdiv class=\u0022popup-content info eu-cookie-compliance-content\u0022\u003E\n \u003Cdiv id=\u0022popup-text\u0022 class=\u0022eu-cookie-compliance-message\u0022 role=\u0022document\u0022\u003E\n \u003Ch2\u003EIEEE websites place cookies on your device to give you the best user experience. By using our websites, you agree to the placement of these cookies. To learn more, read our \u003Ca href=\u0022https:\/\/www.ieee.org\/security-privacy.html\u0022\u003EPrivacy policy\u003C\/a\u003E\u003C\/h2\u003E\n\n \u003C\/div\u003E\n\n \n \u003Cdiv id=\u0022popup-buttons\u0022 class=\u0022eu-cookie-compliance-buttons\u0022\u003E\n \u003Cbutton type=\u0022button\u0022 class=\u0022agree-button eu-cookie-compliance-secondary-button\u0022\u003EAccept \u0026amp; Close\u003C\/button\u003E\n \u003Cbutton type=\u0022button\u0022 class=\u0022decline-button eu-cookie-compliance-default-button\u0022\u003EClose\u003C\/button\u003E\n \u003C\/div\u003E\n \u003C\/div\u003E\n\u003C\/div\u003E","use_mobile_message":false,"mobile_popup_html_info":"\u003Cdiv aria-labelledby=\u0022popup-text\u0022 class=\u0022eu-cookie-compliance-banner eu-cookie-compliance-banner-info eu-cookie-compliance-banner--opt-in\u0022\u003E\n \u003Cdiv class=\u0022popup-content info eu-cookie-compliance-content\u0022\u003E\n \u003Cdiv id=\u0022popup-text\u0022 class=\u0022eu-cookie-compliance-message\u0022 role=\u0022document\u0022\u003E\n \n \u003C\/div\u003E\n\n \n \u003Cdiv id=\u0022popup-buttons\u0022 class=\u0022eu-cookie-compliance-buttons\u0022\u003E\n \u003Cbutton type=\u0022button\u0022 class=\u0022agree-button eu-cookie-compliance-secondary-button\u0022\u003EAccept \u0026amp; Close\u003C\/button\u003E\n \u003Cbutton type=\u0022button\u0022 class=\u0022decline-button eu-cookie-compliance-default-button\u0022\u003EClose\u003C\/button\u003E\n \u003C\/div\u003E\n \u003C\/div\u003E\n\u003C\/div\u003E","mobile_breakpoint":768,"popup_html_agreed":false,"popup_use_bare_css":false,"popup_height":"auto","popup_width":"100%","popup_delay":1000,"popup_link":"\/node\/75","popup_link_new_window":true,"popup_position":false,"fixed_top_position":true,"popup_language":"en","store_consent":false,"better_support_for_screen_readers":false,"cookie_name":"","reload_page":false,"domain":"","domain_all_sites":false,"popup_eu_only":false,"popup_eu_only_js":false,"cookie_lifetime":100,"cookie_session":0,"set_cookie_session_zero_on_disagree":0,"disagree_do_not_show_popup":false,"method":"opt_in","automatic_cookies_removal":true,"allowed_cookies":"","withdraw_markup":"\u003Cbutton type=\u0022button\u0022 class=\u0022eu-cookie-withdraw-tab\u0022\u003EPrivacy settings\u003C\/button\u003E\n\u003Cdiv aria-labelledby=\u0022popup-text\u0022 class=\u0022eu-cookie-withdraw-banner\u0022\u003E\n \u003Cdiv class=\u0022popup-content info eu-cookie-compliance-content\u0022\u003E\n \u003Cdiv id=\u0022popup-text\u0022 class=\u0022eu-cookie-compliance-message\u0022 role=\u0022document\u0022\u003E\n \u003Ch2\u003EWe use cookies on this site to enhance your user experience\u003C\/h2\u003E\n\u003Cp\u003EYou have given your consent for us to set cookies.\u003C\/p\u003E\n\n \u003C\/div\u003E\n \u003Cdiv id=\u0022popup-buttons\u0022 class=\u0022eu-cookie-compliance-buttons\u0022\u003E\n \u003Cbutton type=\u0022button\u0022 class=\u0022eu-cookie-withdraw-button \u0022\u003EWithdraw consent\u003C\/button\u003E\n \u003C\/div\u003E\n \u003C\/div\u003E\n\u003C\/div\u003E","withdraw_enabled":false,"reload_options":0,"reload_routes_list":"","withdraw_button_on_info_popup":false,"cookie_categories":[],"cookie_categories_details":[],"enable_save_preferences_button":true,"cookie_value_disagreed":"0","cookie_value_agreed_show_thank_you":"1","cookie_value_agreed":"2","containing_element":"body","settings_tab_enabled":false,"olivero_primary_button_classes":"","olivero_secondary_button_classes":"","close_button_action":"close_banner","open_by_default":true,"modules_allow_popup":true,"hide_the_banner":false,"geoip_match":true},"user":{"uid":0,"permissionsHash":"2bf5427da4c4f216ae510b60abe4485fa8abb96c2045dab1a2b106f8d96053f3"}}</script> <script src="/sites/default/files/js/js_lrVDSetPbHRUiqsljDQW_kWPeMXwhC6Lri5jAVpXXHY.js"></script> <script src="https://static.addtoany.com/menu/page.js" async></script> <script src="/sites/default/files/js/js_VhHd6WgNP8Ifk95pI2L_5nx7AUIyTrFJG25-mkWRRFs.js"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.0/MathJax.js?config=TeX-AMS-MML_HTMLorMML"></script> <script src="/sites/default/files/js/js_qQFwpOKBMST-UbSYAZfRB2Lt29beY6iZSUEG82GZ7ow.js"></script> <script src="/modules/contrib/eu_cookie_compliance/js/eu_cookie_compliance.min.js?v=9.5.11" defer></script> <script src="/sites/default/files/js/js_axLZASNquLR-V87mkWuM-txM1CIoT9lkOo9kDJb8D3I.js"></script> </body> </html>