-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should a section about Open Access publishing be included #4
Comments
I think it's ok to mention open access as A Thing, but good to keep out of any advocacy. Worth mentioning open access because some federal mandates are requiring some research products to be made open access, but you can still keep out of the philosophical promotion even when having that conversation. But okay to leave out for now, if easier. |
I wasn't saying that Open Access isn't worth mentioning or even advocating for. But it's not clear to me how to fit it in here persuasively under the scope of Reproducible Research using Jupyter Notebooks. You can certainly do reproducible research with Jupyter Notebooks perfectly well without ever publishing in an Open Access journal. I.e., Open Access publishing (in contrast to open access to source code, data, and other ingredient research products) is a subject separate from that of Reproducible Research, and I think trying to tie them together helps neither. |
I think that we should table this discussion and see what the technology looks like sometime in the future. I agree w/ @hlapp that right now there is no clear link between notebooks + OA publishing that deserves its own special treatment. The reproducible work materials are already somewhat duplicated between the jupyter + R courses, so unless this is explicitly OK and/or preferred, it'd be better not to increase the duplication. |
We have a pretty awkward transition between the DOI lesson and the open access information. Might naturally sort itself out later on, but right now somewhat being deliberately ignored.
The text was updated successfully, but these errors were encountered: