<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<rss version="2.0">
  <channel>
    <title>Sarwari, R.</title>
    <link>http://repub.eur.nl/res/aut/15954/</link>
    <description>List of Publications</description>
    <language>en</language>
    <image>
      <url>http://repub.eur.nl/static-eur/img/logo.png</url>
      <title>RePub, Erasmus University Rotterdam</title>
      <link>http://repub.eur.nl</link>
    </image>
    <item>
      <title>Functional identification of genes causing estrogen independence of human breast cancer cells (Article)</title>
      <link>http://repub.eur.nl/res/pub/24207/</link>
      <pubDate>2009-03-01T00:00:00Z</pubDate>
      <description>Endocrine treatment of breast cancer is widely applied and effective. However, in advanced disease cases, the tumors will eventually progress into an estrogen-independent and therapy-resistant phenotype. To elucidate the molecular mechanisms underlying this endocrine therapy failure, we applied retroviral insertion mutagenesis to identify the main genes conferring estrogen independence to human breast cancer cells. Estrogen-dependent ZR-75-1 cells were infected with replication-defective retroviruses followed by selection with the anti-estrogen 4-hydroxy-tamoxifen. In the resulting panel of 79 tamoxifen-resistant cell lines, the viral integrations were mapped within the human genome. Genes located in the immediate proximity of the retroviral integration sites were characterized for altered expression and their capacity to confer anti-estrogen resistance when transfected into breast cancer cells. Out of 15 candidate BCAR (breast cancer anti-estrogen resistance) genes, seven (AKT1, AKT2, BCAR1, BCAR3, EGFR, GRB7, and TRERF1/BCAR2) were shown to directly underlie estrogen independence. Our results show that insertion mutagenesis is a powerful tool to identify BCAR loci, which may provide insights into the molecular and cellular mechanisms of breast tumor progression and therapy resistance thereby offering novel targets for the development of tailor-made therapeutical and prevention strategies. </description>
    </item> <item>
      <title>The nickel-responsive regulator NikR controls activation and repression of gene transcription in Helicobacter pylori. (Article)</title>
      <link>http://repub.eur.nl/res/pub/13954/</link>
      <pubDate>2005-11-01T00:00:00Z</pubDate>
      <description>The NikR protein is a nickel-dependent regulatory protein which is a member of the ribbon-helix-helix family of transcriptional regulators. The gastric pathogen Helicobacter pylori expresses a NikR ortholog, which was previously shown to mediate regulation of metal metabolism and urease expression, but the mechanism governing the diverse regulatory effects had not been described until now. In this study it is demonstrated that NikR can regulate H. pylori nickel metabolism by directly controlling transcriptional repression of NixA-mediated nickel uptake and transcriptional induction of urease expression. Mutation of the nickel uptake gene nixA in an H. pylori 26695 nikR mutant restored the ability to grow in Brucella media supplemented with 200 microM NiCl2 but did not restore nickel-dependent induction of urease expression. Nickel-dependent binding of NikR to the promoter of the nixA gene resulted in nickel-repressed transcription, whereas nickel-dependent binding of NikR to the promoter of the ureA gene resulted in nickel-induced transcription. Subsequent analysis of NikR binding to the nixA and ureA promoters showed that the regulatory effect was dependent on the location of the NikR-recognized binding sequence. NikR recognized the region from -13 to +21 of the nixA promoter, encompassing the +1 and -10 region, and this binding resulted in repression of nixA transcription. In contrast, NikR bound to the region from -56 to -91 upstream of the ureA promoter, resulting in induction of urease transcription. In conclusion, the NikR protein is able to function both as a repressor and as an activator of gene transcription, depending on the position of the binding site.</description>
    </item>
  </channel>
</rss>