Vicky Steeves | October 25, 2017
Vicky's ORCID: 0000-0003-4298-168X
This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.
We do a lot of very different things in very different ways during our research. But the final conclusion is always just a paper-- let's challenge that.
Today, we're talking about GREEN open access. You will be self-archiving your work!
Data and code must be:
Not selfishly: it helps advance your field of research!
Selfishly: citations!
Data and code should be cited within our work for the same reasons journal articles are cited:
to give credit where credit is due (original author/producer) and to help other researchers find the material.
Step 1: Write/version code in GitHub.
Step 2: Use the Open Science Framework to store data, documentation, etc.
Step 3: Publish & reap all your analytics!
Let's check out a brief example before getting into the details!
GitHub is a website where you can upload a copy of your Git repository. It allows people to collaborate via Git along with some other features.
GitHub is great because it allows folks to
I teach it at Bobst! Check it out.
Git
GitHub
A free and open source project management tool that connects researchers to the tools they are already using to make management easier through the research cycle.
Sign up at osf.io using your NetID and create your account.
Click on "Sign In" and at the bottom of the sign-in box, the link for "Login Through Your Institution."
Go to https://osf.io or just click "My Projects" on the top bar.
Click "Create Project" and fill in the form.
Click "add" button next to the title of the page.
Search for the person to your right and add them.
Try adding an account of your own by clicking on your profile, then "Settings," then "Configure Add-on Account." Click on "Connect Account" next to an addon.
Go to project "Settings," then "Select Add-ons"
Click on "Files" on Your Project Top Menu
From here, you can:
When you click on a file in OSF, it renders right in-browser. On the bottom right is the "tag" field, where you can enter whatever you want.
Try adding 2 tags to your file and compare with the person to your right
When you click on a file in OSF storage, you can also see and download all the versions of that file that have been uploaded.
THE CATCH: The file has to be uploaded with the same name!
This also has a robust versioning. And you can compare versions side-by-side.
Use the "Home" wiki page as a table of contents listing project goals, personnel, sub-components, and links to important files.
Components are essentially "sub-projects" that can have their own set of collaborators, add-ons, and access controls.
Everything (files, subcomponents, wiki docs) gets a short permalink in OSF. That makes it easy to share via e-mail, Twitter, pastebins, etc.
You can also share projects via a view-only link, including an option to anonymize contributors for blind peer review.
Step 1: Comment & style your code—
Step 1: Put your data into an open format!
Step 2: Package Your Materials
When you want to publish your final product, you register it. All the files are pulled into an archive on OSF storage, and the project becomes read-only.
You can get a DOI for this project, and include it in a "Supplementary Materials Section" of a journal article.
All OSF projects start private. We can make them public and publish them, we reap some benefits, like built-in analytics!
Email me: vicky.steeves@nyu.edu
Learn more about RDM: guides.nyu.edu/data_management
Get this presentation: guides.nyu.edu/data_management/resources
Make an appointment: guides.nyu.edu/appointment
Vicky's ORCID: 0000-0003-4298-168X
This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.