|
|
(42 intermediate revisions not shown) |
Line 1: |
Line 1: |
- | <!-- ------------------------------------------------From 2011 Macquarie--------------------------------------------- -->
| + | {{:Team:UQ-Australia/Template:Header}} |
| + | {|style="width:100%;" border="0" cellpadding="10" cellspacing="0" |
| + | |- valign="top" |
| + | |rowspan="2"|The UQ-Australia iGEM team has been involved in a number of human practices and outreach activities throughout the year. In particular, we have [[#Outreach|'''presented synthetic biology''']] to high school students at the [[#Biofutures |'''BioFutures''']] camp and to [[#PAIN Physics Society |'''undergraduate physics students''']]. Additionally, we have reviewed the [[#Patenting|'''issue of patented parts''']] present to iGEM, and have been involved in the [[#Collaboration|'''collaborative effort''']] to create CommunityBricks and AlumniGEM. All these activities are summarised below. |
| + | |[[File:UQ-Australia_logo_2011.png|125x125px|link=https://2011.igem.org/Team:UQ-Australia]] |
| + | |- |
| + | |} |
| | | |
| + | == <span style="color:#558822">Patenting</span> == |
| | | |
- | <html>
| + | In a dynamic field such as synthetic biology, discovery moves at an astounding pace and is driven by the findings of groups from all around the world. However, conflict often arises when the choice between collaboration and commercialisation arises, and consequently patents have become commonplace in the scientific world. In the last 5 years, 34% of respondents had applied for or received a patent on their findings. Additionally, 68% stated that they had sent research tools to others in academia [1]. This is especially relevant in iGEM, a competition whose explicit aim is to remain open source and collaborative. We examine whether this is a realistic or achievable goal within the framework of patents in the scientific world. |
- | <body>
| + | |
- | <body style="background-color:#772288">
| + | |
- | </body>
| + | |
| | | |
| | | |
- | <head>
| + | Within iGEM, the stipulation that all BioBricks must remain open source and redistributable means that patented material is inherently excluded from submission. This sort of restriction differs somewhat from the usual research experience, where 91% of scientists have not checked for patents on the material they used in the last 5 years [1]. However, iGEM falls in a unique `grey area’, which effectively prevents the use of any patented materials by participating teams with the requirement to submit their parts to the Registry to be redistributed. Although teams are using parts solely for research purposes, the nature of the registry and iGEM’s distribution kits means that by redistributing parts iGEM would be infringing on the patent holder. The UQ-Australia iGEM team is limited in their project due to patents on key components. |
- | <style type="text/css">
| + | |
- | body {background-color:#A11F37;}
| + | |
| | | |
- | <!-- Wiki Hacks -->
| |
| | | |
| + | In the past, the issue of patenting has been less significant on iGEM with a recent survey indicating that less than twenty teams faced any legal issues regarding patenting and their parts [2]. This would likely be since the majority of teams worked in bacteria, where the parts have either never been patented, or any patents have since expired. However, as more explore synthetic biology in mammalian projects, patenting is going to become an unavoidable issue. Consequently, we propose two possible mechanisms for iGEM to handle patents on biological parts. |
| | | |
- | {
| |
- | overflow: -moz-scrollbars-vertical !important;
| |
- | resize: none;
| |
- | background-color: #f5f6f7;
| |
- | }
| |
| | | |
- | #top-section {
| + | The first - and seemingly simplest - solution is to simply allow teams to use patented parts, and require them to submit the sequences online (including detailed information on how they modified and used it), but without requiring the submission of physical DNA samples. This would mean that other teams could still utilise parts by purchasing them direct from the license holder and modifying them as per the instructions, without the traffic or redistribution of any patented parts. The problem with this idea is that it is highly likely that the iGEM registry would then rapidly fill with these ‘information only’ pieces that cannot be included in the distribution kit. This goes against the central aim of iGEM and the BioBrick model if there is no sharing of parts. A slight alternative to this model would be to limit the number of patented parts each team could use and submit in such a way, but we feel that this still goes against the aims of iGEM, and depending on the individual team’s project may well still present problems. |
- | height: 20px;
| + | |
- | border-left: none;
| + | |
- | border-right: none;
| + | |
- | }
| + | |
| | | |
- | #siteSub {
| |
- | display:none;
| |
- | }
| |
| | | |
- | #search-controls {
| + | As a result, we have developed another alternative solution. In this case, we propose that iGEM should enter into formal agreements with the companies or individuals holding the license of many patented materials. This could operate in a similar manner to iGEM’s current sponsorship agreements, whereby the companies in question get advertising on the iGEM website, or a presence at the jamborees, and in return they provide iGEM with an overarching licence agreement that allows the distribution of patented parts within the competition (i.e. amongst registered teams). In this way, the registry could continue operating as is, and teams would be unhindered in taking on their projects. This avoids the current ‘don’t ask, don’t tell’ mentality that some has, and alleviates the issue of unwary teams not knowing to search for patents before initiating their projects. |
- | display:none;
| + | |
- | }
| + | |
| | | |
- | .firstHeading {
| |
- | display:none;
| |
- | }
| |
| | | |
- | #search-controls {
| + | However, we do see that this plan could open iGEM up to the influence of outside corporations, and of course that not all companies may be willing to undertake such a partnership. To keep iGEM independent of such parties, we think a well-defined agreement would be required that specifies exactly what each party agrees to, which we assume must be similar to any agreement iGEM has with its current sponsors. In effect, this agreement would just be another form of sponsorship, with both parties benefiting; the patent holders get access and exposure to a cohort of intelligent young scientists who will soon be entering the workforce or undertaking further research, while iGEM gets the ability to redistribute and modify these items within the competition’s community. |
- | margin-top:0px;
| + | |
- | }
| + | |
| | | |
- | #footer-box {
| |
- | display:none;
| |
- | }
| |
| | | |
| + | We foresee this option as a solution that complies with the aims of both patent-holders and iGEM: |
| | | |
| + | Patent holders: |
| + | * maintain ownership of their items |
| + | * Profit in the long-term from past iGEM participants continuing to use their products outside of the competition |
| | | |
- | #contentSub {
| |
- | display:none;
| |
- | }
| |
| | | |
- | #siteSub {
| + | iGEM: |
- | display:none;
| + | * unlimited use of patented products |
- | }
| + | * can offset any potential licensing fee by providing advertising to the companies |
| + | * has the ability to share and standardise patented parts within the competition |
| + | * maintains its independence from outside interests |
| | | |
- | #search-controls {
| |
- | display:none;
| |
- | }
| |
| | | |
- | .firstHeading { | + | Although iGEM has remained a staunchly open-source arena for innovation in synthetic biology, we feel that the current trend in science to patent any promising discoveries will mean that iGEM and the intellectual property (IP) field will inevitably cross paths more and more often as time goes on. Consequently, immediate action should be taken to achieve the best possible outcome for participating iGEM teams, while also retaining iGEM’s independent, open source nature as much as possible. We have presented two possible solutions to this problem – the first allows iGEM to avoid any direct contact with IP holders, but means that the quality of the distribution kit and BioBrick library could be compromised over time. The second solution requires more direct negotiation with licence holders, but would hopefully result in a licencing agreement allowing iGEM to keep on largely as it has been run in the past. If iGEM does decide to confront this issue, the choice it makes will depend on the direction the competition, and indeed synthetic biology as a whole, wishes to take in the future. In this constantly adapting scientific landscape, it is important that iGEM is able to fit in amongst the framework established by industry and the academic world to facilitate discovery and innovation, which is at the centre of synthetic biology and the scientific discipline. |
- | display:none;
| + | |
- | }
| + | |
| | | |
- | #search-controls {
| |
- | margin-top:0px;
| |
- | }
| |
| | | |
- | #footer-box {
| + | [1] Lei, Z, Juneja, R & Wright, BD, 2009, ‘Patents versus patenting: implications of intellectual property protection for biological research’, Nature Biotechnology, vol. 27, pp. 36-40. |
- | display:none;
| + | |
- | }
| + | |
| | | |
- | #top-section {
| + | [2] Mexico-UNAM-CINVESTAV, 2010, `Human Practices: Survey Results', accessed 4 August 2011 from https://2010.igem.org/Team:Mexico-UNAM-CINVESTAV/Home |
- | height: 20px;
| + | |
- | border-left: none;
| + | |
- | border-right: none;
| + | |
- | }
| + | |
| | | |
- | .left-menu {
| |
- | margin-top:-12px;
| |
- | }
| |
| | | |
- | .right-menu { | + | We would like to thank Randy Rettberg from iGEM, David Douglas from [http://www.uq.edu.au/hprc/ School of History, Philosophy, Religion and Classics] at the [http://www.uq.edu.au/ University of Queensland], Tim Kastelle of the [http://www.business.uq.edu.au/ UQ Business School] at [http://www.uq.edu.au/ University of Queensland] and Anne Fitzgerald from Creative Commons for their insightful discussion and thought provoking questions about the sharing patenting system. |
- | margin-top:-12px;
| + | |
- | }
| + | |
| | | |
- | .left-menu ul {
| |
- | border: none;
| |
- | }
| |
| | | |
- | #menubar li a {
| + | == <span style="color:#558822">Outreach</span> == |
- | color:#8C8984;
| + | |
- | background-color:transparent;
| + | |
- | }
| + | |
| | | |
- | #menubar ul {
| + | As part of the Human practices work, UQ-Australia has promoted synthetic biology and iGEM to others. Major outreach ventures had included a presentation and activity at [http://www.ausbiotech.org/content.asp?pageid=156 Biofutures]: a national biotechnology student forum and is intended to also include a presentation at a local high school and [http://physics.uq.edu.au/pain/ PAIN Physics Society]. |
- | color:transparent;
| + | The presentations had varying aims to suit the varying audience. |
- | background-color:transparent;
| + | |
- | }
| + | |
| | | |
- | #menubar {
| + | === <span style="color:#D4A017">Biofutures </span>=== |
- | background-color:transparent;
| + | |
- | font-size:85%;
| + | |
- | line-height:1em;
| + | |
- | position:absolute;
| + | |
- | top:10px;
| + | |
- | white-space:nowrap;
| + | |
- | width:50%;
| + | |
- | z-index:5;
| + | |
- | height:20px;
| + | |
- | overflow:hidden
| + | |
| | | |
- | }
| + | {|style="width:100%;" border="0" cellpadding="10" cellspacing="0" |
| + | |- valign="top" |
| + | |width=125"|[[File:BF logo 2011.jpg|125x125px|link=http://www.ausbiotech.org/content.asp?pageid=156]] |
| + | |[http://www.ausbiotech.org/content.asp?pageid=156 Biofutures] is a biotechnology forum for Year 11 and 12 students from Australia and New Zealand. UQ-Australia ran a workshop on 3 July 2011. This workshop included a presentation and a group activity. There are [http://www.facebook.com/media/set/?set=a.239278726099649.74195.174356539258535&l=f672fa7c36&type=1 pictures] and notes from this. |
| + | The aim of the contribution to Biofutures was to introduce iGEM as a possible option for them when they pursue their tertiary studies. |
| | | |
- | .left-menu {
| + | From this activity, students and mentors |
- | left:0;
| + | * went through some of the thinking process followed by the iGEM students when formulating a project |
- | padding-left: 0px;
| + | * gained an idea of what has been happening for synthetic biology/ iGEM |
- | }
| + | * were able to put synthetic biology into perspective with science and society |
- | .right-menu {
| + | |- |
- | right:0;
| + | |} |
- |
| + | |
- | } | + | |
| | | |
- | .firstHeading { display:none; }
| |
- | }
| |
| | | |
- | #menubar{
| |
- | color: #transparent;
| |
- | }
| |
| | | |
- | #menubar.right-menu {
| + | Notes for the Biofutures and PAIN activities can be [https://static.igem.org/mediawiki/2011/7/76/UQ-iGEM-Outreach.zip '''downloaded HERE'''] and are in [http://openwetware.org/wiki/IGEM_Outreach:Synbio_Problem_Solving '''CommunityBricks''']! |
- | margin-top:-12px;
| + | |
- | }
| + | |
| | | |
- | .right-menu ul {
| + | === <span style="color:#D4A017">PAIN Physics Society</span>=== |
- | border: none;
| + | |
- | }
| + | |
| | | |
- | #menubar{
| |
- | top:15px;
| |
- | z-index:25;
| |
- |
| |
- | }
| |
- |
| |
- | #menubar {
| |
- | background-color:f5f6f7;
| |
- | font-size:85%;
| |
- | line-height:1em;
| |
- | position:absolute;
| |
- | top:10px;
| |
- | white-space:nowrap;
| |
- | width:50%;
| |
- | z-index:5;
| |
- | height:20px;
| |
- | overflow:hidden
| |
- |
| |
- | }
| |
- |
| |
- | img[src*="/wiki/skins/common/images/wiki.png"]{
| |
- | width:0;
| |
- | height:60px;
| |
- | padding-right:975px;
| |
- | background:#transparent;
| |
- | }
| |
- |
| |
- |
| |
- |
| |
- | ul#list-nav {
| |
- | list-style:none;
| |
- | margin:7px 75px 7px;
| |
- |
| |
- | padding:0;
| |
- | width:1000px
| |
- |
| |
- | }
| |
- |
| |
- | ul#list-nav li {
| |
- | display:inline
| |
- | }
| |
- |
| |
- | ul#list-nav li a {
| |
- | text-decoration:none;
| |
- | padding:5px 0;
| |
- | width:100px;
| |
- | background:#A11F37;
| |
- | color:#eee;
| |
- | float:left;
| |
- | text-align:center;
| |
- | border-left:1px solid #fff;
| |
- | }
| |
- |
| |
- | ul#list-nav li a:hover {
| |
- | background:#a2b3a1;
| |
- | color:#000
| |
- | }
| |
- |
| |
- |
| |
- |
| |
- | <!-- End of Wiki Hacks -->
| |
- |
| |
- |
| |
- |
| |
- |
| |
- |
| |
- | </body>
| |
- | </html>
| |
- |
| |
- |
| |
- |
| |
- |
| |
- |
| |
- |
| |
- |
| |
- |
| |
- |
| |
- |
| |
- | <!-- -------------------------------------------------From 2009 UQ--------------------------------------------------- -->
| |
- |
| |
- |
| |
- | __NOTOC__
| |
- | <html>
| |
- | <body style="background-color:#772288">
| |
- |
| |
- | <style>
| |
- | h1.firstHeading { display: none; }
| |
- |
| |
- | p {text-align: justify;}
| |
- |
| |
- | a:link { color: #603371; text-decoration: none}
| |
- | a:visited { color:#603371; text-decoration: none}
| |
- | a:hover { color:#f29400; text-decoration: none}
| |
- | a:active { color:#f29400; text-decoration: none}
| |
- |
| |
- | #bodyContent { padding: 10px auto; width: 910px; margin: auto; clear: none; }
| |
- |
| |
- | table#team_members { text-align: justify; border: 0; }
| |
- | table#team_members h2, table#team_members h3 { clear: both; }
| |
- |
| |
- |
| |
- | /*-----------------------------------------------------------------------------------------------*/
| |
- | div.MenuBar ul li ul.DropDownMenu {
| |
- | display: none; /* Hides all drop-down menus. */
| |
- |
| |
- | }
| |
- | /*
| |
- | li:hover works in IE7 and FF2.
| |
- | a:hover works in IE6 and FF2.
| |
- | a:hover breaks li:hover in FF2.
| |
- | */
| |
- | div.MenuBar ul li:hover ul.DropDownMenu li ul.SideMenu,
| |
- | div.MenuBar ul li a:hover ul.DropDownMenu li a ul.SideMenu {
| |
- | display: none; /* Hides all side menus. */
| |
- | }
| |
- | /*------------------------------------------------------------------------------------- Menu Bar */
| |
- | div.MenuBar {
| |
- | font: arial, helvetica, sans-serif;
| |
- | height: 50px;
| |
- | width: 910px;
| |
- | /*width: 100%*/
| |
- | margin: 0;
| |
- | border-top: 0;
| |
- | border-right: 0;
| |
- | border-left: 0;
| |
- | padding: 0;
| |
- | background: black;
| |
- |
| |
- | }
| |
- | div.MenuBar ul {
| |
- | font: arial, helvetica, sans-serif;
| |
- | text-align: center;
| |
- | list-style-type: none;
| |
- | margin: 0;
| |
- | border: 0;
| |
- | padding: 0;
| |
- | background: black;
| |
- | }
| |
- | div.MenuBar ul li {
| |
- | font: arial, helvetica, sans-serif;
| |
- | display: block;
| |
- | padding: 0;
| |
- | margin: 0;
| |
- | font-size: 1.3em;
| |
- | float: left;
| |
- | background: black;
| |
- | text-align: center;
| |
- | width: 90px;
| |
- | position: relative; /* Sets the positioning context for each drop-down menu. */
| |
- | }
| |
- |
| |
- | div.MenuBar ul li a {
| |
- | font: arial, helvetica, sans-serif;
| |
- | display: block;
| |
- | background: black;
| |
- | height: 40px; /* Keep height + padding-top + padding-bottom sync with the menu bar height. */
| |
- | color: #ffffff;
| |
- | padding-top: 4px;
| |
- | padding-bottom: 4px;
| |
- | padding-left: 1em; /* Sets the left space between top-level items. */
| |
- | padding-right: 1em; /* Sets the right space between top-level items. */
| |
- | text-decoration: none;
| |
- | }
| |
- |
| |
- | /*------------------------------------------------------------------------------ Drop-Down Menus */
| |
- | div.MenuBar ul li:hover ul.DropDownMenu,
| |
- | div.MenuBar ul li a:hover ul.DropDownMenu {
| |
- | display: block;
| |
- | width: 10em; /* Drop-down menu width.
| |
- | Use MenuTailor.css to customize. */
| |
- | height: 1em;
| |
- | padding: 1px; /* Sets the drop-down menu "effective border" width. */
| |
- | position: absolute;
| |
- | top: 23px; /* Places the drop-down menu under the menu bar.
| |
- | Keep it sync with the menu bar height. */
| |
- | left: 0; /* Aligns the drop-down menu to its top-level item. */
| |
- | background-color: black; /* Selected item. */
| |
- | color: #FFFFFF;
| |
- |
| |
- | }
| |
- | div.MenuBar ul li:hover ul.DropDownMenu li a,
| |
- | div.MenuBar ul li a:hover ul.DropDownMenu li a {
| |
- | width: 10em; /* Keep it sync with the drop-down menu width.
| |
- | Use MenuTailor.css to customize. */
| |
- | height: 1em;
| |
- | padding-left: 0;
| |
- | padding-right: 0;
| |
- | background-color: black; /* Selected item. */
| |
- | color: #FFFFFF;
| |
- | }
| |
- | ul.DropDownMenu li a span {
| |
- | display: block;
| |
- | padding-left: 0.75em; /* Sets the left space of each drop-down menu item. */
| |
- | padding-right: 0.25em; /* Sets the right space of each drop-down menu item. */
| |
- | text-align: right; /* Aligns the >> symbol to the right. */
| |
- | }
| |
- | ul.DropDownMenu li a span span {
| |
- | float: left; /* Aligns the text (back) to the left. */
| |
- | font: 12px arial, helvetica, sans-serif; /* Required for IE55. */
| |
- | height: 20px;
| |
- | color: #FFFFFF;
| |
- | }
| |
- | /*----------------------------------------------------------------------------------- Side Menus */
| |
- | div.MenuBar ul li:hover ul.DropDownMenu li:hover ul.SideMenu,
| |
- | div.MenuBar ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu {
| |
- | display: block;
| |
- | width: 11em; /* Side menu width.
| |
- | Use MenuTailor.css to customize. */
| |
- | padding: 1px; /* Sets the side menu "effective border" width. */
| |
- | position: absolute;
| |
- | top: -1px; /* Aligns the side menu to its drop-down menu item.
| |
- | Keep it sync with the side menu "effective border" width. */
| |
- | left: 13em; /* Places the side menu to the right of the drop-down menu.
| |
- | Keep it sync with the drop-down menu width.
| |
- | Use MenuTailor.css to customize. */
| |
- | }
| |
- | div.MenuBar ul li:hover ul.DropDownMenu li:hover ul.SideMenu li a,
| |
- | div.MenuBar ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu li a {
| |
- | width: 11em; /* Keep it sync with the side menu width.
| |
- | Use MenuTailor.css to customize. */
| |
- | font: 12px arial, helvetica, sans-serif; /* Required for IE55. */
| |
- | left: 13em; /* Places the side menu to the right of the drop-down menu.
| |
- | Keep it sync with the drop-down menu width.
| |
- | Use MenuTailor.css to customize. */
| |
- | }
| |
- | div.MenuBar ul li ul.DropDownMenu li ul.SideMenu li a span {
| |
- | padding-left: 1.5em; /* Sets the left space of each side menu item. */
| |
- | padding-right: 0.5em; /* Sets the right space of each side menu item. */
| |
- | text-align: left;
| |
- | font: 12px arial, helvetica, sans-serif; /* Required for IE55. */
| |
- | left: 13em; /* Places the side menu to the right of the drop-down menu.
| |
- | Keep it sync with the drop-down menu width.
| |
- | Use MenuTailor.css to customize. */
| |
- | }
| |
- | /*----------------------------------------------------------------------------- Browser Specific */
| |
- | * html div.MenuBar ul li a {
| |
- | float: left; /* Required for IE55 and IE6.
| |
- | Breaks O9.
| |
- | Hidden (* html) from non-IE browsers. */
| |
- | }
| |
- | * html ul.DropDownMenu li a:hover {
| |
- | cursor: hand; /* Required for IE55.
| |
- | Hidden (* html) from non-IE browsers. */
| |
- | }
| |
- | ul.DropDownMenu li a:hover {
| |
- | cursor: pointer; /* Required for IE6 and IE7.
| |
- | Hidding it (* html) from non-IE browsers breaks IE7!
| |
- | }
| |
- | * html div.MenuBar a:hover {
| |
- | text-decoration: none; /* Required for IE55 and IE6.
| |
- | Hidden (* html) from non-IE browsers. */
| |
- | }
| |
- | * html div.MenuBar ul li table,
| |
- | * html div.MenuBar ul li table td {
| |
- | border: 0; /* Required for IE55 and IE6.
| |
- | Hidden (* html) from non-IE browsers. */
| |
- | }
| |
- | /*------------------------------------------------------------------------------- Default Colors */
| |
- | div.MenuBar {
| |
- | background-color: Menu;
| |
- | border-bottom: 1px solid ButtonShadow;
| |
- | }
| |
- | div.MenuBar a {
| |
- | background-color: Menu; /* Top-level unselected items. */
| |
- | color: MenuText;
| |
- | }
| |
- | div.MenuBar ul li:hover a,
| |
- | div.MenuBar ul li a:hover {
| |
- | color: #ea7f16;
| |
- | background-color: Highlight; /* Top-level selected item. */
| |
- | color: HighlightText;
| |
- | }
| |
- | /*...............................................................................................*/
| |
- | div.MenuBar ul li:hover ul.DropDownMenu,
| |
- | div.MenuBar ul li a:hover ul.DropDownMenu {
| |
- | background-color: ButtonShadow; /* Sets the drop-down menu "effective border" color. */
| |
- | }
| |
- | div.MenuBar ul li:hover ul.DropDownMenu li a,
| |
- | div.MenuBar ul li a:hover ul.DropDownMenu li a {
| |
- | background-color: Menu; Drop-down menu unselected items.
| |
- | Sets the drop-down menu "effective background" color. */
| |
- | color: MenuText;
| |
- | }
| |
- | div.MenuBar ul li:hover ul.DropDownMenu li:hover a,
| |
- | div.MenuBar ul li a:hover ul.DropDownMenu li a:hover {
| |
- | background-color: Highlight; /* Drop-down menu selected item. */
| |
- | color: HighlightText;
| |
- | }
| |
- | /*...............................................................................................*/
| |
- | div.MenuBar ul li:hover ul.DropDownMenu li:hover ul.SideMenu,
| |
- | div.MenuBar ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu {
| |
- | background-color: ButtonShadow; /* Sets the side menu "effective border" color. */
| |
- | }
| |
- | div.MenuBar ul li:hover ul.DropDownMenu li:hover ul.SideMenu li a,
| |
- | div.MenuBar ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu li a {
| |
- | background-color: Menu; /* Side menu unselected items.
| |
- | Sets the side menu "effective background" color. */
| |
- | color: MenuText;
| |
- | }
| |
- | div.MenuBar ul li:hover ul.DropDownMenu li:hover ul.SideMenu li a:hover,
| |
- | div.MenuBar ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu li a:hover {
| |
- | background-color: Highlight; /* Side menu selected item. */
| |
- | color: HighlightText;
| |
- | }
| |
- | /*-----------------------------------------------------------------------------------------------*/
| |
- | /*Script-Free 3-Level Menu 1.2 Tailor
| |
- | www.CesarDaniel.info
| |
- | /*-------------------------------------------------------------------------------------- General */
| |
- | body {
| |
- | background: white;
| |
- | color: black;
| |
- | margin: 0;
| |
- | border: 0;
| |
- | padding: 0;
| |
- | }
| |
- |
| |
- |
| |
- | div.MenuBar {
| |
- | font: 13px arial, helvetica, sans-serif;
| |
- | }
| |
- | div.MenuBar ul {
| |
- | font: 13px arial, helvetica, sans-serif; /* Required for IE55. */
| |
- | }
| |
- | /*--------------------------------------------------------------------------------------- Colors */
| |
- | div.MenuBar {
| |
- | background-color: black; /* Selected item. */
| |
- | color: #FFFFFF;
| |
- | border-bottom: 1px solid ButtonShadow;
| |
- | }
| |
- | div.MenuBar a,
| |
- | div.MenuBar ul li:hover ul.DropDownMenu li a,
| |
- | div.MenuBar ul li a:hover ul.DropDownMenu li a,
| |
- | div.MenuBar ul li:hover ul.DropDownMenu li:hover ul.SideMenu li a,
| |
- | div.MenuBar ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu li a {
| |
- | background-color: black; /* Selected item. */
| |
- | color: #FFFFFF;
| |
- | }
| |
- | div.MenuBar ul li:hover a,
| |
- | div.MenuBar ul li a:hover,
| |
- | div.MenuBar ul li:hover ul.DropDownMenu li:hover a,
| |
- | div.MenuBar ul li a:hover ul.DropDownMenu li a:hover,
| |
- | div.MenuBar ul li:hover ul.DropDownMenu li:hover ul.SideMenu li a:hover,
| |
- | div.MenuBar ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu li a:hover {
| |
- | background-color: #603371; /* Selected item. */
| |
- | color: #FFFFFF;
| |
- | }
| |
- | div.MenuBar ul li:hover ul.DropDownMenu,
| |
- | div.MenuBar ul li a:hover ul.DropDownMenu,
| |
- | div.MenuBar ul li:hover ul.DropDownMenu li:hover ul.SideMenu,
| |
- | div.MenuBar ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu {
| |
- | background-color: ButtonShadow; /* Sets the drop-down and side menus "effective border" color. */
| |
- | }
| |
- | /*--------------------------------------------------------------------------------------- Widths */
| |
- | /*
| |
- |
| |
- | /*
| |
- | Menu Bar 1
| |
- | Drop-Down Menu #2
| |
- | */
| |
- | div.MenuBar#navi ul li:hover ul.DropDownMenu#MB1-DDM4,
| |
- | div.MenuBar#navi ul li a:hover ul.DropDownMenu#MB1-DDM4,
| |
- | div.MenuBar#navi ul li:hover ul.DropDownMenu#MB1-DDM4 li a,
| |
- | div.MenuBar#navi ul li a:hover ul.DropDownMenu#MB1-DDM4 li a {
| |
- | width: 11em; /* Drop-down menu width. */
| |
- | }
| |
- | div.MenuBar#navi ul li:hover ul.DropDownMenu#MB1-DDM5,
| |
- | div.MenuBar#navi ul li a:hover ul.DropDownMenu#MB1-DDM5,
| |
- | div.MenuBar#navi ul li:hover ul.DropDownMenu#MB1-DDM5 li a,
| |
- | div.MenuBar#navi ul li a:hover ul.DropDownMenu#MB1-DDM5 li a {
| |
- | width: 12em; /* Drop-down menu width. */
| |
- | }
| |
- |
| |
- | /*...............................................................................................*/
| |
- | /*
| |
- | Menu Bar 1
| |
- | Drop-Down Menu #2
| |
- | Side Menu #1
| |
- | */
| |
- | div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM1,
| |
- | div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM1 {
| |
- | left: 15.5em !important; /* Places the side menu to the right of the drop-down menu.
| |
- | Keep it sync with the drop-down menu width. */
| |
- | }
| |
- | div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM1,
| |
- | div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM1,
| |
- | div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM1 li a,
| |
- | div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM1 li a {
| |
- | width: 10em; /* Side menu width. */
| |
- | }
| |
- | /*...............................................................................................*/
| |
- | /*
| |
- | Menu Bar 1
| |
- | Drop-Down Menu #2
| |
- | Side Menu #2
| |
- | */
| |
- | div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM2,
| |
- | div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM2 {
| |
- | left: 15.5em !important; /* Places the side menu to the right of the drop-down menu.
| |
- | Keep it sync with the drop-down menu width. */
| |
- | }
| |
- | div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM2,
| |
- | div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM2,
| |
- | div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM2 li a,
| |
- | div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM2 li a {
| |
- | width: 10em; /* Side menu width. */
| |
- | }
| |
- | /*...............................................................................................*/
| |
- | /*
| |
- | Menu Bar 1
| |
- | Drop-Down Menu #2
| |
- | Side Menu #3
| |
- | */
| |
- | div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM3,
| |
- | div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM3 {
| |
- | left: 15.5em !important; /* Places the side menu to the right of the drop-down menu.
| |
- | Keep it sync with the drop-down menu width. */
| |
- | }
| |
- | div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM3,
| |
- | div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM3,
| |
- | div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM3 li a,
| |
- | div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM3 li a {
| |
- | width: 10em; /* Side menu width. */
| |
- | }
| |
- | /*...............................................................................................*/
| |
- |
| |
- | </style>
| |
- |
| |
- |
| |
- | <body>
| |
- | <div id="header"><img src=" https://static.igem.org/mediawiki/2009/a/a6/UQ_banner.jpg" /></div>
| |
- | <div class='MenuBar' id="navi">
| |
- | <ul>
| |
- | <li>
| |
- | <a href="https://2011.igem.org/Team:UQ-Australia" style="color: white">Home
| |
- | <!--[if gt IE 6]><!--></a><!--<![endif]-->
| |
- | <!--[if lt IE 7]><table border="0" cellpadding="0" cellspacing="0"><tr><td><![endif]-->
| |
- | <!--[if lte IE 6]></td></tr></table></a><![endif]-->
| |
- | </li>
| |
- | <li>
| |
- | <a href="https://2011.igem.org/Team:UQ-Australia/Team" style="color: white">Team
| |
- | <!--[if gt IE 6]><!--></a><!--<![endif]-->
| |
- | <!--[if lt IE 7]><table border="0" cellpadding="0" cellspacing="0"><tr><td><![endif]-->
| |
- | <!--[if lte IE 6]></td></tr></table></a><![endif]-->
| |
- | </li>
| |
- | <li>
| |
- | <a href="https://2011.igem.org/Team:UQ-Australia/Project" style="color: white">Project
| |
- | <!--[if gt IE 6]><!--></a><!--<![endif]-->
| |
- | <!--[if lt IE 7]><table border="0" cellpadding="0" cellspacing="0"><tr><td><![endif]-->
| |
- | <!--[if lte IE 6]></td></tr></table></a><![endif]-->
| |
- |
| |
- | </li>
| |
- | <li>
| |
- |
| |
- | <a href="https://2011.igem.org/Team:UQ-Australia/Parts" style="color: white">Parts
| |
- | <!--[if gt IE 6]><!--></a><!--<![endif]-->
| |
- | <!--[if lt IE 7]><table border="0" cellpadding="0" cellspacing="0"><tr><td><![endif]-->
| |
- | <!--[if lte IE 6]></td></tr></table></a><![endif]-->
| |
- | </li>
| |
- | <li>
| |
- |
| |
- | <a href="https://2011.igem.org/Team:UQ-Australia/Data" style="color: white">Data
| |
- | <!--[if gt IE 6]><!--></a><!--<![endif]-->
| |
- | <!--[if lt IE 7]><table border="0" cellpadding="0" cellspacing="0"><tr><td><![endif]-->
| |
- | <!--[if lte IE 6]></td></tr></table></a><![endif]-->
| |
- | </li>
| |
- | <li>
| |
- | <a href="https://2011.igem.org/Team:UQ-Australia/Modeling" style="color:white">Modelling
| |
- | <!--[if gt IE 6]><!--></a><!--<![endif]-->
| |
- | <!--[if lt IE 7]><table border="0" cellpadding="0" cellspacing="0"><tr><td><![endif]-->
| |
- | <!--[if lte IE 6]></td></tr></table></a><![endif]-->
| |
- | </li>
| |
- | <li>
| |
- | <a href="https://2011.igem.org/Team:UQ-Australia/Notebook" style="color: white">Notebook
| |
- | <!--[if gt IE 6]><!--></a><!--<![endif]-->
| |
- | <!--[if lte IE 6]></td></tr></table></a><![endif]-->
| |
- |
| |
- |
| |
- | </li>
| |
- | <li>
| |
- | <a href="https://2011.igem.org/Team:UQ-Australia/Safety" style="color: white">Safety
| |
- | <!--[if gt IE 6]><!--></a><!--<![endif]-->
| |
- | <!--[if lt IE 7]><table border="0" cellpadding="0" cellspacing="0"><tr><td><![endif]-->
| |
- | <!--[if lte IE 6]></td></tr></table></a><![endif]-->
| |
- | </li>
| |
- | <li>
| |
- | <a href="https://2011.igem.org/Team:UQ-Australia/Human_Practices" style="color: white">Human Practices
| |
- | <!--[if gt IE 6]><!--></a><!--<![endif]-->
| |
- | <!--[if lt IE 7]><table border="0" cellpadding="0" cellspacing="0"><tr><td><![endif]-->
| |
- | <!--[if lte IE 6]></td></tr></table></a><![endif]-->
| |
- | </li>
| |
- |
| |
- | <li>
| |
- | <a href="https://2011.igem.org/Team:UQ-Australia/Attributions" style="color: white">Attributions</a>
| |
- | </li>
| |
- | </ul>
| |
- |
| |
- | </div>
| |
- | <div id="header_bottom"><img src="https://static.igem.org/mediawiki/2008/e/ef/Navi_bg.gif" alt="" / ></div>
| |
- | </body>
| |
- | </html>
| |
- |
| |
- | <!-- -----------------------------------------------------Text------------------------------------------------------ -->
| |
- |
| |
- |
| |
- |
| |
- |
| |
- |
| |
- | == <span style="color:#558822">Outreach</span> ==
| |
- |
| |
- | As part of the Human practices work, UQ-Australia has promoted synthetic biology and iGEM to others. Major outreach ventures had included a presentation and activity at [http://www.ausbiotech.org/content.asp?pageid=156 Biofutures]: a national biotechnology student forum and is intended to also include a presentation at a local high school and [http://physics.uq.edu.au/pain/ PAIN Physics Society].
| |
- | The presentations had varying aims to suit the varying audience.
| |
- |
| |
- | ==== <span style="color:#883622">Biofutures </span>====
| |
- |
| |
- | [http://www.ausbiotech.org/content.asp?pageid=156 Biofutures] is a biotechnology forum for Year 11 and 12 students from Australia and New Zealand. UQ-Australia ran a workshop on 3 July 2011. This workshop included a presentation and a group activity. There are [http://www.facebook.com/media/set/?set=a.239278726099649.74195.174356539258535&l=f672fa7c36&type=1 pictures] and notes from this.
| |
- | The aim of the contribution to Biofutures was to introduce iGEM as a possible option for them when they pursue their tertiary studies.
| |
| | | |
| + | {|style="width:100%;" border="0" cellpadding="10" cellspacing="0" |
| + | |- valign="top" |
| + | |width=125"|[[File:PAIN-UQ-Physics-Students-Society.png|125x125px|link=http://http://physics.uq.edu.au/pain]] |
| + | |[http://physics.uq.edu.au/pain/ PAIN Physics Society] is a student society for students with an interest in physics at the University of Queensland. Due to the interdisciplinary nature of synthetic biology and the generality of physics, a brief introduction to a new field of science seemed fitting. |
| + | The aim of hosting a PAIN event is to promote synthetic biology as an emerging research field and to promote interdisciplinary on both the biology and physics sides. |
| From this activity, students and mentors | | From this activity, students and mentors |
| + | * drew analogies between synthetic biology and cybernetics |
| * went through some of the thinking process followed by the iGEM students when formulating a project | | * went through some of the thinking process followed by the iGEM students when formulating a project |
| * gained an idea of what has been happening for synthetic biology/ iGEM | | * gained an idea of what has been happening for synthetic biology/ iGEM |
- | * were able to put synthetic biology into perspective | + | * were able to put synthetic biology into perspective with science and society |
| + | |- |
| + | |} |
| | | |
- | === <span style="color:#883622">Physics Society </span>===
| + | == <span style="color:#558822">Collaboration</span> == |
| | | |
- | [http://physics.uq.edu.au/pain/ PAIN Physics Society] PAIN Physics Society is a student society for students with an interest in physics at the University of Queensland. Due to the interdisciplinary nature of synthetic biology and the generality of physics, a brief introduction to a new field of science seemed fitting. | + | UQ-Australia iGEM Team has joined the [http://openwetware.org/wiki/IGEM_Outreach:Contact '''iGEM Collaboration Committee''']. This committee includes: |
- | The aim of hosting a PAIN event is to promote synthetic biology as an emerging research field and to promote interdisciplinary on both the biology and physics sides.
| + | * '''<span style="color:#D4A017">Madeline Grade</span>''' from [https://2011.igem.org/Team:Arizona_State '''Arizona State iGEM Team'''] |
| + | * '''<span style="color:#D4A017">Nisarg Patel</span>''' from [https://2011.igem.org/Team:Arizona_State '''Arizona State iGEM Team'''] |
| + | * '''<span style="color:#D4A017">Madeline Grade</span>''' from [https://2011.igem.org/Team:Arizona_State '''Arizona State iGEM Team'''] |
| + | * '''<span style="color:#D4A017">Nisarg Patel</span>''' from [https://2011.igem.org/Team:Arizona_State '''Arizona State iGEM Team'''] |
| + | * '''<span style="color:#D4A017">Jovian Yu</span>''' from [https://2011.igem.org/Team:Brown-Stanford '''Brown-Stanford iGEM Team'''] |
| + | * '''<span style="color:#D4A017">Max Song</span>''' from [https://2011.igem.org/Team:Brown-Stanford '''Brown-Stanford iGEM Team'''] |
| + | * '''<span style="color:#D4A017">Alyssa Henning</span>''' from [https://2011.igem.org/Team:Cornell '''Cornell iGEM Team'''] |
| + | * '''<span style="color:#D4A017">Ann Bui</span>''' from [https://2011.igem.org/Team:UQ-Australia '''UQ-Australia'''] |
| + | * '''<span style="color:#D4A017">Natasha Gomez</span>''' from [https://2011.igem.org/Team:Panama '''Panama iGEM Team'''] |
| + | * '''<span style="color:#D4A017">Grimaldo Elias</span>''' from [https://2011.igem.org/Team:UTP-Panama '''UTP Panama'''] |
| | | |
- | This event will be on a Friday evening in September.
| |
| | | |
- | == <span style="color:#558822">Patenting</span> ==
| |
| | | |
- | In a dynamic field such as synthetic biology, discovery moves at an astounding pace and is driven by the findings of groups from all around the world. However, conflict often arises when the choice between collaboration and commercialisation arises, and consequently patents have become commonplace in the scientific world. In the last 5 years, 34% of respondents had applied for or received a patent on their findings. Additionally, 68% stated that they had sent research tools to others in academia [1]. This is especially relevant in iGEM, a competition whose explicit aim is to remain open source and collaborative. We examine whether this is a realistic or achievable goal within the framework of patents in the scientific world.
| + | '''Together we have set up [http://openwetware.org/wiki/IGEM_Outreach:About CommunityBricks] and [https://igem.org/Alumni_Association AlumniGEM]!''' |
| | | |
| | | |
- | Within iGEM, the stipulation that all BioBricks must remain open source and redistributable means that patented material is inherently excluded from submission. This sort of restriction differs somewhat from the usual research experience, where 91% of scientists have not checked for patents on the material they used in the last 5 years [1]. However, iGEM falls in a unique `grey area’, which effectively prevents the use of any patented materials by participating teams with the requirement to submit their parts to the Registry to be redistributed. Although teams are using parts solely for research purposes, the nature of the registry and iGEM’s distribution kits means that by redistributing parts iGEM would be infringing on the patent holder. The UQ-Australia iGEM team has had to remodel their circuit design after encountering patents on key components.
| + | {|style="width:100%;" border="0" cellpadding="10" cellspacing="0" |
| + | |-valign="top" |
| + | |width="440"|[[File:Cbricks.png|130x130px|link=http://openwetware.org/wiki/IGEM_Outreach]] |
| + | This is to be a registry of Human Practices activities available to everyone. |
| + | These would include notes and reflections from human practices activities of all ranges. |
| | | |
| + | The aim was to improve upon a simple 5-minute survey as performed in the past as 'the' human practices work and extending this to a collection of many activities, possibly combined to create the perfect activity for every audience. |
| | | |
- | In the past, the issue of patenting has been less significant on iGEM with a recent survey indicating that less than twenty teams faced any legal issues regarding patenting and their parts [2]. This would likely be since the majority of teams worked in bacteria, where the parts have either never been patented, or any patents have since expired. However, as more explore synthetic biology in mammalian projects, patenting is going to become an unavoidable issue. Consequently, we propose two possible mechanisms for iGEM to handle patents on biological parts. | + | In future years of the competition, it is hoped that past activities would be cataloged here to create registry of standardised interchangeable activities...much reflecting the structure of iGEM. |
| | | |
| + | |width="12"| |
| + | |width="440"|[[File:Brown-Stanford_alumnigem.png|200x100px|link=https://igem.org/Alumni_Association]] |
| | | |
- | [1] Lei, Z, Juneja, R & Wright, BD, 2009, ‘Patents versus patenting: implications of intellectual property protection for biological research’, Nature Biotechnology, vol. 27, pp. 36-40.
| + | The aim of the AlumniGEM is to create a platform where past (and current!) iGEMers can |
| + | * re-connect with each other |
| + | * receive notifications about scholarships, internships and jobs |
| + | * receive invitations to reunions |
| | | |
- | [2] Mexico-UNAM-CINVESTAV, 2010, `Human Practices: Survey Results', accessed 4 August 2011 from https://2010.igem.org/Team:Mexico-UNAM-CINVESTAV/Home
| + | From the database of past iGEMers, this would also be a great for new iGEMers wanting to know the ins and outs of what it takes to be an iGEMer before joining. |
| + | This is reflected in the survey being conducted here with collaboration from the [https://2011.igem.org/Team:Cambridge '''Cambrigde iGEM Team''']. |
| + | |
| + | |
| + | Discussions with Meagan Lizarazo from iGEM HQ have led to the integration of AlumniGEM with iGEM to allow access to the platform for all participants. |
| + | |} |