OpenWetWare:Ideas: Difference between revisions

From OpenWetWare
Jump to navigationJump to search
No edit summary
 
(164 intermediate revisions by 25 users not shown)
Line 1: Line 1:
Note to sign your name+date in a reply type <nowiki>~~~~</nowiki>
{{cpnavbar}}


==Wikicities==
{| cellspacing="3" width="712px" class="green1" cellpadding="3"
|
[[Image:Ideas.png]] Welcome to Ideas discussion area.


In the newest Tech. Review, I stumbled upon [http://www.wikicities.com/ wikicities]. They have connections with Wikipedia. It looks to be a relatively new site (2004?) but they basically host a collection of wikis on specific topics. Some kind of community openwetware like site on there seems like it would be a good idea. We would not need to be responsible for the system administration headaches and I'm sure there are other benefits of having a centralized location for the wiki. We should definitely keep lab/group specific stuff here. I'm not sure what the use of this could be, but I see lots of benefit of allowing the world to edit some things like protocols. They currently have almost nothing under their biology category. --[[User:Austin|Austin]] 17:01, 29 Jul 2005 (EDT)
==How you can help==
*Distribute information from [[OpenWetWare:Ideas/IdeasArchive]] to respective areas.
*Firm up one of these ideas and put it on the official [[OpenWetWare:To do list|to do list]].
==Use of Mediawiki commons on OWW?==
[[User:Steven J. Koch|Steve Koch]] 03:16, 16 April 2008 (EDT):Has it been discussed previously the possibility of using images from Mediawiki commons on OWW. The way Wikipedia does it, so that you can use the same <nowiki>[[Image:whatever.png]]</nowiki> and if it doesn’t exist on OWW it will try to grab it from the commons?  I would use this in my research pages and my courses. (It would also be convenient if private wikis could use public wiki images (and templates) in a similar manner.I have no clue how hard this is to implement (I was just reminded of it today due to our discussion about tracking MediaWiki with OWW)…maybe it is easily copied from Wikipedia?


==Adding new groups to OWW==
==Invitations==
*'''[[User:Jason R. Kelly|Jason R. Kelly]] 08:44, 8 August 2007 (EDT):''' Should have a button/page that allows people to easily invite their friends/labmates to join OWW.  This is more relevant if we establish lab groups, etc, where we are storing the connections between users.  E.g. a person could join and then invite their whole lab, adding all of them to the group 'Endy lab' or whatever all in one shot.
:Agree--[[User:Dan Bolser|Dan]] 14:04, 13 February 2008 (CST)
**'''[[User:Bill Flanagan|wjf]] 14:10, 13 February 2008 (CST)''':I did something like this before. It's pretty simple. Al would be needed would be a form and an emai message. Hmm... let's think about it. I like the idea. You would also get an email message when the user joined.


I would like to build an OWW-based wiki for a student group in which I am involved, Students for Global Sustainability. I think there are many benefits of using OWW for this purpose, including:
==Search within tags/categories==
*'''[[User:Jason R. Kelly|Jason R. Kelly]] 09:56, 17 July 2007 (EDT):''' Would be nice to be able to have a 'search protocols' box. If we had tags/categories working well, it seems like this is something that could be implemented fairly easily.  If it was well done it would probably remove the need for an auto-generated, well-organized summary page (e.g. [[Protocols]] could be replaced by a search box).  This will become more important down the line as I suspect the single summary page won't scale.
*'''[[User:Etchevers|Alethea]] 09:02, 5 September 2008 (EDT)''': ''Is'' there a tag search capacity somewhere? Am I the only person who ''still'' can not conduct a successful search from either the lefthand navigation pane, or from within my lab notebook, and does this have more to do with my navigator or platform than with OWW?


# Many OWW researchers are interested in building bugs that will help solve world problems (energy, pollution control, material production, etc.) and SfGS is also interested in the same problems. Discourse amongst the two groups would prove mutually beneficial.
==Private/public lab notebooks==
# Biologists are underrepresented in the  sustainability community at MIT, and the community would be strengthened by their inclusion.
*'''[[User:Jason R. Kelly|Jason R. Kelly]]:''' A [http://chem-bla-ics.blogspot.com/2007/06/nature-should-host-our-electronic-lab.html post here] mentions an idea we've kicked around before that is similar to the "publish to OWW button" where a page from a private wiki is published automatically to the public OWW.  One thought is that we might consider private wikis that are specifically dedicated to be lab notebooks, they would publish to a subpage on the userpage User:Jason Kelly/notebookName, so the collisions problem of the publish to OWW button might not be a problem.  Also, we could have tools -- like the calendar, preloaded on the lab notebook wikis.  I think a set of powerful lab notebook tools would be powerful for both the private and public wikis.  The best way to get content on OWW is if scientists are digitizing right when they are doing the work.
# SfGS provides a different interface with the poltical/conservationalist scene than OWW researchers typically encounter. Such exposure could be good for career development, enhanced world view, etc.
**'''[[User:Bill Flanagan|Bill Flanagan]]11:45, 13 August 2007 (EDT):''' I have part of the "publish to OWW" button close to working. I wrote a class that will take all of the templates, images, file attachments, and the wiki text itself from any wiki page and copy it to a new page in another wiki without loss of any detail or formatting information. This would be a mechanism for the publishing of the page itself. I'm creating a new [[OpenWetWare:Software/Publish to OWW Button|Publish to OWW Button]] page to track this feature. I'll put together a demo to let folks see how it works. There are a number of issues that need to be handled in doing this including security, preservation of OWW content (we don't want this walking over similarly named templates or images in OWW, for example), how to select new page names, how to specify multiple pages, etc.
**'''[[User:Bill Flanagan|Bill Flanagan]]11:52, 13 August 2007 (EDT):''' I can create a set of pages that will be pre-populated in a lab notebook. These pages can contain references to specific extensions which also would be included. There would be a canned set of templates, pages, and images that would be used to seed all new lab notebooks as they are created. Over time, the specific contents of these can be customized as different specializations are required for different labs.
**'''[[User:Bill Flanagan|Bill Flanagan]]11:56, 13 August 2007 (EDT):''' Getting content into OWW fast seems and keeping it there is a great challenge. I've spoken to a few folks about what would make the OWW Lab Notebook more useful. As it is, if it takes longer to do it here than in a paper lab notebook, there still is a good reason to use it. Hopefully we can introduce compelling features that will make them a lot more useful.
***'''[[User:Steven J. Koch|Steven J. Koch]] 15:26, 13 August 2007 (EDT)''':One thing I want in my lab is one or a couple "cheap" computers that are pretty much just for entering notes on the wiki. In this case, seemingly trivial barriers to using the wiki can prevent users from entering things in their lab notebook.  For example, making sure the computer is always on, unlocked, with browser on OWW page, and keyboard usable with gloves on. Here are some things that come to mind that can help from the OWW side:
***# Group signons (such as "Koch Lab") for making edits.  Users could sign their entries with the group identity (<nowiki>~~~~</nowiki>) followed by their real name (which they can manually type). The reason this may help is because users are reluctant to use other people's signon and as trivial as it sounds, people aren't going to log off and back on to add a simple lab notebook entry.  Also, group work is common.  As far as I know, this wouldn't require code, just a policy to allow user accounts of the type "Koch Lab."
***#*'''[[User:Bill Flanagan|Bill Flanagan]] 7:36, 16 August 2007 (EDT)''': Steve, if this is for "write-only" updates, there may be another way to do this. I like your idea of a "group login". Let me understand your requirement a little better. Do you need this for general OWW access, where you would be skipping around between several pages or would most of the updates be to a single page? If the updates for each user were all to go to one page, such as a page in a lab notebook, I can imagine a model where we could continuously append updates for a user to the end of a page or within a specified section within a page. Maybe something like "live journal". You could then go back to clean up the page when you take off the gloves (or not!) and get back to your own PC. All of the captured updates could be tagged with their update time. You could append a line or even an entire page. If you specified a section that didn't exist within the page, it could be appended to the end of it.
***#*:'''[[User:Steven J. Koch|Steven J. Koch]] 09:15, 16 August 2007 (EDT)''':I haven't used LiveJournal (yeah I know, behind the times), but here is what I was thinking that wouldn't require code: We have a regular OWW account with name "Koch Lab".  We have a cheap computer in the lab that is always logged on to OWW as "Koch Lab."  Multiple browser windows or tabs are open to various project lab notebooks.  So, two students could be working on project #1 and go to that page and add an entry such as: "<nowiki>~~~~</nowiki>:Me and so and so made this sample and we saw this and that." and the entry would be signed as "koch lab."  I don't know if that is the best idea, but that's what I was thinking.  It would be easy, but maybe there's a problem I'm not seeing.
***#*'''[[User:Jason R. Kelly|Jason R. Kelly]] 20:50, 16 August 2007 (EDT):'''The reason we currently don't allow group logins is mostly because knowing who makes an edit helps OWW members be more comfortable with allowing others to edit their work.  There's more social pressure against inappropriate edits when you are using you own name than if you are shielded by a group account.  Also, you can use it as another metric for quality (e.g. "oh, steve's a smart guy, his change to this protocol is probably legit...")  I hadn't considered the shared computer issue though, don't know if solving that is worth the trade off of allowing anonymity.
***#Longer-lived sign-on cookies.  For some reason, my public OWW account expires very quickly.  Private wiki doesn't seem to ever expire. In terms of conveneneince mentioned in item #1 above, a very long-lived sign on would be good.
***#*'''[[User:Austin J. Che|Austin Che]] 15:44, 13 August 2007 (EDT)''': Under your preferences on the public wiki, click 'remember me' (and do this when you log in also). On the private wiki, this option is automatically set for you.
***#**'''[[User:Steven J. Koch|Steven J. Koch]] 16:04, 13 August 2007 (EDT)''':I did have the "remember me" checked, and have since the beginning (and I just double-checked).  I remember some discussion of this from several months ago.  Maybe it is some other quirk, such as because I am a member of a private wiki?  (I actually have no problem being signed on permanently to the private wiki, even though my public wiki session expires very quickly.)
***#**'''[[User:Ricardo Vidal|Ricardo Vidal]] 20:18, 27 August 2007 (EDT)''': I too have noticed that the cookie expires too quickly. Could it be a browser issue? I don't have access to the private wiki so it's probably not related.


I have set up a prototype page called [[Students for Global Sustainability Wiki]]. Please let me know how you feel about welcoming in the SfGS community to OWW.
==RSS digests==
*So we have the capability to provide RSS feeds of labs or projects (see [[Endy:Screening plasmid]] [http://openwetware.org/index.php?filter=Endy:Screening_plasmid&feed=rss&title=Special:Recentchanges RSS feed].), though it's not especially obvious how to set it up.  However with every edit showing up it overwhelms the ol feed reader -- would be nice to provide a daily digest.  [http://lifehacker.com LifeHacker] does this so might be model there on how to implement.


--[[Samantha Sutton]]
==Add a reference==
*'''[[User:Jason R. Kelly|Jason R. Kelly]] 18:25, 10 June 2007 (EDT):'''A wizard for adding a reference in the biblio format automatically. 


:: I think this is a fine idea.  For the most part there is little downside to bringing more MIT people into the wiki, as long as they are respectful of naming conventions, etc.  For instance, even if a group creates a new wiki front page that is largely self-contained (i.e. it doesn't link to anything else in OWW) it doesn't really hurt the rest of the wiki at all. It just means we have more people using OWW which means they are more likely to encourage their labs to use it / copy edit stuff they see on our pages, etcFor a particular group there might not be huge upside, but i don't see much downside at all.
==Wiki to PDF converter==
::-[[User:Jasonk|Jasonk]] 08:22, 24 Jul 2005 (EDT)
*'''[[User:Reshma P. Shetty|Reshma]] 15:11, 23 May 2007 (EDT)''': At a panel discussion on use of wiki's in education at MIT yesterday, there were several comments from educators that while wiki's were great for collaboration, they aren't great for putting together proper reports.  For example, they said that if a group of students start writing stuff up on a wiki, eventually they have to move everything to a Microsoft Word document in order to make a report that was submittable for the class assignment.  My guess is that part of this sentiment is psychological ... since the wiki feels like a work in progress, users don't feel as much need to clean up errors and spelling mistakes.  And part of this sentiment is the practical problem of it being hard to print out a wiki page and make it look "polished". Right now, since we can compose [[User:Austin J. Che/Extensions/LatexDoc|latex docs on the wiki]] that look "polished", it shouldn't be very difficult to write an extension that goes from wiki markup direct to a latex-generated PDFIt might be useful to be able to generate a "polished" version of a page.
**'''[[User:Jason R. Kelly|Jason R. Kelly]] 18:05, 24 May 2007 (EDT):''' This would be especially valuable for the [[Reviews]] section.  If you wanted to submit a review periodically for peer-review and publication in traditional journals then it would be nice to be able to dump it straight from the wiki.
**'''[[User:Cameron Neylon|Cameron Neylon]] 22 July 2007:''' Agreed. Even just if people want to print something out of have a portable version of it this would be useful.


==Wiki Meeting 6/22/05 Notes==
==Gel annotater==
We decided to open the wiki up to other groups local to MIT and that openwetware was not a crappy name.


Before we bring other labs on board we decided that it would be good to have an example of a protocol page (or several pages) as we would like to see them develop. The (somewhat of a) consensus on this was:
*'''[[User:Jason R. Kelly|Jason R. Kelly]] 16:54, 16 May 2007 (EDT):'''Basically same technology that you use to tag images in facebook, but used to tag relevant lanes/bands on a gel or other image.
*A general page such as [[DNA Ligation]] which gives background information as well as a version of the protocol where each step is explained with the relevant biology.  Also, the "biological lore" which is usually not written down in standard protocol books could accumulate on this pageThe version of the protocol on this page could be imagined as stepping towards a "standard" protocol or be imagined as a beautiful information resource about the biology behind the steps, depending on your philosophy.
*'''[[User:Austin J. Che|Austin Che]] 20:20, 16 May 2007 (EDT)''': See also [[OpenWetWare:Software/Image_Editor]]
*Links within that page to individual (or user) protocol pages. This will enable labs/users to be more likely to participate/view the general page and would be a source to glean information to be put into the general page (such as identify points where the protocols differ).
**'''[[Sri Kosuri]] ([[User talk:Skosuri|talk]]) 19:09, 17 May 2007 (EDT)''': Doesn't seem very easy to useI wonder if we could incorporate something like [http://www.frankmanno.com/ideas/css-imagemap/ this] into the site.


To Do list: (before inviting labs):
==Tell user about this edit==
#Perfect the [[DNA Ligation]] protocol (and some others)
*[[User:Jasonk|Jasonk]] 08:46, 23 April 2007 (EDT): One of the more annoying things about the wiki is that when I post a reply to someone on a random talk page I don't know for sure that they will notice itA lot of time I end up emailing them "I replied to your comment, follow this link", just to be sure. Would be nice to include a feature on the edit page that had a box to type in the username of anyone you wanted to get an email telling them about the edit. (would include a link, etc). People could opt out of receiving the emails in the their preferences, and the email itself could explain how -- so don't think it would bother people too much or anything.
#Make a good openwetware [[Main Page|front page]]
#*Put my/sri's comments on [[Talk:Main Page]]
#Add an "ettiquette" type of page
#*Done: [[Etiquette]] -- need to work on formatting of this page.
To Do list: (additional ideas): --[[User:Rshetty|Reshma]] 11:29, 27 Jun 2005 (EDT)
#Develop a logo to replace the media wiki logo in the top left corner of each page (perhaps just a simple OWW from the logo on the Main Page).
#*Been working on it.  I have one that might work perhaps.  I'll put up a few options.  --[[User:Skosuri|Sri Kosuri]] 11:49, 27 Jun 2005 (EDT)
#Add a redirect from the old Endipedia site to the new OpenWetWare site.
#*There already is one: [http://model.mit.edu/endipedia] --[[User:Skosuri|Sri Kosuri]] 11:49, 27 Jun 2005 (EDT)
#*: Perhaps there should be a redirect from http://model.mit.edu/endipedia/index.php?title=Main_Page as well? --[[User:Rshetty|Reshma]] 12:18, 27 Jun 2005 (EDT)
#Add a google search of OpenWetWare pages only to the Main Page to improve search functionality.
#*This might take some hacking.  We also should change the sidebar on the left. --[[User:Skosuri|Sri Kosuri]] 11:49, 27 Jun 2005 (EDT)
Also, we gave some thought to a stable lab protocol resource, potentially independent of the wiki.  I think this could potentially be useful but needs to be better specified.  For instance, I think that Endy:Protocol could serve a similar purpose and live on the openwetware wiki.  We could then create a locked version of these once a year (or whenever) to be sued locally by people who wanted a stable resource.


I will also be adding the BEiNG (biological energy interest group) front page in next couple days, and give them user access on Monday of next week.  I don't think they will be creating many protocols at least to start; they'll probably just be adding content to their space.
==Add protocol to my notebook==
--[[User:Jasonk|Jasonk]] 20:11, 22 Jun 2005 (EDT)
Could have a click feature on protocol pages that would automatically put a link to the protocol on a sub-page of the userpage like [[User:Jasonk/Protocols]].  This could also automatically add the protocol to the user's watchlist.


==Wiki Name Update ==
==Down the road features that I would like==
The need for a name other than endipedia is becoming more apparent. An idea that has been floating around is OpenWetWare (a la opencourseware).  It is meant to be a repository of biological information in generalFor now, the domains openwetware.mit.edu / openwetware.org / openwetware.com have been reservedWhat are people's thoughts? --[[User:Skosuri|Sri Kosuri]] 12:47, 22 Jun 2005 (EDT).
*From [http://www.socialtext.com Social Text], I learned of the possibility of emailing to a wiki.  The personal wiki they set up for me by default allows me to email to the main page, or to email and automatically create new pages.  They also have a "blog"-type page.  When you create a blog, it gets it's own email address, and then when you send an email, it gets added to the top of the blog.  I think it is set to only accept email from certain addresses.  I have no clue how hard it would be to add this to OWW.  It would help me in that I often have ideas or notebook entries that would be nice to quickly add without editing wiki text.  I know that sounds lazy, but in general, the lower the barriers to editing the more stuff will get in.
** I wrote the Wikilist extension with the idea of slowly integrating email with the wiki. Every page currently does have an email ID (e.g. [[Special:Wikilist/OpenWetWare:Ideas]]). If you go there, you can see the email address of a page (e.g. wikilist+SOMEID). Any emails to that address are sent to all users listed on the page (thus it acts like a mailing list). I've also thought about automatically posting the email to the discussion page of the target page. However, the main issue has been figuring out the right way to deal with authentication. Email is inherently unauthenticated. I guess checking the from address against the entire OWW database and then doing a lookup of the OWW user is possible. --[[User:Austin|Austin Che]] 16:41, 23 January 2007 (EST)
** I hadn't thought about the spam or authentication problem.  Your idea sounds good, but I guess it's still easy to fake a "from address" right?  Maybe in the near term I should figure out an off-line solution (just send email to myself and then cut and paste when I have time).  Thanks for your answers, Austin! And thanks for showing me that email extension, I will keep it in mind--[[User:Skoch3|Skoch3]] 17:01, 23 January 2007 (EST)
** Yes faking from addresses is trivial. If you are willing to (and your email client is capable of it), it would be possible and easy to implement a way for authentication to be passed in extra email headers. So you would have to add to every email to the wiki something of the form X-OpenWetWare-Password: Secret which would kind of authenticate you. Some mail clients let you do this trivially while I believe it's impossible with others, but I could possibly implement this and see who has use for it. --[[User:Austin|Austin Che]] 18:44, 23 January 2007 (EST)
** I'd say hold off, since it's not clear anyone else needs it, and I am still learning.  Thank you for thinking about this --[[User:Skoch3|Skoch3]] 21:37, 23 January 2007 (EST)
*In the same vein as emailing to the wiki, I have a dream of being able to call and leave messages on the wiki.  This is for when I am in my car and remember something.  Of course, an actual voice recording would be a lot of data and too annoying to ever manually convert into textSo, one would want the wiki to have voice recognition software to convert the voicemail into a text notebook entry. Yes, I know this is a long way off!
** This isn't that much harder than the email. The main thing is how are you going to specify a page name on your phone? Also, voice recognition really isn't that great. --[[User:Austin|Austin Che]] 16:41, 23 January 2007 (EST)
** Yeah, I can see that the voice recognition wouldn't work too well. Maybe for this and the email idea above, a better solution is to handle these things "off the wiki" and then manually "dump" information into the right place via normal mechanismsActually I guess what I really want is an assistant who I can call. :) --[[User:Skoch3|Skoch3]] 17:01, 23 January 2007 (EST)
*OK, I know this idea is really tough too, but maybe there's work going on I don't know of.  I am a user of evil microsoft products.  I actually like Outlook and I suspect that since I will be doing email, I will also use the Outlook Calendar, and task list (to do).  Would there be some way of "synching" outlook with a wiki?  So that I could use the convenient way on Outlook of adding calendar events and task lists, but have it synched with public wiki pages?  Some kind of wiki outlook plug in? OK, I know the market for that would be small.  Synching with Outlook would then also make it easier to somehow add stuff to the wiki via a PDA--[[User:Skoch3|Skoch3]] 16:25, 23 January 2007 (EST)
**'''[[User:Rshetty|Reshma]] 17:01, 23 January 2007 (EST)''': It is possible to view Google calendars on a wiki.  See [[Endy:Victor3_plate_reader#Plate_reader_schedule]] for an example.  So if you could get Outlook to sync with a Google calendar, then you could just display the Google calendar on a particular wiki page.  That is the most straightforward way to do it right now (or at least the way that requires no new coding/functionality).
**Very interesting, that looks like it would work for me, so I will look into it.  Thank you!--[[User:Skoch3|Skoch3]] 17:04, 23 January 2007 (EST)


At the 6/22/05 meeting, everyone agreed on OpenWetWare. --[[User:Rshetty|Reshma]] 12:18, 27 Jun 2005 (EDT)
==OWW journal clubs==
*--[[User:Vincent|Vincent]] 05:58, 7 December 2006 (EST): Organizing a section of OWW where several journal clubs would be hosted (Computational Biology, Synthetic Biology, Lab Techniques in Microbiology ...) -- Has it been tried before ? Not at the lab level but with article discussions openly discussed by OWW users.


==Protocols==
A given OWW journal club would have a focus on a defined area (use of categories), a place where people could suggest articles to be reviewed , and a selected article (voted every 2 weeks for example) being open for discussion through an open forum. It could be concluded by a conference call if people are motivated (more constraining to organize). It would be great to build a rich literature review that OWW could share and point to in the rest of the wiki.
I think we should change how we store protocols on the wiki.  I think we should have general entries into the protocol section.  For example, the entry on [[DNA Ligation]] will contain only information on what DNA ligation is, and how it generally works.  In addition, this general page will have a listing of specific protocols that can be different for any number of reasons (For example, see the DNA ligation entries for the [[Endy:DNA ligation using T4 DNA ligase|Endy protocol]] or the [[Knight:DNA ligation using NEB Quick Ligation Kit|Knight protocol]]). In general, people should post why (or how and what are the consequences) their protocol is different. Feel free to post personal protocols here as well. --[[User:Skosuri|Sri Kosuri]] 11:38, 21 Jun 2005 (EDT)


This should also alleviate some of the concerns about losing control of lab protocols if we open up the wiki to too many other people. We could try and have a type of etiquette where you don't edit pages that have "Endy:" if you're not in the endy lab, or don't edit "skosuri:" if you aren't sri. This wouldn't be a hard line edit permissions systems of course, but rather just something that tells people, "feel free to correct minor errors, but if you're going to make a major change you need to justify it well and probably make sure the page "owners" know about it."
Dear OWWers,
--[[User:Jasonk|Jasonk]] 12:08, 21 Jun 2005 (EDT)
I started an online journal club page with a draft here: [[Journal Club]]. Have a look and extend at your leisure. So far it's only a static article review. But with the excellent chat feature that was added recently, people could gather on a specific article page and really discuss world-wide. [[User:Jasu|Jasu]] 09:41, 18 April 2007 (EDT)


:Additionally, I really don't forsee this being a major problem at all, I think if we just tell people "this is a shared space, be respectful of each other" then it will develop naturally. For instance no one has made major edits to my user page other than me since we started the wiki even though we haven't had any sort of sub-domain rules in place. The last thing I want to do is give the impression that you might edit something and screw it up/piss someone off because, again, the biggest problem we will have is people not participating. (not people breaking stuff) --[[User:Jasonk|Jasonk]] 12:17, 21 Jun 2005 (EDT)
==OWW Short Course==
*'''[[User:LonChubiz|Lon]] 13:33, 30 November 2006 (CST):''' Although there are protocol and course pages on OWW, both containing educational information and objectives, it might be good to have some more refined experiments. By this, I mean for newcomers to the biological sciences (new lab members, new labs) or those moving into new areas to have a set of standard experiments they could perform to establish good laboratory techniques and to be able to communicate problems with OWW members and/or their labmates. This could also be an alternative for lab instructors to use. This could be something like an updated and more encompassing Short Course in Microbial Genetics (or any another good lab manual).


::While I can understand the justification for Sri's scheme, I am inclined to disagree with it.  The most appealing aspect of the wiki in my mind is the fact that you can revise other's protocols at will.  By placing different versions of the ligation protocol on different pages and prefixing them with names, you are discouraging (albeit subtly) group editing of protocols.  I personally prefer that people revise and annotate my protocols as much as possible so that I can learn either more streamlined methods of doing things and troubleshoot my own experiments betterIf my protocols are labeled with Reshma or even Knight indicating that someone "owns" those pages, I think that you discourage this. This is why I was in favor of retaining centralized locations for technical information.  And why I would be in favor of retaining a single ligation protocol page.
==Academic Job Openings==
*'''[[User:Jasonk|Jasonk]] 11:52, 10 November 2006 (EST):''' Came up at the last SC meeting, could have a place to post open post-doc positions, faculty, etcCould also have corporate job postings, but that's probably already covered pretty well by Monster.com type websites.


::The other issue that Sri's suggestion raises is do we really want everyone to be following a different protocol?  One of the goals of Synthetic Biology at least is to turn what are currently experiments into simple procedures that even a monkey can do so that the engineering of biological systems can be done with ease.  As Tom has often pointed out, assembling two pieces of DNA together should be a standard procedure not a new experiment each time as is often the case in biology now.  My understanding is that this is the driving motivation for projects like the [[Standard E. coli Strain for BioBricks | standard strain]] and [[BioBrick Parts for Plasmid Engineering | BioBricks plasmids]].  Admittedly, I was one of the people who first started labelling different protocols as Knight lab versus Endy lab (mostly because of a lack of better distinction between versions of protocols).  But I guess I thought that over time, these two protocols versions would merge into a single protocol that everyone uses (with possibly some tweaks to account for your personal experiment).  Having N number of protocols that M people use seems contrary to much of what Synthetic Biology is trying to accomplish.
==Calendar with all scientific conferences==
*'''[[User:Jasonk|Jasonk]] 11:52, 10 November 2006 (EST)''': Suggested by TomThis would be a calendar strictly for scientific conferences, since it's often tough to find out about conferences you might be interested in.


::Of course, the caveat to what I have said above is that not everyone is doing Synthetic Biology and thus not everyone necessarily has an interest in pursuing a policy of standardizationI don't intend these comments to be a critique of Sri's suggestionI am just trying to point out that the organization of the wiki may help determine whether we progress towards a large and diverse web of molecular biology information or towards a standardized set of procedures for biological engineeringWe should think about what our goal is (and there are advantages to both) and organize our wiki accordingly. As is likely obvious, I am in favor of the latter. --[[User:Rshetty|Reshma]] 13:03, 21 Jun 2005 (EDT)
==OWW Journals==
*'''[[User:Jasonk|Jasonk]] 01:50, 25 October 2006 (EDT):''' Based on conversations with Chris Surridge, our 2nd OWW Open Science Seminar series speaker, it looks like starting a journal may get much easier.  The general idea is to use PLoS One as a commoditized peer-reviewing service.  Articles that get through the PLoS One filter have been verified for publication-quality science, but have not been subjected to any subjective merit criteria (e.g. is this good enough for publication in Nature?)  This is where OWW can come in, user groups on OWW could aggregate and "re-publish" open access (OA) content that has made it onto PLoS One (or any other OA journal).  Basically, we would serve as an aggegator of articles that conform to some quality standard set by an editorial board from that communityAn author published in the OWW Journal of Synthetic Biology could site their PLoS one reference as well as a 're-publication' referenceIf the OWW Journal actually gained some clout, an author would probably simply list being published in the aggregator rather than the PLoS One reference, since it would carry more weight (e.g. the paper had to get over the merit quality bar -- "is this good enough for publication in OWW Journal of Synth Bio?")a very high bar, indeed ;Additionally, we could provide commentary on the papers that are of interest, "blog-esque" posts from notable community members, etc...
*[http://pkp.sfu.ca/?q=ojs open source journal management software]


:::I also agree with Reshma that standardization of certain sets of protocols is a good thing that we should work towards, as long as the conditions in which the standards are to be used are definedI think the point of this proposed change, is that we can now do bothNot only could this be a place for biological engineers to work on a shared, standardized protocolIt could be a great place to define/debug/improve those protocols based on the information being stored by individual researchers and what works for themPractically, there is no reason that those SB standards could not be placed in a protocol such as SB:The Protocol.  I think forcing people to contribute to a shared protocol will, in the short-term and long-term, discourage engagement of people who don't think they should change "the standard"In addition, it will discourage labs that think don't want to use the "standard protocol" for whatever reason (e.g., don't want to pay for a qiagen kit).  As a nascent community, I would be more worried about this, than too many people putting their own individual protocols up--[[User:Skosuri|Sri Kosuri]] 13:42, 22 Jun 2005 (EDT)
==[[OpenWetWare:Reviews]]==
*'''[[User:Jasonk|Jasonk]] 09:26, 6 October 2006 (EDT):''' Along the lines of adopt-a-protocol, it might be great to have adopt a topic area as wellBasically, trying to solve the problem of review articles always being out of dateIt seems like the job of writing reviews would be much simpler if it was done on the fly as new papers came outTHat way when a new paper came accross your desk in the area you review you could read it, and then add the relevant details and the reference to the OWW Review pageThis is in contrast to coming back to that same paper a year later when you're asked to write a review and having to re-read it, re-analyze it, etcSeems like a win-win for the both the review-writer (less work) and the readers (who get a more up-to-date source.)


==Wiki Changes incorporating SyntheticBiology.org and multiple entry pages==
==Adopt-a-protocol==
'''The process has started.  See [[Main Page v2]]


<font color="red">'''Adding a figure to clarify what I was suggesting'''  [[User:Endy|Endy]] 14:37, 12 Jun 2005 (EDT)</font>
''Moved to [[Talk:Protocols/Template]].''


[[Image:wiki.jpg|left|thumb|200px|Wiki ArchitectureThe basic idea is that we have a single, monolithic wiki that has one set of users, all trusted. To start, these users comprise Tom's lab and my own and anybody else who is helping us locallyEach of the (currently) five different front pages would have it's own unique front page, but would serve content that was maintained and edited via a single wiki. So, Austin, syntheticbiology.org will still need a front pageEither it's a static front page or a wiki-based front page.  I don't know how good a job we can do with the editing of the look and feel of a wiki-based front page.  Need to try to convert the endy lab front page into a wiki format and see how it goes. [[User:Endy|Endy]] 14:42, 12 Jun 2005 (EDT)]]
==Page Authorship==
*'''[[User:Jasonk|Jasonk]] 22:57, 8 August 2006 (EDT)''': There might be a benefit to having the option to lock in an "author" at the time of page creationWe could limit this to pages with a namespace in front of them (e.g. 'Endy:foo'), to prevent someone from locking down a 'shared area' page like [[DNA ligation]]Other people could edit the page, but there would be an official author -- that means the author would have the benefit of getting credit for the content of the page (e.g. perhaps when you hit cite this page, only the offical author would come up), but also be saddled with ensuring some level of quality (whatever they were comfortable attaching their name to)This might help enable some downstream OWW applications, like providing real scientific attribution for OWW contributions or for publishing results, etc.  I suspect that assigning a page an official authorship would be the exception rather than the rule, but might be a useful option to have -- just something to think about longer term, wanted to write it down.


<font color="black">
==Sidebar==
*'''[[User:Jasonk|Jasonk]] 16:38, 27 July 2006 (EDT)''':The customize sidebar extension is great, but I don't think any new user would notice it.  Maybe at the bottom of the side bar we should include a link be default that says update my sidebar and would take the user to a pregenerated sidebar page for them with comments on how to change it.  once they figured it out they could remove the link themselves from their sidebar if they don't want it there.


*that we rename the front page of the wiki (i.e., "endipedia")... by getting rid of the front page of the wiki
*that we have one wiki which serves endy lab, tk lab, and our synthetic biology working group.
*that the endy lab web page move in its entirety into a wiki-format, and that http://mit.edu/endy point to an internal wiki sub-page that is the new "endipedia."
*that the TK folks consider constructing a TiKipedia for the TK lab and that there be an internal wiki sub-page that is the TiKipedia port of entry.
*that the syntheticbiology.org website point to an internal wiki sub-page that is the new syntheticipedia, and that we move all information now on that website into wiki-format -- that site has gotten really stale, even though we are doing a lot more work.
*that a new URL (www.stinkjet.org) point to a still different internal wiki page that we can use to promote discussions of issues related to the development of second generation biological technology.


(emailed out by Drew 6/9/05)
==Navigation==
*'''--[[User:Johncumbers|Johncumbers]] 16:38, 16 July 2006 (EDT)''': A big problem I've found with OWW, and I'd like to see if anyone else has the same problem.  I can't stay logged in, e.g Flickr, Amazon retains who I am, but OWW doesn't.  Is this just me?  This leads to the seconds part of the problem.  When I go to log-in, it always returns me the link to go back to the main page, I then have to use the back button to go back to the page I want to edit.  These are not huge problems, but they really confuse new people that I introduce to the site.  They find it really frustrating to navigate at the beginning.  Anyone else found this when trying to introduce new people to OWW/Mediawiki?
**[[User:Smeister|Smeister]] 07:38, 17 July 2006 (EDT) OWW keeps me logged in unless I log in from another computer - in that case I get logged out from the first. Are you maybe sharing your account? I assume you do not have any cookie setting problems since Flickr etc works for you...
**[[User:Jasonk|Jasonk]] 09:25, 17 July 2006 (EDT): I stay logged in as well normally... However, to avoid getting linked back to the main page, use the link at the top right corner to log in - it will then offer a link back to the page you were coming from, rather than a link to the Main Page (I agree it is annoying when it links to the Main Page).
**[[User:Austin|Austin]] 13:59, 17 July 2006 (EDT): On one computer, I can't stay logged in. On another, I always stay logged in. I've not been able to figure out the cause.
**[[User:Skoch3|Skoch3]] 16:14, 23 January 2007 (EST): I always seem to have to re-log in.  I use one computer, but it's a laptop with a lot of different IP addresses during the day I think.  It seems I have to log in to my private wiki more often than the public, but not sure.  I have been assuming that it was just some quirk between the private wiki log on and the OWW.


:*I think that one of the major advantages of the wiki as it stands now is the centralized nature of the technical information.  By having having a single wiki page devoted to say "Ligations", everyone can contribute and place information about debugging problematic experiments in one place for the benefit of others. If we had separate ligation pages for the Endy, TK lab and Synthetic Biology then the barrier is raised to ongoing discussions between people about protocols. Therefore, if we do decide to change the wiki organization I would vote for maintaining a centralized place for technical information for all three groups. We can still eliminate the Main Page just by creating a new technical information front page that is linked off of all three groups.
==Page watch function==
:*I prefer sbpedia to syntheticipedia.
'''[[User:Smeister|Smeister]] 08:20, 17 July 2006 (EDT) ''' I love the "watch page" function and would like to organize more activities in the lab, taking advantage of it. However, there is no way of knowing who in the lab is watching a page at any moment. You basically never know if anybody is paying attention at all. Would a query page for this be very hard to incorporate? It sure would enhance overall transparency and I guess it would also be useful for some of these OWW discussion pages...
:*What is the difference between the synthetic biology wiki and a wiki about development of second generation biological technology?  Shouldn't the latter be a part of the former?
:--[[User:Rshetty|Reshma]] 09:41, 10 Jun 2005 (EDT)


:*We should definitely keep the central repository of information but I think the idea of having several "fronts" to that repository makes sense.
*'''--[[User:Johncumbers|Johncumbers]] 13:14, 17 July 2006 (EDT)'''  I agree, I don't use the page watch as much as I'd like. I like you ridea Steven, It would be also nice if it had a little number like 'my watchlist(44)'  to let you know what's inside there each day and encourage you to click on it.
:*This would probably require us to be better at crosslisting or categorizing our pages so that an interested visitor coming in through the sbpedia front page can get at the same pages that someone coming in from the Endy lab page can get at.
:*Might be good to incorporate the iGEM team wiki also so that it is easier for them to use our info. and for us to give feedback on their plans.


:*--[[User:Bcanton|BC]] 10:03, 10 Jun 2005 (EDT)
==Comment button==
*'''--[[User:Johncumbers|Johncumbers]] 13:14, 17 July 2006 (EDT)''' could the signature button be changed to include the * and <nowiki>'''</nowiki> that we put in for comments.  Another idea would be a protocol notes button that creates a note link for a protocol.  Currently if you want to add a note to a protocol, you have to either put it at the bottom, it would be better if it created a link within the page without you having to type it all out.  e.g if the protocol is located at Protocols:Drosophila/chip on chip then when I post a note, it automatically creates a link to Protocols:Drosophila/chip on chip/note1  without me having to do it.  get the idea?


==Active Discussions==
'''[[User:Lucks|Lucks]] 20:16, 3 April 2006 (EDT)''':The topic on Flexible Science Databases has been moved to [[OpenWetWare:Software/Flexible_Science_Databases]].


:*agree with above, i think it might not be too difficult, we just need to make sure that we all point to the same centralized tech pages. I think one organizational decision is whether it is better to have another layer (i.e. a technical info front page) or multiple shared tech pages which can be linked to from any front page that would be relevant, for instance, tech pages:
==Subarticles==
:#Protocols
:#Equip
:#Strains
:#Vectors
:*etc.


:*Both Endy and Knight front pages would link to all of these, but SBpedia (or i might just call is 'SyntheticBiology.org') might only link to Strains and Vectors for instance.


:*definitely agree with bringing the iGEM wiki page into the umbrella, will let them use (and improve) our protocols more easily.
==Recent Changes in Ideas==
{{Special:Recentchanges/n=OpenWetWare^b=Ideas,n=OpenWetWare talk^b=Ideas&limit=50}}
       
|}


:*Stinkjet could be specific to forward looking BBF-type stuff, i.e. more focused on issues of open source biological engineering, safety when everyone has a 'stinkjet' on their desk, etc.  SyntheticBiology.org might point more towards current issues, i.e. latest tech reports on BBs stuff, info about the registry, etc.  They would of course point towards each other...  maybe there is too much redudancy, but i do like the stinkjet.org domain name.
__NOTOC__
 
:--[[User:Jasonk|Jasonk]] 10:21, 10 Jun 2005 (EDT)
 
:I like the idea.  I think we should begin building out the front pages though until we make the switch.  Also, we should figure out a naming scheme for lab/group specific stuff, like group meetings and whatnot.  Also, we should agree on early on about what parts are going to be jointly worked on, ie., protocols.  --[[User:Skosuri|Sri Kosuri]]
 
:*I also don't see the point of having multiple wikis. It just makes searching/management more difficult. Wikipedia has information about everything under the sun (except for synthetic biology) and yet they don't seem to have a problem with needing to split stuff into different encyclopedias. What about the concept of [[Wikipedia:Help:Namespace]] rather than completely separate pages? The only issue I can think of is for access control where certain pages should have different permissions than others. I don't know if that's possible but then the whole idea of a Wiki should be public access. So I'm all for a single wiki and if there's something that needs to be separated by labs, prefix pages with Endy: if needed.
 
:*I've redirected syntheticbiology.org to this wiki. There was no [[Synthetic Biology]] page here?
 
:*As for sbpedia, it sounds too much like expedia and I'd rather stay away from any Microsoft associations.
 
:--[[User:Austin|Austin]] 16:07, 11 Jun 2005 (EDT)
 
==Communicating Changes to the Wiki==
This has come up a couple of times.  For those who check changes to the Wiki more frequently than checking for updates to \. I don't think its a problem.  But it might be good to find a way to easily communicate changes to the wiki to all (who is all?).  Possible ideas include -
*Just mail the endylab and tklab when you put up something.  Easy but not very streamlined.
*Get the wiki to automatically send daily/weekly updates of non-minor changes to a mailing list of interested parties.  Not sure if this is possible. Actually looks like enotif will do this, its a plugin for mediawiki.  You choose to receive emails or not and which pages you want to be alerted to changes in. --[[User:Bcanton|BC]] 16:25, 26 May 2005 (EDT)
*Might be possible to automatically keep a recent updates section on the main page.
*Have everyone install RSS readers and subscribe to the RSS feed. Maybe a bit OTT!
 
Feedback?
 
--[[User:Bcanton|BC]] 16:15, 26 May 2005 (EDT)
 
==Synthetic Biology Community on DSpace==
 
I posted [[DSpace community | this]] below under Presentations/posters/papers but then thought it might not be very noticeable so I am reposting it with its own heading.  It is a page about creating a Synthetic Biology community on DSpace which would enable us to post all digital materials produced by the group online and determine who gets access to them.  Feedback much appreciated (you can also email me if you don't want to post on the wiki). --[[User:Rshetty|Reshma]] 15:54, 26 May 2005 (EDT)
 
==User Wikis==
Barry and I thought it might be cool to do an experiment evaluating "personal" wikis as a data organization tool.  Similar to the local file structure that you would have in your computer home directory, but with better linking between sections and more transparent content.  i.e. Not just word files in sub folders that I can't readily search or link between.  (yes sri, i know spotlight can search them, but you still can't link easily)
 
I also think that if lab members format more of their personal remarks, etc, in wiki format they will be much more likely to make their way into the public wiki space.  So will see how this works out. Of course this could all be done within the user pages on the current wiki, but i think there is some value to being able to take personal notes that aren't public domain.  (but which eventually can move there easily).
 
Thoughts? Also, if you want to try it out for yourself we can set that up.
[[User:Jasonk|Jasonk]] 14:41, 26 May 2005 (EDT)
 
:-Mac Users: if you want an easy walk through on how to set up your own wiki, go [http://meta.wikimedia.org/wiki/Running_MediaWiki_on_Mac_OS_X here].  Takes about 30mins and sets up an Apache Web Server, a SQLl database, PHP and mediawiki.  And its all OSS also! --[[User:Bcanton|BC]] 16:19, 26 May 2005 (EDT)
 
:-This seems like an interesting idea.  One thing I am wondering is say I have a personal wiki and document a project on my personal wiki.  How easy would it be for me, in the future, to move my wiki pages onto the lab wiki?  Especially if I only want to move a section of my wiki to the lab wiki.  If it is difficult to do this then it reduces the likelihood that people will eventually release their personal wiki pages to the public domain.  Personal wikis might still be useful for the person but perhaps less useful as the documentation of a project that eventually gets released to the world. --[[User:Rshetty|Reshma]] 13:14, 27 May 2005 (EDT)
 
::-My thought on this is that right now if i had a project that i didn't want on the public wiki i would be documenting it on a word file on my personal computer anyway.  So using a personal wiki instead just means that the formatting is already in place to just cut and paste to the public wiki when/if i'm ready to do that.  So there may be a little work in moving it over (i.e. there's not just a "merge" button), but it should be less work then if i had just made a word file.[[User:Jasonk|Jasonk]] 15:31, 29 May 2005 (EDT)
 
:-This raises one of a few drawbacks to the personal wiki idea.  The others are the difficulty of making a well ordered hard copy of your material, and embedding files is more cumbersome than when using Word or something equivalent.  The merging of wikis problem might be partially solved by using a similar structure for a personal wiki as for the lab wiki and using the same list of categories, which would automatically integrate your pages into the lab wiki.  For that to work, we'd need to rely on categories more than we do now.  I'd be interested to hear from someone who knows about SQL databases and how easy it might be too merge two databases or portions of one database with another.  I liked the personal wiki idea just as a way to organize my own material and make it easier to cut and paste individual pages to the lab wiki if I wanted.  I think this would be really useful when developing a new protocol, it could live on a personal wiki until it works and then get moved over to the lab wiki.  Time will tell though if it is ueful.  --[[User:Bcanton|BC]] 15:37, 27 May 2005 (EDT)
 
==Categories==
 
I think we could use the Categories feature of the wiki more effectively.  Having a list called Protocols and a category called Protocols seems redundant.  What about using Categories to connect group pages across lists?  For instance, a "Running systems in a &mu;reactor" category could include links to ordering microfluidics (under Protocols), the Scope (under Equipment), media (under Materials) and other relevant pages.  This approach would essentially use Lists and Categories as two separate "dimensions" along which pages can be grouped.  --[[User:Rshetty|Reshma]] 21:13, 25 May 2005 (EDT)
 
*Yeah that's good -- I like the idea of grouping things from multiple lists in relevant ways, the question is when do categories become more useful then just creating a "Running systems in a &mu;reactor" page and then linking to everything like that?  For instance take the media (or the scope), how many categories could it end up being in?  running a &mu;reactor, running a macro chemostat, growing a batch culture, etc.  In that case I think having seperate "group pages" or something that each individually pointed to the media might be better.  [[User:Jasonk|Jasonk]] 00:55, 26 May 2005 (EDT)
*I think the categories might pay off better if we had a lot of protocols that were distributed accross different heirarchical list schemes.  For instance if I started adding new protocols to my user page directly, in some sort of heirarchy that was relevant to me, i.e. "frequently used protocols" vs. "infrequently used protocols" or something, then I could just slap a category tag at the end and know that I had placed it into an appropriate spot in the aggregate general protocol area.  Also, could imagine if you aggregated a few lab wikis together that had pre-defined heirarchies, the categories could serve to create a common protocol space without everyone having to conform to the same list scheme.  So it might be that they are more useful down the line (or not), but it certainly doesn't hurt to give any system a try and see if it proves useful (can always change it easily).  [[User:Jasonk|Jasonk]] 00:55, 26 May 2005 (EDT)
 
 
 
 
I guess i'd like to think about what other categories would be useful. 
 
==Lab Notebook==
 
Not planning on throwing my lab notebook online just yet, but if you were to consider using the wiki for such a thing you might want to have some sort of encrypted date/user signature.  This would potentially give the more paranoid among us more ammunition in their attempt at defaming the person who "scooped" them in this guerilla war we call academics. (sarcasm tags would also be nice) [[User:Jasonk|Jasonk]] 18:27, 23 May 2005 (EDT)
 
Some relevant links:(thanks ilya)
*Open Source Electronic Lab Notebook Software
[http://www.opensourceeln.org/Members/webmaster/core/description.txt OSELN]
 
*Also, the pharmaceutical industry has some pretty serious electronic signature rules, which are patent-safe.  Expensive to implement and likely overkill for academia but:
[http://www.21cfrpart11.com/ Rule21 CFR Part11]]
 
==Suggested new name: knendipedia==
 
* I think knendipedia might be a more appropriate name for this wiki :).  (I liked knendipedia better than enightipedia). What do you think? -[[User:Rshetty|Reshma]] 10:07, 11 May 2005 (EDT)
* Maybe we should just go with something like SynthBioWiki or something, would make it easier to add more friends down the line, not sure the knendipedia approach scales, shetkoscanknendipedia :) [[User:Jasonk|Jasonk]] 18:26, 23 May 2005 (EDT)
* How about SBpedia - pronounced speedia --[[User:Bcanton|BC]] 19:33, 23 May 2005 (EDT)
**My one problem with the above two suggestions is that not everyone does 'synthetic biology' ie me, francios, jeff, ty, heather...  --[[User:Skosuri|Sri Kosuri]] 23:29, 25 May 2005 (EDT)
***good point, then how about some generic bio term, like geneipedia, or some such nonsense.[[User:Jasonk|Jasonk]] 00:53, 26 May 2005 (EDT)
 
== User page / posting personal ideas ==
It would be nice to post pages which are non-editable for things like your personal opinion on something scientific.  I.e. the type of stuff that might be found on your user page.  This also becomes more important if we open the wiki to be world-writable.
 
We could accomplish this by making all users admistrators since admins have ability to "protect" pages and lock them from editing.  This would work so long as members were all trusted, but if we decide to expand member base we might like to have a way of doing it without giving everyone admin access.
 
Anyone know of how to do it without giving admin access?
 
== Presentations/posters/papers ==
 
One thing that struck me as potentially useful would be a place to archive presentations and posters.  Might be useful to be able to look over others presentations to see how they presented things etc.  Similarly, it might be nice to also be able to post works in progress like papers or various writeups etc.  Of course, I can imagine several levels of release like private (probably wouldn't post), release to the Knight/Endy lab (wiki?) and release to the world (http://www.syntheticbiology.org?).<br>
*Does the wiki have a good mechanism for posting documents?  A quick look suggested to me that you could only upload pictures.<br>
**i think you can only do pictures, best bet for docs seems to be store elsewhere and link - i like the idea of having a place on model where we can dump all wiki docs/ppts/etc in a centralized place.[[User:Jasonk|Jasonk]] 14:40, 28 Apr 2005 (EDT)
**Can now post whatever type of file you like [[User:Jasonk|Jasonk]] 18:30, 23 May 2005 (EDT)
* Can sections of the wiki be made off limits to those without user accounts.  ie non-readable?
** Not very easily.  --[[User:Skosuri|Skosuri]] 14:36, 28 Apr 2005 (EDT)
**they can be made non-writable, though. see idea above [[User:Jasonk|Jasonk]] 14:46, 28 Apr 2005 (EDT)
*Or alternatively people can post documents in their own public directories.  Use MIT's certificate system to control who access the directories and then just put an external link on the wiki.  This gives maximum control over access to the author but does not centralize documents as much.  This also may be problematic as people graduate or leave the lab.
** This is a good idea for now.  In the future, we could create a section on model to have a username and login for private files.  --[[User:Skosuri|Skosuri]] 14:36, 28 Apr 2005 (EDT)
*Any better ideas?
** Why don't we create a Synthetic Biology community on MIT's DSpace.  Go [[DSpace community | here]] for more information and to contribute to the discussion. --[[User:Rshetty|Reshma]] 13:18, 26 May 2005 (EDT)
 
== Collaborators ==
 
Forgot to mention in lab meeting, but will be giving the Knight lab write access to the pages, talked with reshma and austin and they thought it made more sense to just have one wiki we could share rather than cross referencing seperate wikis.  (might need a new name then).
 
Also, we could consider starting Collaborative Projects pages, for things such as the Standard BB strain, etc.
 
== Ideas from Lab Meeting 4/27 ==
 
=== Openness of the wiki ===
 
Options for public access:
#World-writable and readable
#World-readable only
#World-no access
#Hybrid
#*World can write to discussion but not to main articles.
 
We decided that we should go with option 2 for the time being at least until the wiki stabilizes and then consider making the wiki world-writable.

Latest revision as of 06:02, 5 September 2008

Back to Community Portal

Welcome to Ideas discussion area.

How you can help

Use of Mediawiki commons on OWW?

Steve Koch 03:16, 16 April 2008 (EDT):Has it been discussed previously the possibility of using images from Mediawiki commons on OWW. The way Wikipedia does it, so that you can use the same [[Image:whatever.png]] and if it doesn’t exist on OWW it will try to grab it from the commons? I would use this in my research pages and my courses. (It would also be convenient if private wikis could use public wiki images (and templates) in a similar manner.) I have no clue how hard this is to implement (I was just reminded of it today due to our discussion about tracking MediaWiki with OWW)…maybe it is easily copied from Wikipedia?

Invitations

  • Jason R. Kelly 08:44, 8 August 2007 (EDT): Should have a button/page that allows people to easily invite their friends/labmates to join OWW. This is more relevant if we establish lab groups, etc, where we are storing the connections between users. E.g. a person could join and then invite their whole lab, adding all of them to the group 'Endy lab' or whatever all in one shot.
Agree--Dan 14:04, 13 February 2008 (CST)
    • wjf 14:10, 13 February 2008 (CST):I did something like this before. It's pretty simple. Al would be needed would be a form and an emai message. Hmm... let's think about it. I like the idea. You would also get an email message when the user joined.

Search within tags/categories

  • Jason R. Kelly 09:56, 17 July 2007 (EDT): Would be nice to be able to have a 'search protocols' box. If we had tags/categories working well, it seems like this is something that could be implemented fairly easily. If it was well done it would probably remove the need for an auto-generated, well-organized summary page (e.g. Protocols could be replaced by a search box). This will become more important down the line as I suspect the single summary page won't scale.
  • Alethea 09:02, 5 September 2008 (EDT): Is there a tag search capacity somewhere? Am I the only person who still can not conduct a successful search from either the lefthand navigation pane, or from within my lab notebook, and does this have more to do with my navigator or platform than with OWW?

Private/public lab notebooks

  • Jason R. Kelly: A post here mentions an idea we've kicked around before that is similar to the "publish to OWW button" where a page from a private wiki is published automatically to the public OWW. One thought is that we might consider private wikis that are specifically dedicated to be lab notebooks, they would publish to a subpage on the userpage User:Jason Kelly/notebookName, so the collisions problem of the publish to OWW button might not be a problem. Also, we could have tools -- like the calendar, preloaded on the lab notebook wikis. I think a set of powerful lab notebook tools would be powerful for both the private and public wikis. The best way to get content on OWW is if scientists are digitizing right when they are doing the work.
    • Bill Flanagan11:45, 13 August 2007 (EDT): I have part of the "publish to OWW" button close to working. I wrote a class that will take all of the templates, images, file attachments, and the wiki text itself from any wiki page and copy it to a new page in another wiki without loss of any detail or formatting information. This would be a mechanism for the publishing of the page itself. I'm creating a new Publish to OWW Button page to track this feature. I'll put together a demo to let folks see how it works. There are a number of issues that need to be handled in doing this including security, preservation of OWW content (we don't want this walking over similarly named templates or images in OWW, for example), how to select new page names, how to specify multiple pages, etc.
    • Bill Flanagan11:52, 13 August 2007 (EDT): I can create a set of pages that will be pre-populated in a lab notebook. These pages can contain references to specific extensions which also would be included. There would be a canned set of templates, pages, and images that would be used to seed all new lab notebooks as they are created. Over time, the specific contents of these can be customized as different specializations are required for different labs.
    • Bill Flanagan11:56, 13 August 2007 (EDT): Getting content into OWW fast seems and keeping it there is a great challenge. I've spoken to a few folks about what would make the OWW Lab Notebook more useful. As it is, if it takes longer to do it here than in a paper lab notebook, there still is a good reason to use it. Hopefully we can introduce compelling features that will make them a lot more useful.
      • Steven J. Koch 15:26, 13 August 2007 (EDT):One thing I want in my lab is one or a couple "cheap" computers that are pretty much just for entering notes on the wiki. In this case, seemingly trivial barriers to using the wiki can prevent users from entering things in their lab notebook. For example, making sure the computer is always on, unlocked, with browser on OWW page, and keyboard usable with gloves on. Here are some things that come to mind that can help from the OWW side:
        1. Group signons (such as "Koch Lab") for making edits. Users could sign their entries with the group identity (~~~~) followed by their real name (which they can manually type). The reason this may help is because users are reluctant to use other people's signon and as trivial as it sounds, people aren't going to log off and back on to add a simple lab notebook entry. Also, group work is common. As far as I know, this wouldn't require code, just a policy to allow user accounts of the type "Koch Lab."
          • Bill Flanagan 7:36, 16 August 2007 (EDT): Steve, if this is for "write-only" updates, there may be another way to do this. I like your idea of a "group login". Let me understand your requirement a little better. Do you need this for general OWW access, where you would be skipping around between several pages or would most of the updates be to a single page? If the updates for each user were all to go to one page, such as a page in a lab notebook, I can imagine a model where we could continuously append updates for a user to the end of a page or within a specified section within a page. Maybe something like "live journal". You could then go back to clean up the page when you take off the gloves (or not!) and get back to your own PC. All of the captured updates could be tagged with their update time. You could append a line or even an entire page. If you specified a section that didn't exist within the page, it could be appended to the end of it.
            Steven J. Koch 09:15, 16 August 2007 (EDT):I haven't used LiveJournal (yeah I know, behind the times), but here is what I was thinking that wouldn't require code: We have a regular OWW account with name "Koch Lab". We have a cheap computer in the lab that is always logged on to OWW as "Koch Lab." Multiple browser windows or tabs are open to various project lab notebooks. So, two students could be working on project #1 and go to that page and add an entry such as: "~~~~:Me and so and so made this sample and we saw this and that." and the entry would be signed as "koch lab." I don't know if that is the best idea, but that's what I was thinking. It would be easy, but maybe there's a problem I'm not seeing.
          • Jason R. Kelly 20:50, 16 August 2007 (EDT):The reason we currently don't allow group logins is mostly because knowing who makes an edit helps OWW members be more comfortable with allowing others to edit their work. There's more social pressure against inappropriate edits when you are using you own name than if you are shielded by a group account. Also, you can use it as another metric for quality (e.g. "oh, steve's a smart guy, his change to this protocol is probably legit...") I hadn't considered the shared computer issue though, don't know if solving that is worth the trade off of allowing anonymity.
        2. Longer-lived sign-on cookies. For some reason, my public OWW account expires very quickly. Private wiki doesn't seem to ever expire. In terms of conveneneince mentioned in item #1 above, a very long-lived sign on would be good.
          • Austin Che 15:44, 13 August 2007 (EDT): Under your preferences on the public wiki, click 'remember me' (and do this when you log in also). On the private wiki, this option is automatically set for you.
            • Steven J. Koch 16:04, 13 August 2007 (EDT):I did have the "remember me" checked, and have since the beginning (and I just double-checked). I remember some discussion of this from several months ago. Maybe it is some other quirk, such as because I am a member of a private wiki? (I actually have no problem being signed on permanently to the private wiki, even though my public wiki session expires very quickly.)
            • Ricardo Vidal 20:18, 27 August 2007 (EDT): I too have noticed that the cookie expires too quickly. Could it be a browser issue? I don't have access to the private wiki so it's probably not related.

RSS digests

  • So we have the capability to provide RSS feeds of labs or projects (see Endy:Screening plasmid RSS feed.), though it's not especially obvious how to set it up. However with every edit showing up it overwhelms the ol feed reader -- would be nice to provide a daily digest. LifeHacker does this so might be model there on how to implement.

Add a reference

  • Jason R. Kelly 18:25, 10 June 2007 (EDT):A wizard for adding a reference in the biblio format automatically.

Wiki to PDF converter

  • Reshma 15:11, 23 May 2007 (EDT): At a panel discussion on use of wiki's in education at MIT yesterday, there were several comments from educators that while wiki's were great for collaboration, they aren't great for putting together proper reports. For example, they said that if a group of students start writing stuff up on a wiki, eventually they have to move everything to a Microsoft Word document in order to make a report that was submittable for the class assignment. My guess is that part of this sentiment is psychological ... since the wiki feels like a work in progress, users don't feel as much need to clean up errors and spelling mistakes. And part of this sentiment is the practical problem of it being hard to print out a wiki page and make it look "polished". Right now, since we can compose latex docs on the wiki that look "polished", it shouldn't be very difficult to write an extension that goes from wiki markup direct to a latex-generated PDF. It might be useful to be able to generate a "polished" version of a page.
    • Jason R. Kelly 18:05, 24 May 2007 (EDT): This would be especially valuable for the Reviews section. If you wanted to submit a review periodically for peer-review and publication in traditional journals then it would be nice to be able to dump it straight from the wiki.
    • Cameron Neylon 22 July 2007: Agreed. Even just if people want to print something out of have a portable version of it this would be useful.

Gel annotater

  • Jason R. Kelly 16:54, 16 May 2007 (EDT):Basically same technology that you use to tag images in facebook, but used to tag relevant lanes/bands on a gel or other image.
  • Austin Che 20:20, 16 May 2007 (EDT): See also OpenWetWare:Software/Image_Editor
    • Sri Kosuri (talk) 19:09, 17 May 2007 (EDT): Doesn't seem very easy to use. I wonder if we could incorporate something like this into the site.

Tell user about this edit

  • Jasonk 08:46, 23 April 2007 (EDT): One of the more annoying things about the wiki is that when I post a reply to someone on a random talk page I don't know for sure that they will notice it. A lot of time I end up emailing them "I replied to your comment, follow this link", just to be sure. Would be nice to include a feature on the edit page that had a box to type in the username of anyone you wanted to get an email telling them about the edit. (would include a link, etc). People could opt out of receiving the emails in the their preferences, and the email itself could explain how -- so don't think it would bother people too much or anything.

Add protocol to my notebook

Could have a click feature on protocol pages that would automatically put a link to the protocol on a sub-page of the userpage like User:Jasonk/Protocols. This could also automatically add the protocol to the user's watchlist.

Down the road features that I would like

  • From Social Text, I learned of the possibility of emailing to a wiki. The personal wiki they set up for me by default allows me to email to the main page, or to email and automatically create new pages. They also have a "blog"-type page. When you create a blog, it gets it's own email address, and then when you send an email, it gets added to the top of the blog. I think it is set to only accept email from certain addresses. I have no clue how hard it would be to add this to OWW. It would help me in that I often have ideas or notebook entries that would be nice to quickly add without editing wiki text. I know that sounds lazy, but in general, the lower the barriers to editing the more stuff will get in.
    • I wrote the Wikilist extension with the idea of slowly integrating email with the wiki. Every page currently does have an email ID (e.g. Special:Wikilist/OpenWetWare:Ideas). If you go there, you can see the email address of a page (e.g. wikilist+SOMEID). Any emails to that address are sent to all users listed on the page (thus it acts like a mailing list). I've also thought about automatically posting the email to the discussion page of the target page. However, the main issue has been figuring out the right way to deal with authentication. Email is inherently unauthenticated. I guess checking the from address against the entire OWW database and then doing a lookup of the OWW user is possible. --Austin Che 16:41, 23 January 2007 (EST)
    • I hadn't thought about the spam or authentication problem. Your idea sounds good, but I guess it's still easy to fake a "from address" right? Maybe in the near term I should figure out an off-line solution (just send email to myself and then cut and paste when I have time). Thanks for your answers, Austin! And thanks for showing me that email extension, I will keep it in mind--Skoch3 17:01, 23 January 2007 (EST)
    • Yes faking from addresses is trivial. If you are willing to (and your email client is capable of it), it would be possible and easy to implement a way for authentication to be passed in extra email headers. So you would have to add to every email to the wiki something of the form X-OpenWetWare-Password: Secret which would kind of authenticate you. Some mail clients let you do this trivially while I believe it's impossible with others, but I could possibly implement this and see who has use for it. --Austin Che 18:44, 23 January 2007 (EST)
    • I'd say hold off, since it's not clear anyone else needs it, and I am still learning. Thank you for thinking about this --Skoch3 21:37, 23 January 2007 (EST)
  • In the same vein as emailing to the wiki, I have a dream of being able to call and leave messages on the wiki. This is for when I am in my car and remember something. Of course, an actual voice recording would be a lot of data and too annoying to ever manually convert into text. So, one would want the wiki to have voice recognition software to convert the voicemail into a text notebook entry. Yes, I know this is a long way off!
    • This isn't that much harder than the email. The main thing is how are you going to specify a page name on your phone? Also, voice recognition really isn't that great. --Austin Che 16:41, 23 January 2007 (EST)
    • Yeah, I can see that the voice recognition wouldn't work too well. Maybe for this and the email idea above, a better solution is to handle these things "off the wiki" and then manually "dump" information into the right place via normal mechanisms. Actually I guess what I really want is an assistant who I can call. :) --Skoch3 17:01, 23 January 2007 (EST)
  • OK, I know this idea is really tough too, but maybe there's work going on I don't know of. I am a user of evil microsoft products. I actually like Outlook and I suspect that since I will be doing email, I will also use the Outlook Calendar, and task list (to do). Would there be some way of "synching" outlook with a wiki? So that I could use the convenient way on Outlook of adding calendar events and task lists, but have it synched with public wiki pages? Some kind of wiki outlook plug in? OK, I know the market for that would be small. Synching with Outlook would then also make it easier to somehow add stuff to the wiki via a PDA--Skoch3 16:25, 23 January 2007 (EST)
    • Reshma 17:01, 23 January 2007 (EST): It is possible to view Google calendars on a wiki. See Endy:Victor3_plate_reader#Plate_reader_schedule for an example. So if you could get Outlook to sync with a Google calendar, then you could just display the Google calendar on a particular wiki page. That is the most straightforward way to do it right now (or at least the way that requires no new coding/functionality).
    • Very interesting, that looks like it would work for me, so I will look into it. Thank you!--Skoch3 17:04, 23 January 2007 (EST)

OWW journal clubs

  • --Vincent 05:58, 7 December 2006 (EST): Organizing a section of OWW where several journal clubs would be hosted (Computational Biology, Synthetic Biology, Lab Techniques in Microbiology ...) -- Has it been tried before ? Not at the lab level but with article discussions openly discussed by OWW users.

A given OWW journal club would have a focus on a defined area (use of categories), a place where people could suggest articles to be reviewed , and a selected article (voted every 2 weeks for example) being open for discussion through an open forum. It could be concluded by a conference call if people are motivated (more constraining to organize). It would be great to build a rich literature review that OWW could share and point to in the rest of the wiki.

Dear OWWers, I started an online journal club page with a draft here: Journal Club. Have a look and extend at your leisure. So far it's only a static article review. But with the excellent chat feature that was added recently, people could gather on a specific article page and really discuss world-wide. Jasu 09:41, 18 April 2007 (EDT)

OWW Short Course

  • Lon 13:33, 30 November 2006 (CST): Although there are protocol and course pages on OWW, both containing educational information and objectives, it might be good to have some more refined experiments. By this, I mean for newcomers to the biological sciences (new lab members, new labs) or those moving into new areas to have a set of standard experiments they could perform to establish good laboratory techniques and to be able to communicate problems with OWW members and/or their labmates. This could also be an alternative for lab instructors to use. This could be something like an updated and more encompassing Short Course in Microbial Genetics (or any another good lab manual).

Academic Job Openings

  • Jasonk 11:52, 10 November 2006 (EST): Came up at the last SC meeting, could have a place to post open post-doc positions, faculty, etc. Could also have corporate job postings, but that's probably already covered pretty well by Monster.com type websites.

Calendar with all scientific conferences

  • Jasonk 11:52, 10 November 2006 (EST): Suggested by Tom. This would be a calendar strictly for scientific conferences, since it's often tough to find out about conferences you might be interested in.

OWW Journals

  • Jasonk 01:50, 25 October 2006 (EDT): Based on conversations with Chris Surridge, our 2nd OWW Open Science Seminar series speaker, it looks like starting a journal may get much easier. The general idea is to use PLoS One as a commoditized peer-reviewing service. Articles that get through the PLoS One filter have been verified for publication-quality science, but have not been subjected to any subjective merit criteria (e.g. is this good enough for publication in Nature?) This is where OWW can come in, user groups on OWW could aggregate and "re-publish" open access (OA) content that has made it onto PLoS One (or any other OA journal). Basically, we would serve as an aggegator of articles that conform to some quality standard set by an editorial board from that community. An author published in the OWW Journal of Synthetic Biology could site their PLoS one reference as well as a 're-publication' reference. If the OWW Journal actually gained some clout, an author would probably simply list being published in the aggregator rather than the PLoS One reference, since it would carry more weight (e.g. the paper had to get over the merit quality bar -- "is this good enough for publication in OWW Journal of Synth Bio?"). a very high bar, indeed ;) Additionally, we could provide commentary on the papers that are of interest, "blog-esque" posts from notable community members, etc...
  • open source journal management software

OpenWetWare:Reviews

  • Jasonk 09:26, 6 October 2006 (EDT): Along the lines of adopt-a-protocol, it might be great to have adopt a topic area as well. Basically, trying to solve the problem of review articles always being out of date. It seems like the job of writing reviews would be much simpler if it was done on the fly as new papers came out. THat way when a new paper came accross your desk in the area you review you could read it, and then add the relevant details and the reference to the OWW Review page. This is in contrast to coming back to that same paper a year later when you're asked to write a review and having to re-read it, re-analyze it, etc. Seems like a win-win for the both the review-writer (less work) and the readers (who get a more up-to-date source.)

Adopt-a-protocol

Moved to Talk:Protocols/Template.

Page Authorship

  • Jasonk 22:57, 8 August 2006 (EDT): There might be a benefit to having the option to lock in an "author" at the time of page creation. We could limit this to pages with a namespace in front of them (e.g. 'Endy:foo'), to prevent someone from locking down a 'shared area' page like DNA ligation. Other people could edit the page, but there would be an official author -- that means the author would have the benefit of getting credit for the content of the page (e.g. perhaps when you hit cite this page, only the offical author would come up), but also be saddled with ensuring some level of quality (whatever they were comfortable attaching their name to). This might help enable some downstream OWW applications, like providing real scientific attribution for OWW contributions or for publishing results, etc. I suspect that assigning a page an official authorship would be the exception rather than the rule, but might be a useful option to have -- just something to think about longer term, wanted to write it down.

Sidebar

  • Jasonk 16:38, 27 July 2006 (EDT):The customize sidebar extension is great, but I don't think any new user would notice it. Maybe at the bottom of the side bar we should include a link be default that says update my sidebar and would take the user to a pregenerated sidebar page for them with comments on how to change it. once they figured it out they could remove the link themselves from their sidebar if they don't want it there.


Navigation

  • --Johncumbers 16:38, 16 July 2006 (EDT): A big problem I've found with OWW, and I'd like to see if anyone else has the same problem. I can't stay logged in, e.g Flickr, Amazon retains who I am, but OWW doesn't. Is this just me? This leads to the seconds part of the problem. When I go to log-in, it always returns me the link to go back to the main page, I then have to use the back button to go back to the page I want to edit. These are not huge problems, but they really confuse new people that I introduce to the site. They find it really frustrating to navigate at the beginning. Anyone else found this when trying to introduce new people to OWW/Mediawiki?
    • Smeister 07:38, 17 July 2006 (EDT) OWW keeps me logged in unless I log in from another computer - in that case I get logged out from the first. Are you maybe sharing your account? I assume you do not have any cookie setting problems since Flickr etc works for you...
    • Jasonk 09:25, 17 July 2006 (EDT): I stay logged in as well normally... However, to avoid getting linked back to the main page, use the link at the top right corner to log in - it will then offer a link back to the page you were coming from, rather than a link to the Main Page (I agree it is annoying when it links to the Main Page).
    • Austin 13:59, 17 July 2006 (EDT): On one computer, I can't stay logged in. On another, I always stay logged in. I've not been able to figure out the cause.
    • Skoch3 16:14, 23 January 2007 (EST): I always seem to have to re-log in. I use one computer, but it's a laptop with a lot of different IP addresses during the day I think. It seems I have to log in to my private wiki more often than the public, but not sure. I have been assuming that it was just some quirk between the private wiki log on and the OWW.

Page watch function

Smeister 08:20, 17 July 2006 (EDT) I love the "watch page" function and would like to organize more activities in the lab, taking advantage of it. However, there is no way of knowing who in the lab is watching a page at any moment. You basically never know if anybody is paying attention at all. Would a query page for this be very hard to incorporate? It sure would enhance overall transparency and I guess it would also be useful for some of these OWW discussion pages...

  • --Johncumbers 13:14, 17 July 2006 (EDT) I agree, I don't use the page watch as much as I'd like. I like you ridea Steven, It would be also nice if it had a little number like 'my watchlist(44)' to let you know what's inside there each day and encourage you to click on it.

Comment button

  • --Johncumbers 13:14, 17 July 2006 (EDT) could the signature button be changed to include the * and ''' that we put in for comments. Another idea would be a protocol notes button that creates a note link for a protocol. Currently if you want to add a note to a protocol, you have to either put it at the bottom, it would be better if it created a link within the page without you having to type it all out. e.g if the protocol is located at Protocols:Drosophila/chip on chip then when I post a note, it automatically creates a link to Protocols:Drosophila/chip on chip/note1 without me having to do it. get the idea?

Active Discussions

Lucks 20:16, 3 April 2006 (EDT):The topic on Flexible Science Databases has been moved to OpenWetWare:Software/Flexible_Science_Databases.

Subarticles

Recent Changes in Ideas

List of abbreviations:
N
This edit created a new page (also see list of new pages)
m
This is a minor edit
b
This edit was performed by a bot
(±123)
The page size changed by this number of bytes

17 April 2024

     15:34  BioMicroCenter:Element Sequencing‎‎ 3 changes history +295 [Challee‎ (3×)]
     
15:34 (cur | prev) +195 Challee talk contribs
     
14:22 (cur | prev) +100 Challee talk contribs
     
14:07 (cur | prev) 0 Challee talk contribs
     13:10  BioMicroCenter:SingleCell diffhist +30 Noelani Kamelamela talk contribs (→‎10X CHROMIUM X)
     12:43  BioMicroCenter diffhist −15 Noelani Kamelamela talk contribs

16 April 2024

N    19:59  Nanoimprint Lithography (NIL) - Carter Paul‎‎ 10 changes history +7,205 [CarterPaul‎ (10×)]
     
19:59 (cur | prev) +769 CarterPaul talk contribs (→‎Thermal NIL Process)
     
19:53 (cur | prev) 0 CarterPaul talk contribs (→‎Thermal NIL Process)
     
19:53 (cur | prev) 0 CarterPaul talk contribs (→‎Thermal NIL Process)
     
19:52 (cur | prev) +1 CarterPaul talk contribs (→‎Thermal NIL Process)
     
19:50 (cur | prev) +202 CarterPaul talk contribs (→‎Thermal NIL Process)
     
19:17 (cur | prev) −20 CarterPaul talk contribs (→‎References)
     
19:17 (cur | prev) −1 CarterPaul talk contribs
     
19:11 (cur | prev) +4,278 CarterPaul talk contribs
     
18:53 (cur | prev) +1,891 CarterPaul talk contribs
N    
18:42 (cur | prev) +85 CarterPaul talk contribs (Created page with "{{Template:CHEM-ENG590E}} =Motivation= =Introduction to NIL= =Thermal NIL Process=")
     19:40 Upload log CarterPaul talk contribs uploaded File:NIL1.png
N    18:40  3D Cell Culture - McLean Taggart, Emma Villares, Maximillian Marek, Scott LeBlanc, Adam Lyons and Jacob Belden diffhist +24,060 CarterPaul talk contribs (Created page with "{{Template:CHEM-ENG590E}} ==Introduction== While most microfluidic devices incorporate a 2D cell culture design, in which a single layer of cells is grown on the bottom of a device, these systems suffer from poor <i>in vivo</i> mimicry, as, in the human body, most cells grow in all directions.<sup>https://doi.org/10.5114/aoms.2016.63743 1</sup> To address this limitation, 3D cell culture devices have been developed - in w...")
     18:38  CHEM-ENG590E:Wiki Textbook‎‎ 2 changes history +63 [CarterPaul‎ (2×)]
     
18:38 (cur | prev) +50 CarterPaul talk contribs (→‎Chapter 1 - Microfabrication)
     
18:37 (cur | prev) +13 CarterPaul talk contribs
     18:36  3D Cell Culture - McLean Taggart, Emma Villares, Maximillian Marek, Scott LeBlanc, and Adam Lyons diffhist +5,343 CarterPaul talk contribs (Added a Technique and applications section)
     10:20  Yarn Microfluidics - Roger Dirth‎‎ 12 changes history +442 [Rcostello‎ (12×)]
     
10:20 (cur | prev) +41 Rcostello talk contribs (→‎Applications)
     
10:19 (cur | prev) +36 Rcostello talk contribs (→‎Applications)
     
10:18 (cur | prev) +36 Rcostello talk contribs (→‎Introduction)
     
10:17 (cur | prev) +38 Rcostello talk contribs (→‎Fabrication)
     
10:17 (cur | prev) +38 Rcostello talk contribs (→‎Washburn Equation)
     
10:16 (cur | prev) +38 Rcostello talk contribs (→‎Wicking Rate)
     
10:16 (cur | prev) +37 Rcostello talk contribs (→‎Introduction)
     
10:15 (cur | prev) +36 Rcostello talk contribs (→‎Wicking Rate)
     
10:14 (cur | prev) +36 Rcostello talk contribs (→‎Fabrication)
     
10:14 (cur | prev) +34 Rcostello talk contribs (→‎Applications)
     
10:14 (cur | prev) +36 Rcostello talk contribs (→‎Introduction)
     
10:13 (cur | prev) +36 Rcostello talk contribs (→‎Introduction)
     08:18  3D Printed Microfluidic Robots - Helen Hua‎‎ 2 changes history +6 [Michele Caggioni‎ (2×)]
     
08:18 (cur | prev) +22 Michele Caggioni talk contribs (→‎Actuation)
     
08:18 (cur | prev) −16 Michele Caggioni talk contribs (→‎Actuation)
     08:11  3D Printing Overview diffhist +422 Michele Caggioni talk contribs

15 April 2024

     23:43  User:Yanbin Huang‎‎ 2 changes history +170 [Yanbin Huang‎ (2×)]
     
23:43 (cur | prev) 0 Yanbin Huang talk contribs (→‎Granted Patents)
     
23:43 (cur | prev) +170 Yanbin Huang talk contribs (→‎Granted Patents)
     22:11  The paper that launched microfluidics - Xi Ning‎‎ 11 changes history +4,793 [Xning098‎ (11×)]
     
22:11 (cur | prev) −6 Xning098 talk contribs (→‎Summary)
     
22:07 (cur | prev) −12 Xning098 talk contribs (→‎Synthesis)
     
22:06 (cur | prev) 0 Xning098 talk contribs
     
22:06 (cur | prev) +1 Xning098 talk contribs
     
22:05 (cur | prev) 0 Xning098 talk contribs
     
22:03 (cur | prev) +630 Xning098 talk contribs
     
22:01 (cur | prev) +3,189 Xning098 talk contribs
     
21:44 (cur | prev) +688 Xning098 talk contribs (→‎Separation and quantification)
     
21:33 (cur | prev) +306 Xning098 talk contribs
     
21:29 (cur | prev) −2 Xning098 talk contribs (→‎Electrokinetic effect)
     
21:28 (cur | prev) −1 Xning098 talk contribs (→‎Separation and quantification)
     21:45  (Upload log) [Xning098‎ (2×)]
     
21:45 Xning098 talk contribs uploaded File:Figure 4 Tdesign.png
     
21:30 Xning098 talk contribs uploaded File:Figure 3 Set-up3.png