Karthikdevan (Talk | contribs) |
|||
Line 9: | Line 9: | ||
<div class="row" style="grid-template-columns: 768px; background: #ffffff; justify-content: center;"> | <div class="row" style="grid-template-columns: 768px; background: #ffffff; justify-content: center;"> | ||
<div class="box mainbox" style="padding: 40px; color: #161b1f; background: white;"> | <div class="box mainbox" style="padding: 40px; color: #161b1f; background: white;"> | ||
− | < | + | <h1>An easy access platform with a database of various host organisms and a collection of tools to work with them.</h1> |
− | < | + | <h2>The blueprint of an organism</h2> |
To create the database of host organisms, we first started by defining a template/blueprint of the data that needs to be collected about each organism. Our proposed blueprint consists of the following: | To create the database of host organisms, we first started by defining a template/blueprint of the data that needs to be collected about each organism. Our proposed blueprint consists of the following: | ||
<ul> | <ul> | ||
Line 27: | Line 27: | ||
<li>Genome sequence</li> | <li>Genome sequence</li> | ||
</ul> | </ul> | ||
− | < | + | <h1>Building the database</h1> |
A database site design consists of two essential components: a backend that is responsible, storing data on the server and serve the data when requested, and a front-end that is responsible for creating a visual interface between the back-end and the user. | A database site design consists of two essential components: a backend that is responsible, storing data on the server and serve the data when requested, and a front-end that is responsible for creating a visual interface between the back-end and the user. | ||
<h2>Back-end</h2> | <h2>Back-end</h2> | ||
Line 33: | Line 33: | ||
<h2>Front-end</h2> | <h2>Front-end</h2> | ||
The front-end was done using HTML, CSS and JavaScript. | The front-end was done using HTML, CSS and JavaScript. | ||
− | < | + | <h1>User Experience Design</h1> |
<h2>Home page</h2> | <h2>Home page</h2> | ||
When the user hits on the home page, (s)he can either search for organisms, browse through the index or choose to contribute data for an organism that are not yet in the database. | When the user hits on the home page, (s)he can either search for organisms, browse through the index or choose to contribute data for an organism that are not yet in the database. | ||
Line 43: | Line 43: | ||
The details about each organism can be viewed on the view page. The page is designed for easy navigation to different sections of the entry. This page also contains a link to edit the entry | The details about each organism can be viewed on the view page. The page is designed for easy navigation to different sections of the entry. This page also contains a link to edit the entry | ||
− | < | + | <h1>Chassis tools</h1> |
We decided to make ChassiDex the one-stop solution for dealing with your host. Hence, we intended to integrate some chassis tools which can be used on the different chassis within the database. These are tools that are vital to molecular biology work on the chassis and such an assembly of tools at one place eases the process of working with them. | We decided to make ChassiDex the one-stop solution for dealing with your host. Hence, we intended to integrate some chassis tools which can be used on the different chassis within the database. These are tools that are vital to molecular biology work on the chassis and such an assembly of tools at one place eases the process of working with them. | ||
Line 49: | Line 49: | ||
We have designed and integrated a highly interactive tool for codon optimization. The optimized sequence can be manually edited to remove restriction sites or reduce GC content, using a drop-down menu that shows codons that can be used to replace the current codon without changing the amino acid. | We have designed and integrated a highly interactive tool for codon optimization. The optimized sequence can be manually edited to remove restriction sites or reduce GC content, using a drop-down menu that shows codons that can be used to replace the current codon without changing the amino acid. | ||
− | < | + | <h2>Future work</h2> |
We plan to similarly integrate more such chassis tools such as those for genome analysis and metabolic simulations. | We plan to similarly integrate more such chassis tools such as those for genome analysis and metabolic simulations. | ||
Revision as of 23:46, 27 October 2017
Design
An easy access platform with a database of various host organisms and a collection of tools to work with them.
The blueprint of an organism
To create the database of host organisms, we first started by defining a template/blueprint of the data that needs to be collected about each organism. Our proposed blueprint consists of the following:- Scientific name (genus, species and strain) and taxonomy
- Biosafety level
- A description of what makes the host special for synthetic biology applications
- Genotype
- Growth characteristics
- Culture sources for obtaining the organism
- Maintenance protocols
- Transformation protocols
- Other protocols
- Biobrick parts for this organism
- Vectors for the organism
- Metabolic models
- Genome sequence