Openscapes Week 3 Digest

[adamkemberling]

Below is an abbreviated recap of what was covered in week three of the OPENSCAPES-FDD meeting:

Goals: We discussed open communities and coding strategies for future us with special guest Kim Bastille, NOAA NEFSC

Task for next time: Explore community resources, prepare to present your Pathway

Have a Seaside Chat with your broader research group

Explore more Community Tools
Prepare to present your Pathway on Call 4 (Oct 29)

Each group has 5 minutes to share their pathway: (3 min present + 2 min Qs)
Share your Pathway Doc in our PathwayShare folder before Call 4
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 Invite with Zoom links for Friday.

nmfs-openscapes

The NOAA NMFS Cohort (happening at the same time as our FDD Cohort) is leading a lot of community events of interest.
You can join the NMFS R User Group by signing up here. The NMFS Openscapes GitHub org is assembling resources for Open Science efforts within NMFS. One upcoming event:

Oct 26th 9am PST. 508 Compliance and R Markdown documents. Kelli Johnson from the NMFS Cohort plus 2 others with experience preparing R Markdown reports that are 508 Complaint will talk about their experience with this process. Link to the Event
Slide Decks:

These are also available publicly from openscapes.org/series

• Open Communities
• Coding Strategies for Future Us: State of the Ecosystem Product Development Workflow by Kim Bastille
• Coding Strategies for Future Us: Expanding OuR Communities by Chanté Davis - the guest teacher in the the NOAA NMFS Cohort that might be of interest (see more about it above)
• Discovering Community Tools -- we did not review this during the call, but these might be a helpful place to start for exploring more community tools, potentially during a seaside chat.

A few lines from shared notes in the Agenda doc:

• Folks shared lots of great people and things that influence their work - it's definitely worth reading through the roll call to get some inspiration!
• Learned we are part of more communities than we thought we were - and are interested in joining more. Some common groups were: Twitter, South Coast UseR, RLadies...and Openscapes!
• Interest in creating a space for the FDD community to continue these types of conversations. Ideas included: using Slack, webinars, FDD office hours.
• Kim's Coding Strategies for Future Us presentation and discussion resonated with the group
• Yes to the Apple Tree Workflow and the idea that although products (apples) may be varied, the workflows stay the same (e.g. Rmd Code Chunks converted to Individual R scripts)!
• Barriers that exist for sharing analytical or data workflows within your existing teams included:
• Keeping team members that use R and those that do not in the same reproducible workflow. Thinking through options for this. +1 +1 +1
• Figuring out what workflows look like when there is some confidential data in the pipeline - Perhaps we can look to other communities of practice for help with this (e.g. CDC, census information, etc.).
• Ideas to better strengthen the consistency of your scientific workflow: quality, reproducibility and utility of code, data, data workflows, lab and field (ship) workflows that you use day to day included:
• Consistency in file naming/organization would help keep things from getting cluttered and messy +1
• Working on annotating my code better so that my teammates and future me can figure out what I was doing and how to tweak it +1
• Working towards creating flow charts that show how different files, codes, and outputs are all related. Inspired by Jessica Gephart’s example +1 +1