OpenWetWare:Why join? - Revision history

Christopher M Gowen: /* Vandalism */

2009-03-18T04:34:50Z

Vandalism

←Older revision		Revision as of 04:34, 18 March 2009
Line 53:		Line 53:

	==== Vandalism ====		==== Vandalism ====
-	One of the biggest concerns with wikis is the ability for anyone to vandalize other people's work. ~~While sites~~ like wikipedia are able to [[Wikipedia:Dealing_with_vandalism\|deal with it]] because they have such a large benevolent user base compared to the number of vandalisms. The community we are creating with OpenWetWare is significantly smaller. Thus, we can't assume that vandals will be caught quickly. Therefore, we have decided to make it such that only registered users and groups can edit content. That way, each edit is trackable to a specific person, which can be tracked down by their email address. We find that this public embarrassment factor, while increasing barriers to entry, provides sufficient impetus to prevent malicious or inconsiderate editing. So far, we have had no problems with vandalism, or unwanted edits, whether malicious or otherwise. Thus, we feel that this system is working. We will re-evaluate if and when a single instance of a problem arises.	+	One of the biggest concerns with wikis is the ability for anyone to vandalize other people's work. Sites like wikipedia are able to [[Wikipedia:Dealing_with_vandalism\|deal with it]] because they have such a large benevolent user base compared to the number of vandalisms. The community we are creating with OpenWetWare is significantly smaller. Thus, we can't assume that vandals will be caught quickly. Therefore, we have decided to make it such that only registered users and groups can edit content. That way, each edit is trackable to a specific person, which can be tracked down by their email address. We find that this public embarrassment factor, while increasing barriers to entry, provides sufficient impetus to prevent malicious or inconsiderate editing. So far, we have had no problems with vandalism, or unwanted edits, whether malicious or otherwise. Thus, we feel that this system is working. We will re-evaluate if and when a single instance of a problem arises.

	==== Permissions ====		==== Permissions ====

SoniaT: /* Persistent Information */

2006-03-29T00:35:36Z

Persistent Information

←Older revision		Revision as of 00:35, 29 March 2006
Line 18:		Line 18:
	==Why are wikis useful for research labs?==		==Why are wikis useful for research labs?==

-	===~~Persistant~~ Information===	+	===Persistent Information===
-	The amount of information and expertise that is accrued in labs is tremendous. Conveying this information and expertise to subsequent lab members and to the greater scientific community now often relies on talking and interacting closely with the right people. One reason for this is that it is quite difficult to put these thoughts down in a systematic way. Tremendous amounts of individual expertise and information is lost when lab members leave (a key problem given the high turnover rate of academic labs). The wiki provides a low-barrier of entry method for lab members to contribute that information to a database which will persist after they leave the lab.	+	The amount of information and expertise that is accrued in labs is tremendous. Conveying this information and expertise to subsequent lab members and to the greater scientific community now often relies on talking and interacting closely with the right people. One reason for this is that it is quite difficult to put these thoughts down in a systematic way. Tremendous amounts of individual expertise and information is lost when lab members leave (a key problem given the high turnover rate of academic labs). The wiki provides a low-barrier of entry method for lab members to contribute that information to a database which will persist after they leave the lab.

	===Dynamic Information===		===Dynamic Information===

Jason R. Kelly: /* Reasons to join */

2006-03-01T13:46:57Z

Reasons to join

←Older revision		Revision as of 13:46, 1 March 2006
Line 40:		Line 40:
	Second, the shared resources sections have the potential to be much better than with any lab alone. Since most labs have many of these shared resources in common, it behooves us to collaborate on their content generation and upkeep, rather than repeating that work over and over again.		Second, the shared resources sections have the potential to be much better than with any lab alone. Since most labs have many of these shared resources in common, it behooves us to collaborate on their content generation and upkeep, rather than repeating that work over and over again.

