Feedback & Questions

[mekline]

One of our most important goals right now is making sure the project is accessible to people who are potential users but *haven't * though a ton about metadata and data management design. And there are areas (especially in testing and writing instructions) where people who are really good at their domain and don't spend all day thinking about JSON schemas are exactly who we'll need help from to make Psych-DS a useful resource!

This is an issue, which just means it's a known task/problem Psych-DS is trying to solve. This one is very general: the goal is to find out what people find confusing when they first encounter this project. If you got here by clicking the link on the README, you can contribute to this issue by either making a comment below (you have to make a free Github account first) or filling out this form.

Instructions:

Take a look at the readme, and ask questions. This is supposed to be an informative page for someone seeing the project for the first time, but probably doesn't accomplish that goal very well yet.

Questions might include :

• "Okay, but how do I actually ..."

• "What does this term mean?" (Please ask me! I find most google results in this area impenetrable. I only really started thinking about this a few months ago, and only succeeded by actually talking to humans.)

• "Isn't this just the same as [X procedure/tool/practice]? <-- either it is, which means we need to know about it, or it isnt and we need to explain PsychDS better!

• How would this help with [issue I think maybe is unique to my research or how I work]?

• ESPECIALLY if you are new to github, what is unclear? This is another topic where googling can be overwhelming/unhelpful. In the future we may be doing more actual editing of docs on github itself, but for now, we are mainly using it to organize what we are working on and what is coming up on the horizon (using the Issues.) Github can be very opaque, and we want to make sure it's not a barrier to participation.