The preferred mechanism for sharing research data is via data repositories. Authors can use Repository Finder, FAIRsharing, and re3data.org to search for a suitable repository. Research data should be submitted to discipline-specific, community-recognised repositories where possible, or to general-purpose repositories, if no suitable community resource is available. We encourage authors to select a data repository that issues a persistent identifier, preferably a Digital Object Identifier (DOI), and has established a robust preservation plan to ensure the data is preserved in perpetuity.
If you share your research data on a repository please provide a URL link to your research data in your manuscript file under the heading ‘Data Availability Statement’, this URL link will be added to your article on publication. For more information, please go to What is a Data Availability Statement and how do I write and submit one?
Sage partnership with the Figshare Data Repository
A number of Sage journals participate in a partnership with Figshare, an open repository of research data, whereby Sage automatically archives your research data when you choose to submit this alongside your article, within the existing manuscript submission workflow.
All research datasets submitted will be assigned a DOI upon submission to Figshare to ensure the dataset is discoverable and citable. The dataset will also be displayed in a widget powered by Figshare next to the article on Sage Journals and will be available on the Figshare platform.
If your article is accepted, your accompanying research data will be published on the Figshare repository platform with a CC BY license, permitting unrestricted use of your data.
This is an optional service, and authors are not required to use this workflow for their research data and can use other repositories if they prefer.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article