Reviewing is the act of approving or rejecting an submitted item, with feedback, before it becomes publicly available.
There are two different types of reviewer, institutional and group reviewer. An institutional reviewer can approve and manage revision requests from every group in the SciLifeLab institution. Whereas a group reviewer only can manage requests coming within their group and subgroups below their managed groups.
This role is available only in the Configure institution page. Institutional reviewers can assign and unassign requests from everyone.They can also edit all the metadata for the items sent in for review and assigned to them. Institutional reviewers can add comments and send emails to submitting authors, for any of the pending/open requests visible to them.
As an institutional reviewer you can turn on reviewing in the Administration page by selecting the group you want to turn on reviewing for (groups inherit reviewing settings, so if you turn it on at the top level, all subgroups will have reviewing turned on, as well), selecting Configure, and scrolling down to Administration. There, you will have the option to turn on reviewing.
This role is available only in the Configure group page, displayed as Reviewer in the role drop down. Group reviewers can only assign requests to themselves. They can also edit all the metadata for the items sent in for review and assigned to themselves. Group reviewers can add comments and send emails to submitting authors for any of the pending/open requests visible to them.
When an end user chooses to publish an item on the SciLifeLab Data Repository, an email is automatically sent to every reviewer stated as reviewers for the group the item is published in.
All reviewing requests can be found in the reviewing pool from the reviewer account. All reviewers set either at the group level or institution level will receive both email notifications and will also have them listed in the reviewing pool. If you would like to receive reviewing requests for every subgroup at your institution, you will need to add yourself as a reviewer to each subgroup or you can simply set yourself as an institutional reviewer. While you won’t be displayed as a reviewer on every Edit group page, you will be an implicit reviewer there and you will receive all the requests.
If the user creates the item in My data, then the review request will go to the group the user is assigned to. If the user creates the item in a group project, then the reviewing request is sent to that group.
To view items for review, click on the dropdown menu and select Review requests. You will then see all open review requests, whether they’ve been assigned to you or not. You can opt to view only your assigned requests and sort by newest or oldest first. The number you see in the menu displays unassigned, open requests. The number might be different from what you see when you enter the pool. By default, the pool shows all the requests even if they are assigned already, filtered by the group(s) you can review. If you know there are open review requests but you cannot see them, it means they must be assigned to groups that you cannot review.
To process an item through review, select the item and assign it to yourself as the reviewer. As an institutional reviewer, you can assign the request to yourself or to other reviewers that are assigned to the same group of the request. If you are a group reviewer, you can only assign the request to yourself.
Once a reviewer has been assigned to review an item they will review the item according to the checks outlined below.
✓ Check if the item appears to contain human data. Consider contacting the submitter if you have any doubts regarding this.
✓ Does the item include a README file
✓ Does the README file include a DOI to the item
✓ Does the item include a manifest file
The purpose of filling out the metadata form thoroughly is to maximize the reusability of the item. Once an item is published on the SciLifeLab Data Repository it should be self-explanatory. The SciLifeLab Data Repository should be used as a catch-all space, i.e. everything that is connected to the submitted item should also be submitted to or linked to here.
This is a mandatory field where a title for the submitted item should be entered. The title should have an understandable scientific meaning, strive for an informative yet concise title. Make sure that the title is meaningful for someone without prior knowledge of the item. Avoid using underscores in the title as it can reduce the findability of an item.
✓ Check that the title is meaningful and doesn’t contain underscores or file extensions.
This is a mandatory field where the submitter can add the authors of the item. Every person that has been involved in the creation of the item should be added here; adding all of the authors makes the item more findable. You can remove yourself as an author if you are uploading on behalf of someone else.
✓ In the case of the item being connected to an article, check if the authors listed here seem reasonable in relation to the authors of the article. Consider contacting the submitter if you have doubts about the authors stated.
This is a mandatory field where a discipline category is chosen for the item. The list of categories is fixed and based on the Australian and New Zealand Standard Research Classification (ANZSRC) Fields of Research (FOR) codes. Choose all categories that apply for the item. The list of categories is not specific for the field of life science which sometimes can make it difficult to find a correct category. However, remember that the keywords can be used to increase specificity in those cases.
This is a mandatory field that is filled out by a reviewer. The purpose of this field is to connect the item with the correct SciLifeLab research group, platform or unit where applicable. The submitter can contact the Data Centre in order to suggest an appropriate group or regarding questions about the group assigned to the item. See all currently public groups here: https://scilifelab.figshare.com/groups.
✓ Choose the correct group for the item(the main group Science For Life Laboratory or one of its subgroups). Consult with the submitter if you have doubts about the appropriate group belonging. If the item belongs to a group project, the item should have the same group belonging as the project.
Please note: When editing the group belonging of an item the current review request will be archived and a new request will be created. The reviewer will then need to assign themselves to that review request once again.
This is a mandatory field where the submitter can select what kind of item is being submitted.
The following item types can be uploaded to the SciLifeLab Data Repository:
✓ Check if the uploaded item is labelled with the correct item type. When item type is presentation, poster or a preprint, take extra notice in making sure the submitter has permission to upload all that is included in the item, for example figures.
This is a mandatory field where the submitter can add keywords to the item. The keywords can be more specific than the categories and should be used as a means to make the item more findable. Units submitting an item are encouraged to include the name of the unit as a keyword. There is no upper limit of the number of keywords, but remember to keep the keywords accurate and relevant. In order to increase interoperability of the item the keywords should be written in a formal and broadly applicable language.
It is a free-text field and so special attention should be paid to the correct spelling of keywords. Misspelling keywords will decrease the findability of the item. Searches based on keywords are not case sensitive.
✓ Check if the keywords appear to be spelled correctly. Consider contacting the submitter if you have doubts about the spelling.
This is a mandatory, free-text field where a description of the item can be added. For someone interested in the item it can be informative to know the purpose of the item, e.g. why was it generated/produced. If the item is connected to an article, the abstract of the article could be included in the description. In this field, information about specific software needed to open a file and the version of the software used by the submitters should be stated, along with a URL or DOI to this software. In order to increase interoperability of the item the description should be written in a formal, accessible, shared and broadly applicable language for knowledge representation.
Specific things to consider depending on the item type:
State who generated or collected the data and, if possible, specify the date this was done.
Specify whether the data is raw or processed. In case of processed data, describe how it has been processed.
✓ In the case of the item being connected to an article, check if the article abstract is included in the description.
This is a non-mandatory field that can be used to add funding information related to your data or other materials in this item. One or several funders and/or grant numbers can be added. When typing a grant number the system will automatically search the Dimensions database for the grant. If the information is found, a hyperlink will be generated to the Dimensions page.
✓ If the grants are not hyperlinked, check if they appear in the Dimension database bytyping the grant number in manually and see if a dropdown menu appears. Note that pasting in grant information or typing in the grant name may not trigger an automatic search of the Dimensions database.
These are non-mandatory fields that should be used to reference the publication connected to the item. The title and the DOI of the connected article should be stated in respective fields.
When the item is published, a title and hyperlink to the publication will appear in a box on the right-hand side of the public page for the item. This requires that both fields are filled out.
✓ Check that nothing more than the title of the connected article is stated and check that the resource DOI matches the title.
This is a non-mandatory field where references besides the reference to the article directly connected to the item could be listed. However, when adding a reference it is preferable to write an explanation for the reference, which is not possible in this field. Therefore references can be added, along with an explanation, in the field “Description”.
Below are some examples of references that can be added:
✓ Check that all references are valid URL’s.
This is a mandatory field where a licence for the item is stated. A licence normally limits how the item can be reused and altered, in what context it can be used and how the creator should be credited. It is recommended that the licence selected be as open as possible. The appropriate licence can sometimes be specified by the funder or the publisher. If access to the item is restricted, the Restricted Access licence should be chosen.
✓ If it is a metadata record only, check that the licence is Restricted Access.
This is a mandatory field where the submitter can state a publisher. The publisher can be, for instance, the university, the institute or the unit with which the submitter is affiliated. In general the publisher is the home organisation of the submitter and not the data owner.
✓ Check that a publisher has been stated correctly.
This is a mandatory field that should be filled with the email address of the person to whom questions about the item should be directed.
This is a non-mandatory field where the submitter can state an email address to which any access requests for the files should be sent. This is useful when the item has restricted access, for whatever reason. If you are using the built in request access functionality this field does not need to be filled out.
✓ If possible, check that the email address stated is a functioning email address.
✓ Check if the buit in request access functionality is being used. If so, this field should not be filled out.
After the reviewer has checked the item and its metadata, they will be given three options.
See “Publish” below.
This option is relevant when the item is unsuitable for publication on the repository. The submitter will be notified of this by email. The reviewer should include a comment specifying why the item is declined and returned.
This option is relevant when there are more substantial ‘errors’ in the item/metadata that needs to be edited by the submitter. Tick the Notify owner by email box and the comment will be sent to the submitter of the item by email. The submitter can then reply to this email. This way, the comments can be discussed in order to make adjustments required before approval.
The option Approve and publish is relevant when the item can be published as it is or when you only detect small ‘errors’ in the metadata that can be edited directly by the reviewer without consulting the submitter. If there is mandatory metadata missing or if you simply want to change some of the metadata, please use the Save button from the Edit item tab before approving. If you do not save the changes, you will approve the previous version.
When the reviewer is happy with both the item and its metadata the reviewer should choose the option Approve and publish. The submitter will be notified of this by email.
When publishing items in a project, remind the submitter to make the project public. This is only possible when at least one of the items in the project has been published.