(added link to python) |
m (navbar active bugfix) |
||
(3 intermediate revisions by the same user not shown) | |||
Line 27: | Line 27: | ||
these with a link. This is especially useful to refer to standard protocols. | these with a link. This is especially useful to refer to standard protocols. | ||
The python script, the JavaScript file and a CSS file are freely available to the whole iGEM community. You can download a zip file | The python script, the JavaScript file and a CSS file are freely available to the whole iGEM community. You can download a zip file | ||
− | containing the script, templates and example data <a href=" | + | containing the script, templates and example data <a href="https://static.igem.org/mediawiki/2017/b/b2/T--Bielefeld-CeBiTec--LabnotesGenerator.zip">here</a>. Please acknowledge iGEM team Bielefeld-CeBiTec 2017 when |
− | using this tool and feel free to tell your friends about it. | + | using this tool and feel free to tell your friends about it.<br><br> |
− | + | We say thank you to the teams <a href="https://2017.igem.org/Team:TU_Darmstadt">TU-Darmstadt</a> and <a href="https://2017.igem.org/Team:Cologne-Duesseldorf">Cologne-Duesseldorf</a> | |
+ | for testing the beta versions of our gift for the iGEM community! | ||
</article> | </article> | ||
</div> | </div> | ||
Line 70: | Line 71: | ||
<article> | <article> | ||
You can find more information in case of problems in the README file which comes with the other files in the ZIP file. | You can find more information in case of problems in the README file which comes with the other files in the ZIP file. | ||
− | You can find it also <a href="README">here</a> in the wiki. | + | You can find it also <a href="#README">here</a> in the wiki. |
</article> | </article> | ||
</div> | </div> | ||
Line 79: | Line 80: | ||
<h3> Usage </h3> | <h3> Usage </h3> | ||
<article> | <article> | ||
+ | To run the script, open a console and navigate via the command line into the desired folder. Then call the script. | ||
+ | If you are not familiar with command line tools, look in the internet how to open and use a console on your operating system. | ||
The basic call of the script is | The basic call of the script is | ||
</article> | </article> | ||
Line 143: | Line 146: | ||
The order of the entries does not matter. Entries are sorted automatically | The order of the entries does not matter. Entries are sorted automatically | ||
by the date.<br> | by the date.<br> | ||
+ | If you do not want to show an information, you can write "?" or "???" into this | ||
+ | line. You cannot hide the procedure, date or the experiment title.<br> | ||
<br> | <br> | ||
names-dict:<br> | names-dict:<br> | ||
Line 183: | Line 188: | ||
-h or -help get info to all commands<br> | -h or -help get info to all commands<br> | ||
</div> | </div> | ||
+ | <article> | ||
+ | Troubleshooting:<br> | ||
+ | Some characters are not displayed, why?<br> | ||
+ | -> Be sure to use the coding "UTF-8" for you labnotes.txt. To do this click on | ||
+ | "save as" and choose the correct coding.<br> | ||
+ | <br> | ||
+ | The first entry is not generated?<br> | ||
+ | -> Sometimes it seems, like a wrong coding adds additional characters to the | ||
+ | begining of the file, which are not visible. Add some empty lines before the | ||
+ | first entry and it should be recognized in the next run.<br> | ||
+ | <br> | ||
+ | The information of procedure, inveestigators and more in a single entry is | ||
+ | messed up, why?<br> | ||
+ | -> Check your entry in the labnotes.txt, you probably forgot one line. | ||
+ | Remember: Even if you do not want to show one information, do not leave this | ||
+ | line out! Use "?" or "???" instead! | ||
+ | </article> | ||
</div> | </div> | ||
</div> | </div> | ||
Line 189: | Line 211: | ||
<h3> Changelog</h3> | <h3> Changelog</h3> | ||
<article> | <article> | ||
− | + | 2017-10-23<br> | |
+ | Release of the first puclic version | ||
</article> | </article> | ||
</div> | </div> | ||
Line 201: | Line 224: | ||
</body> | </body> | ||
<script> | <script> | ||
− | $("#").addClass("active"); | + | $("#notebook").addClass("active"); |
+ | $("#notebook-lng").addClass("active"); | ||
</script> | </script> | ||
</html> | </html> | ||
{{Team:Bielefeld-CeBiTec/Footer}} | {{Team:Bielefeld-CeBiTec/Footer}} |
Latest revision as of 17:57, 24 October 2017
Labnotes Generator
The tool takes data from all provided files and sorts them by given date. Afterwards, a HTML file with the correct HTML classes is created. To include the desired style the user can provide a customized CSS file, which recognizes and styles the given classes. To add images, you have to write the HTML code into the procedure section. The provided java script file is necessary to expand and collapse the singe boxes. If provided, the tool will also recognize special keywords and connects these with a link. This is especially useful to refer to standard protocols. The python script, the JavaScript file and a CSS file are freely available to the whole iGEM community. You can download a zip file containing the script, templates and example data here. Please acknowledge iGEM team Bielefeld-CeBiTec 2017 when using this tool and feel free to tell your friends about it.
We say thank you to the teams TU-Darmstadt and Cologne-Duesseldorf for testing the beta versions of our gift for the iGEM community!
Preparation
>YYYY-MM-DD
Team
Experiment (Aim/superior experimental context)
Investigators
Title (Title or main task of the experiment)
Procedure
Team
Experiment (Aim/superior experimental context)
Investigators
Title (Title or main task of the experiment)
Procedure
The “Procedure” part consists of multiple lines starting right after the “Title” line. You can write just text or add also a minus at the beginning of each line to add bullet points. Multiple minuses for building up a hierarchy are possible, too. Be sure to save these files with a coding in “UTF-8”, otherwise you cannot display characters like “µ” in “µl”.
{"key1" : "substitution1",
"key2" : "substitution2",
"key3" : "substitution3"}
"key2" : "substitution2",
"key3" : "substitution3"}
Usage
python labnotes_creator.py <input file/folder>
-names <names dict> -protocols <protocols dict>
-top <html top insert>
-bottom <html bottom insert>
-bottom <html bottom insert>
-nojs -nocss
-out <output folder/path>
README
Use the *_template.txt files to create your own files.
labnotes file:
Following date formats are accepted:
YYYY-MM-DD
DD.MM.YYYY
MM/DD/YYYY
You can use "-" at the beginning of each line in the procedure to create bullet points. Use multiple minuses in a row to create lower levels of the list.
After each entry you have to place an empty line.
Using HTML code for formating, like "<i>italic text</i>" is possible.
The order of the entries does not matter. Entries are sorted automatically by the date.
If you do not want to show an information, you can write "?" or "???" into this line. You cannot hide the procedure, date or the experiment title.
names-dict:
Use the initials as key and the full names as values for the dictionary format. New entries are seperated by commas. The last entry is not followed by a comma. The file has to be saved with the ANSI coding, otherwise it cannot be imported into python as a dictionary!
protocols-dict:
Same rules for this dictionary as for the names-dict. The template contains in the value also a placeholder for a link. The keywords can consist of multiple words. All letters MUST be written in lower case! Otherwise it wont work.
command line input:
example call:
-python labnotes_generator.py labnotes_example.txt -names names_dict_example.txt -protocols protocols_example.txt -out output
-> creates HTML, JS and CSS files in new folder "output"
-> creates HTML, JS and CSS files in new folder "output"
python labnotes_generator.py <input file/folder>
-> in case of refer to a folder ALL files within this folder have to be labnote files!
-> in case of refer to a folder ALL files within this folder have to be labnote files!
-names <txt file> specifies file containing names directory
-protocols <txt file> specifies file containing protocol directory
-top <HTML file> specifies HTML file to which the new generated content is appended to
-bottom <HTML file> specifies HTML file which is appended to the generated content
-out <name of output folder> specify existing or not existing folder/path to which all generated content is saved to
-nocss suppress generating a CSS file
-nojs suppress generating a JS file
-h or -help get info to all commands
-protocols <txt file> specifies file containing protocol directory
-top <HTML file> specifies HTML file to which the new generated content is appended to
-bottom <HTML file> specifies HTML file which is appended to the generated content
-out <name of output folder> specify existing or not existing folder/path to which all generated content is saved to
-nocss suppress generating a CSS file
-nojs suppress generating a JS file
-h or -help get info to all commands
Some characters are not displayed, why?
-> Be sure to use the coding "UTF-8" for you labnotes.txt. To do this click on "save as" and choose the correct coding.
The first entry is not generated?
-> Sometimes it seems, like a wrong coding adds additional characters to the begining of the file, which are not visible. Add some empty lines before the first entry and it should be recognized in the next run.
The information of procedure, inveestigators and more in a single entry is messed up, why?
-> Check your entry in the labnotes.txt, you probably forgot one line. Remember: Even if you do not want to show one information, do not leave this line out! Use "?" or "???" instead!
Changelog
Release of the first puclic version