OpenWetWare:ProjectDevelopment/OWW peer review process
A process by which authors on OWW can invite community peer review of their content.
Challenge or opportunity the development project answers
Giving the community a more quantitative means of knowing which content is well-tested, what could be changed or improved, and why.
Examples of what could be done or how it would work
This system could be used for any piece of content on OWW, but I'll use a protocol as an example.
A button called "prime time" appears at the bottom of every protocol. When the author of the protocol feels that it is ready for wider distribution or review, he or she clicks the button. The protocol is time- and date-stamped. It can be uploaded to a repository with a link back to the working version.
When committed to Primetime, the protocol acquires a dashboard of buttons in its sidebar. One of them might be "I use this". Another might be "add review comments" etc. Yet another might be "Users". If you like the protocol and use it, you click on the "I use this" button, and your name is added to the list of users. If you want to make comments, you click the comments button and a text box appears. The button could also take you to protocol's talk page.
Now, let's say you do a search for "Beta glactosidase assay." Up pops the list of available protocols, ranked by the number of users it's collected. If you roll your cursor over the user button in protocol's dashboard it shows a list of OWW member names who have "certified" it. Roll over the "review comments" button and read the comments they've left.
Why the project should happen now
Community peer review could be an important step toward formal peer review by external publications, and it can help potential users find the best protocols more quickly.
Who are the immediate customers?
All OWW members.