See the SciLifeLab data guidelines.
There are several ways to upload your data:
When uploading an item you will be asked to fill in a metadata form. The metadata form consists of both mandatory and non-mandatory fields. The purpose of filling out the metadata form thoroughly is to make the submitted item reusable. Once an item is published on the SciLifeLab Data Repository it should be self explained. 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 or linked to here.
This is a mandatory field where a title for the submitted item should be given. The title should have an understandable scientific meaning, strive for an informative yet concise title. If the item is connected to an article, it can 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 authors of the item. Every author that should be credited for this item shall 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 aren’t specified for the field of life science which sometimes can make it difficult to find a correct category. Remember that the keywords can be used as an addition to the category field in those cases.
This is a mandatory field which is filled out by a reviewer. The purpose of this is to connect the item with the correct research group or facility when applicable. The submitter can contact the data center regarding questions about the group assigned to your item.
This is a mandatory field where the submitter can choose a type for the item.
The following item types can be uploaded to the SciLifeLab Data Repository:
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 your item more findable. 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 requires extra attention on the spelling of the words. Misspelling keywords will decrease the findability of the item. When searching for items based on keywords the search is 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 add 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 necessary version of the software should be stated. Add a URL or DOI to this software in the metadata field labelled References. 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 of this event.
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 should be used if the research was funded. If the research was funded one or several funders and/or grant number can be added here.
This is a non-mandatory field that should be used to reference a publication that is connected to the item. Only the title of the connected article should be included here.
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 your item. This requires that both this field and the field labelled Resource DOI are filled out.
This is a non-mandatory field that should be used to reference a publication that is connected to the item. If the item is connected to an article the DOI of that article should be included here.
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 your item. This requires that both this field and the field labelled Resource title are filled out.
This is a non-mandatory field where all references besides the reference to the connected article should be listed.
Below follow 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 to choose a licence as open as possible. The appropriate licence can sometimes be specified by the founder or the publisher. If the item is under some restricted access the Restricted Access licence should be chosen. Available licences:
This is a non-mandatory field where the submitter can state a publisher. The publisher can for instance be the university, the institute or the facility to which the submitter is affiliated.
This is a mandatory field where an email address to the person that should be contacted regarding questions about the item should be stated.
This is a non-mandatory field where the submitter can state an email address to which any access request of the files should be sent. This is useful when the item, for different reasons, has restricted access.
There are a number of reasons why you may want to conditionally upload your files:
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 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.
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.
Click on the Reserve Digital Object Identifier button in the metadata form to reserve a DOI for your item. This DOI 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 users 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 that bring it together under a theme. They can be either private or public and can be assigned a DOI.
Before publishing, consider attaching both a readme.txt file and a manifest file, containing a checksum, to the item. The readme.txt file should preferably contain the same metadata as are stated in the metadata form. This will simplify for someone who downloads the item.
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 amends 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.
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.
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.