F1yingFish (Talk | contribs) |
|||
(12 intermediate revisions by 3 users not shown) | |||
Line 7,168: | Line 7,168: | ||
<span class="icon-bar"></span> | <span class="icon-bar"></span> | ||
</button> | </button> | ||
− | <a class="navbar-brand" href=" | + | <a class="navbar-brand" href="https://2016.igem.org/Team:Edinburgh_UG"> |
<img src="https://static.igem.org/mediawiki/2016/9/92/Edinburgh_logo2_MINI.png" alt=""> | <img src="https://static.igem.org/mediawiki/2016/9/92/Edinburgh_logo2_MINI.png" alt=""> | ||
</a> | </a> | ||
Line 7,189: | Line 7,189: | ||
<a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Human Practices<span class="caret"></span></a> | <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Human Practices<span class="caret"></span></a> | ||
<ul class="dropdown-menu" role="menu"> | <ul class="dropdown-menu" role="menu"> | ||
− | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Silver">Silver</a> </li> | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Overview">Overview</a> </li> |
− | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Gold">Gold</a> </li> | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/HP/Silver">Silver</a> </li> |
+ | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/HP/Gold">Gold</a> </li> | ||
+ | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Medal_Criteria">Medal Criteria</a> </li> | ||
<li><a href="https://2016.igem.org/Team:Edinburgh_UG/Integrated_Practices">Integrated Practices</a> </li> | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Integrated_Practices">Integrated Practices</a> </li> | ||
<li><a href="https://2016.igem.org/Team:Edinburgh_UG/Engagement">Engagement</a> </li> | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Engagement">Engagement</a> </li> | ||
+ | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Ethics">Ethics</a> </li> | ||
+ | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Mary_Queen_of _Scots">Mary Queen of Scots</a> </li> | ||
</ul> | </ul> | ||
</li> | </li> | ||
Line 7,203: | Line 7,207: | ||
<li><a href="https://2016.igem.org/Team:Edinburgh_UG/Demonstrate">Demonstrate</a></li> | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Demonstrate">Demonstrate</a></li> | ||
<li><a href="https://2016.igem.org/Team:Edinburgh_UG/Notebook">Notebook</a></li> | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Notebook">Notebook</a></li> | ||
− | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/ | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Protocols">Protocols</a></li> |
+ | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Limitations">Advantages and Limitations</a></li> | ||
</ul> | </ul> | ||
</li> | </li> | ||
Line 7,224: | Line 7,229: | ||
</li> | </li> | ||
<li> | <li> | ||
− | <a href=" | + | <a href="https://2016.igem.org/Team:Edinburgh_UG/Collaboration">Collaboration</a> |
</li> | </li> | ||
<li class="dropdown"> | <li class="dropdown"> | ||
<a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Awards<span class="caret"></span></a> | <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Awards<span class="caret"></span></a> | ||
<ul class="dropdown-menu" role="menu"> | <ul class="dropdown-menu" role="menu"> | ||
− | |||
<li><a href="https://2016.igem.org/Team:Edinburgh_UG/Software">Software</a> </li> | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Software">Software</a> </li> | ||
</ul> | </ul> | ||
Line 7,236: | Line 7,240: | ||
<a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Safety<span class="caret"></span></a> | <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Safety<span class="caret"></span></a> | ||
<ul class="dropdown-menu" role="menu"> | <ul class="dropdown-menu" role="menu"> | ||
− | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Safety | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Safety/Biological Safety">Biological Safety</a></li> |
− | + | ||
</ul> | </ul> | ||
</li> | </li> | ||
Line 7,275: | Line 7,278: | ||
<h2 class="featurette-heading">Introduction | <h2 class="featurette-heading">Introduction | ||
</h2> | </h2> | ||
− | <p class="lead">This summer our team, BabblED, designed and implemented a modular system for storing data in DNA. Through our modular design, we were able to incorporate error-correcting and safety mechanisms into our BabbleBricks | + | <p class="lead">This summer our team, BabblED, designed and implemented a modular system for storing data in DNA. Through our modular design, we were able to incorporate error-correcting and safety mechanisms into our BabbleBricks (information containing DNA fragments). Read below to find out more about the motivations behind our project and how we have optimised DNA as a storage medium. </p> |
Line 7,284: | Line 7,287: | ||
<!-- Second Featurette --> | <!-- Second Featurette --> | ||
<div class="featurette" id="services"> | <div class="featurette" id="services"> | ||
− | <img class="featurette-image img-circle img-responsive pull-left" src=" | + | <img class="featurette-image img-circle img-responsive pull-left" src="https://static.igem.org/mediawiki/2016/d/d5/Datacenter.jpg"> |
<h2 class="featurette-heading">The Age of Big Data | <h2 class="featurette-heading">The Age of Big Data | ||
</h2> | </h2> | ||
Line 7,294: | Line 7,297: | ||
<!-- Third Featurette --> | <!-- Third Featurette --> | ||
<div class="featurette" id="contact"> | <div class="featurette" id="contact"> | ||
− | <img class="featurette-image img-circle img-responsive pull-right" src=" | + | <img class="featurette-image img-circle img-responsive pull-right" src="https://static.igem.org/mediawiki/2016/8/80/Rsz_datalaw.jpg"> |
<h2 class="featurette-heading">Data Law | <h2 class="featurette-heading">Data Law | ||
</h2> | </h2> | ||
Line 7,304: | Line 7,307: | ||
<div class="featurette" id="contact"> | <div class="featurette" id="contact"> | ||
− | <img class="featurette-image img-circle img-responsive pull-right" src=" | + | <img class="featurette-image img-circle img-responsive pull-right" src="https://static.igem.org/mediawiki/2016/2/28/Rsz_tape.jpg"> |
<h2 class="featurette-heading">Archival Data Crisis | <h2 class="featurette-heading">Archival Data Crisis | ||
</h2> | </h2> | ||
<p class="lead">In addition to the data that is legally required to be retained, fundamental social institutions such as universities and libraries will archive data, whether it be ancient manuscripts or academic journals, for hundreds of years. </p> | <p class="lead">In addition to the data that is legally required to be retained, fundamental social institutions such as universities and libraries will archive data, whether it be ancient manuscripts or academic journals, for hundreds of years. </p> | ||
− | <img class="img-responsive center" src=" | + | <br> |
+ | |||
+ | <img class="img-responsive center" src="https://static.igem.org/mediawiki/2016/7/72/Casete2.jpg"> | ||
<p class="lead">Archival data that is accessed infrequently and must be kept in a stable form for long periods of time is often stored on magnetic tape. </p> | <p class="lead">Archival data that is accessed infrequently and must be kept in a stable form for long periods of time is often stored on magnetic tape. </p> | ||
<p class="lead">Through our conversations with data librarians, specialists and computing experts, we came to realise that there is an issue with storing archival data on tape. Our conversations with the National Library of Scotland shed some light on this. Magnetic tape has a life span of 6 years; though this is longer than the 2-year life span of hard drives, it poses a massive cost to archivists; every six years have to read and rewrite this data onto new tapes. This year it will take them 10 days to transfer 100TB of data, and it will cost them £230 in power costs, £310 to pay staff and £916 for the new tapes. In 2022, they will need to transfer 937TB of data; this will take them 71 days and cost £5,344 in total. Obviously, this process is unfeasible in the long term. </p> | <p class="lead">Through our conversations with data librarians, specialists and computing experts, we came to realise that there is an issue with storing archival data on tape. Our conversations with the National Library of Scotland shed some light on this. Magnetic tape has a life span of 6 years; though this is longer than the 2-year life span of hard drives, it poses a massive cost to archivists; every six years have to read and rewrite this data onto new tapes. This year it will take them 10 days to transfer 100TB of data, and it will cost them £230 in power costs, £310 to pay staff and £916 for the new tapes. In 2022, they will need to transfer 937TB of data; this will take them 71 days and cost £5,344 in total. Obviously, this process is unfeasible in the long term. </p> | ||
Line 7,320: | Line 7,325: | ||
<div class="featurette" id="contact"> | <div class="featurette" id="contact"> | ||
− | <img class="featurette-image img-circle img-responsive pull-right" src=" | + | <img class="featurette-image img-circle img-responsive pull-right" src="https://static.igem.org/mediawiki/2016/f/f4/Dna2.jpg"> |
<h2 class="featurette-heading">DNA Data Storage | <h2 class="featurette-heading">DNA Data Storage | ||
</h2> | </h2> | ||
− | <p class="lead">DNA is nature’s form of information storage. Though not the first to think of | + | <p class="lead">DNA is nature’s form of information storage. Though not the first to think of it our team believes that DNA is the ideal long term storage medium both in nature but also for human generated data. DNA is denser, longer lasting and more sustainable than any other storage medium. </p> |
− | + | ||
<p class="lead">This summer, we decided to address the set backs faced by previous DNA storage projects. Firstly, we designed our system to be modular; information stored by our system is encoded in 50bp DNA fragments termed BabbleBricks. Our Bricks are assembled into larger constructs to densely store any type of data. Our BabbleBricks have allowed our system to be more accessible and more secure. For example, our assembly method is up to 3 times cheaper than de novo DNA synthesis. The BabbleBricks also allowed the incorporation of various error-correcting mechanisms that ensure your data can be accessed and read after long term storage. </p> | <p class="lead">This summer, we decided to address the set backs faced by previous DNA storage projects. Firstly, we designed our system to be modular; information stored by our system is encoded in 50bp DNA fragments termed BabbleBricks. Our Bricks are assembled into larger constructs to densely store any type of data. Our BabbleBricks have allowed our system to be more accessible and more secure. For example, our assembly method is up to 3 times cheaper than de novo DNA synthesis. The BabbleBricks also allowed the incorporation of various error-correcting mechanisms that ensure your data can be accessed and read after long term storage. </p> | ||
− | < | + | <br> |
+ | |||
Line 7,339: | Line 7,345: | ||
</h2> | </h2> | ||
<p class= "lead">1. https://www-01.ibm.com/software/data/bigdata/what-is-big-data.html </p> | <p class= "lead">1. https://www-01.ibm.com/software/data/bigdata/what-is-big-data.html </p> | ||
+ | <p class="lead"> 2. http://www.computerworld.com/article/2493701/data-center/by-2020--there-will-be-5-200-gb-of-data-for-every-person-on-earth.html </p> | ||
+ | <p class="lead"> 3. https://www.eradar.eu/data-retention-periods/ </p> | ||
+ | <p class="lead"> 4. https://www.gov.uk/government/collections/data-retention-and-investigatory-powers-act-2014</p> | ||
+ | <p class="lead"> 5. http://science.sciencemag.org/content/337/6102/1628.full </p> | ||
+ | <p class="lead"> 6. http://www.nature.com/news/how-dna-could-store-all-the-world-s-data-1.20496 </p> | ||
+ | <p class="lead"> 7. https://homes.cs.washington.edu/~luisceze/publications/dnastorage-asplos16.pdf </p> | ||
− | |||
+ | </div> | ||
− | |||
− | |||
<!-- Footer --> | <!-- Footer --> |
Latest revision as of 23:57, 19 October 2016
Project Description
Introduction
This summer our team, BabblED, designed and implemented a modular system for storing data in DNA. Through our modular design, we were able to incorporate error-correcting and safety mechanisms into our BabbleBricks (information containing DNA fragments). Read below to find out more about the motivations behind our project and how we have optimised DNA as a storage medium.
The Age of Big Data
Every day, we generate more than 2.5 billion gigabytes of new data1. At this rate, by 2020 the amount of digital data we have produced will exceed 40 zettabytes… this is estimated to be fifty-seven times the number of grains of sand on all beaches on Earth2. This data is generated and collected from everywhere: tweets, Facebook messages, Google maps searches, transaction records and pictures.
Much of this digitally generated data is stored instantly on the flash memory devices found in our phones or on our laptops, but much of it, as required by law, must be archived for a longer period of time.
Data Law
Parliamentary law in the United Kingdom requires companies to retain generated data for anywhere from 12 months to 50 years3. For example, the Data Retention and Investigatory Powers Act of 2014, states that any commercial company that provides communication services, such as telephone or internet companies, must retain all customer data for 12 months. This is so that the data can be accessed by law enforcement should it be needed to investigate a crime4. Other laws such as The Ionising Radiations Regulations 1999 or The Control of Substances Hazardous to Health Regulations 2002, necessitate data related to medical or hazardous substances be retained for 40-50 years.
In most cases, this data will likely be generated on a computer or a digital system. However, long-term storage of this data is unlikely to be on a computer or flash memory medium.
Archival Data Crisis
In addition to the data that is legally required to be retained, fundamental social institutions such as universities and libraries will archive data, whether it be ancient manuscripts or academic journals, for hundreds of years.
Archival data that is accessed infrequently and must be kept in a stable form for long periods of time is often stored on magnetic tape.
Through our conversations with data librarians, specialists and computing experts, we came to realise that there is an issue with storing archival data on tape. Our conversations with the National Library of Scotland shed some light on this. Magnetic tape has a life span of 6 years; though this is longer than the 2-year life span of hard drives, it poses a massive cost to archivists; every six years have to read and rewrite this data onto new tapes. This year it will take them 10 days to transfer 100TB of data, and it will cost them £230 in power costs, £310 to pay staff and £916 for the new tapes. In 2022, they will need to transfer 937TB of data; this will take them 71 days and cost £5,344 in total. Obviously, this process is unfeasible in the long term.
The National Library of Scotland stores data that dates back to the 9th century- imagine if these precious pieces of human history. If we lost our capacity to archive ancient texts, not to mention data from new discoveries, how would be retain human knowledge?
DNA Data Storage
DNA is nature’s form of information storage. Though not the first to think of it our team believes that DNA is the ideal long term storage medium both in nature but also for human generated data. DNA is denser, longer lasting and more sustainable than any other storage medium.
This summer, we decided to address the set backs faced by previous DNA storage projects. Firstly, we designed our system to be modular; information stored by our system is encoded in 50bp DNA fragments termed BabbleBricks. Our Bricks are assembled into larger constructs to densely store any type of data. Our BabbleBricks have allowed our system to be more accessible and more secure. For example, our assembly method is up to 3 times cheaper than de novo DNA synthesis. The BabbleBricks also allowed the incorporation of various error-correcting mechanisms that ensure your data can be accessed and read after long term storage.
References
1. https://www-01.ibm.com/software/data/bigdata/what-is-big-data.html
2. http://www.computerworld.com/article/2493701/data-center/by-2020--there-will-be-5-200-gb-of-data-for-every-person-on-earth.html
3. https://www.eradar.eu/data-retention-periods/
4. https://www.gov.uk/government/collections/data-retention-and-investigatory-powers-act-2014
5. http://science.sciencemag.org/content/337/6102/1628.full
6. http://www.nature.com/news/how-dna-could-store-all-the-world-s-data-1.20496
7. https://homes.cs.washington.edu/~luisceze/publications/dnastorage-asplos16.pdf