|
|
(59 intermediate revisions not shown) |
Line 16: |
Line 16: |
| <h1>Cooperation</h1> | | <h1>Cooperation</h1> |
| <p class="bigsplashtext"> | | <p class="bigsplashtext"> |
- | 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! | + | How we helped the iGEM community and how others helped us. |
| </p> | | </p> |
| </div> | | </div> |
Line 33: |
Line 33: |
| | | |
| <div class="splashalavalikko"> | | <div class="splashalavalikko"> |
- | <a href="#Seekers">Seeker tools</a><br> | + | <a href="#Seekers">Seeker Tools</a><br> |
| <a href="#Interlab">Interlab Study</a><br> | | <a href="#Interlab">Interlab Study</a><br> |
| <a href="#Interteam">Interteam Cooperation</a><br> | | <a href="#Interteam">Interteam Cooperation</a><br> |
Line 50: |
Line 50: |
| <div class="navbar navbar-default extrabar" data-spy="affix"> | | <div class="navbar navbar-default extrabar" data-spy="affix"> |
| <nav> | | <nav> |
- | <a id="Seekers-submenu" class="active" href="#Seekers">Seeker tools</a> | + | <a id="Seekers-submenu" class="active" href="#Seekers">Seeker Tools</a> |
| <a id="Interlab-submenu" href="#Interlab">Interlab Study</a> | | <a id="Interlab-submenu" href="#Interlab">Interlab Study</a> |
| <a id="Interteam-submenu" href="#Interteam">Interteam Cooperation</a> | | <a id="Interteam-submenu" href="#Interteam">Interteam Cooperation</a> |
Line 59: |
Line 59: |
| <div class="link" id="Seekers"></div> | | <div class="link" id="Seekers"></div> |
| | | |
- | <h2>Seekers</h2> | + | <h2>Seeker Tools</h2> |
- | | + | <div class="row"> |
- | <p>
| + | |
- | 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.
| + | |
- | </p>
| + | |
- | | + | |
- | <p>
| + | |
- | 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 <a href="http://github.com/iGEM-QSF">Quiet Sushi Force.</a>
| + | |
- | </p>
| + | |
- | | + | |
- | <p>
| + | |
- | 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.
| + | |
- | </p>
| + | |
- | | + | |
- | <p>
| + | |
- | 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.
| + | |
- | </p>
| + | |
- | | + | |
- | <div class="row margintop"> | + | |
| <div class="col-md-6 text-col-left"> | | <div class="col-md-6 text-col-left"> |
- | <h3>BioBrick Seeker</h3>
| |
| <p> | | <p> |
- | The major tools we made are the Seeker-brand tools. First we made <a href="http://igem-qsf.github.io/BioBrick-Seeker/dist/">BioBrick Seeker.</a> 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. | + | Right from the start, we decided that we were going to develop software tools to make the work of our team easier. We also wanted to share the tools with the iGEM Community to help everyone else, too! |
| + | </p> |
| + | <p> |
| + | We made two different Seeker brand tools (BioBrick Seeker and Team Seeker) for making the research part of iGEM projects a little easier. Both have tens of thousands of lines of data to search through, but the results update in real-time. Both get their content from JSON files that can be easily added to and which are completely separate from the code, so expanding the tools for the future can be done by just adding new data! |
| + | </p> |
| + | <p> |
| + | Both of the Seekers were written in JavaScript using the <a href="http://angularjs.org/">Angular.js</a> library. They use Yeoman for scaffolding and deployment, and they are currently running on GitHub Pages. GitHub Pages is a free service that handles requests very quickly, so the Seekers will stay available for the foreseeable future. |
| + | </p> |
| + | <p> |
| + | All of the code is available as open source on GitHub and is free to be reused, modified and expanded. All of our programming projects can be found through our GitHub organization <a href="http://github.com/iGEM-QSF">Quiet Sushi Force</a>. |
| + | </p> |
| + | </div> |
| + | <div class="col-md-6"> |
| + | <blockquote> |
| + | Awesome work! Very nice tool for fast search through the list of parts, very much appreciated. |
| + | <cite>Liu iGEM 2014</cite> |
| + | </blockquote> |
| + | <img src="https://static.igem.org/mediawiki/2014/3/32/Aalto_Helsinki_Seekers_Hand.png" class="img-responsive smallerimg center-block"></img> |
| + | </div> |
| + | </div> |
| + | <h3>BioBrick Seeker</h3> |
| + | <div class="row"> |
| + | <div class="col-md-6 text-col-left"> |
| + | <p> |
| + | <a href="http://igem-qsf.github.io/BioBrick-Seeker/dist/">BioBrick Seeker</a> was created 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. |
| + | </p> |
| + | <p> |
| + | All of the code and installation instructions for future development are available on <a href="http://github.com/iGEM-QSF/BioBrick-Seeker">the BioBrick Seeker GitHub page</a>. |
| </p> | | </p> |
| + | <h4> BioBrick Seeker Reception </h4> |
| <p> | | <p> |
- | All of the code and installation instructions are available at the project's <a href="http://github.com/iGEM-QSF/BioBrick-Seeker">GitHub page.</a> | + | The tool was received very well and got a lot of mentions on Twitter and got even featured on the iGEM 2014 Help page. We put Google Analytics on the site to get a rough idea of where in the world the tool was actually used. It turned out that it has been used on five different continents by many many teams all around the world! |
| </p> | | </p> |
| + | <img src="https://static.igem.org/mediawiki/2014/9/93/AaltoHelsinki_seekertweet.png" class="img-responsive margintop"> |
| + | <img src="https://static.igem.org/mediawiki/2014/d/d8/Aalto_Helsinki_Seeker_Twitter.png" class="img-responsive margintop"> |
| </div> | | </div> |
| <div class="col-md-6 img-100"> | | <div class="col-md-6 img-100"> |
| <img src="https://static.igem.org/mediawiki/2014/9/94/Aalto_Helsinki_Biobrickseeker.png" class="img-responsive"></img> | | <img src="https://static.igem.org/mediawiki/2014/9/94/Aalto_Helsinki_Biobrickseeker.png" class="img-responsive"></img> |
| <p class="kuvateksti"> | | <p class="kuvateksti"> |
- | 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. | + | BioBrick Seeker in action, searching for BioBricks that have the word 'fluorescent' in their description. |
| + | </p> |
| + | <img src="https://static.igem.org/mediawiki/2014/b/b3/Aalto_Helsinki_BBSeeker_sessions.png" class="img-responsive"></img> |
| + | <p class="kuvateksti"> |
| + | BioBrick Seeker has been used all around the world, on five continents! From this map you can see the of the amount of sessions from different countries: the darker blue, the more sessions there has been from the country. Picture taken on October 12th 2014. |
| </p> | | </p> |
| </div> | | </div> |
| </div> | | </div> |
| | | |
- | <div class="row margintop"> | + | <h3>Team Seeker</h3> |
| + | <div class="row"> |
| <div class="col-md-6 text-col-left"> | | <div class="col-md-6 text-col-left"> |
- | <h3>Team Seeker</h3>
| |
| <p> | | <p> |
- | The second seeker was <a href="http://igem-qsf.github.io/iGEM-Team-Seeker/dist/">Team Seeker</a>, 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. | + | <a href="http://igem-qsf.github.io/iGEM-Team-Seeker/dist/">Team Seeker</a> is a tool that you can use to search through the project abstracts of past teams. With this tool you don't need to use hours of research time to make sure that your idea hasn't been done yet in iGEM but you can just type in what you wish to find! With Team Seeker it's also easy to find all the projects that are close to your interests and this way the background research becomes a lot easier. Team Seeker has a smart phrase search; writing relevant phrases or words in the search bar brings up projects relating to them. |
| </p> | | </p> |
- |
| |
| <p> | | <p> |
- | All of the code and installation instructions are available at the project's <a href="http://github.com/iGEM-QSF/iGEM-Team-Seeker">GitHub page.</a> | + | All of the code and installation instructions for future development are available at the project's <a href="http://github.com/iGEM-QSF/iGEM-Team-Seeker">GitHub page.</a> |
| </p> | | </p> |
| </div> | | </div> |
Line 109: |
Line 124: |
| <img src="https://static.igem.org/mediawiki/2014/a/a1/Aalto_Helsinki_Teamseeker.png" class="img-responsive"> | | <img src="https://static.igem.org/mediawiki/2014/a/a1/Aalto_Helsinki_Teamseeker.png" class="img-responsive"> |
| <p class="kuvateksti"> | | <p class="kuvateksti"> |
- | Here's a screenshot of Team Seeker. | + | Looking for bioplastic worms with Team Seeker. |
| </p> | | </p> |
| </div> | | </div> |
Line 123: |
Line 138: |
| | | |
| <h2>Interlab Study</h2> | | <h2>Interlab Study</h2> |
| + | <p>We participated in the Measurement Interlab Study arranged by iGEM. Here are our results. |
| + | </p> |
| + | <h3>Devices We Used</h3> |
| + | <ol> |
| + | <li>BBa_I20260 in pSB3K3 (sequencing data in a <a href="https://static.igem.org/mediawiki/2014/9/91/AaltoHelsinki_interlabs39.png">picture</a> or <a href="https://static.igem.org/mediawiki/2014/3/3e/AaltoHelsinki_interlabs39.pdf">text</a> format)</li> |
| + | <li>BBa_K823005 + BBa_E0240 in pSB1C3 (B0032-E0040-B0015) in pSB1C3 (sequencing data in a <a href="https://static.igem.org/mediawiki/2014/8/8a/AaltoHelsinki_interlabs41.png">picture</a> or <a href="https://static.igem.org/mediawiki/2014/6/61/AaltoHelsinki_interlabs41.pdf">text</a> format)</li> |
| + | <li>BBa_K823012 + BBa_E0240 (B0032-E0040-B0015) in pSB1C3 (sequencing data in a <a href="https://static.igem.org/mediawiki/2014/8/8b/AaltoHelsinki_interlabs42.png">picture</a> or <a href="https://static.igem.org/mediawiki/2014/c/cb/AaltoHelsinki_interlabs42.pdf">text</a> format)</li> |
| + | </ol> |
| + | <h3>Protocols</h3> |
| + | <h4 class="nopaddingtop">Building the Devices</h4> |
| + | <p> |
| + | We built the test devices with the same ligation protocol that we have used for all our ligations. The protocol can be found <a href="https://static.igem.org/mediawiki/2014/0/02/Aalto_Helsinki_Protocols.pdf">here (click)</a>. |
| + | </p> |
| + | <h4>Testing Protocol</h4> |
| + | <p> |
| + | The samples were grown in LB broth, in <em>E. coli</em> Top10 and they were incubated in 37 C° (shaker 220 rpm) for 17 hours. Before measuring the GFP levels, the samples were diluted to achieve the same OD<sub>600</sub> and 100 ul of each sample was pipetted onto a 96-well black microtiter plate. We had three samples of all three devices. |
| + | </p> |
| + | <p> |
| + | The microtiter plate was inserted in a Thermo Scientific Varioskan and the following parameters were set: |
| + | </p> |
| + | <ul> |
| + | <li>Excitation wavelength: 470 nm</li> |
| + | <li>Emission wavelength: 511 nm</li> |
| + | <li>Bandwidth: 5nm</li> |
| + | <li>Measurement time: 500 ms</li> |
| + | </ul> |
| + | <p> |
| + | We used BBa_K592009 (in pSB1C3, grown in Top10) in LB, and LB only as negative controls. We didn’t have a positive control for these measurements. |
| + | </p> |
| + | <h3>Results</h3> |
| + | <p> |
| + | All measurement data (<a ref="results"></a>) is in Relative Fluorescence Units (RFU). |
| + | </p> |
| + | <div class="row"> |
| + | <div class="img-center"> |
| + | <img src="https://static.igem.org/mediawiki/2014/a/ae/AaltoHelsinki_Interlabs.png" ref="results" class="img-responsive"></img> |
| + | <p class="kuvateksti"> |
| + | <b><span ref="results">.</span></b> Measurement data. |
| + | </p> |
| + | </div> |
| + | </div> |
| | | |
| </article> | | </article> |
Line 134: |
Line 190: |
| <h2>Interteam Cooperation</h2> | | <h2>Interteam Cooperation</h2> |
| <h3>ETH Zürich</h3> | | <h3>ETH Zürich</h3> |
- | <p>Complexity survey (more than 20 entries) and Low Budget iGEM Challenge</p> | + | <h4 class="nopaddingtop">Low Budget iGEM Challenge</h4> |
| + | <p> |
| + | We did some extraordinary intercountry collaboration with <a href="https://2014.igem.org/Team:ETH_Zurich">ETH Zürich team</a>. Together we participated in the Low Budget iGEM Challenge arranged by Colombia's iGEM team. With ETH Zürich we planned, carried out and reported our experiments regarding an accessible, easy and low cost PCR method. You can find our entry from <a href="https://static.igem.org/mediawiki/2014/9/9f/Aaltohelsinki_low_budget_challenge.pdf">here</a>. Furthermore, we made a video describing our method in more detail. You can find the video featuring Oskari from Aalto-Helsinki and Sumana from ETH Zürich below: |
| + | </p> |
| <div class="row"> | | <div class="row"> |
| <div class="img-center"> | | <div class="img-center"> |
- | <a href="http://www.youtube.com/embed/icPgP3OOVOQ?rel=0"><img src="https://static.igem.org/mediawiki/2014/1/18/Aalto_Helsinki_Collab_Video.png" class="responsive-img"></a> | + | <a href="http://www.youtube.com/embed/icPgP3OOVOQ?rel=0" target="_blank"><img src="https://static.igem.org/mediawiki/2014/1/18/Aalto_Helsinki_Collab_Video.png" class="img-responsive"></a> |
| <p class="kuvateksti"> | | <p class="kuvateksti"> |
- | We participated in the Low Budget iGEM Challenge together! <a href="http://www.youtube.com/embed/icPgP3OOVOQ?rel=0">Click to watch the video</a>. | + | We participated in the Low Budget iGEM Challenge together with ETH Zürich! <a href="http://www.youtube.com/embed/icPgP3OOVOQ?rel=0">Click to watch the video</a>. |
| </p> | | </p> |
| + | </div> |
| + | </div> |
| + | |
| + | <div class="row"> |
| + | <div class="col-md-8 text-col-left"> |
| + | <h4>Complexity Survey</h4> |
| + | <p> |
| + | ETH Zürich team investigated the emergence of complex patterns. We helped their human practice part by filling out their survey about how we perceive complexity in everyday life as in biology and its emergence and how we react to it. We shared the survey for our friends and collected responses on our Facebook page. As a result, we reached over 20 entries and received this awesome badge as a reward! |
| + | </p> |
| + | </div> |
| + | <div class="col-md-4"> |
| + | <div class="center-block"></html>{{:Team:ETH_Zurich/human/survey/badge|width=300px}}<html></div> |
| + | <p class="kuvateksti">Here's the badge we earned for getting more than 20 entries for ETH-Zürich's complexity survey!</p> |
| </div> | | </div> |
| </div> | | </div> |
| | | |
| <h3>Colombia</h3> | | <h3>Colombia</h3> |
- | <p>Mathematical modeling Low Buget iGEM Challenge entry</p> | + | <div class="row"> |
| + | <div class="col-md-8 text-col-left"> |
| + | <p> |
| + | We Skyped with Daniela from Colombia iGEM team and agreed on participating their human practices project, the Low Budget iGEM Challenge. We also discussed about her previous experiences and how they have done mathematical modeling in the previous years. This way, we could validate whether our approach to modeling was on the right track. It was very interesting to discuss about the differences in research and how it affects iGEM in Colombia. For example, ordering primers, kits or other materials takes a lot longer and it really limits the way of working there. |
| + | </p> |
| + | </div> |
| + | <div class="col-md-4 img-100"> |
| + | <img src="https://static.igem.org/mediawiki/2014/6/68/Aalto_Helsinki_Skype_Colombia.jpg" class="img-responsive"></img> |
| + | <p class="kuvateksti"> |
| + | Minttu, Oskari and Pietu skyping to Columbia. |
| + | </p> |
| + | </div> |
| + | </div> |
| | | |
| <h3>Paris-Saclay</h3> | | <h3>Paris-Saclay</h3> |
- | <p>Skype call, receiving the advice, first contact to iGEM seniors, Bioart collaboration to Finland</p> | + | <div class="row"> |
| + | <div class="col-md-8 text-col-left"> |
| + | <p> |
| + | Paris-Saclay was the first iGEM team we got to talk to. It was great to hear of people doing the same kind of thing, though it was also kind of intimidating with such a big group and many advisors. It seemed like we'd need more knowledge to pull this off. Being a Finnish team, we appropriately Skyped from a sauna-themed meeting room! We did wear clothes, though. |
| + | </p> |
| + | <p> |
| + | We got a lot of good tips about where to start, what to focus on and what to expect at Jamboree. They were doing bio art, so we contacted Aalto University's Biofilia (a biological art unit under the Aalto ARTS) for them. Biofilia were very interested in talking with the Paris-Saclay team about their "Ceci n'est pas un citron" project. |
| + | </p> |
| + | </div> |
| + | <div class="col-md-4 img-100"> |
| + | <img src="https://static.igem.org/mediawiki/2014/6/6e/Aalto_Helsinki_Paris_Saclay_picture.jpg" class="img-responsive"></img> |
| + | <p class="kuvateksti"> |
| + | This is how Paris Saclay's team saw us during the Skype call. Image courtesy of <a href="https://2014.igem.org/Team:Paris_Saclay">Paris Saclay 2014 team</a>. |
| + | </p> |
| + | </div> |
| + | </div> |
| | | |
| <h3>Virginia</h3> | | <h3>Virginia</h3> |
- | <p>Survey participation, 20 entries</p> | + | <div class="row"> |
| + | <div class="col-md-8 text-col-left"> |
| + | <p> |
| + | We participated in Virginia iGEM team's survey regarding synthetic biology. It was easier said than done, however. We wandered around Helsinki city centre looking for volunteers with time to answer the survey and offered buns and coffee as an exchange for their time. After a long day we finally reached over 20 responses! |
| + | </p> |
| + | </div> |
| + | <div class="col-md-4"> |
| + | <div id="virginiabadge"> |
| + | <a href="https://2014.igem.org/Team:Virginia/HumanPractices"><img height="180" src="https://static.igem.org/mediawiki/2014/b/b0/Virginia_Transparent.png" width="250"></a> |
| + | </div> |
| + | <p class="kuvateksti">This is the well deserved badge we received for reaching over 20 entries on Virginia's survey!</p> |
| + | </div> |
| + | </div> |
| | | |
| <h3>Amsterdam 2012</h3> | | <h3>Amsterdam 2012</h3> |
- | <p>Meetings with a PhD student Tania from University of Helsinki, plenty of advice and feedback about our pitch etc.</p> | + | <p> |
| + | We were contacted by Tania Quirin via Facebook. She's from Amsterdam 2012 iGEM team and she's doing her PhD at University of Helsinki. We met Tania several times and got very valuable feedback about our work and presentation but also reflected our experiences to theirs. |
| + | </p> |
| + | <p> |
| + | Tania has been encouraging and supporting our team in so many ways and even came to see us on <a href="https://2014.igem.org/Team:Aalto-Helsinki/Business#Sos">Summer of Startups Demo Day</a>. She was the first iGEM alumna we actually met. She also connected us with iGEM-winning Groningen 2012 team's Arjan. |
| + | </p> |
| | | |
| <h3>Groningen 2012</h3> | | <h3>Groningen 2012</h3> |
- | <p>Skype call, getting to know to the factors what makes an iGEM project successful one</p> | + | <p> |
| + | We had a long Skype call with Arjan Oldebesten from iGEM-winning Groningen 2012. We were very excited for this opportunity to hear about full scale iGEM experience including world championship Jamboree. |
| + | </p> |
| + | <p> |
| + | Trying to understand the factors for successful iGEM project, we discovered that success in iGEM does not require a huge amount of experience, top-notch facilities nor a mentor constantly guiding the team and its progress. They had a fairly simple, yet very interesting idea and they worked they way from bottom to top. They got the attitude, the hard work and the necessary support. |
| + | </p> |
| + | <p> |
| + | Based on these conversations, we think success in iGEM can be within our reach, too, even though we are the first Finnish team participating in iGEM! In fact, we believe that being the first team makes us look for advice from all over the world and brings a truly international feeling to the project. |
| + | </p> |
| | | |
| </article> | | </article> |
Line 169: |
Line 293: |
| $('#navigation a[href^="https://2014.igem.org' + location.pathname + '"]').addClass('active'); | | $('#navigation a[href^="https://2014.igem.org' + location.pathname + '"]').addClass('active'); |
| } else $('#navigation a.home').addClass('active'); | | } else $('#navigation a.home').addClass('active'); |
- | function() {
| |
- | var link = document.createElement('link');
| |
- | link.type = 'image/x-icon';
| |
- | link.rel = 'shortcut icon';
| |
- | link.href = 'https://static.igem.org/mediawiki/2014/7/7a/Aaltohelsinki_favicon.png';
| |
- | document.getElementsByTagName('head')[0].appendChild(link);
| |
- | }();
| |
| }); | | }); |
| + | </script> |
| + | <script type="text/javascript"> |
| + | // Picture reference script |
| + | /* |
| + | USAGE: |
| + | tag img with a ref that is connected to the image, such as: |
| + | <img src="aaltohelsinki.com/testikuva.png" ref="varioskan" /> |
| + | When you insert a reference in text, put a tag with a ref attribute: |
| + | <a ref="varioskan"></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 "figure x" where x is the |
| + | correct figure number. If span or anchor has "." as the inner html, the |
| + | caption will be capitalized. |
| + | */ |
| + | var images = $('img[ref]'); |
| + | $.each(images, function(index, e){ |
| + | var referenceName = e.getAttribute("ref"); |
| + | if (!e.id){ |
| + | e.setAttribute("id","figure"+(index+1)); |
| + | } |
| + | $.each($('a[ref="'+referenceName+'"]'), function(j, e2){ |
| + | e2.setAttribute("href","#"+e.id); |
| + | if (e2.innerHTML == "."){ |
| + | e2.innerHTML = "Figure " + (index+1); |
| + | } else { |
| + | e2.innerHTML = "figure " + (index+1); |
| + | } |
| + | }); |
| + | $.each($('span[ref="'+referenceName+'"]'), function(j, e2){ |
| + | e2.setAttribute("href","#"+e.id); |
| + | if (e2.innerHTML == "."){ |
| + | e2.innerHTML = "Figure " + (index+1); |
| + | } else { |
| + | 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], img[tab]'); |
| + | $.each(tables, function(index, e){ |
| + | var tableName = e.getAttribute("tab"); |
| + | if (!e.id){ |
| + | e.setAttribute("id","table"+(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); |
| + | } |
| + | }); |
| + | } |
| + | ); |
| </script> | | </script> |
| </html> | | </html> |
| {{:Team:Aalto-Helsinki/footer}} | | {{:Team:Aalto-Helsinki/footer}} |