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

Draft Survey Plan #12

Open
Tracked by #4
sk8forether opened this issue Mar 24, 2022 · 7 comments
Open
Tracked by #4

Draft Survey Plan #12

sk8forether opened this issue Mar 24, 2022 · 7 comments
Assignees

Comments

@sk8forether
Copy link
Collaborator

We need to complete a draft survey plan for the entire survey as a first priority. This will enable us to align objectives with questions and data collection. Previous Survey Planning efforts and the first Survey Draft can be used as a starting point.

@sk8forether sk8forether self-assigned this Mar 24, 2022
@exoticDFT
Copy link
Member

exoticDFT commented Feb 8, 2023

From 2022:

  • US-RSE Membership Metrics
  • Basic demographics to start? - Vandana
  • Benchmarking activity, repeat and track changes - Vandana
  • Let people know the purpose - collecting names to track who answered, but aggregating it for distribution - Vandana
  • Then connect as optional questions for new members - help us planning activities, speakers, topics, etc. - Vandana

@lparsons
Copy link
Member

lparsons commented Feb 8, 2023

From meeting notes:

@JeffCarver
Copy link

@lparsons the E&T WG has also been discussing a survey. The SC has an agenda item to discuss surveys. Can we make sure to coordinate things before any group sends out a survey?

@sk8forether
Copy link
Collaborator Author

From my discussions with @cmaimone last year, we thought it would be good to have one single survey annually for all of US-RSE to minimize survey fatigue and ensure regularity. So, we were thinking of drafting a survey plan and then seeing if any of the WGs wanted to contribute, I believe.

I am happy to pick this back up with the help of anyone interested, but will miss the next DEI-WG meeting.

Also, it is probably good to share these here too (just shared them in Slack):

For anyone who collects data on gender identity and/or sexual orientation in surveys, here are some great resources/recommendations:
https://www.whitehouse.gov/wp-content/uploads/2023/01/SOGI-Best-Practices.pdf
https://www.nationalacademies.org/our-work/measuring-sex-gender-identity-and-sexual-orientation-for-the-national-institutes-of-health

@exoticDFT
Copy link
Member

Some notes from our Feb 9th meeting:

Survey planning:

  • Next step: gather the WGs (E&T, DEI, ???) and SC in a collective meeting
  • Adrian Price-Whelan part of Simons - worked on AstroPy (successful OOS/community)
  • Create a Slack channel for this topic?

The second bullet we were discussing the fact that Michelle Barker from ReSA would like to organize a call with Adrian Price-Whelan from Simons to discuss how we might work together.

@exoticDFT
Copy link
Member

Some notes from 10/27/2023 WG DEI meeting:

  • What do we need to do for the larger demographic survey?
    • Anna has connection to a creator for the Mathematical Society survey (could give a talk?)
    • Need to discuss with Tab results from conference survey (see above)
  • Start some affinity groups based on results from the larger demographic survey

@exoticDFT
Copy link
Member

Notes from 03/13/2024:

  • Dan brought up that the UK-RSE was having a discussion on determining need for RSEs at institutions
    • A few people found local surveys useful
      • Could our survey also include some questions about RSE institutions, and not just RSEs?
    • E.g. how many RSEs do you think are at your institution?, how are they supported?
    • Or do we want a part of the survey to be just for RSE leaders?
    • Or a completely different survey for this?
      -Who has experience handling IRBs? Jeff, Christina?, Nasir?

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

4 participants