Date: Tue, 19 Mar 2024 14:04:08 +0000 (UTC) Message-ID: <213725772.888.1710857048209@localhost> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_887_138367151.1710857048209" ------=_Part_887_138367151.1710857048209 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Comments submitted through the Cochrane Library are received by the Edit= orial and Methods Department (EMD) Comments Support team, who will act with= in two working days of receipt. Comments that are not about the Cochrane Re= view (e.g. comments about the website functionality, access, or display) or= are offensive, nonsensical, spam or duplicates will be dealt with by the C= omments Support team. All other comments will be sent to the Managing Edito= r and Feedback Editor of the relevant Cochrane Review Group (CRG).
The Feedback Editor assesses the comment and decides:
The Feedback Editor and the Managing Editor should agree the appropriate= course of action and share this and the comment with all the review author= s.
The Feedback Editor should respond promptly to the comment contributor t= o acknowledge receipt, thanking the contributor, and explaining what the ne= xt steps will be, with a timeline.
The review may or may not be amended or updated, or in extreme cases, wi= thdrawn, in response to a comment.
If the comment does prompt a change to the review, the Managing Editor w= ill make relevant changes as agreed with the review authors and the Feedbac= k Editor. The contributor should be informed of the outcome.
The Feedback Editor responds to the contributor informing them of the de= cision and give a brief explanation.
Minor comments could include spelling or typographic errors, make very g= eneral statements, or may be requests about the review or its status. Minor= comments are not normally published unless the comment (or its response) o= ffers insight or interest to readers, or an opportunity to provide useful c= larification.
The Feedback Editor responds to the contributor informing them of the ac= tion taken.
It may be appropriate to thank the contributor in the Acknowledgements s= ection of the Review.
It is important that substantive comments are published as soon as possi= ble, unless the CRG has a compelling reason not to do so, or if the contrib= utor does not wish the comment to be published. Examples of comments that m= ight not be published are those where it becomes apparent that the contribu= tor is clearly mistaken, or when the CRG has a reason to believe that the c= ontributor has a significant, undeclared conflict of interest. The Feedback= Editor should raise concerns about conflict of interest with the contribut= or. All substantive comments should be published within three weeks after s= ubmission.
A response from the review authors is usually sought and should be publi= shed subsequently. Review authors' responses should be confined to comments= about the review itself and should relate directly to the content of the c= omment. In some cases it may be more appropriate for one of the CRG editori= al team to respond.
The key steps are:
CRGs should aim to publish substantive comments within three weeks follo= wing Comment submission.
In some cases the comment may be edited or summarized (for example if th= e comment is particularly long with repetitious content, or it goes outside= the scope of the review being commented on) by the Feedback Editor, who wi= ll send the revised version to the comment contributor, informing them of t= he intention to publish the revised version. The contributor will have alre= ady consented to editing and publication of the comment when they submitted= the Comment, so this is a courtesy,
A substantive Comment should be published on the Cochrane Library, and t= he CRG should aim to publish it within three weeks of its submission.
To publish a Comment the CRG should indicate this to the Comments Suppor= t team via the Support ticketing email. The team will then publish the Comm= ent on the Cochrane Library, and notify about publication via the same Coch= rane Support ticketing email once this is done.
When the Comment is published the comment contributor receives an automa= ted notification.
The Comment is displayed in the =E2=80=98Read comments on this review=E2= =80=99 section of a review on the Cochrane Library.
Responses to the original comment should be submitted as new comments us= ing the Commenting system from the review on= the Cochrane Library, making sure to clearly indicate which Comment is= being responded to; for example, by addressing the commenter and the Comme= nt title. There will be one named author of the response as per the form fi= lled in on the Cochrane Library. The publication process will be managed by= the Comments Support team. The original commentor will not receive any aut= omated notification about a response being published.
If the CRG is concerned about too much time elapsing before responding, = they can publish a holding statement; for example, =E2=80=9Cwe thank [comme= nter] for their comments, and the review authors will be responding in due = course etc.=E2=80=9D
If the authors do not wish to respond or are unable to respond, the CRG = can respond appropriately to the comment in their place. In certain cases, = the Editor in Chief or a member of the EMD may publish a response to a Comm= ent.
Comments are no longer managed in RevMan. Older comments dating from whe= n comments were previously managed in RevMan, can be deleted from RevMan on= ce they have been published on the Cochrane Library. The comments have thei= r own DOI and version history; and exist independently of the review.