Personal tools
You are here: Home → Projects → The IMS → IMS Bulletins → IMS Bulletin #55 (8 June 2007)
 

IMS Bulletin #55 (8 June 2007)

Index

  1. Tip: Searching archived IMS Bulletins for information
  2. Centralised copy editing in Archie
  3. Report on Archie module submission for Issue 3, 2007
  4. Authors who are testing RevMan 5
  5. Questions of the week
    • (a) We had previously withdrawn a review because it was out-of-date. It has now been updated by two new reviews, both of which are ready to be released for publication. How can we remove the withdrawn review from publication and indicate that the new reviews have updated it?
    • (b) We have a duplicate registered title in Archie. If we delete the duplicate title, this will trigger a deregister message, which would be misleading. How should we delete the duplicate record in Archie?

1. Tip: Searching archived IMS Bulletins for information

You can seach for specific information in the archived IMS Bulletins by using the browser's "Find in page" search (typically with Ctrl-F as the keyboard shortcut) on the index of Bulletins at http://www.cc-ims.net/Projects/newIMS .

2. Centralised copy editing in Archie

A new Copy Edit Support system was piloted in 2006 using Archie, as a result of which it was agreed that centralised copy editing should be carried out in Archie using RevMan 4.3. The system was extended to 6 CRGs earlier this year and Copy Edit Support hopes to be able to offer copy editing through Archie to all CRGs by next year. Around 20 CRGs use Copy Edit Support at the moment. If you currently do not use Copy Edit Support but would like to discuss the possibility of your CRG using Copy Edit Support through Archie or are a CRG that currently uses Copy Edit Support but would like to start using Archie for centralised copy editing, please contact Laura Mellor, Associate Editor, John Wiley & Sons at lmellor@wiley.co.uk

For your information, at a recent meeting, the Publishing Policy Group stated that they expect CRGs to use the Wiley Copy Edit Support system.

3. Report on Archie module submission for Issue 3, 2007 (from Ben Hickling, Project Editor, John Wiley & Sons)

Wiley collected data for all Cochrane entities from Archie at module submission time and e-mailed feedback reports to all CRGs. No errors were found in the data, but four CRGs and three non-CRGs requested late changes, so their modules were unlocked to allow these to be made, then re-collected.

We'd like to take this opportunity to remind RGCs to check the Publication Reports in Archie for their CRGs ahead of submission (contact your IMS Support person if you are unsure of how to do this), and also to ensure that when RGCs are out of the office at submission time, there is still someone checking Wiley's e-mailed submission reports.

4. Authors who are testing RevMan 5

Some authors, who have signed up as RevMan 5 alpha or beta testers, or both, may have asked you for an Archie user account. This is not a reason for an author being given an Archie account and you should, therefore, not initiate the registration process. The RevMan 5 web page has been updated with this information and, if you wish, you can refer any authors who ask you for an Archie user account to this page at http:/ /www.cc-ims.net/RevMan/RevMan5/.

5. Questions of the week

(a) Question: We had previously withdrawn a review because it was out-of-date. It has now been updated by two new reviews, both of which are ready to be released for publication. How can we remove the withdrawn review from publication and indicate that the new reviews have updated it?

Answer: There are two ways to manage this situation at the moment.

(a) Publish both reviews as new reviews. You must must do this if you published new protocols to help prepare the two reviews that form the update to the withdrawn review. Remember to add a published note to both reviews to cross reference them with the withdrawn review, which must remain withdrawn, and edit the published note in the withdrawn review to refer to the new reviews.

(b) Change the Unique ID of one of the new reviews to match the Unique ID of the withdrawn review so that the record of the previously withdrawn review will be reinstated as a substantive update when next published. (Ask your IMS Support person to help you do this.) Publish the other review as a new review. Remember to explain within both reviews that the previously withdrawn version of the review has been updated by two reviews; in other words, in each review, cite the other review as the other part of the update for the previously withdrawn review; include this information in the What's new section of the updated review and as a published note for the new review.

Please note that it is the Collaboration's policy that withdrawn reviews should never be removed from publication and, to reflect this policy, Archie will not allow you to do this.

(b) Question: We have a duplicate registered title in Archie. If we delete the duplicate title, this will trigger a 'deregister' message, which would be misleading. How should we delete the duplicate record in Archie?

Answer: If you don't want to want to generate a 'deregister' message but wish to remove the record completely from Archie, you can move the Stage to Protocol and then delete the record in the Protocol stage since deleting a protocol does not generate a 'deregister' message.

Document Actions