See the SciLifeLab data guidelines.
There are several ways to upload your data:
A user’s quota can be updated if the user requests it. Administrators cannot modify quota directly for a user – they can only approve or reject the user’s request. To request more quota, the user needs to go in my data and request more from above the item table.
When publishing an item on the SciLifeLab Data Repository, consider uploading both a README file and a manifest file to the item. This will improve accessibility for those downloading the item. The README file should preferably contain the same metadata as that of the metadata form, including the DOI to the item. The manifest file should contain a list of every file included in the item. When uploading a file to the SciLifeLab Data Repository, a checksum for the file is automatically generated. Click on Preview item in the metadata form to view the files checksum.
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.
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.
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 SciLifeLab 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.
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:
When uploading a presentation, poster or a preprint, take extra notice in making sure that you have 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, accessible, shared and broadly applicable language for knowledge representation.
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.
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.
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.
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.
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:
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.
This is a mandatory field where the submitter should 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.
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.
There are a number of reasons why you may want to conditionally upload your files, for example, you might want to restrict access until a publication is accepted or ensure that only certain users can access the item whilst it is under embargo. Multiple solutions exist to accommodate user requirements related to conditionally uploading an item/data. Please see the below table for advice on which solution would be most suitable for your needs.
|Reason to conditionally upload data||Which section to look to for advice|
|Files may include ethically or commercially sensitive data||See ”Metadata record” section|
|Data/item can not be made available before a given date/indefinitely||See ”Embargo and restricted publishing” section|
|There is a need to enable some users/groups to access your item during the embargo period||See ”Embargo and restricted publishing” section|
|The data/files involved in the item are stored elsewhere, but you want to link it to this repository in order to get a DOI||See ”Linked file” section|
|You want to reserve a DOI for the data that you will include in a publication )||See ”Reserve DOI” section|
|You want to make the data accessible only to reviewers while your manuscript is under review for publication||See ”Sharing private data” section|
Tick the metadata record only box at the top of the screen and enter a reason for this choice. This option only appears if you haven’t uploaded a file to the item. For information on publishing human data, see here.
To use this functionality, select the Apply Embargo and restricted Access button in the metadata form. You can select a time period for the embargo or, select ‘permanent embargo’, where restrictions to the underlying data will apply. It is not necessary to apply the embargo to the entire item. Indeed, you can choose whether the embargoapplies only to the files or to the entire content (files and metadata). You can then choose who can access the embargoed content (i.e. before the embargo period expires). By choosing “Nobody”, you ensure that nobody will have access to the embargoed content until the embargo period expires. Choosing “Custom” instead enables you to select whether access should be restricted to all users of the SciLifeLab Data Repository when they are logged in, or just specific groups (it is possible to select one or more) within the SciLifeLab Data Repository.
The item owner can also change the title of the embargo to describe the type of embargo applied (the standard text is ‘File(s) under embargo’) and can optionally add a reason as to why this item is under an embargo.
It is now possible to allow users to request access to your embargoed files. Note though that this functionality is not available for metadata only records. To enable the functionality, tick the Allow anybody to request access to the embargoed files box. You can include additional information as a message for anyone requesting access to the files. When this functionality is enabled, a button with the text Request access to files will appear on your published item. Anyone looking to request access needs to be a user of a Figshare instance. When users click on this button, they will see your added message and can choose to send an access request. If a user requests access to your restricted files through this feature, you and your institutional administrators will receive an email request to grant access. There is currently no way to share restricted access files with a user in the interface, this has to be done using an external service.
Click the Link File button at the top of the screen and copy the link in the box. This option only appears if you haven’t uploaded a file to the item.
Click on the Reserve Digital Object Identifier button in the metadata form to reserve a DOI for your item. This DOI becomes active when the item is published and can be used to cite your data in publications.
Click on the Generate private link button in the metadata form to create a link that you can share. If desired, this link can be disconnected in the future. Please note that this link should not be used to cite your data in publications.
Projects are collaborative spaces used for ongoing work. You can upload data that is in progress and have collaborators make comments. You can also collaborate with people outside SciLifeLab by inviting them to your project.
Please note that the project owner and members cannot edit another uploader’s items. Items must be downloaded, edited, and re-uploaded to the project. To create a project, go to My Data, select the Projects tab and click on the +Create a new project button.
Project members can either be collaborators or viewers. Invite members with existing accounts (institutional or figshare.com) by using the search function. The invited members will see their invite under the Activity page. When they accepted the invitation the project will appear under their Project page. Invite members without an account by clicking on the invite new users link. The invited members will receive an email including a link to create a figshare.com account. Outside of the scope of a project users with figshare.com accounts will publish their items on figshare.com and their future work won’t be associated with SciLifeLab.
There are two different types of projects: individual projects and group projects. The person creating the project will be the owner of the project regardless of project type chosen.
|Individual Projects||Group Projects|
|Everyone uses their own quota and account storage.||Submitters’ quota will not be used, storage allocation comes directly from the project.|
|People take their work with them if they leave the project.||All work is stored on institutional storage and remains within the project space if people leave.|
|Items are created using the metadata schema of the submitter.||Contributors must adopt the metadata schema of the project owner.|
|Items appear in the group chosen in the review process.||Items appear in the group chosen in the review process. It is recommended for this to be the same group as chosen for the project.|
|Items published by users from outside the organisation don’t have to go through review.||Items published by users from outside the organisation have to go through review.|
Collections are ways of collating data and bringing it together under a theme. They can be either private or public and can be assigned a DOI.
You can go back and edit items after you’ve made them publicly available. To edit an item, click on the pencil that appears to the right of your item when hovering over it in My Data. When editing a published item the item will be sent for a new review. To expedite this review, please send a message to email@example.com and explain which changes that were made to the item. Some changes may trigger a new version of the item. See here to find out which amendments will generate a new version. When a new version is generated, the previous versions will still be available. Each version will have its own DOI, where the version number is added as a suffix to the original DOI.
You can also batch edit items that have already been published: in My Data, select the items to be updated, click on Actions at the top of the page, and select Edit in batch. Once you’ve selected the items to be edited in bulk, select the metadata fields to edit.
When editing an embargoed record, the same changes that trigger a new version for public items will send the item back for review. Amending or removing the embargo will also send the item back for review.
Click on the Delete item button in the metadata form to delete a private item.
Published items are considered to be published permanently and can only be deleted in special cases.
Answer: An item is an entry to the repository that contains metadata and potentially also associated files. In other words, ‘item’ is used as an umbrella term for both metadata-only records and records with public, embargoed or linked files. An item can be included in groups, projects and/or collections. Each item is assigned a DOI (Digital Object Identifier), a permanent identifier.
Answer: When you type a grant number into the ‘funder field’, the system will automatically search the Dimensionsdatabase for the grant. If the information is found, a hyperlink will be generated to the Dimensions page; bridging the connection between research outputs and the funder. Note that pasting in grant information or typing in the grant name may not trigger an automatic search of the Dimensions database, so if no dropdown menu appears, simply try typing the grant number in manually.
To add grant information that doesn’t appear in Dimensions, simply type the grant information into the field and don’t select anything from the drop-down menu. If your grant does not appear, but you still wish to add a hyperlink to the grant, you may manually add a link in the “Descriptions” field.
Answer: Yes, it is possible to add information about a publication to a published item. Further, if the publication(s) using the data in the item is published after the item, the item should be updated to include information about the publication in order to connect the data with the publication once it is published. Edits to a published item will trigger the review process again. As with all edits to published items, please send a note to firstname.lastname@example.org summarising the changes made. This will expedite the review process, as the review can focus on the changes made.
Answer: Yes, the submitter can choose to apply an embargo when completing the metadata form before submitting the item for review for publication. Please consult the “Embargo and restricted publishing” section for more information.
Answer: Yes, the submitter can chose to reserve a DOI for the item when completing the metadata form before submitting the item for review for publication. Please consult the “Reserve DOI” section for more information.
Answer: Yes, the submitter can chose to generate a private link for the item when completing the metadata form before submitting the item for review for publication. This private link can then, for example, be sent to reviewers who can view the item before the item is published. Please consult the “Sharing private data” section for more information.
Answer: Yes, it is possible to add a published item to a project. Only members of the project can add items into that project. Project members can do this by going into My Data and choosing the action “Move to/from project” for one or more items.
Answer: Once an item is sent for review, a member of the review team will get back to the submitter with either comments, an approval or a decline of the item. In general, the review process takes around one week. Please note that during public holidays this may be a bit longer.
For further questions, please contact email@example.com.