Display Settings:

Format

Send to:

Choose Destination
Traffic. 2010 Aug;11(8):1034-43. doi: 10.1111/j.1600-0854.2010.01080.x. Epub 2010 May 11.

Genetic analysis of yeast Sec24p mutants suggests cargo binding is not co-operative during ER export.

Author information

  • 1Department of Biological Sciences, Columbia University, New York, NY, USA.

Abstract

Many eukaryotic secretory proteins are selected for export from the endoplasmic reticulum (ER) through their interaction with the Sec24p subunit of the coat protein II (COPII) coat. Three distinct cargo-binding sites on yeast Sec24p have been described by biochemical, genetic and structural studies. Each site recognizes a limited set of peptide motifs or a folded structural domain, however, the breadth of cargo recognized by a given site and the dynamics of cargo engagement remain poorly understood. We aimed to gain further insight into the broader molecular function of one of these cargo-binding sites using a non-biased genetic approach. We exploited the in vivo lethality associated with mutation of the Sec24p B-site to identify genes that suppress this phenotype when overexpressed. We identified SMY2 as a general suppressor that rescued multiple defects in Sec24p, and SEC22 as a specific suppressor of two adjacent cargo-binding sites, raising the possibility of allosteric regulation of these domains. We generated a novel set of mutations in Sec24p that distinguish these two sites and examined the ability of Sec22p to rescue these mutations. Our findings suggest that co-operativity does not influence cargo capture at these sites, and that Sec22p rescue occurs via its function as a retrograde SNARE.

PMID:
20477990
[PubMed - indexed for MEDLINE]
PMCID:
PMC2904401
Free PMC Article

Images from this publication.See all images (6)Free text

Fig. 1
Fig. 2
Fig. 3
Fig. 4
Fig. 5
Fig. 6
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Full text links

    Icon for Blackwell Publishing Icon for PubMed Central
    Loading ...
    Write to the Help Desk