-
Notifications
You must be signed in to change notification settings - Fork 1
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
add Fig. 3 #82
Comments
So just for my understanding because this is not clear from the different info streams: figure 3 is the figure with demographic trends through time. Are we saying that, even though there is no (?) IRB approval to share the raw data, we might show a figure? |
I have added a suggestion for a figure to the manuscript. This figure lumps all affirmative responses to the NEAD question about belonging to a traditionally underrepresented group (i.e. both gender and ethnicity) in one count and turns this into the percentage of participants. It would be nice if we could use this because it does show a clear trend. However, I am really unclear as to what we can and cannot put in the paper what with this IRB stuff. A number of issues now hinge on this (I've labeled them). |
So the decision is to NOT add a figure like this at all because any usage of NEAD data is not allowed. |
right. we could do gender by eyeball, but that is as far as we can go. |
I recognize that dropping this idea is the easiest solution, but determining gender through means other than applying for permission to release protected data, or eyeballing, is neither that hard nor is it rarely done. In fact, there are APIs and software packages for doing this based on names alone:
I'm happy to try and run our names through the Bottom line, I think diversity in informatics is really important, and I think the data we have is interesting enough to at least try for the one demographic diversity that is relatively easy to come by even without releasing protected data. |
Go for it, then! With the NEAD data it looked like there was actually
something worth reporting so if we can get substantially similar results by
legal means I am all for it.
Op Sat, 10 Dec 2016 om 01:29 schreef Hilmar Lapp <[email protected]>
… Reopened #82 <#82>.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#82 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAGf-hsf13FpkfMAx3IqByuy7YyCwJMCks5rGfJYgaJpZM4JYaxU>
.
|
I'll hold off until I get the 👍 from @arlin as in the end it will have to pass muster with his IRB, if I understand correctly. |
Yes, thanks @hlapp, please go ahead. I am planning a meeting with them next week to discuss the new manuscript. |
reconstruct from data
The text was updated successfully, but these errors were encountered: