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. If the item is connected to an article, it may be appropriate for the item title to be the same as the title of the article or to include the article title in the item title.
This is a mandatory field where the submitter can add the authors of the item. Every author that has been involved in the creation of the item should be added here; adding all of the authors makes the item more findable.
If the item is connected to an article the authors listed here could be the same as the authors of the article, but this is not always the case.
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 research group or facility where applicable. The submitter can contact the SciLifeLab Data Centre regarding questions about the group assigned to the item.
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. Facilities submitting an item are encouraged to include the name of the facility 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.
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 link 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 facility 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.
There are a number of reasons why you may want to conditionally upload your files:
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.
Select the Apply Embargo button in the metadata form. Select a time period for the embargo; for permanent embargoes, select ‘permanent embargo’ at the bottom of the dropdown menu. Choose whether the embargo is on the files only or on the entire content (files and metadata).
The item owner can also optionally add an option reason as to why this item is under an embargo. This is useful for people who are viewing the public metadata record.
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. Projects are secure spaces that can be used for sensitive data. You can also collaborate with people outside your institution by inviting them to your project.
There are two different types of projects: individual projects and group projects.
|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 subgroup of the uploader.||Items appear in the subgroup of the project owner.|
|Items published by users from outside the organisation don’t have to go through review (if review is turned on for the group).||Items published by users from outside the organisation have to go through review (if review is turned on for the group).|
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. Some changes may trigger a new version. See here to find out which amendments will generate a new version of your item. 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.
For further questions, please contact email@example.com.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.