OpenWetWare:Presentations/Tools - Revision history

Austin J. Che: /* Science */

2006-08-02T14:41:12Z

Science

←Older revision		Revision as of 14:41, 2 August 2006
Line 27:		Line 27:
	*Process bibtex files into well formatted wikitext.		*Process bibtex files into well formatted wikitext.
	* Easy ability to embed more complicated viewing/editing tools (perhaps some API?). For example, a genome browser.		* Easy ability to embed more complicated viewing/editing tools (perhaps some API?). For example, a genome browser.
		+	* Example of putting parts registry completely into wiki

	===Publishing===		===Publishing===

Austin J. Che at 14:36, 2 August 2006

2006-08-02T14:36:14Z

←Older revision		Revision as of 14:36, 2 August 2006
Line 26:		Line 26:
	**This would be great because it would let communities build up around a particular protocol for instance. So if I was having trouble with a protocol, I could potentially email some of the people that we're watching it to get some help, etc.		**This would be great because it would let communities build up around a particular protocol for instance. So if I was having trouble with a protocol, I could potentially email some of the people that we're watching it to get some help, etc.
	*Process bibtex files into well formatted wikitext.		*Process bibtex files into well formatted wikitext.
		+	* Easy ability to embed more complicated viewing/editing tools (perhaps some API?). For example, a genome browser.

	===Publishing===		===Publishing===

Barry Canton: /* Science */

2006-08-02T14:33:04Z

Science

←Older revision		Revision as of 14:33, 2 August 2006
Line 25:		Line 25:
	* A tool to monitor who is "watching" a page/namespace		* A tool to monitor who is "watching" a page/namespace
	**This would be great because it would let communities build up around a particular protocol for instance. So if I was having trouble with a protocol, I could potentially email some of the people that we're watching it to get some help, etc.		**This would be great because it would let communities build up around a particular protocol for instance. So if I was having trouble with a protocol, I could potentially email some of the people that we're watching it to get some help, etc.
		+	*Process bibtex files into well formatted wikitext.

	===Publishing===		===Publishing===

Barry Canton: /* Misc */

2006-08-02T14:32:18Z

Misc

←Older revision		Revision as of 14:32, 2 August 2006
Line 37:		Line 37:
	===Misc===		===Misc===
	* Bulk image upload		* Bulk image upload
		+	* Ability to select a piece of text on a page and see who edited that text rather than trying to look through the edit history for an unattributed comment.

Jason R. Kelly: /* Needed tools */

2006-08-02T14:29:39Z

Needed tools

←Older revision		Revision as of 14:29, 2 August 2006
Line 17:		Line 17:
	* Laboratory management (what reagents are in the freezer?)		* Laboratory management (what reagents are in the freezer?)
	* Better user group system		* Better user group system
-		+	* Private pages
		+	**In a way that is non-obtrusive. e.g. I don't want to be banging into private pages all the time if I'm browsing the site...
	===Science===		===Science===
	* Wiki database		* Wiki database
Line 35:		Line 36:

	===Misc===		===Misc===
-	* Private pages
-	**In a way that is non-obtrusive. e.g. I don't want to be banging into private pages all the time if I'm browsing the site...
	* Bulk image upload		* Bulk image upload

Jason R. Kelly: /* Science */

2006-08-02T14:26:05Z

Science

←Older revision		Revision as of 14:26, 2 August 2006
Line 23:		Line 23:
	* Integrated discussion boards.		* Integrated discussion boards.
	* A tool to monitor who is "watching" a page/namespace		* A tool to monitor who is "watching" a page/namespace
-	**This would be great because it would let communities build up around a particular protocol for instance. So if I was having trouble with it, I could potentially email some of the people that we're watching it to get some help, etc.	+	**This would be great because it would let communities build up around a particular protocol for instance. So if I was having trouble with a protocol, I could potentially email some of the people that we're watching it to get some help, etc.

	===Publishing===		===Publishing===

Jason R. Kelly: /* Needed tools */

2006-08-02T14:25:42Z

Needed tools

←Older revision		Revision as of 14:25, 2 August 2006
Line 21:		Line 21:
	* Wiki database		* Wiki database
	* Semantic info		* Semantic info
		+	* Integrated discussion boards.
		+	* A tool to monitor who is "watching" a page/namespace
		+	**This would be great because it would let communities build up around a particular protocol for instance. So if I was having trouble with it, I could potentially email some of the people that we're watching it to get some help, etc.

	===Publishing===		===Publishing===
Line 26:		Line 29:
	* Easy connection with publishers ('send to Nature')		* Easy connection with publishers ('send to Nature')
	* Citations. Have Cite extension but would be ideal to have a doi per page.		* Citations. Have Cite extension but would be ideal to have a doi per page.
-

	===Personalized wiki===		===Personalized wiki===
	* More customizable recent changes (SpecialRecentChanges is a great start, but is a bit confusing for new users, maybe SpecialRecChanges w/ a prettier UI), for instance, I should be able to see all changes by a subset of users, all changes to pages I'm "watching", and all changes to a list of namespaces (e.g., Endy:, Knight:).		* More customizable recent changes (SpecialRecentChanges is a great start, but is a bit confusing for new users, maybe SpecialRecChanges w/ a prettier UI), for instance, I should be able to see all changes by a subset of users, all changes to pages I'm "watching", and all changes to a list of namespaces (e.g., Endy:, Knight:).
		+	* Tagging - I should be able to tag pages so that i can organize them for myself (for instance, I could tag DNA ligation as 'Protocol', 'DNA'). This way I could then look at my protocol tag and only get the protocols I care about rather than having to navigate the entire protocols section. The other advantage of this, of course, is to allow us to then aggregate the user generated tagging information in order to organize the general protocols area.

	===Misc===		===Misc===
	* Private pages		* Private pages
	**In a way that is non-obtrusive. e.g. I don't want to be banging into private pages all the time if I'm browsing the site...		**In a way that is non-obtrusive. e.g. I don't want to be banging into private pages all the time if I'm browsing the site...
