Revision Date: 2023.09.29
...
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
This procedure describes the processes used by Sage Employees to initiate a request for an anonymous manuscript review and processes used by Sage Governance to assign anonymous manuscript reviewer accounts for external users. Steps in this process include:
Request to set up data access for manuscript review
Providing process acknowledgement to Researcher
Assigning anonymous reviewer accounts
Creating an anonymous reviewer team and setting up reviewer account access
Emailing anonymous reviewer log-in credentials to the Journal Editor
Review the status of in-use accounts quarterly
Closing out anonymous reviewer accounts
Decommissioning of anonymous reviewer Synapse Referee accounts (as needed)
Anchor | ||||
---|---|---|---|---|
|
The objective of this Reliable Method for Sage Employees is to understand the process for requesting an anonymous manuscript review, which includes:
...
Gathering necessary information for review setup, which includes communication with Sage Employees (as needed), Researchers, and Editors.
Executing process acknowledgement with the Researcher
Assigning accounts and distributing login credentials to the Editor
Completing quarterly reviews, account close-outs and decommissioning of accounts
Anchor | ||||
---|---|---|---|---|
|
This Reliable Method applies to all Sage Employees who are responsible for providing information for and the execution of the anonymous manuscript review process.
Anchor | ||||
---|---|---|---|---|
|
Editor: The journal editor in charge of the submitted manuscript
Researcher: The primary researcher who is submitting the manuscript
Reviewers: Anonymous reviewers managed by the editor
Sage: Employees of Sage Bionetworks
Synapse ACT: Synapse Access and Compliance Team
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Sage Employee files a Jira ticket in the Sage Governance (SG) project utilizing the component “Anonymous Reviewer Account Request”
Sage Employee comments the following information in the Jira issue (or as much as is known to them):
Journal name
Editor name and email
Researcher name and email
Manuscript name
Links to Synapse entities (Syn IDs) required for manuscript review
Additional information that is helpful to Sage ACT that may be included in the Jira ticket:
Do reviewer accounts need access to the full project or just to a specific folder?
Do anonymous reviewer accounts require view or download access?
Have the relevant folder(s) &/or entities been shared with ACT by giving the team “Administrator” access?
Number of reviewer accounts required for the review?
Anchor | ||||
---|---|---|---|---|
|
ACT sends anoverview of the anonymous manuscript review process via email to the Researcher.
Researcher replies with their acknowledgement
ACT copies and pastes acknowledgement reply in Jira issue
Anchor | ||||
---|---|---|---|---|
|
ACT will:
In the ACT Zone Facilitating Anonymous Journal Reviews Wiki page, verify if the reviewer account is available by comparing the “List of Active Reviewer Accounts” table with the “In-Use Accounts” table
Ensure the account has the proper qualifications for the respective dataset (i.e., validated, certified, etc.)
Assign each reviewer their own account for the current review
If all accounts are in use, follow instructions for creating a new reviewer account
Anchor | ||||
---|---|---|---|---|
|
ACT will:
Follow instructions in the Anonymous Reviewer Synapse Accounts page (managed by the Platform team). Use the synapse-service@sagebase.org distribution list to create a new, unique service account.
Steps for creating a new account:
Refer to the Synapse Referee Accounts team page and ACT Zone tables to choose a name for the service account that has not been used yet, e.g., synapse-referee-journalreview-26.
Go to Synapse.org
Click “Register Now”
On the Create Synapse Account page, create an email address using the following naming convention:
synapse-referee+$journal-0d@sagebase.org
Refer to the ACT Zone List of Active Reviewer Accounts table for the next number in the sequence.
Click the “Send Registration Info” button
Open Gmail and go to Google Groups Synapse Referee Accounts inbox
In inbox, open the no-reply email to the newly created email account and click on the link to create the new account
On the Register with Synapse page, enter the following information:
Create username: synapse-referee-$journal-0d
Example: synapse-referee-journalreview-26
Create and confirm password. Save this password for entry under step 4.b.iii below.
Click “Next”
Review and complete Synapse Pledge
Click “Next”
Click the refresh button
Log out of the new Synapse account
Add new account to the Synapse Referee Accounts team page, which is used to track and update accounts:
You must be a Team Manager to add a new Synapse referee member account. If you are not a Team Manager, click “Join” to request to be added as a Manager to the team
Log into Gmail Google Synapse Referee Accounts group, LastPass, and the Synapse Referee Accounts page
Create an entry in the Notes section of LastPass for each new account, and enter the email, username and password. Choose the “Shared synapse referee” label from the drop-down menu.
Log into Synapse with your personal account credentials
Go to the Synapse Referee Team page and send an email invite to the new Synapse referee email account
Log out of Synapse and log back in using the new Synapse Referee email and password from LastPass.
Go to the Gmail Google Groups Synapse Referee Account inbox and accept the “Join” invitation for the new Synapse Referee Account. You will be automatically routed to the Synapse Referee Team page. Verify that the new account has been added.
Log out of Synapse, LastPass and Google Group email accounts.
Anchor | ||||
---|---|---|---|---|
|
Log in to your Synapse account
Go to the Teams tab in Synapse. Click “Create a New Team”
Create Team name in the following format: manuscript name_year
Add Reviewer team to Synapse entity/entities under Project Sharing Settings or Folder Sharing Settings:
Grant the team access at the Project OR Folder level as determined by Researcher
Give Reviewers either View OR Download permissions based on the Researcher’s preference
Under the newly created Team, click Team Actions menu, click Edit Team. Ensure the following options are unchecked so that users can join the team by invite only:
“Users can join this team without manager authorization”
“Any Synapse user can send messages to this team”
Click “Save”
Under the Team Actions menu, click ACT Manage Access Requirements
Click “Create a New Access Requirement”
Choose the “Click-wrap” radio button
Click “Next”
Add the Click-wrap template provided in Figure 1 and click Save
Under the Team Actions menu, click Invite User
Invite the Synapse Referee reviewer accounts to join the team
Note: Do not accept the clickwrap on behalf of the reviewers! The reviewers need to agree to the clickwrap to conduct the anonymous manuscript review.
ACT logs the following information for each Synapse Referee Account in the “In-Use Accounts table in the ACT Zone Facilitating Anonymous Journal Reviews Wiki.
Reviewer Account Name
Account ProfileID
Date Added
Date of Expiry
Researcher
Project Name
Project SynID
Access Level
Account Type
Jira Issue
Anonymous Manuscript Review click-wrap template:
...
####**Before conducting the manuscript review, please agree to the following terms and conditions for anonymous data access:** **You agree to only access and use the data necessary for the purpose of reviewing the submitted manuscript, and to delete any data downloaded immediately after submitting your review if applicable.** You agree to abide by the Synapse [Terms of Use](https://s3.amazonaws.com/static.synapse.org/governance/SageBionetworksSynapseTermsandConditionsofUse.pdf?v=4) and [Privacy Policy](https://s3.amazonaws.com/static.synapse.org/governance/SynapsePrivacyPolicy.pdf?v=5). You confirm that you will not attempt to re-identify research participants for any reason, including for re-identification theory research. You will not reset your account username or password. If you have issues logging into the account, please inform the Journal Editor. You agree to report any misuse or data release, intentional or inadvertent, to the Journal Editor within 2 business days of initial knowledge. |
Anchor | ||||
---|---|---|---|---|
|
ACT will use email template in Figure 2 to provide Synapse Anonymous Reviewer account information to the journal editor.
ACT will use One Time Secret Password to generate a secret password link for each anonymous reviewer account by copying the Synapse login credentials from the LastPass Shared Synapse Referee Account (username, email and password), generating a secret password and copying the password into the email template.
Using the template insert:
Manuscript name
Author
Link to Synapse entities
One Time Secret Password (Note: Each reviewer should have individual accounts and login credentials)
ACT will email the template to the Editor and update the Jira to indicate that the credentials have been sent. (Note: Do not put the login credentials for the anonymous reviewer accounts in the Jira)
...
Dear X, Synapse accounts have been assigned for the review of the manuscript "[MANUSCRIPT NAME]" by [FIRST AUTHOR]. Each link below contains account login information. One unique account and credentials link has been generated for each manuscript reviewer. Please note that the links are available for 7 days and will expire once they are clicked once, so please forward each link directly to each reviewer without clicking on it yourself. All reviewers associated with this manuscript review should log into a unique Synapse account. Login information link for Reviewer 1: [Link created from Share a secret - One Time ] Login information link for Reviewer 2: [Link created from Share a secret - One Time ] Login information link for Reviewer 3: [Link created from Share a secret - One Time ] Please instruct each reviewer to:
Once the reviewers have completed their review, please reply to myself and the Synapse ACT (act@sagebionetworks.org), and we will remove reviewer access to each respective account. Note that by default, reviewers will lose access to their accounts after 6 months. If you need to extend reviewer access, please let me know via email before [date]. Please let me know if you or the reviewers have any questions. As a reminder, reviewers must remain anonymous, so any account or data access questions they may have should go through you and can be directed towards the researcher and the Synapse ACT (act@sagebionetworks.org). Thank you, X |
Anchor | ||||
---|---|---|---|---|
|
ACT emails the Researcher for status of the manuscript review
If Researcher requests an extension, ACT will update the ACT Zone “In-Use” Table and maintain the Reviewer’s access.
If Researcher needs to provide access to new Reviewers, follow the process in Section C for assigning reviewer accounts and extend access to all in-use reviewers.
If review is complete, ACT will revoke access to assigned Reviewer(s).
If ACT is unable to reach the Researcher, ACT may also reach out to the Editor to confirm the status of the review.
Remove anonymous reviewer account access after 6 months if the Researcher hasn’t requested an extension (or is lost to follow up).
Anchor | ||||
---|---|---|---|---|
|
Once the review is concluded, ACT should revoke access to entities used for the anonymous manuscript review accounts by removing the Anonymous Manuscript Team from the entities and deleting the Reviewer Accounts from the team.
ACT will reset all reviewer account passwords by:
Logging into the anonymous reviewer Synapse account and changing the password.
Update the new account password in LastPass under the Shared-Synapse-Referee-Accounts in the Notes section.
Note: ACT members will need to be invited to this Note in order to have access to passwords and be able to update passwords. This does not apply to the Gmail Google Group account that is tied to the Synapse account.
ACT will update the ACT Zone by moving the information from the “In-Use Accounts” table to the “Previous Assignment of Accounts” table.
ACT will comment on Jira when the account close-out process has been completed and resolve the Jira issue.
Anchor | ||||
---|---|---|---|---|
|
ACT will check the ACT Zone In-Use Accounts table to ensure the account isn’t currently being used. If the account is listed in the Previous Assignment of Accounts table, then the account close-out process has been completed and Sage ACT can proceed with the decommissioning process.
Refer to the IT Confluence /wiki/spaces/IT/pages/1200816129 instructions, step #7.
Create a Jira issue under the IT Operations Project and request removal of the Synapse account. Provide the user Profile ID and Synapse Referee email address in the description.
Once IT has confirmed removal of the account:
Move the account to the “List of Decommissioned Reviewer Accounts and their Access Level” table.
Delete the account information in LastPass.
Delete the account from the Synapse Referee Accounts page.
Anchor | ||||
---|---|---|---|---|
|
Revision #, Date | Description |
V1, 2023.09.29 | New version as RM. |
...