Making your data public

When first created, records are given a temporary accession number beginning with tmp: instead of urn:mavedb:.

Temporary records are only visible to the uploader and to any contributors that have been added to the record. If you want to access these datasets via API, you can create an API key on your user profile page to enable authentication.

When the record is ready to be made public, you can click on the padlock icon to “publish” the record.

Warning

Once a record is published, it cannot be unpublished. If you need to fix errors in a dataset after publication, see: Deprecating score sets.

Once the data is published, several fields (including the target, scores, and counts) will become un-editable. However, most free-text metadata can still be revised after the dataset becomes public, and changes to these fields are tracked.

Note

Score sets are the only record type that can be published. When the first score set associated with an experiment is published, the associated experiment and experiment set will also become public.

Data licensing

When uploading score set information to the database, the user can choose one of three licenses:

• CC0 (Public domain)

• CC BY 4.0 (Attribution) license

• CC BY-SA 4.0 (Attribution-ShareAlike)

Note

Only datasets licensed under CC0 will be included as part of the bulk download archive.

By default, new score sets will have the CC0 license. The license can be changed after publication, but previously downloaded copies of the dataset will retain the license they were downloaded under. The license is listed in the header of downloaded CSV files and also in the API.

Users also have the option of adding a free-text data usage policy to a score set, such as terms that dictate use of pre-publication data. For example, data producers may wish to assert their right to publish the results of certain analyses first. The data usage policy will be added to the header of any downloaded data files if one is present.

Deprecating score sets

If you need to fix an error after a dataset becomes public and is no longer editable, MaveDB supports the deprecation of score sets. When creating a new score set, the user can specify an existing score set to replace.