<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div><font face="Helvetica">Hello <i>Xenopus</i> community,</font></div><div><font face="Helvetica"><br></font></div><div><font face="Helvetica">Please find attached the working guidelines for <i>Xenopus</i> transgenic and mutant line nomenclature.</font></div><div><font face="Helvetica"><br></font></div><div><font face="Helvetica">For transgenic lines, the first step is to name your construct(s), then base the Tg line name on the Tg construct name. </font></div><div><font face="Helvetica">Mutant lines are named after the location of the mutation, whether it is
known (use a gene symbol) or unknown (use a described phenotype).</font></div><div><font face="Helvetica"><br></font></div><div><font face="Helvetica">Remember, only those lines that are maintained in the lab and/or supplied to other researchers or stock centers need official names - transient lines do not need official need names.</font></div><div><font face="Helvetica"><br></font></div><div><div>These guidelines have been posted on Xenbase forums - the <i>Xenopus</i> community discussion board. </div><div>Please feel free to pose questions and use cases to Xenbase (<a href="mailto:xenbase@ucalgary.ca">xenbase@ucalgary.ca</a>) or post on the forums board.</div></div><div><br></div><div>The examples given in the guidelines are generally straight forward, but we all know Tg constructs can be very complicated, We will post extended guidelines to Xenbase & Xenbase Forums this Fall, which will cover more complex constructs.</div><div><br></div><div></div></body></html>