-	Third, wiki's also require some backend users that upkeep not only the content, but the look and feel, and overall organization. Currently we have a few people that do this in the backgroud, that have led to current state of OpenWetWare. However, if you ask any of them, there are not nearly enough people for all the work that could be done. Starting a lab wiki from scratch would probably require some initial effort on the behalf of these people. However, tapping into a community that already exists would probably reduce the amount of effort compared to starting from scratch. Also, it would provide us with more of these backend users :-).	+	Third, wiki's also require some [[OpenWetWare:Getting started 3\|backend, "power" users]] that upkeep not only the content, but the look and feel, and overall organization. Currently we have a few people that do this in the backgroud, that have led to current state of OpenWetWare. However, if you ask any of them, there are not nearly enough people for all the work that could be done. Starting a lab wiki from scratch would probably require some initial effort on the behalf of these people. However, tapping into a community that already exists would probably reduce the amount of effort compared to starting from scratch. Also, it would provide us with more of these backend users :-).

	Fourth, there are collaborative sections that will be better the more labs that join. For example, the [[Protocols]] section provides a general area to post protocols. While a protocol describing how to perform ''in vitro'' [[DNA Ligation \| DNA ligation]] is useful from one lab, it is probably even more useful for many. The [[DNA Ligation \| DNA ligation]] protocol just describes a general method, while the [[Endy:DNA ligation using T4 DNA ligase\|Endy Lab]] and the [[Knight:DNA ligation using NEB Quick Ligation Kit\|Knight Lab]] have their own protocols and reasons to do them differently. A balance between shared and lab-specific protocol space allows for optimization of protocols and faster learning curves for new lab members trying to learn techniques.		Fourth, there are collaborative sections that will be better the more labs that join. For example, the [[Protocols]] section provides a general area to post protocols. While a protocol describing how to perform ''in vitro'' [[DNA Ligation \| DNA ligation]] is useful from one lab, it is probably even more useful for many. The [[DNA Ligation \| DNA ligation]] protocol just describes a general method, while the [[Endy:DNA ligation using T4 DNA ligase\|Endy Lab]] and the [[Knight:DNA ligation using NEB Quick Ligation Kit\|Knight Lab]] have their own protocols and reasons to do them differently. A balance between shared and lab-specific protocol space allows for optimization of protocols and faster learning curves for new lab members trying to learn techniques.

Jason R. Kelly: /* Shared Materials Information */

2006-03-01T13:44:57Z

Shared Materials Information

←Older revision		Revision as of 13:44, 1 March 2006
Line 28:		Line 28:

	===Shared Materials Information===		===Shared Materials Information===
