Team:British Columbia/Human Practices/IP

From 2012.igem.org

(Difference between revisions)
(Created page with "{{Template:Team:British_Columbia_Header}}")
Line 1: Line 1:
{{Template:Team:British_Columbia_Header}}
{{Template:Team:British_Columbia_Header}}
 +
 +
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 out 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.
 +
 +
To accomplish this, we have decided to make a Frequently Asked Questions (FAQ) page, patent application flow chart, and a decision tree.
 +
 +
Insert 3 icons for each of the three components: FAQ, Flow Chart, Decision Tree

Revision as of 19:55, 26 September 2012

British Columbia - 2012.igem.org

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 out 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.

To accomplish this, we have decided to make a Frequently Asked Questions (FAQ) page, patent application flow chart, and a decision tree.

Insert 3 icons for each of the three components: FAQ, Flow Chart, Decision Tree