MetaReviewer

We're back with a new #MetaReviewerMondays series we are calling Meta in Motion #metainmotion We plan to spotlight one project using @Meta_Reviewer per month; four total are planned with an option for more. #systematicreview #metaanalysis #evidencesynthesis #correlation

People keep asking us... (more later today!)

Determining which effect size to calculate is tough, y'all. We know the pain of sifting through various summary statistics, modeling approaches, and incomplete data! So we designed the Effect Size Decision Tree to help synthesis teams navigate the process.

#MetaReviewerMondays #NewYearNewReview We introduce the Effect Size Decision Tree! #metaanalysis #effectsize metareviewer.org/learn/new-y…

This is Part 1 of a two-part series on "Citations in MetaReviewer". Stay tuned for the stunning conclusion next week!

#MetaReviewerMondays #NewYearNewReview @jrpolanin takes a look at citations in @Meta_Reviewer!

Perhaps you are thinking 'c'mon @Meta_Reviewer, we know you made this story up because you wanted internet points'. To that we say: pictures or it's not real! (i.e., here's our now closed GitHub ticket) Help Us Help You - send us (good) help desk requests to metareviewer@air.org

Yes irony abounds this week as @im_tired_yall explains the do's and dont's of submitting a Help Desk request.

It happens! Fortunately @Meta_Reviewer is designed to allow for changes to coding forms. @CharlieEbersole walks users through the process of using the coding form editor within the application. Problem solved!

We consider. We consult. We try out. We pilot. We test. We pilot (again). We modify. Finally, we implement data extraction. And then... four weeks into the process, someone finds a study that doesn't fit the coding form and... Our coding form must change.