|
|
Line 191: |
Line 191: |
| Do not put href attribute, it will be replaced with a link to the image. | | Do not put href attribute, it will be replaced with a link to the image. |
| Moreover, inner html of the anchor tag will be "figure x" where x is the | | Moreover, inner html of the anchor tag will be "figure x" where x is the |
- | correct figure number. | + | correct figure number. If span or anchor has "." as the inner html, the |
| + | caption will be capitalized. |
| */ | | */ |
| var images = $('img[ref]'); | | var images = $('img[ref]'); |
Line 213: |
Line 214: |
| } else { | | } else { |
| e2.innerHTML = "figure " + (index+1); | | e2.innerHTML = "figure " + (index+1); |
| + | } |
| + | }); |
| + | } |
| + | ); |
| + | |
| + | // Table reference script |
| + | /* |
| + | USAGE: |
| + | tag table with a tab that is connected to the table, such as: |
| + | <table ref="intensities" /> |
| + | When you insert a reference in text, put a tag with a ref attribute: |
| + | <a tab="intensities"></a> |
| + | Do not put href attribute, it will be replaced with a link to the image. |
| + | Moreover, inner html of the anchor tag will be "table x" where x is the |
| + | correct table number. If span or anchor has "." as the inner html, the |
| + | caption will be capitalized. |
| + | */ |
| + | var tables = $('table[tab]'); |
| + | $.each(tables, function(index, e){ |
| + | var tableName = e.getAttribute("tab"); |
| + | if (!e.id){ |
| + | e.setAttribute("id","figure"+(index+1)); |
| + | } |
| + | $.each($('a[tab="'+tableName+'"]'), function(j, e2){ |
| + | e2.setAttribute("href","#"+e.id); |
| + | if (e2.innerHTML == "."){ |
| + | e2.innerHTML = "Table " + (index+1); |
| + | } else { |
| + | e2.innerHTML = "table " + (index+1); |
| + | } |
| + | }); |
| + | $.each($('span[tab="'+tableName+'"]'), function(j, e2){ |
| + | e2.setAttribute("href","#"+e.id); |
| + | if (e2.innerHTML == "."){ |
| + | e2.innerHTML = "Table " + (index+1); |
| + | } else { |
| + | e2.innerHTML = "table " + (index+1); |
| } | | } |
| }); | | }); |
Cooperation
Contributing to the community is an important part of iGEM. It is also very cool to get to know other iGEM teams and help them with their projects!
Seekers
From the start, we planned to develop software tools to make the work of our team easier. We also want to share the tools with the iGEM Community to help everyone.
All the code is available as open source on GitHub and is free to be reused, modified or expanded. All of the projects can be found through our GitHub organization Quiet Sushi Force.
We made two different Seekers for making background research for iGEM projects a little easier. They are both written in JavaScript using the Angular.js library. The data in both is a massive JSON file that is easily modifiable and can be changed without doing any modifications to the code, so expanding the tools for the future only requires adding data.
Both use Yeoman for scaffolding and deployment and they are currently running on GitHub Pages, which is free and handles requests very fast, so they will stay available for the foreseeable future.
BioBrick Seeker
The major tools we made are the Seeker-brand tools. First we made BioBrick Seeker. to make searching for the needed BioBricks in the 2014 iGEM Distribution a bit easier. It can be used to find Bricks with a certain keyword or list all from a certain type. It even has a search for the part names to see if the Brick you need is in this year's distribution.
All of the code and installation instructions are available at the project's GitHub page.
Here's a screenshot of BioBrick Seeker and how it works if you want to search for a BioBrick that has the word 'fluorescent' in its description.
Team Seeker
The second seeker was Team Seeker, a tool to search through the project abstracts of past teams to see if something you've been thinking about has been done before and to find projects that work in a similar field to your own. It has a smart phrase search so writing anything in the search bar should bring up what you need.
All of the code and installation instructions are available at the project's GitHub page.
Here's a screenshot of Team Seeker.
Interlab Study
Interteam Cooperation
ETH Zürich
Complexity survey (more than 20 entries) and Low Budget iGEM Challenge
Colombia
Mathematical modeling Low Buget iGEM Challenge entry
Minttu, Oskari and Pietu skyping to Columbia.
Paris-Saclay
Skype call, receiving the advice, first contact to iGEM seniors, Bioart collaboration to Finland
Virginia
Survey participation, 20 entries
Amsterdam 2012
Meetings with a PhD student Tania from University of Helsinki, plenty of advice and feedback about our pitch etc.
Groningen 2012
Skype call, getting to know to the factors what makes an iGEM project successful one