Privately stored research: for research outputs uploaded to your account and stored privately or in draft a license is not mandatory, as only you can access it at this stage.
Publicly stored research: all publicly stored research outputs are stored under a license. By making your items publicly available, you retain ownership of your research objects (as is often not the case with traditional publishing).
Please see our Copyright and Licensing Policy for more information.
Please note: The list of available licenses may vary depending on which instance of Figshare you’re using (the free version of figshare.com, an institutional version, or a publisher version, for example). If you’d like to learn more about the licenses available to free users on figshare.com, please visit: https://help.figshare.com/article/copyright-and-license-policy.
Some of the most common licenses on Figshare are:
More details on each of these licenses can be found below.
CC0 can be particularly important for the sharing of data and databases, since it otherwise may be unclear whether highly factual data and databases are restricted by copyright or other rights. Databases may contain facts that, in and of themselves, are not protected by copyright law.
CC0 is recommended for tabular data and databases and is used by hundreds of organizations. It is especially recommended for scientific data. Although CC0 doesn’t legally require users of the data to cite the source, it does not take away the moral responsibility to give attribution, as is common in scientific research.
View License Deed | View Legal Code
By licensing your research outputs under CC-BY, Figshare ensures that your research is openly available whilst still ensuring that others give you credit, in the form of a citation, should they use or refer to the research object. This license lets others distribute, remix, tweak, and build upon your work (even commercially) as long as they credit you for the original creation. This is the most accommodating of licenses offered. It is recommended for maximum dissemination and use of licensed materials.
View License Deed | View Legal Code
This license lets others remix, tweak, and build upon your work even for commercial purposes, as long as they credit you and license their new creations under the identical terms. This license is often compared to “copyleft” free and open source software licenses. All new works based on yours will carry the same license, so any derivatives will also allow commercial use. This is the license used by Wikipedia, and is recommended for materials that would benefit from incorporating content from Wikipedia and similarly licensed projects.
View License Deed | View Legal Code
This license allows for redistribution, commercial and non-commercial, as long as it is passed along unchanged and in whole, with credit to you.
View License Deed | View Legal Code
This license lets others remix, tweak, and build upon your work non-commercially, and although their new works must also acknowledge you and be non-commercial, they don’t have to license their derivative works on the same terms.
View License Deed | View Legal Code
This license lets others remix, tweak, and build upon your work non-commercially, as long as they credit you and license their new creations under the identical terms.
View License Deed | View Legal Code
This license is the most restrictive of the six licenses, only allowing others to download your works and share them with others as long as they credit you, but they can’t change them in any way or use them commercially.
View License Deed | View Legal Code
The Restrictive License Template has been developed specifically to license material that contains personal or other confidential information that has a high security risk associated with its release. It may also be used for material that is to be licensed under some form of limiting or restrictive condition (such as a time limit on use, or payment arrangements other than an initial once-only fee).
The BSD 3-Clause Software License can be applied to software that has been wholly created by your organisation, where the code does not include code licensed under the GNU GPL License. Software/code licensed under the BSD 3-Clause License can be incorporated into software that is licensed under the GNU GPL License. However, the reverse (incorporating GNU GPL Licensed software/code into software licensed under the BSD 3 Clause License) is not permitted. The BSD 3-Clause License is also compatible with the Apache Software License.
This information has been provided by AUSGoal - Australian Governments Open Access and Licensing Framework.
With the ODC-BY 1.0 license you are free:
(Note: “Database” is a collection of material (the Contents) arranged in a systematic or methodical way and individually accessible by electronic or other means.)
As long as you attribute any public use of the database, or works produced from the database, in the manner specified in the license. For any use or redistribution of the database, or works produced from it, you must make clear to others the license of the database and keep intact any notices on the original database.
This information has been provided by Open Data Commons.
Here is another handy guide that provides further detail: "The Legal Side of Open Source".
Can’t find your answer here, check the community discussion or raise a support ticket.
Share this article:
