IMS Bulletin #42 (8 September 2006)

Index

1. Report on Archie module submission for Issue 3, 2006
2. Reminders
   • (a) Resolving duplicates
   • (b) Removal of CRG Entity role 'Member'
3. Closing of Super User accounts
4. Choosing a Primary entity: prioritising the Entity role 'Author' over the role 'Member' with a non-CRG
5. New Entity roles
6. Question of the week: Why, when I try to remove RevMan 4.2 from my PC using Control Panel > Add/Remove Programs, does it launch the Uninstall Wizard for 4.3 beta?

1. Report on Archie module submission for Issue 3, 2006 (From Ben Hickling, Project Editor, The Cochrane Library, John Wiley & Sons)

Wiley collected data for all Cochrane entities from Archie at module submission time and e-mailed feedback reports to all CRGs by 10.15 am UK time on Thursday. No errors were found in the data, but five CRGs and one non-CRG found mistakes in their reports and requested to make corrections, so their modules were unlocked to allow these to be made, then re-collected.

2. Reminders

(a) Resolving duplicates Please remember that it is important that at least one Super User in your CRG receives messages about duplicates and suggested changes and responds promptly to them. You can change the settings for what messages you receive, and how. You can do this for both yourself and any people you have edit permissions for. Go to the Settings tab of Properties and click Edit Notifications ... to open the Notifications window.

(b) Removal of CRG Entity role 'Member' The Entity role 'Member' is not an agreed role for use by CRGs - see RGC User Guide: Managing Contact Details during Phase 1 of the IMS. If you have not already removed the Entity role 'Member' from your list of available CRG Entity roles, please do so as soon as possible.

3. Closing of Super User accounts

When a staff member of an editorial office with a Super User account leaves their employment, the RGC should ensure that the person's Super User account is closed either by deleting the person's record altogether (if they have no ongoing Entity or Document roles) or by deleting the Entity role Super User from their record.

4. Choosing a Primary entity: prioritising the Entity role 'Author' over the role 'Member' with a non-CRG

The basic principle behind the idea of a Primary entity is that the entity that is most often in contact with a person will also be the entity most likely to be aware if there is a change in contact details. In some cases the person in question will be working equally closely with several entities, and in such cases this will have to be resolved between the entities. However, some roles naturally suggest that the person should have that entity as primary, such as 'RGC', 'Staff' or 'Co-ordinating Editor'. Similarly, some roles indicate a closer affiliation than others. For example, the Entity role 'Editor' would take precedence over the role 'Author', which in turn is a stronger affiliation than 'Mailing list', etc. Which role should take precedence may not always be obvious, as, for example, in the case of someone with the Entity role 'Author' who also has the affiliation 'Member' with a non-CRG. In this case, we recommend that the Entity role 'Author' take precedence over 'Member' with the non-CRG because CRGs are responsible for the publication of authors' contact details in the CDSR.

5. New Entity roles

Two new web-related Entity roles have been added to the list of available Entity roles for CRGs. They are:

(a) Website Contributor: how this CRG Entity role will be used has not yet been agreed and, therefore, it currently has no permissions; and

(b) Website Publisher: this CRG Entity role currently allows the person to edit and publish the website_source document in the root of the Documents folder for CRGs who are using the resources for Cochrane Entity websites - for more information about the website resources, see www.cochrane.org/entitysites

4. Question of the week

Question: Why, when I try to remove RevMan 4.2 from my PC using Control Panel > Add/Remove Programs, does it launch the Uninstall Wizard for 4.3 beta?

Answer: This happens because when you install another version of RevMan, in this case RevMan 4.3, it recognises and shares some of the components of the software with the version of RevMan currently installed. If you then try to remove the previous version, in this case RevMan 4.2, it will remove these shared components so you will not be able to launch RevMan 4.3. We suggest that in such cases it is safer to reinstall RevMan 4.3.