-	[[Materials\|Chemicals]], [[Vectors \| vectors]], [[Strains \| strains]], [[Materials#Antibiotics\|antibiotics]], [[Computing\|computing]], ''etc.'', can have their own wiki pages listing general information, safety, and more. Since these are things which are general information rather than lab-specific (like protocols) they could be shared across labs. For example if a protocol called for the use of [[Ampicillin]], it could include a link to [[[[Ampicillin\|this]], so if you forget the mode of action of ampicillin you just click rather than have to go dig it up in [[Molecular Cloning]].	+	[[Materials\|Chemicals]], [[Vectors \| vectors]], [[Strains \| strains]], [[Materials#Antibiotics\|antibiotics]], [[Computing\|computing]], ''etc.'', can have their own wiki pages listing general information, safety, and more. Since these are things which are general information rather than lab-specific (like protocols) they could be shared across labs. For example if a protocol called for the use of [[Ampicillin]], it could include a link to [[Ampicillin\|this]], so if you forget the mode of action of ampicillin you just click rather than have to go dig it up in [[Molecular Cloning]].

	A list of [[Equipment\|equipment]] provides a useful shared resource to make labs aware of the available local equipment. Also, equipment pages serve as a central repository for control experiments and other information about the device. For example, the [[Endy:Victor3 plate reader\|Victor3 plate reader]] located in the Endy Lab has posted not only simple usage information, but also sets of controls on a variety of topics such as how the [[Endy:Victor3 lamp energy\|lamp energy]] affects signal to noise ratios.		A list of [[Equipment\|equipment]] provides a useful shared resource to make labs aware of the available local equipment. Also, equipment pages serve as a central repository for control experiments and other information about the device. For example, the [[Endy:Victor3 plate reader\|Victor3 plate reader]] located in the Endy Lab has posted not only simple usage information, but also sets of controls on a variety of topics such as how the [[Endy:Victor3 lamp energy\|lamp energy]] affects signal to noise ratios.

Jason R. Kelly: /* Shared Materials Information */

2006-03-01T13:44:44Z

Shared Materials Information

←Older revision		Revision as of 13:44, 1 March 2006
Line 28:		Line 28:

	===Shared Materials Information===		===Shared Materials Information===
-	[[Materials\|Chemicals]], [[Vectors \| vectors]], [[Strains \| strains]], [[Materials#Antibiotics\|antibiotics]], [[Computing\|computing]], ''etc.'', can have their own wiki pages listing general information, safety, and more. Since these are things which are general information rather than lab-specific (like protocols) they could be shared across labs. For example if a protocol called for the use of [[Ampicillin]], it could include a link to this, so if you forget the mode of action of ampicillin you just click rather than have to go dig it up in [[Molecular Cloning]].	+	[[Materials\|Chemicals]], [[Vectors \| vectors]], [[Strains \| strains]], [[Materials#Antibiotics\|antibiotics]], [[Computing\|computing]], ''etc.'', can have their own wiki pages listing general information, safety, and more. Since these are things which are general information rather than lab-specific (like protocols) they could be shared across labs. For example if a protocol called for the use of [[Ampicillin]], it could include a link to [[[[Ampicillin\|this]], so if you forget the mode of action of ampicillin you just click rather than have to go dig it up in [[Molecular Cloning]].

	A list of [[Equipment\|equipment]] provides a useful shared resource to make labs aware of the available local equipment. Also, equipment pages serve as a central repository for control experiments and other information about the device. For example, the [[Endy:Victor3 plate reader\|Victor3 plate reader]] located in the Endy Lab has posted not only simple usage information, but also sets of controls on a variety of topics such as how the [[Endy:Victor3 lamp energy\|lamp energy]] affects signal to noise ratios.		A list of [[Equipment\|equipment]] provides a useful shared resource to make labs aware of the available local equipment. Also, equipment pages serve as a central repository for control experiments and other information about the device. For example, the [[Endy:Victor3 plate reader\|Victor3 plate reader]] located in the Endy Lab has posted not only simple usage information, but also sets of controls on a variety of topics such as how the [[Endy:Victor3 lamp energy\|lamp energy]] affects signal to noise ratios.

Austin J. Che: /* Our own space */

2006-01-18T23:45:18Z

Our own space

←Older revision		Revision as of 23:45, 18 January 2006
Line 48:		Line 48:

	==== Our own space ====		==== Our own space ====
-	Many labs feel as though their presence will be diluted in a larger site such as OpenWetWare. This is a concern we share to some extent. For example, ~~both~~ http://web.mit.edu/endy ~~and http://www.syntheticbiology.org both point~~ to ~~pages~~ within OpenWetWare, and this arrangement may have less branding effect than if ~~the sites~~ were independent. We have found the collaborative and dynamic nature of OpenWetWare to be worth the loss in brand. In addition, what we have been finding is that there are ways to make the navigational experience for the user more branded. For example, [[Endy:Research\|most Endy lab pages]] have a [[Template:EndyLab\|navigation bar template]] that allows visitors to traverse the Endy lab pages easily, without being too distracted by all the other content available. We are currently working on ways to customize this further (for example, the ability to change the sidebar). If you have any ideas, let us know.	+	Many labs feel as though their presence will be diluted in a larger site such as OpenWetWare. This is a concern we share to some extent. For example, http://web.mit.edu/endy points to a page within OpenWetWare, and this arrangement may have less branding effect than if it were independent. We have found the collaborative and dynamic nature of OpenWetWare to be worth the loss in brand. In addition, what we have been finding is that there are ways to make the navigational experience for the user more branded. For example, [[Endy:Research\|most Endy lab pages]] have a [[Template:EndyLab\|navigation bar template]] that allows visitors to traverse the Endy lab pages easily, without being too distracted by all the other content available. We are currently working on ways to customize this further (for example, the ability to change the sidebar). If you have any ideas, let us know.

	Another reason people want their own space is that someone from the Endy Lab doesn't necessarily want a Grossman lab ruffian to edit their protocols, and vice versa. To combat this to some extent, we have been labeling lab-specific pages (pages that a lab doesn't want edited by other labs) by prefacing them with the lab/organization name (for example [[Endy:Research]]). As a matter of etiquette, everyone is asked to be respectful of pages that are not part of the user's organization. We have not had problems with this so far.		Another reason people want their own space is that someone from the Endy Lab doesn't necessarily want a Grossman lab ruffian to edit their protocols, and vice versa. To combat this to some extent, we have been labeling lab-specific pages (pages that a lab doesn't want edited by other labs) by prefacing them with the lab/organization name (for example [[Endy:Research]]). As a matter of etiquette, everyone is asked to be respectful of pages that are not part of the user's organization. We have not had problems with this so far.

Ilya at 21:49, 14 December 2005

2005-12-14T21:49:15Z

←Older revision		Revision as of 21:49, 14 December 2005
Line 59:		Line 59:

	Generally, we feel the tendency is for labs, particularly in the biological sciences, not to share information in a generally available way. (Most labs are very helpful on an individual, case by case basis however.) But if everyone shares their expertise then ultimately everyone benefits from the "open commons" of information. There is also often a general concern that by making ideas/expertise publicly available, such as on a website, you risk someone else either a) scooping your work or b) somehow losing your edge against other labs. Usually, however, if you are open and sharing of information, then others will respond in kind with the long-term benefits outweighing short-term disadvantages. Two proofs of this principle are the open source software community and wikipedia. Alternatively, there is the purely pedagogical reason that a fundamental goal of all universities is education: we have an obligation to share our information in any way possible.		Generally, we feel the tendency is for labs, particularly in the biological sciences, not to share information in a generally available way. (Most labs are very helpful on an individual, case by case basis however.) But if everyone shares their expertise then ultimately everyone benefits from the "open commons" of information. There is also often a general concern that by making ideas/expertise publicly available, such as on a website, you risk someone else either a) scooping your work or b) somehow losing your edge against other labs. Usually, however, if you are open and sharing of information, then others will respond in kind with the long-term benefits outweighing short-term disadvantages. Two proofs of this principle are the open source software community and wikipedia. Alternatively, there is the purely pedagogical reason that a fundamental goal of all universities is education: we have an obligation to share our information in any way possible.
