<?xml version='1.0'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:atom="http://www.w3.org/2005/Atom" >
<channel>
	<title><![CDATA[BOL: Related items]]></title>
	<link>https://bioinformaticsonline.com/related/21312?offset=20</link>
	<atom:link href="https://bioinformaticsonline.com/related/21312?offset=20" rel="self" type="application/rss+xml" />
	<description><![CDATA[]]></description>
	
	<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/22995/bioinformatics-phd-postdoc-job-rejection</guid>
	<pubDate>Thu, 02 Jul 2015 08:52:46 -0500</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/22995/bioinformatics-phd-postdoc-job-rejection</link>
	<title><![CDATA[Bioinformatics PhD / PostDoc / Job Rejection]]></title>
	<description><![CDATA[<div><p>While your PhD or PostDoc application, it is more common that you got rejected by many professors. Don't disappoint reply it calmly.</p><p><img src="http://bioinformaticsonline.com/mod/photo/rejected1.png" alt="image" style="border: 0px; border: 0px;"></p><p>In grad school, I shared a house with three Bioinformatics PhD students. One, when he applied to a particular professor, received a letter that said, essentially, "If you are applying because you want to enrich yourself, great. If you are applying because you want a job, you should know that you won't get one." I am trying to tell you this is because if you, with a good background in Bioinformatics, are passing up opportunities, you must be a strong candidate in many areas. Enrich yourself.<br /><br /> So, my suggestion is take a deep breath, forgot about all. Don&rsquo;t take it personally. It's been usual processes while hunting for a good lab and professor. Take is positive, I am not sure why they reject, but don't worry perhaps the lab don't deserve you. Always remember there are billions of reasons not to hire someone for projects, especially in a research sector.<br /><br /> My suggestion, please do not whine about how you were a great research candidate for the post, and you just can't understand why they were so stupid as to have rejected you! This feeling will not win you any points in research, community. Especially, when in todays socially connected era everyone is linked. Remember, a nice E-mail saying, "I really wished to working with you on this project and I hope we cross paths again," is all you need to send to the professor. Send a thank you note to the professor. Thank them for the time they spend to judge you. In the future, If you and the professor (of your dream) are attending a bioinformatics conference, invite him/her to lunch (please remember to pay the bill). In today evolving scientific ere, always remember to build your solid network in order to get a job of interest. Join all possible networking sites like LinkedIn, ResearchGate, Acamedia, FB for the same reason. You as a researcher always build a bridge with student/researcher/colleague/professor who have the research potential to lead in research and hire you. Just because you didn't get this project, doesn't mean there isn't another that will open up in couple of month.<br /><br /> Mostly, jobs that are hard to get are hard to get. Only you can decide if the continued sacrifices are worth the expected payout. If it is, keep on plowing. Build relationships. Attend conferences.</p><p>Image ref @ JaSonYa</p></div>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/26303/maker</guid>
	<pubDate>Sun, 07 Feb 2016 15:59:24 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/26303/maker</link>
	<title><![CDATA[MAKER]]></title>
	<description><![CDATA[<p>MAKER is a portable and easily configurable genome annotation pipeline.Its purpose is to allow smaller eukaryotic and prokaryotic genome projects to independently annotate their genomes and to create genome databases. MAKER identifies repeats, aligns ESTs and proteins to a genome, produces ab-initio gene predictions and automatically synthesizes these data into gene annotations having evidence-based quality values.</p>
<p>More at http://www.yandell-lab.org/software/maker.html</p><p>Address of the bookmark: <a href="http://www.yandell-lab.org/software/maker.html" rel="nofollow">http://www.yandell-lab.org/software/maker.html</a></p>]]></description>
	<dc:creator>Jitendra Narayan</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/26322/liftover</guid>
	<pubDate>Mon, 08 Feb 2016 15:45:03 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/26322/liftover</link>
	<title><![CDATA[liftover]]></title>
	<description><![CDATA[<p><span>Convenient conversions between genome assemblie.&nbsp;The liftover package makes it easy to remap genomic coordinates to a different genome assembly. </span></p>
<p><span>More at https://github.com/aaronwolen/liftover<br></span></p>
<p><span>https://www.bioconductor.org/help/workflows/liftOver/</span></p><p>Address of the bookmark: <a href="https://github.com/aaronwolen/liftover" rel="nofollow">https://github.com/aaronwolen/liftover</a></p>]]></description>
	<dc:creator>Jitendra Narayan</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/27225/painless-package-development-for-r</guid>
	<pubDate>Tue, 03 May 2016 05:31:06 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/27225/painless-package-development-for-r</link>
	<title><![CDATA[Painless package development for R]]></title>
	<description><![CDATA[<p>Devtools makes package development a breeze: it works with R&rsquo;s existing conventions for code structure, adding efficient tools to support the cycle of package development. With devtools, developing a package becomes so easy that it will be your default layout whenever you&rsquo;re writing a significant amount of code.</p>
<p>Before you get started be sure to check out:</p>
<ul>
<li><a href="https://groups.google.com/forum/#%21forum/rdevtools" title="Google devtools Group">devtools Google Group &ndash;&nbsp;https://groups.google.com/forum/#!forum/rdevtools</a></li>
<li><a href="http://adv-r.had.co.nz/" title="Hadley W Online Book">book on &ldquo;Advanced R programming&rdquo; &ndash;&nbsp;http://adv-r.had.co.nz/</a></li>
<li><a href="https://github.com/hadley/devtools" title="devtools GitHub">GitHub repository &ndash;&nbsp;https://github.com/hadley/devtools</a></li>
</ul>
<h3 id="getting_started">&nbsp;</h3><p>Address of the bookmark: <a href="https://www.rstudio.com/products/rpackages/devtools/" rel="nofollow">https://www.rstudio.com/products/rpackages/devtools/</a></p>]]></description>
	<dc:creator>Abhi</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/10394/bioinformatics-protocols</guid>
	<pubDate>Mon, 05 May 2014 10:21:41 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/10394/bioinformatics-protocols</link>
	<title><![CDATA[Bioinformatics Protocols]]></title>
	<description><![CDATA[<h2><span> RNA Seq </span></h2>
<p><strong> Basic Galaxy Tutorial </strong></p>
<ul>
<li><a href="https://docs.google.com/document/pub?id=1KbTiBHtvHLfPRZ39AY3uriazrINA8TJzgjjwn1zPP7Y">RNA-Seq tutorial</a> based on <a href="http://www.nature.com/protocolexchange/protocols/2327">Trapnell et al. (2012)</a> <em>Nature Protocols</em></li>
</ul>
<dl><dd>In this tutorial we cover the concepts of <a href="http://en.wikipedia.org/wiki/RNA-Seq">RNA-Seq</a> differential gene expression (DGE) analysis using a very small synthetic dataset from a well studied organism.</dd></dl>
<p><strong> Advanced Galaxy Tutorial </strong></p>
<ul>
<li><a href="https://docs.google.com/document/d/1fQ1XfeOKhezJUDTzMXtZVY20c3RGoHe-HLvFOGzqU4s/pub">RNA-Seq (Advanced) Tutorial</a></li>
</ul>
<dl><dd>In this tutorial we compare the performance of three statistically-based differential expression tools:</dd><dd>* CuffDiff</dd><dd>* EdgeR</dd><dd>* DESeq2</dd></dl>
<p><strong> Advanced Command Line Tutorial </strong></p>
<ul>
<li><a href="https://docs.google.com/document/d/1ayJXtgBP1OXtnV7o7lq4QHKMNk5SdPHFq4hGkqndBtI/pub">Graphical Output with CummeRbund</a> introduces some basic commands using the cummeRbund package of the R programming language</li>
</ul>
<dl><dd>You will need to install R, RStudio and cummeRbund on your PC (explained in the Tutorial). You will learn how to produce graphical output from RNA-Seq analysis previously done using a Cuffdiff analysis.</dd></dl>
<h2><span> Variant Detection </span></h2>
<p><strong> Basic Galaxy Tutorial </strong></p>
<ul>
<li><a href="https://docs.google.com/document/pub?id=1ZRzrjjOCvtAu3m-IKL-rbJ1f4On60dDL_IEwG7oejdI">Variant Detection tutorial</a></li>
</ul>
<dl><dd>In this tutorial we cover the concepts of detecting small variants (SNVs and indels) in human genomic DNA using a small set of reads from chromosome 22.</dd></dl>
<p><strong>Advanced Galaxy Tutorial</strong></p>
<ul>
<li><a href="https://docs.google.com/document/pub?id=1CuKkKylVDb03tnN7RSWl5EUzleetn0ctjmvaidPKLxM">Variant Detection (Advanced) Tutorial</a></li>
</ul>
<dl><dd>In this tutorial we compare the performance of three statistically-based variant detection tools:</dd><dd>* SAMtools: Mpileup</dd><dd>* GATK: Unified Genotyper</dd><dd>* FreeBayes</dd><dd>Each of these tools takes as its input a BAM file of aligned reads and generates a list of likely variants in VCF format</dd></dl>
<p><strong>Pipelines</strong> are for those who are comfortable with using the UNIX command line; and often allow more control over branching and iteration logic.</p>
<ul>
<li><a href="https://github.com/claresloggett/variant_calling_pipeline">WGS/exome GATK-based variant calling pipeline</a></li>
</ul>
<dl><dd>This is a basic variant-calling and annotation pipeline developed at the Victorian Life Sciences Computation Initiative (VLSCI), University of Melbourne. It is based around BWA, GATK and ENSEMBL and was originally designed for human (or similar) data. The master branch is configured for WGS data; there is an exome branch configured for variant calling in exome data.</dd><dd>To run the pipeline you will need Rubra: <a href="https://github.com/bjpop/rubra">https://github.com/bjpop/rubra</a>. Rubra uses the python Ruffus library: <a href="http://www.ruffus.org.uk/">http://www.ruffus.org.uk/</a>.</dd></dl>
<p><strong>Protocols</strong></p>
<ul>
<li><a href="https://docs.google.com/document/d/1lfDYNzHjfDA1pHTHd-0w3xHhg7L4TipT1gRfzgiV8es/pub">Familial Variant Calling</a></li>
</ul>
<dl><dd>In this protocol we discuss and outline the process of calling familial related mutations.</dd></dl>
<ul>
<li><a href="https://docs.google.com/document/d/1PIhm8NrFGaSK0hxpDcp8wUOz11ZkOaHIrpnJshMgDec/pub">Somatic Variant Calling</a></li>
</ul>
<dl><dd>In this protocol we discuss and outline the process of identifying somatic variants or mutations.</dd></dl>
<h2><span> Assembly </span></h2>
<p><strong> Basic Galaxy Tutorial </strong></p>
<ul>
<li><a href="https://docs.google.com/document/pub?id=1N3AB9ptISUu4zULqe1kXpVF0BDyGb5f5yzxWSJd_WNM">Genome assembly tutorial</a></li>
</ul>
<dl><dd>In this tutorial we carry out de novo assembly of a microbial genome. We have also written a <a href="https://docs.google.com/document/d/1xs-TI5MejQARqo0pcocGlymsXldwJbJII890gnmjI0o/pub">De novo Genome Assembly for Illumina Data</a> Protocol for a more generic description of the method.</dd></dl>
<p><strong> Protocol </strong></p>
<ul>
<li><a href="https://docs.google.com/document/d/1xs-TI5MejQARqo0pcocGlymsXldwJbJII890gnmjI0o/pub">De novo Genome Assembly for Illumina Data</a></li>
</ul>
<dl><dd>In this protocol we discuss and outline the process of de novo assembly for small to medium sized genomes. Use our <a href="https://docs.google.com/document/pub?id=1N3AB9ptISUu4zULqe1kXpVF0BDyGb5f5yzxWSJd_WNM">Genome assembly tutorial</a> to learn a specific case of using Galaxy to carry out de novo assembly of a microbial genome.</dd></dl>
<h2><span> Small RNAs </span></h2>
<p><strong> Basic Galaxy Tutorial </strong></p>
<ul>
<li><a href="https://docs.google.com/document/d/1WAObJr7M0m8U-2ku-0Y0Sdt_IHmqd1h8WaJHPhnJ1lM/pub">Quality control for small RNA</a></li>
</ul>
<dl><dd>This tutorial covers initial steps of the workflow for analysis of short RNA expression such as a quality control of the raw reads, processing of the raw reads for the subsequent analysis and initial quality assessment of the library.</dd></dl>
<h2><span> ChIP Seq </span></h2>
<p><strong> Protocol </strong></p>
<ul>
<li><a href="https://docs.google.com/document/d/1UPJC8dsiDeP5R9MH9U0IvoDgPF2Q3EOstAuzS3e6WCE/pub">ChIP-Seq</a></li>
</ul>
<dl><dd>In this protocol we discuss ChIP-Seq: a method to analyze the interaction between proteins and DNA.</dd></dl>
<h2><span> Amplicons </span></h2>
<p><strong>Protocol</strong></p>
<ul>
<li><a href="https://docs.google.com/document/d/1uW7JzxG86QzS92hTyeuNsLhX_d1XFbaZPSjh7jWxcSg/pub">Amplicon Alignment</a></li>
</ul>
<dl><dd>In this protocol we discuss and outline the process of aligning custom amplicons using primers for high precision.</dd></dl>
<h2><span> Learn Galaxy </span></h2>
<p><a href="https://docs.google.com/document/d/1wsdJDYfjZVg2uJxm9AHi_j0mY3X1M1F4gB-elkuYL7c/pub">Introduction to Galaxy,</a> for those who are very new to Galaxy.</p>
<p><a href="https://docs.google.com/document/d/1t7vVqa3mdeZYPv5-8hiHBFBYhNiynV_3mWByno9-wUM/pub">Using Histories and Workflows,</a> for those with some Galaxy knowledge.</p>
<p>The Galaxy project website has many <a href="http://wiki.galaxyproject.org/Learn">tutorials</a> and <a href="http://wiki.galaxyproject.org/Learn/Screencasts">screencasts</a> about using Galaxy and the tools, and developing new tools.</p><p>Address of the bookmark: <a href="https://genome.edu.au/wiki/Learn" rel="nofollow">https://genome.edu.au/wiki/Learn</a></p>]]></description>
	<dc:creator>Rahul Nayak</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/11030/r-programming-and-jobs-website</guid>
	<pubDate>Sun, 25 May 2014 14:43:57 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/11030/r-programming-and-jobs-website</link>
	<title><![CDATA[R programming and Jobs website]]></title>
	<description><![CDATA[<p>Welcome to the R Jobs section of ProgrammingR.com. If your organization has an R employment opportunity that you would like to have posted here, submit it via the <a href="http://www.programmingr.com/contact" title="contact page">contact page</a>. Prospective employees: use the contact information provided in the position listing to apply or contact the hiring organization.</p><p>Address of the bookmark: <a href="http://www.programmingr.com/category/stype/r-job-listings/" rel="nofollow">http://www.programmingr.com/category/stype/r-job-listings/</a></p>]]></description>
	<dc:creator>Pragati Singh</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/news/view/20440/linux-operating-system-aimed-at-scientists</guid>
	<pubDate>Mon, 19 Jan 2015 08:30:49 -0600</pubDate>
	<link>https://bioinformaticsonline.com/news/view/20440/linux-operating-system-aimed-at-scientists</link>
	<title><![CDATA[Linux operating system aimed at scientists]]></title>
	<description><![CDATA[<p>The Bio-Linux operating system is based on Ubuntu 14.04 LTS (Trusty Tahr), and the previous version was using Ubuntu 12.04 LTS. The developers only use LTS releases and that means that upgrades for this distro don't come along all that often.<br /> <br /> This Linux distribution is aimed at scientists and it comes with more than 250 bioinformatics packages, 50 graphical applications and several hundred command line tools. And this is just skimming the surface of what the OS can do. Users have access to even more apps from the official repositories.</p><h3>Bio-Linux is using an Ubuntu LTS version as its base</h3><p>The fact that it uses Ubuntu LTS versions for the base is a good thing because it means its users won't have to worry about the support. Ubuntu 14.04 LTS is supported until 2019, so people who are using Bio-Linux shouldn't have a problem.<br /> <br /> "An updated Bio-Linux 8 version is now on the website in ISO and OVA versions. As usual, there is no need to download this version if you are an existing user. All updates to existing packages will be applied to your system through the update manager and new packages are all available via apt-get or Synaptic," reads the <a href="http://nebclists.nerc.ac.uk/pipermail/bio-linux-announce/2015-January/000020.html" target="_blank">announcement</a>.<br /> <br /> The changelog also states that a problem that was preventing the desktop to not start on VirtualBox has been fixed, the QIIME and Bowtie-Bio tools have been upgraded, the pandaseq paired end assembler has been added, and the beginners tutorial specific to Bio-Linux 8 has been improved.<br /> <br /> Check out the official announcement for a complete list of changes and updates. You can <a href="http://linux.softpedia.com/get/System/Operating-Systems/Linux-Distributions/Bio-Linux-45495.shtml" target="_blank"><strong>download Bio-Linux 8.0.5</strong></a> right now from Softpedia and give it a spin. It has the Unity desktop and now it runs very well in virtual environments.</p><p>Reference @ http://news.softpedia.com/news/Bioinformatics-Distro-Bio-Linux-8-0-5-Now-Available-for-Download-469867.shtml</p>]]></description>
	<dc:creator>Pranjali Yadav</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/videolist/watch/20585/dna-transcription-advanced</guid>
	<pubDate>Thu, 29 Jan 2015 05:31:42 -0600</pubDate>
	<link>https://bioinformaticsonline.com/videolist/watch/20585/dna-transcription-advanced</link>
	<title><![CDATA[DNA Transcription (Advanced)]]></title>
	<description><![CDATA[<iframe width="" height="" src="https://www.youtube-nocookie.com/embed/SMtWvDbfHLo" frameborder="0" allowfullscreen></iframe><p>Transcription is the process by which the information in DNA is copied into messenger RNA (mRNA) for protein production. Originally created for DNA Interactive ( http://www.dnai.org ). TRANSCRIPT: The Central Dogma of Molecular Biology: "DNA makes RNA makes protein" Here the process begins. Transcription factors assemble at a specific promoter region along the DNA. The length of DNA following the promoter is a gene and it contains the recipe for a protein. A mediator protein complex arrives carrying the enzyme RNA polymerase. It manoeuvres the RNA polymerase into place... inserting it with the help of other factors between the strands of the DNA double helix. The assembled collection of all these factors is referred to as the transcription initiation complex... and now it is ready to be activated. The initiation complex requires contact with activator proteins, which bind to specific sequences of DNA known as enhancer regions. These regions may be thousands of base pairs distant from the start of the gene. Contact between the activator proteins and the initiation-complex releases the copying mechanism. The RNA polymerase unzips a small portion of the DNA helix exposing the bases on each strand. Only one of the strands is copied. It acts as a template for the synthesis of an RNA molecule which is assembled one sub-unit at a time by matching the DNA letter code on the template strand. The sub-units can be seen here entering the enzyme through its intake hole and they are joined together to form the long messenger RNA chain snaking out of the top.</p>]]></description>
	
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/21096/how-to-prepare-your-bioinformatics-cv</guid>
	<pubDate>Mon, 09 Feb 2015 01:50:01 -0600</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/21096/how-to-prepare-your-bioinformatics-cv</link>
	<title><![CDATA[How to Prepare your Bioinformatics CV ?]]></title>
	<description><![CDATA[<p>Preparing a CV is also an art as well as a requirement for a person applying for a job .<br /> Curriculum Vitae is the first impression on the employer so it should be the best.How It can be the best can be learnt.Here is a link where you can get guidelines on how CV can be prepared and a sample also. Preparing your own Curriculum Vitae can seem a daunting task, quite apart from what to put in and what to leave out, describing your own strengths and abilities isn't easy. What we have tried to do with the following guidelines is to make the whole process a much easier one and ensure that you end up with a professional document which shows you how to pitch your skills and stand out from the crowd. In the current economic and employment climate, employers are looking to consistently improve on productivity and match a prospective employee's skills and experience with the job needs, both now and in the future.<br /> <strong><br /> Presentation and layout</strong><br /> Always ensure that your CV is laser-printed on white, good quality paper, use a clean typeface and don't go smaller than 12 point.<br /> The use of sub-headings (e.g. Personal details, career history, etc.) will help potential employers glean the information they require with ease.<br /> There should be clear spaces between category headings for easy clarification and definition.<br /> Your name, address and phone number(s) should form the start of the document. If you are giving a work number add the following - 'please use with discretion.'<br /> Commencing with your present or most recent employer, state your career history. Then list your professional qualifications. If you have been working for many years list your academic qualifications and a very brief mention as to your college or schooling.<br /> If you are just commencing your working life, having previously been a student, provide more in depth knowledge regarding your academic achievements to date.<br /> <br /> <strong>Content</strong></p><p>Starting with your current or most recent employment provide details of your position as follows:</p><ul>
<li>A chronological CV should be arranged in reverse chronological order. It should be apparent immediately where you are now.</li>
<li>Remember that an application form is limited to the few things that a particular institution wants to know about everybody. A CV lets you give information that is unique to you. Add all your key accomplishments and activities in the initial draft. In subsequent drafts, you can remove information that may not be pertinent.</li>
<li>Resist the temptation to append explanatory sentences or language, which will distract the reader from the basic information being presented. The language of a CV is abbreviated and succinct. When applying for residency training, you will have the opportunity to express yourself in a personal or biographical statement. In the future, when applying for a job or some other type of position, you will want to include an appropriate cover letter with your CV to explain your particular qualifications and strengths for the position.</li>
<li>Don&rsquo;t despair if your CV doesn&rsquo;t resemble those of other students who are applying to the same residency program. Everybody&rsquo;s CV is different. Even if everyone used the same format suggested in this section, your CV will not resemble others&rsquo; because it doesn&rsquo;t have the same content. No residency program director is looking for a specific CV style. You will receive points for neatness, and readability.</li>
<li>Be honest. If you haven&rsquo;t accomplished anything in a particular category, leave it out. Don&rsquo;t create accomplishments to fill in the spaces. You can be specific about your level of participation in a project or activity, but don&rsquo;t be misleading (i.e., you can say you coordinated membership recruitment for your AMSA chapter, but don&rsquo;t say you were &ldquo;president&rdquo; unless you were).</li>
</ul><ul>
<li>Job title - time that you have held this position</li>
<li>The key tasks and responsibilities that comprise this role's requirements - notable achievements whilst in the role</li>
<li>Where possible quantify your achievements with precise facts and figures, e.g. managed junior staff, handled department budget, prepared management reports</li>
<li>Expand on the skills you are using in your current job which you believe will be valuable in the position(s) for which you are applying</li>
</ul><p>It is not necessary to state the reason you are leaving your current position. This will be a topic for conversation when you are invited for interview or can be covered in your letter of application.<br /> For all previous employment, unless one appointment was more significant than your current or last position, keep details brief i.e. the name of the company, job title, period of employment and the job.<br /> Be sure there are no gaps in your career history - unless for example you took a year out to travel, in which case make reference to this under Interests/Hobbies.<br /> If you are a student just starting work, give any evidence you can to demonstrate your practical skills e.g. school prefect, event organisation, member of sports team, contributor to college magazine or voluntary work.<br /><br /> You are under no obligation to disclose marital status, age or whether or not you have children unless these are specific criteria for selection for a position that you are interested in.<br /> Consider what examples (interests/ hobbies) you can give to show that you match the selection criteria.<br /><br /> If they want someone to work as part of a large team, remember to say if you belong to a local organisation or if you are part of a sports team.<br /><br /> If they want someone who will work on their own for large periods of time, make reference to an Open University course you are considering undertaking.<br /><br /> Your primary objective is to convince the prospective employer that you have the requisite skills, experience and hunger to do the job.<br /><br /> Your CV should be no more than two A4 pages and as every employer is different remember to customise your CV to every job you go after.</p><p>There are abundant books on the contents and presentation of a general CV. A BMJ article published in 1978, offering doctors guidance on how to prepare a CV, has been reprinted in the widely read How to do it series.1 2 A survey among postgraduate deans and training advisers at regional colleges found that the contents and presentation of a model CV for doctors in training has been published.3 It is perhaps surprising to note that these models differ significantly from one another. Although they may be useful as starting points, their differences tend to create confusion and anxiety among students. I would argue that these differences exist because the content and presentation of the "ideal" CV vary considerably among individual applicants, the stage of their careers, and the purposes for which the CV is used. It is impossible to create a generic CV. I have therefore not attempted to draw up another model CV. Rather, the purpose of this article is to outline the general principles and important practical points in preparing a good CV. General principles on contents Before finalising your CV for a particular purpose you must be sure of your objectives, whether it is used as an initial screening or the only selection instrument, and the criteria against which it is judged. What details, and how many of them, to include in your CV depends on these factors. I shall illustrate with examples relevant to medical students.&nbsp;<br /> <br /> (1) Job application Your objective is to get the job. In a job application, the CV is used for two purposes: as an initial screening instrument for shortlisting candidates and as a framework for discussion during the interview. The explicit criteria used for shortlisting are usually given in the job advertisement. For some organisations, separate lists of essential and desirable criteria are given. Alternatively, you can get a good idea of the basic requirements from the job description. Your CV must clearly highlight these criteria, preferably on the first page. These usually include: formal qualifications; registration with the General Medical Council; and the prescribed experience. It is sometimes easy to forget to mention items specifically asked for in the job description (for example, a valid driving licence). The implicit criteria are less easy to pinpoint. For example, how much detail on your BSc dissertation and publications should you include? Should you make a long list of extracurricular activities, interests outside medicine, and positions of responsibility? If you admit to a wide range of extracurricular activities and interests, would you be considered as a candidate with a well balanced mature personality or will it be interpreted to mean that you will have little time or interest to do your job? There are no easy answers. Common sense might tell you that BSc dissertation and publications are more important in application for teaching hospital or research posts, but less important for district hospital posts. Conversely, you might think that interests outside medicine are more important for posts in district hospitals or in general practice. This is, however, not always true. A few consultants at district hospital are highly academic. Information gathered from students and doctors working under the professor or consultant concerned may be vital. Alternatively, it is worth while doing your homework by looking up your prospective consultant in the medical directory. This may occasionally prompt you to include information that you might otherwise have left out. For example, you may find that the consultant qualified in Scotland and has previously worked in Scotland for a considerable time, and you may decide to add in your CV that you studied in a Scottish secondary school. Since the CV is only used as for initial screening, you need not go into your previous experience or extracurricular activities in too much detail. Highlight only the most significant points, and leave the details for the interview. If you are applying for a clinical post, one of your referees should be a consultant for whom you have worked as a student. You should ask for permission to use his/her name before submitting your application.&nbsp;<br /> <br /> (2) Application for research scholarship or PhD studentship The CV and application form are sometimes used as the sole selection instrument, and you must make enquiries before you submit your application. Clearly, academic ability is the main criterion for selection, and you should include as much information relevant to your academic ability and interests as you can. Examples are your A levels, your BSc dissertation, any publications (even in the form of a letter in newspaper), any experience as an editor (for example, for your school magazine). Your extracurricular activities are less important, and you can simply give a short list. At least one of the referees should be an academic - for example, your previous supervisor in your BSc degree.<br /> &nbsp;<br /> (3) Application to join a clinical course in another medical school Preclinical students who have completed an intercalated degree often have the option of applying to join a clinical course in another medical school, although it may become more difficult to do so with the introduction of the new GMC curriculum. Your CV is usually used for shortlisting candidates for interview. The criteria differ slightly among medical schools, but both academic ability and contribution to university life are important. Hence, not only should you highlight your academic achievements but you must also highlight your participation in the university (for example, in sports or music).&nbsp;<br /> <br /> (4) For the information of your tutor or counsellor For most medical schools, you are allocated a tutor who provides both academic and non-academic support and monitors your progress throughout your study on a confidential basis. Students are sometimes asked to submit their up to date CV to their tutors for information. Assuming that the tutors are helpful there is little to gain from over emphasising your strengths or hiding your weaknesses. Once you become a doctor in training after you qualify you will need to undergo an annual assessment of your progress. It serves to certify that you have reached a satisfactory standard, but it is also used as an aid to identify and help with your weaknesses. You may find it difficult to balance these two purposes in presenting your CV. General principles on presentation Now that all students are computer literate, there should be few problems in preparing a well presented CV. The following list serves as a reminder on how to present your CV effectively: Spelling or grammar mistakes - do not rely purely on the spell check on your computer. Ask friends to proofread your CV for you. Consistency - The use of punctuation to open and close sentences, justification, and fonts should be consistent. Readability - The headings should be clear. The font size should be no less than 12 point. Basic criteria - The basic criteria should be easily located, preferably on the first page. Length - The length of your CV increases as you progress up the professional ladder. For students, it should generally be no more than three pages. Quality of print - The CV should be printed on good quality paper, preferably using a laser printer. Practical points In this article, I argue that different versions of a CV may be required for different purposes. Even applications for different posts in the same specialty may require slightly different versions. Also, CVs need to be updated regularly. This would have been time consuming to achieve in the past, but it is now quite simple, with the aid of a basic word processing package. A master CV containing all relevant information should be prepared and saved as a computer file. This should be continuously kept up to date. When the need for a CV arises, it can be tailormade by editing the master document. It is important to save each of these edited versions separately, with the file names indicating the date when it was created and the purpose. It is also important to prepare a cover letter to go with the CV. Key messages A good CV is essential for successful progression up the medical professional ladder The contents of the CV should be tailormade for the purpose it is used for and the criteria against which it is judged. It is important to gather information about these criteria first The CV must be technically well presented, with the basic criteria easily located Information technology has made it simple to regularly update our CVs and allows preparation of different versions of a CV for different purposes with relative ease.</p><p><strong>Reference:</strong></p><p>Prepare a curriculum vitae. BMJ 1978;25(2):1478-9.<br /> O'Brien E. Prepare a curriculum vitae. In: Reece D, ed.&nbsp;<br /> How to do it. Vol 1. London: BMJ Publishing Group, 1995 Chambler AF, Chapman-Sheath PJ, Pearse MF.&nbsp;<br /> A model curriculum vitae: what are the trainers looking for? Hosp Med 1998;59(4):324-6.</p>]]></description>
	<dc:creator>Neel</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/file/view/22047/binc-sample-question-paper</guid>
	<pubDate>Thu, 16 Apr 2015 09:14:14 -0500</pubDate>
	<link>https://bioinformaticsonline.com/file/view/22047/binc-sample-question-paper</link>
	<title><![CDATA[BINC Sample Question Paper !!!]]></title>
	<description><![CDATA[<p>BINC sample question paper round TWO.</p>]]></description>
	<dc:creator>Jitendra Narayan</dc:creator>
	<enclosure url="https://bioinformaticsonline.com/file/download/22047" length="1621" type="text/plain" />
</item>

</channel>
</rss>