Review below and add new text in between the [ ]'s
Hi All,
Thanks for a the Pathways Share session last week! Great job describing this ongoing work in progress, with themes of onboarding, data management, collaborating on big projects across labs, consolidating/comparing different protocols, and more. Below is a light digest of last week, including a reminder for your Seaside Chat before our Call 5 next Thursday, November 4. Looking forward to seeing you then!
Goals: Each team shared their pathway and we will discuss next steps going forward
Task for next time: Listen to a podcast about protocols!
Have a Seaside Chat with your broader research group
Listen to MTMI podcasts (try to distribute among the lab members different episodes, with each listening to one of the following and then discussing the “troubleshooting of something that used to work”
Review open communities slides; report out on communities you use/know about (comment on slides, or add a GitHub Issue)
Co-working (optional). This is a time to come work on your own things, but also be able to talk things through and screenshare to get help from others. Check your emails for Calendar Invites with Zoom links.]
Pathway Presentations:
Themes:
Onboarding
Offboarding
Data storage and archiving - big theme
where to store, who has access? petabytes, collected by diff people, live in diff places, how to collaborate within the lab but also across labs
Naming protocols with more specificity
Protocols having an abstract as well “this works for this kind of experiment but not this other way”
Time burden involved
A few lines from shared notes in the Agenda doc:
“Floating protocol phenomenon” - protocol in Google Drive but not in a folder. “I know we’ve done it, I don’t know where it is”
We all work on diff projects so nice to have a protocols/onboarding shared “project” to all come together and work together
Lenny: what’s a good examples/template of someone leaving
One barrier is integrating some way of managing data with some way of managing physical specimens/samples in the lab.
I hadn’t thought as much about the whole onboarding issue, but I realize it is one we spend a lot of time on, and should have a set approach that would save having to reinvent the wheel.
Tension of github for code and data somewhere else vs keeping code+data together in github
jules32
commented
2 years ago
TODO:
Review below and add new text in between the
[ ]'sHi All,
Thanks for a the Pathways Share session last week! Great job describing this ongoing work in progress, with themes of onboarding, data management, collaborating on big projects across labs, consolidating/comparing different protocols, and more. Below is a light digest of last week, including a reminder for your Seaside Chat before our Call 5 next Thursday, November 4. Looking forward to seeing you then!
Have a good week,
Lenny, Emma, Erin, Julie
Digest: Cohort Call 4 [ 2021-sasi ]
CohortCalls folder - contains video recordings and completed agendas https://openscapes.github.io/2021-sasi - Cohort webpage
Goals: Each team shared their pathway and we will discuss next steps going forward
Task for next time: Listen to a podcast about protocols!
Have a Seaside Chat with your broader research group
Listen to MTMI podcasts (try to distribute among the lab members different episodes, with each listening to one of the following and then discussing the “troubleshooting of something that used to work”
Review open communities slides; report out on communities you use/know about (comment on slides, or add a GitHub Issue)
Co-working (optional). This is a time to come work on your own things, but also be able to talk things through and screenshare to get help from others. Check your emails for Calendar Invites with Zoom links.]
Pathway Presentations:
Themes:
A few lines from shared notes in the Agenda doc:
Tweets