-	* A tool to monitor who is "watching" a page/namespace
-	**This would be great because it would let communities build up around a particular protocol for instance. So if I was having trouble with it, I could potentially email some of the people that we're watching it to get some help, etc.
-	* Integrated discussion boards.
-	* Tagging - I should be able to tag pages so that i can organize them for myself (for instance, I could tag DNA ligation as 'Protocol', 'DNA'). This way I could then look at my protocol tag and only get the protocols I care about rather than having to navigate the entire protocols section. The other advantage of this, of course, is to allow us to then aggregate the user generated tagging information in order to organize the general protocols area.
	* Bulk image upload		* Bulk image upload

Jason R. Kelly at 14:24, 2 August 2006

2006-08-02T14:24:46Z

←Older revision		Revision as of 14:24, 2 August 2006
Line 28:		Line 28:


-	==Personalized wiki==	+	===Personalized wiki===
	* More customizable recent changes (SpecialRecentChanges is a great start, but is a bit confusing for new users, maybe SpecialRecChanges w/ a prettier UI), for instance, I should be able to see all changes by a subset of users, all changes to pages I'm "watching", and all changes to a list of namespaces (e.g., Endy:, Knight:).		* More customizable recent changes (SpecialRecentChanges is a great start, but is a bit confusing for new users, maybe SpecialRecChanges w/ a prettier UI), for instance, I should be able to see all changes by a subset of users, all changes to pages I'm "watching", and all changes to a list of namespaces (e.g., Endy:, Knight:).

Jason R. Kelly: /* Needed tools */

2006-08-02T14:24:24Z

Needed tools

←Older revision		Revision as of 14:24, 2 August 2006
Line 26:		Line 26:
	* Easy connection with publishers ('send to Nature')		* Easy connection with publishers ('send to Nature')
	* Citations. Have Cite extension but would be ideal to have a doi per page.		* Citations. Have Cite extension but would be ideal to have a doi per page.
		+
		+
		+	==Personalized wiki==
		+	* More customizable recent changes (SpecialRecentChanges is a great start, but is a bit confusing for new users, maybe SpecialRecChanges w/ a prettier UI), for instance, I should be able to see all changes by a subset of users, all changes to pages I'm "watching", and all changes to a list of namespaces (e.g., Endy:, Knight:).

	===Misc===		===Misc===
Line 32:		Line 36:
	* A tool to monitor who is "watching" a page/namespace		* A tool to monitor who is "watching" a page/namespace
	**This would be great because it would let communities build up around a particular protocol for instance. So if I was having trouble with it, I could potentially email some of the people that we're watching it to get some help, etc.		**This would be great because it would let communities build up around a particular protocol for instance. So if I was having trouble with it, I could potentially email some of the people that we're watching it to get some help, etc.
-	* More customizable recent changes (SpecialRecentChanges is a great start, but is a bit confusing for new users, maybe SpecialRecChanges w/ a prettier UI), for instance, I should be able to see all changes by a subset of users, all changes to pages I'm "watching", and all changes to a list of namespaces (e.g., Endy:, Knight:).
	* Integrated discussion boards.		* Integrated discussion boards.
	* Tagging - I should be able to tag pages so that i can organize them for myself (for instance, I could tag DNA ligation as 'Protocol', 'DNA'). This way I could then look at my protocol tag and only get the protocols I care about rather than having to navigate the entire protocols section. The other advantage of this, of course, is to allow us to then aggregate the user generated tagging information in order to organize the general protocols area.		* Tagging - I should be able to tag pages so that i can organize them for myself (for instance, I could tag DNA ligation as 'Protocol', 'DNA'). This way I could then look at my protocol tag and only get the protocols I care about rather than having to navigate the entire protocols section. The other advantage of this, of course, is to allow us to then aggregate the user generated tagging information in order to organize the general protocols area.
	* Bulk image upload		* Bulk image upload

Jason R. Kelly: /* Needed tools */

2006-08-02T14:23:14Z

Needed tools

←Older revision		Revision as of 14:23, 2 August 2006
Line 35:		Line 35:
	* Integrated discussion boards.		* Integrated discussion boards.
	* Tagging - I should be able to tag pages so that i can organize them for myself (for instance, I could tag DNA ligation as 'Protocol', 'DNA'). This way I could then look at my protocol tag and only get the protocols I care about rather than having to navigate the entire protocols section. The other advantage of this, of course, is to allow us to then aggregate the user generated tagging information in order to organize the general protocols area.		* Tagging - I should be able to tag pages so that i can organize them for myself (for instance, I could tag DNA ligation as 'Protocol', 'DNA'). This way I could then look at my protocol tag and only get the protocols I care about rather than having to navigate the entire protocols section. The other advantage of this, of course, is to allow us to then aggregate the user generated tagging information in order to organize the general protocols area.
		+	* Bulk image upload