"
Team:British Columbia/Human Practices/IP
From 2012.igem.org
(Difference between revisions)
| Line 17: | Line 17: | ||
We do not intend to make an argument for or against the idea of intellectual property. Our aim is to create a user-friendly platform for all iGEM teams to learn about relevant IP issues. It will present information in a manner that will allow users to make an informed decision about what stance to take when confronted with IP-related decisions. In addition, the guide will help teams navigate through the processes of obtaining or using patents and build a foundation upon which they can then proceed with their projects.</br></br> | We do not intend to make an argument for or against the idea of intellectual property. Our aim is to create a user-friendly platform for all iGEM teams to learn about relevant IP issues. It will present information in a manner that will allow users to make an informed decision about what stance to take when confronted with IP-related decisions. In addition, the guide will help teams navigate through the processes of obtaining or using patents and build a foundation upon which they can then proceed with their projects.</br></br> | ||
| - | <p align=center><font face=arial narrow size= | + | <p align=center><font face=arial narrow size=4><b>Our Survey</b></font></p><font face=arial narrow> |
Our survey methodology was relatively simple. We wanted to confirm our suspicions that other iGEM teams knew as little about "patents and stuff" as we did. We then came up with a set of questions for other teams, trying to evaluate their existing knowledge, their self-assessment of their knowledge, and their desire, if any, to increase that knowledge. Some of us wondered if we'd see evidence of a <a href="http://en.wikipedia.org/wiki/Dunning–Kruger_effect">Dunning–Kruger effect</a>.</br></br> | Our survey methodology was relatively simple. We wanted to confirm our suspicions that other iGEM teams knew as little about "patents and stuff" as we did. We then came up with a set of questions for other teams, trying to evaluate their existing knowledge, their self-assessment of their knowledge, and their desire, if any, to increase that knowledge. Some of us wondered if we'd see evidence of a <a href="http://en.wikipedia.org/wiki/Dunning–Kruger_effect">Dunning–Kruger effect</a>.</br></br> | ||
| Line 23: | Line 23: | ||
After implementing our survey using Google Drive, we sent it to team Calgary for testing. They <b>all</b> took it, and verified it worked. Thanks, Calgary! We then sent an email to <a href="https://igem.org/Team_List?year=2012">every team's primary contact</a>, asking them to take our survey and pass it along to their team. We had a great response, garnering 328 individual responses.</br></br> | After implementing our survey using Google Drive, we sent it to team Calgary for testing. They <b>all</b> took it, and verified it worked. Thanks, Calgary! We then sent an email to <a href="https://igem.org/Team_List?year=2012">every team's primary contact</a>, asking them to take our survey and pass it along to their team. We had a great response, garnering 328 individual responses.</br></br> | ||
| - | <font face=arial narrow size= | + | <p align=center><font face=arial narrow size=4><b>Best Respondents</b></font></p><font face=arial narrow> |
Big thanks to teams <a href="https://2012.igem.org/Team:Bielefeld-Germany">Bielefeld</a>, <a href="https://2012.igem.org/Team:Bonn">Bonn</a>, <a href="https://2012.igem.org/Team:Calgary">Calgary</a>, <a href="https://2012.igem.org/Team:UC_Davis">UC Davis</a>, and <a href="https://2012.igem.org/Team:Warsaw">Warsaw</a> for having more than 80% of their team members, advisors, and instructors answer our survey! They represent the best parts of the iGEM community, helping others create knowledge without asking for much in return.</br></br> | Big thanks to teams <a href="https://2012.igem.org/Team:Bielefeld-Germany">Bielefeld</a>, <a href="https://2012.igem.org/Team:Bonn">Bonn</a>, <a href="https://2012.igem.org/Team:Calgary">Calgary</a>, <a href="https://2012.igem.org/Team:UC_Davis">UC Davis</a>, and <a href="https://2012.igem.org/Team:Warsaw">Warsaw</a> for having more than 80% of their team members, advisors, and instructors answer our survey! They represent the best parts of the iGEM community, helping others create knowledge without asking for much in return.</br></br> | ||
| - | <p align=center><font face=arial narrow size= | + | <p align=center><font face=arial narrow size=4><b>Demographics</b></font></p><font face=arial narrow> |
<div id=graph1> | <div id=graph1> | ||
<img src="https://static.igem.org/mediawiki/2012/a/ae/UBCLocation.png"><img src="https://static.igem.org/mediawiki/2012/f/f4/UBCTeamRole.png"></br> | <img src="https://static.igem.org/mediawiki/2012/a/ae/UBCLocation.png"><img src="https://static.igem.org/mediawiki/2012/f/f4/UBCTeamRole.png"></br> | ||
| Line 33: | Line 33: | ||
<div id=break><p align=center> | <div id=break><p align=center> | ||
| - | <font face=arial narrow size= | + | <font face=arial narrow size=4><b>Experience With IP</b></font></p><font face=arial narrow></div> |
<div id=break><div id=graph><p align=center> | <div id=break><div id=graph><p align=center> | ||
<img src="https://static.igem.org/mediawiki/2012/0/0c/UBCExperience.png"></p></br> | <img src="https://static.igem.org/mediawiki/2012/0/0c/UBCExperience.png"></p></br> | ||
| Line 56: | Line 56: | ||
<div id=break><p align=center> | <div id=break><p align=center> | ||
| - | <font face=arial narrow size= | + | <font face=arial narrow size=4><b>Need a for Guide</b></font></p><font face=arial narrow> |
<img src="https://static.igem.org/mediawiki/2012/9/9f/UBCDepthGainWish.png"></br> | <img src="https://static.igem.org/mediawiki/2012/9/9f/UBCDepthGainWish.png"></br> | ||
| Line 75: | Line 75: | ||
<div id=break><p align=center> | <div id=break><p align=center> | ||
| - | <font face=arial narrow size= | + | <font face=arial narrow size=4><b>Patent Knowledge</b></font></p><font face=arial narrow></html> |
[[File:UBCPatentCost.png]] | [[File:UBCPatentCost.png]] | ||
| Line 86: | Line 86: | ||
<html><p align=center> | <html><p align=center> | ||
| - | <font face=arial narrow size= | + | <font face=arial narrow size=4><b>IP & Current Projects</b></font></p><font face=arial narrow></html> |
[[File:UBCApplyingForIP.png]] | [[File:UBCApplyingForIP.png]] | ||
| Line 100: | Line 100: | ||
<html><p align=center> | <html><p align=center> | ||
| - | <font face=arial narrow size= | + | <font face=arial narrow size=4><b>Opinions</b></font></p><font face=arial narrow></html> |
[[File:UBCPersonalInterest.png]] | [[File:UBCPersonalInterest.png]] | ||
Revision as of 16:10, 3 October 2012
Investigating Intellectual Property in iGEM
Working with novel concepts such as tunable consortia and distribution of the Dsz pathway, the UBC team became curious of whether iGEM projects would be owned as intellectual property (IP). We also realize that almost all research projects require the use of some sort of IP-related component. Even if iGEM teams are not planning to patent their own work, they will likely come across something (e.g., reagent, strain, etc.) that is already patented by someone else. To use these materials properly, we need to understand how to navigate around the legal aspect of patents. The purpose of this part of our Human Practices project is to convey IP knowledge to the community in an iGEM-relevant fashion. We surveyed various iGEM teams about their interest in such an IP primer and asked them about what they already knew, what the would like to know, and how they would like the information presented to them. In constructing our guide, we have met up with professions in the field of biotechnological patenting and incorporated the results of these meetings here. In this respect, our project will serve as a connection between iGEM and experts outside our community. We do not intend to make an argument for or against the idea of intellectual property. Our aim is to create a user-friendly platform for all iGEM teams to learn about relevant IP issues. It will present information in a manner that will allow users to make an informed decision about what stance to take when confronted with IP-related decisions. In addition, the guide will help teams navigate through the processes of obtaining or using patents and build a foundation upon which they can then proceed with their projects.Our Survey
Our survey methodology was relatively simple. We wanted to confirm our suspicions that other iGEM teams knew as little about "patents and stuff" as we did. We then came up with a set of questions for other teams, trying to evaluate their existing knowledge, their self-assessment of their knowledge, and their desire, if any, to increase that knowledge. Some of us wondered if we'd see evidence of a Dunning–Kruger effect. After implementing our survey using Google Drive, we sent it to team Calgary for testing. They all took it, and verified it worked. Thanks, Calgary! We then sent an email to every team's primary contact, asking them to take our survey and pass it along to their team. We had a great response, garnering 328 individual responses.Best Respondents
Big thanks to teams Bielefeld, Bonn, Calgary, UC Davis, and Warsaw for having more than 80% of their team members, advisors, and instructors answer our survey! They represent the best parts of the iGEM community, helping others create knowledge without asking for much in return.Demographics
These questions were relatively straightforward. We just wanted to know who was answering our survey! Happily, it looks like we got a reasonably representative sample of respondents.
Experience With IP
Unsurprisingly, the size of the "Yes" pie slice is almost the same size as the sum of "Advisors" and "Instructors" pie slices above, but let's look into that further.
While the bulk of respondents are still students with no patent experience, this breakdown reveals that approximately half of the participants are advisors and instructors.
Having a larger number of responses to this question than "Yes" answers to the previous one was perplexing. We expected those who indicated having no experience with patents to skip this question. A more sophisticated survey might have only revealed this question upon receiving a yes answer to the previous one.
This was a check-box poll, where respondents could select more than one box.
Need a for Guide
The above graph combines answers to three questions. Note that respondent's median self-assessed level of knowledge is 3, while the median desired level of knowledge is 8 and the median level thought to be obtainable from a brief guide is 6. Respondents thought that a brief guide can get them a good amount of the way to their goal, and this reinforced our motivations.
It is interesting to note how many respondents want to be patent lawyers.
This check-box poll confirmed our suspicions that a FAQ-style guide was the way to go. We likely lead the respondents to that conclusion somewhat. We didn't claim to be perfect social scientists.
Reinforcing that we aren't perfect social scientists, this question should have forced the respondent to make a choice. "Both" is an easy no-thought choice that damages the intent of the question. Regardless, we still learn that respondents are generally enthusiastic to learn about both sides of patents.
Patent Knowledge
IP & Current Projects
Opinions
