Now that your work is out there in the world, we want to share some tips for boosting the visibility of what you've created! Our colleague Tammy Ivins created this list to help you get started.
You can also access this list as a Google Doc (you'll be prompted to make a copy of it) or a Microsoft Word version (embedded below) with checkable check boxes.
Update your scholarly profiles (and/or create as needed)
Place an open-access copy of your work in your institution’s repository (if they have one)
Find your license.
Check your email for the original copyright agreement for your manuscript. Review it to see whether there is language that specifies that you may make your work available via an institutional repository.
OR use the Open Policy Finder list of publisher copyright policies and self-archiving (search for the journal title or publisher)
OR check the publisher's website for author licenses. For example, here is Taylor & Francis' policy.
Confirm that you can publicly share your manuscript in your institution’s repository. This may be described in many ways, including:
Your "institutional/employer website."
A specific repository, such as "your institutional repository" or a "repository designated by your grant funder."
"Any repository" or any "non-commercial repository."
Check what version you are allowed to deposit. Versions include:
Published manuscript = the final, published version (i.e., with the publisher's formatting and page numbers).
Accepted manuscript = includes revisions made through the peer/editorial review process, but it should not include publisher branding or final editing.
Pre-print/submitted = the article draft as you first submitted it for publication. It does not include revisions made through the peer/editorial review process, nor include publisher branding or final editing.
Check if there is an embargo on your manuscript.
This is a period of time, post-publication, that you must wait before the publisher allows it to be publicly shared.
Share a link to your work on any social media platforms you might use.