Skip to content
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

Registered Reports in Primate Neurophysiology #28

Open
18 of 24 tasks
da5nsy opened this issue Sep 24, 2020 · 9 comments
Open
18 of 24 tasks

Registered Reports in Primate Neurophysiology #28

da5nsy opened this issue Sep 24, 2020 · 9 comments

Comments

@da5nsy
Copy link

da5nsy commented Sep 24, 2020

Project Lead: @da5nsy

Mentor: @ivotron

Welcome to OLS-2! This issue will be used to track your project and progress during the program. Please use this checklist over the next few weeks as you start Open Life Science program 🎉.


Week 1 (31 August - 4 September 2020): Meet your mentor!

  • Create an account on GitHub
  • Check if you have access to the HackMD notes set up for your meetings with your mentor
  • Prepare to meet your mentor(s) by completing a short homework provided in the HackMD notes
  • Complete your own copy of the open leadership self-assessment and share it to your mentor
    If you're a group, each teammate should complete this assessment individually. This is here to help you set your own personal goals during the program. No need to share your results, but be ready to share your thoughts with your mentor.
  • Make sure you know when and how you'll be meeting with your mentor.

Before Week 2 (7 - 11 September 2020): Cohort Call (Welcome to Open Life Science!)

  • Create an issue on the OLS-2 GitHub repository for your OLS work and share the link to your mentor.

  • Draft a brief vision statement using your goals

    This lesson from the Open Leadership Training Series (OLTS) might be helpful

  • Leave a comment on this issue with your draft vision statement & be ready to share this on the call

  • Check the Syllabus for notes and connection info for all the cohort calls.

Before Week 3 (14 - 18 September 2020): Meet your mentor!

  • Look up two other projects and comment on their issues with feedback on their vision statement
  • Complete this compare and contrast assignment about current and desired community interactions and value exchanges
  • Complete your Open Canvas (instructions, canvas)
  • Share a link to your Open Canvas in your GitHub issue
  • Start your Roadmap
  • Comment on your issue with your draft Roadmap
  • Suggest a cohort name at the bottom of the shared notes and vote on your favorite with a +1

Before Week 4 (21 - 25 September 2020): Cohort Call (Tooling and roadmapping for Open projects)

  • Look up two other projects and comment on their issues with feedback on their open canvas.

Week 5 and later

  • Create a GitHub repository for your project
  • Add the link to your repository in your issue
  • Use your canvas to start writing a README.md file, or landing page, for your project
  • Link to your README in a comment on this issue
  • Add an open license to your repository as a file called LICENSE.md
  • Add a Code of Conduct to your repository as a file called CODE_OF_CONDUCT.md
  • Invite new contributors to into your work!

This issue is here to help you keep track of work as you start Open Life Science program. Please refer to the OLS-2 Syllabus for more detailed weekly notes and assignments past week 4.

@da5nsy
Copy link
Author

da5nsy commented Sep 24, 2020

Draft vision statement:

I’m working with neurophysiologists and metascientists to create a guide to using the registered report format specifically for those in our field so that we can reap the benefits of the format (peer review in advance of data collection, and reducing publication bias).

Link to repo: https://github.com/da5nsy/Registered-Reports-in-Primate-Neurophysiology

@da5nsy
Copy link
Author

da5nsy commented Sep 24, 2020

I tried putting my vision statement through the upgoer5 process and I'm quite happy with the result:

I am working with people who study cells in small human-like animal brains and people who think really hard about how we actually do that type of work, to make something that helps people write about that type of work in a better way than what happens now,

because that way of writing means that people get help with their plan for the work before they actually do it, rather than on the work after it is already done (which is much less good, obviously, because actually doing the work takes lots of time and money, and you really don't want to do it more than once)

and it also means that work it shared because it is good rather than because something weird was found (which sometimes is exciting and good, but also sometimes is just because of chance).

I've broken it up because as a single sentence it is quite a mouthful!
I think it works really well though! And it definitely forced me to think about how to explain things in a less jargon-y way!

@CooperSmout
Copy link

Hi @da5nsy, excited to see what comes from this project! My background is in cognitive neuroscience, so slightly adjacent to your field, but we have a similar need for more RR support in our field. My colleague held a panel session on developing RR templates at the recent OHBM Open Science Room conference, which might be informative and I'll link here when the recording becomes available.

Regarding your vision statement -- to be honest I think the first version is better! Personally I don't see a problem using terms like 'neurophysiologists' and 'metascientists' in your vision statement because these are your target market, and also think it's better as a single concise statement -- but just my opinion :)

And finally, wanted to highlight a possible synergy between your project and mine (#5), which aims to support open science behaviours through collective action. The basic premise is that individuals (especially ECRs) might not feel comfortable adopting new behaviours due to potential costs, whether real or imagined (e.g., supervisors don't support it, it costs them time, can't publish in prestigious journals), but these costs can be mitigated if enough people act together to make the behaviour a new norm. I'd love to discuss a campaign to support RR in neurophysiology -- we could even build the campaign around the template you develop, which would mutually support the community as it grows (and provide additional pressure on journals to adopt the format). We recently started discussing a similar domain-general idea here, in case you have any feedback.

@CooperSmout
Copy link

My colleague held a panel session on developing RR templates at the recent OHBM Open Science Room conference, which might be informative and I'll link here when the recording becomes available

the link is now available here, just in case you're interested :)

@da5nsy
Copy link
Author

da5nsy commented Oct 1, 2020

Open Canvas: link

@malvikasharan
Copy link
Member

@all-contributors please add @da5nsy for idea and content.

@allcontributors
Copy link
Contributor

@malvikasharan

I've put up a pull request to add @da5nsy! 🎉

@malvikasharan
Copy link
Member

Comments on Open Canvas: @da5nsy, I really like where this canvas is directing you too. I am adding a few suggestion hoping this can help in the next weeks while you develop your idea.

  • do you want to brainstorm what resources you have available (webserver, social media, GitHub repo, team, community etc.) and what you will need specifically, going forward?
  • In metrics, would you also want to have some sort of survey or user interaction to gain their experience at different stages of development to guide the development of your project?
  • Contributors and user profile: you can go even deeper to understand if these people are grad students - if so, can they be taught formally to understand the process of RR - how can they contribute? if they are lab technicians - what resources they can be given to guide their experiments or what experiences they can share, a PI then do we need institutional leadership support to impact how they work (ethics, animal experiment policy etc.)?
  • contributors and user channel: can this be social media, online repository, a google form, community call - how would you create a pathway for them to contribute or use information?

@da5nsy
Copy link
Author

da5nsy commented Nov 26, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants