| Literature DB >> 25228907 |
Kevin Demeure1, Elodie Duriez2, Bruno Domon2, Simone P Niclou1.
Abstract
The search for clinically useful protein biomarkers using advanced mass spectrometry approaches represents a major focus in cancer research. However, the direct analysis of human samples may be challenging due to limited availability, the absence of appropriate control samples, or the large background variability observed in patient material. As an alternative approach, human tumors orthotopically implanted into a different species (xenografts) are clinically relevant models that have proven their utility in pre-clinical research. Patient derived xenografts for glioblastoma have been extensively characterized in our laboratory and have been shown to retain the characteristics of the parental tumor at the phenotypic and genetic level. Such models were also found to adequately mimic the behavior and treatment response of human tumors. The reproducibility of such xenograft models, the possibility to identify their host background and perform tumor-host interaction studies, are major advantages over the direct analysis of human samples. At the proteome level, the analysis of xenograft samples is challenged by the presence of proteins from two different species which, depending on tumor size, type or location, often appear at variable ratios. Any proteomics approach aimed at quantifying proteins within such samples must consider the identification of species specific peptides in order to avoid biases introduced by the host proteome. Here, we present an in-house methodology and tool developed to select peptides used as surrogates for protein candidates from a defined proteome (e.g., human) in a host proteome background (e.g., mouse, rat) suited for a mass spectrometry analysis. The tools presented here are applicable to any species specific proteome, provided a protein database is available. By linking the information from both proteomes, PeptideManager significantly facilitates and expedites the selection of peptides used as surrogates to analyze proteins of interest.Entities:
Keywords: automated tool; human glioblastoma; mass spectrometry; mixed samples; rodent xenografts; targeted proteomics; unique peptide selection
Year: 2014 PMID: 25228907 PMCID: PMC4151198 DOI: 10.3389/fgene.2014.00305
Source DB: PubMed Journal: Front Genet ISSN: 1664-8021 Impact factor: 4.599
Figure 1Schematic of the protein extraction procedure from a human GBM xenografted in a GFP-expressing immunodeficient mouse. Since the excision of the human tumor tissue (in blue) includes a variable proportion of mouse cells (in green), the surrogate peptide selection process of a given protein A must exclusively consider the human specific peptide (blue peptides). Monitoring protein A via human specific peptides in different tumor pieces will eliminate the bias induced by the presence of mouse proteins within the samples.
Figure 2Scheme illustrating how . Required information from the public database is extracted to produce the peptide database (SQLite format) (A). Created peptide databases are stored and can be used for peptide selection queries (B,C). The peptide selection can be done with (B) or without (C) the presence of a background proteome. It is noteworthy that the presence of a background proteome (as in the case of xenografts) (B) will generally reduce the number of surrogate peptide candidates compared to the list of peptides obtained in (C).
List of the different file formats supported by .
| SwissProt/TrEMBL/Uniprot | *.txt, *.dat |
| RefSeq | *.faa |
| IPI | *.dat |
FASTA-like file format that only contains protein sequences and essential protein information.
More complete file format than.faa files. They include additional information such as post-translational modifications (PTMs), single nucleotide polymorphisms (SNPs), etc.
Figure 3Print screen of the results displayed by . Search queries can be performed by protein ID (A), by protein name (B) or by peptide sequence(s) (C). The list of peptides obtained can be filtered out according to the length (e.g., 5 a.a. ≤ peptide length ≤ 22 a.a.), the presence of unwanted amino acid (methionine-containing peptide for example) or the frequency of the peptide sequence within the database (D). The results can be exported in csv file format (E).
Figure 4Print screen showing the results obtained with . The information concerning both proteomes [selected proteomes in (A,B)] is brought together and the number of observation (hits) of the peptide sequence is indicated in each proteome. Human specific peptide candidates are those with one hit in the human proteome [selected in (A)] and no hit in the mouse proteome [selected in (B)] (e.g., HGNSHQGEPR). The results (filtered or not) can be saved in a csv file.