-
-	~~==How do I join or I have a question?==~~
-	Email admin AT openwetware DOT org. Feel free to email regardless of whether you are an individual, a student group, a lab or <insert your group here>. Your research or interests do not necessarily have to be biologically relevant either.

	==Examples==		==Examples==

Ilya: /* How do I join or I have a question? */

2005-12-01T00:32:51Z

How do I join or I have a question?

←Older revision		Revision as of 00:32, 1 December 2005
Line 61:		Line 61:

	==How do I join or I have a question?==		==How do I join or I have a question?==
-	Email ~~endipedia-~~admin AT ~~mit~~ DOT ~~edu~~. Feel free to email regardless of whether you are an individual, a student group, a lab or <insert your group here>. Your research or interests do not necessarily have to be biologically relevant either.	+	Email admin AT openwetware DOT org. Feel free to email regardless of whether you are an individual, a student group, a lab or <insert your group here>. Your research or interests do not necessarily have to be biologically relevant either.

	==Examples==		==Examples==

Jason R. Kelly: /* Examples */

2005-09-19T22:56:55Z

Examples

←Older revision		Revision as of 22:56, 19 September 2005
Line 68:		Line 68:
	[[WikiPedia:Main Page \| Wikipedia]] is a great example of a useful information resource being created via a wiki.		[[WikiPedia:Main Page \| Wikipedia]] is a great example of a useful information resource being created via a wiki.

-	The [[Getting Started on OpenWetWare]] provides a quick walkthough of some of OpenWetWare's possible uses.	+	The [[Getting Started on OpenWetWare]] page provides a quick walkthough of some of OpenWetWare's possible uses.

	==Related Information==		==Related Information==
	See the [[MetaWikiPedia:Interwiki map\|Interwiki map]] for other wiki's.		See the [[MetaWikiPedia:Interwiki map\|Interwiki map]] for other wiki's.

Jason R. Kelly: /* Examples */

2005-09-19T22:56:41Z

Examples

←Older revision		Revision as of 22:56, 19 September 2005
Line 67:		Line 67:

	[[WikiPedia:Main Page \| Wikipedia]] is a great example of a useful information resource being created via a wiki.		[[WikiPedia:Main Page \| Wikipedia]] is a great example of a useful information resource being created via a wiki.
		+
		+	The [[Getting Started on OpenWetWare]] provides a quick walkthough of some of OpenWetWare's possible uses.

	==Related Information==		==Related Information==
	See the [[MetaWikiPedia:Interwiki map\|Interwiki map]] for other wiki's.		See the [[MetaWikiPedia:Interwiki map\|Interwiki map]] for other wiki's.