OpenWetWare:Steering committee/Town Hall Meeting/2008/08/14: Difference between revisions

From OpenWetWare
Jump to navigationJump to search
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==Welcome to the OWW Community Town Hall Meeting for August, 2008==
==Welcome to the OWW Community Town Hall Meeting for August, 2008==
Teleconference dial-in number: 1-617-324-7374.
Use these URL's to get to the chat room if you can't get there from here:
Use these URL's to get to the chat room if you can't get there from here:


Line 7: Line 10:


==This month's topic: '''Curation of content on OWW'''==
==This month's topic: '''Curation of content on OWW'''==
One person's "finished" protocol is another person's starting point. Useful, accurate content on OWW is something we all want, so I'd like to explore the idea of community curation on OWW.
Useful, accurate information on OWW is something we all aspire to, so let's explore the idea of community-based content curation. If one person's "finished" protocol is another person's starting point, how do we ensure that the information in our protocols, and other how-to pages is as good as it can be...  


Please add your ideas, comments, or suggestions here.
Please add your ideas, comments, or suggestions here.
*'''[[User:Jason R. Kelly|Jason R. Kelly]] 21:30, 12 August 2008 (EDT):''' Would be great to try to brainstorm ways that curation could be a way to ''encourage'' contribution rather than something that prevents it.  How do we avoid curation that serves as a gatekeeper lowering overall content contribution - for instance the inabilty to comment in genbank?  Curation can also be a way to encourage contribution - for instance, by creating academic credit via a "stamp of approval" (a la peer-reviewed journals).  Seems a tough balance to strike.


== Follow-up Topics==
== Follow-up Topics==

Latest revision as of 18:32, 12 August 2008

Welcome to the OWW Community Town Hall Meeting for August, 2008

Teleconference dial-in number: 1-617-324-7374.

Use these URL's to get to the chat room if you can't get there from here:

This month's topic: Curation of content on OWW

Useful, accurate information on OWW is something we all aspire to, so let's explore the idea of community-based content curation. If one person's "finished" protocol is another person's starting point, how do we ensure that the information in our protocols, and other how-to pages is as good as it can be...

Please add your ideas, comments, or suggestions here.

  • Jason R. Kelly 21:30, 12 August 2008 (EDT): Would be great to try to brainstorm ways that curation could be a way to encourage contribution rather than something that prevents it. How do we avoid curation that serves as a gatekeeper lowering overall content contribution - for instance the inabilty to comment in genbank? Curation can also be a way to encourage contribution - for instance, by creating academic credit via a "stamp of approval" (a la peer-reviewed journals). Seems a tough balance to strike.

Follow-up Topics

Other Links Cited

Chat

<html>

<div style="width:800px"> <style> .mcrmeebo { display: block; background:url("http://widget.meebo.com/r.gif") no-repeat top right; } .mcrmeebo:hover { background:url("http://widget.meebo.com/ro.gif") no-repeat top right; } </style>

<object width="800" height="600" > <param name="movie" value="http://widget.meebo.com/mcr.swf?id=dGvMJJZSoQ"/> <embed src="http://widget.meebo.com/mcr.swf?id=dGvMJJZSoQ"

 type="application/x-shockwave-flash" width="800" height="600" />

</object>

<a href="http://www.meebo.com/rooms" class="mcrmeebo"> <img alt="http://www.meebo.com/rooms" src="http://widget.meebo.com/b.gif" width="800" height="90" style="border:0px"/> </a>

</div> </html>

Chat log