tooluniverse-proteomics-data-retrieval

Proteomics Data Retrieval

Find and retrieve metadata for publicly available proteomics datasets from MassIVE and ProteomeXchange repositories. Supports searching by species, keyword, or accession, and returns detailed dataset metadata including instruments, publications, species, and post-translational modifications.

When to Use This Skill

Triggers:

"Find proteomics datasets for [organism/disease/protein]"
"Search MassIVE for [keyword]"
"Get details for PXD000001" or "Look up MSV000079514"
"What public mass spectrometry datasets exist for [topic]?"
"Find MS datasets with [PTM type] data"
"List recent human proteomics datasets"

Use Cases:

Dataset Discovery: Search repositories for proteomics experiments related to a research topic
Accession Lookup: Get full metadata for a known dataset accession (PXD or MSV)
Species-Filtered Search: Find all datasets for a specific organism
Cross-Repository Search: Query both MassIVE and ProteomeXchange for comprehensive coverage
Experimental Context: Find published datasets to validate or complement in-house results

COMPUTE, DON'T DESCRIBE

When analysis requires computation (statistics, data processing, scoring, enrichment), write and run Python code via Bash. Don't describe what you would do — execute it and report actual results. Use ToolUniverse tools to retrieve data, then Python (pandas, scipy, statsmodels, matplotlib) to analyze it.

KEY PRINCIPLES

ProteomeXchange is the aggregator -- it indexes datasets from PRIDE, MassIVE, PeptideAtlas, jPOST, and iProX
MassIVE has richer metadata -- includes summaries, keywords, modifications, and contacts
Search both repositories -- ProteomeXchange for breadth, MassIVE for detail
Species uses NCBI taxonomy IDs -- human = 9606, mouse = 10090, rat = 10116
Accession formats: PXD (ProteomeXchange), MSV (MassIVE) -- both accepted by MassIVE_get_dataset
LOOK UP DON'T GUESS -- Never assume which datasets exist, their accessions, or their instrument types. Always search and retrieve metadata to confirm.

Domain Reasoning: Dataset Quality Assessment

Dataset quality depends on instrument, sample preparation, and quantification method. TMT/iTRAQ (isobaric labeling) datasets have ratio compression and co-isolation interference biases that differ from label-free quantification (LFQ). DIA datasets require different analysis pipelines than DDA. Check the original publication for methods before reusing data in a meta-analysis or cross-study comparison. Instrument resolution (Orbitrap > ion trap) and acquisition mode (DIA > DDA for completeness) directly affect how many proteins are quantified and at what confidence.

Core Repositories Integrated

Repository	Coverage	Strengths
MassIVE	10,000+ datasets	Rich metadata (summaries, keywords, modifications, contacts), species filtering by taxonomy ID
ProteomeXchange	Aggregates PRIDE, MassIVE, PeptideAtlas, jPOST, iProX	Broadest coverage, standardized PXD accessions
PDC (NCI Proteomics Data Commons)	250+ cancer proteomics studies (CPTAC, ICPC, APOLLO, CBTN, etc.)	Curated disease/site/analytical-fraction metadata, per-gene spectral-count coverage, clinical case linkage, and direct access to the quantitative abundance matrix (not just file listings)
PRIDE Archive	EBI's proteomics repository -- one of the submission repositories ProteomeXchange aggregates	Full-text keyword search directly against title/description/species/tissue/disease (ProteomeXchange's own search is accession/keyword-only with thinner hits); the only one of these four with real FTP/Aspera file download URLs, not just metadata; a reverse protein->project lookup no other tool here provides
PeptideAtlas	ISB's peptide-level observation atlas -- another ProteomeXchange-aggregated repository, but answers a different question than the dataset-level tools above	The canonical record of which tryptic peptides of a protein have actually been OBSERVED by mass spec, and how often -- not which datasets exist

PeptideAtlas: Peptide-Level Observation Evidence

Unlike the dataset-discovery tools above (which answer "what studies exist"), PeptideAtlas_get_observed_peptides answers "for this specific protein, which peptides have actually been detected, and with what confidence" -- a direct protein-level query, not a dataset search. Constrain by biosequence_name (a UniProt accession, e.g. P02768 for serum albumin) to get that protein's peptides, or omit it with a small row_limit to sample the whole build (the default build indexes millions of peptides). Each result gives peptide_sequence, n_observations (spectral count across the whole atlas), n_samples, best_probability (PeptideProphet), and empirical_proteotypic_score (how uniquely this peptide identifies the protein, vs. one shared across a protein family) -- live-verified against real UniProt accessions. Use this to check whether a specific tryptic peptide is actually detectable before designing a targeted-MS (SRM/PRM) assay around it, or to gauge how well-characterized a protein is by MS overall.

Cancer Proteomics via PDC

Unlike MassIVE/ProteomeXchange (general-purpose MS dataset registries returning metadata/file listings), PDC is scoped to cancer proteogenomics programs and can return the actual quantitative data and per-patient clinical metadata directly — useful when the goal is a cancer-cohort reanalysis rather than a generic dataset search.

Tool	Purpose
`PDC_search_studies`	Substring match against curated `disease_type`, `primary_site`, `analytical_fraction` (Proteome/Phosphoproteome/Acetylome/Ubiquitylome/...), `experiment_type` (TMT10/TMT11/iTRAQ/LFQ), program/project name, or the study title. Program acronyms (`CPTAC`, `ICPC`, `APOLLO`) resolve against PDC's controlled vocabulary so they match every study in the program, not just title hits. Check `matched_curated_metadata` per result — `true` means a curated field matched, not just free-text title
`PDC_get_gene_protein`	Given a gene symbol, returns NCBI/HGNC identifiers, all known protein accessions, and per-study spectral-count evidence (presence/abundance evidence — NOT the quantitative ratio) — use to see which PDC studies have measured a gene of interest before picking one to reanalyze
`PDC_list_programs`	Enumerate all programs (CPTAC, ICPC, APOLLO, CBTN, Georgetown, Broad, ...) and their projects
`PDC_get_study_summary`	Full metadata for one `pdc_study_id` (e.g. `PDC000127`): disease type, site, analytical fraction, experiment type, case/aliquot counts, embargo status, file counts by category — the PDC equivalent of `MassIVE_get_dataset`/`ProteomeXchange_get_dataset`
`PDC_get_clinical_data`	Paginated per-case clinical metadata (case ID, disease type, site, demographics) for a study — use to link proteomic findings to patient characteristics
`PDC_get_quant_data_matrix`	The actual quantitative protein-abundance matrix (gene x aliquot, `log2_ratio` by default) — this is the core CPTAC quantitative output, distinct from `PDC_get_gene_protein`'s spectral counts. Gene rows are truncated to `max_genes` (default 50; raise it to pull more) but the aliquot column header is always returned in full — verified live: `PDC000127` (CPTAC CCRCC) reports 9,591 total gene rows

Workflow: PDC_search_studies(query="<disease/site/program>") → confirm scope with PDC_get_study_summary(pdc_study_id=...) → PDC_get_clinical_data for patient context → PDC_get_quant_data_matrix for the actual abundance values to analyze. Feed the resulting matrix into tooluniverse-proteomics-analysis (Phase 2 onward: preprocessing, differential expression, enrichment) rather than re-deriving that logic here.

PRIDE Archive: Full-Text Search, File Downloads, and Reverse Protein Lookup

PRIDE (EBI's proteomics repository) is one of the submission repositories ProteomeXchange indexes -- the same relationship MassIVE has to ProteomeXchange, just a different partner archive. Reach for PRIDE specifically (rather than, or in addition to, ProteomeXchange/MassIVE) when you need: real full-text search (ProteomeXchange's query param matches thinly against title/accession; PRIDE's PRIDE_search_proteomics matches against title, description, species, and tissue, so a query like "phosphorylation" or "COVID-19 proteome" returns far more relevant hits), actual file download URLs (FTP and Aspera links per file -- none of MassIVE/ProteomeXchange/PDC's tools in this skill return downloadable links, only metadata), or a protein-first search ("which datasets contain protein X" has no equivalent in MassIVE or ProteomeXchange here).

Tool	Purpose
`PRIDE_search_proteomics`	Full-text keyword search (`query`, `page_size` default 20 max 100) across project title/description/species/tissue/disease. Returns rich per-hit metadata directly (organisms, organismParts, diseases, instruments, keywords, submitters, labPIs) -- often enough to shortlist without a follow-up detail call
`PRIDE_get_project`	Full metadata for one `accession` (PXD######): adds `sampleProcessingProtocol`/`dataProcessingProtocol` (methods text), `doi`, `submissionType` (COMPLETE vs PARTIAL), `license`, full submitter records -- richer than either `MassIVE_get_dataset` or `ProteomeXchange_get_dataset` for methods detail
`PRIDE_get_project_files`	Per-file listing for one `accession`: `fileName`, `fileCategory`, `fileSizeBytes`, and `publicFileLocations` with real FTP and Aspera download URLs -- the actual next step after `MassIVE`/`ProteomeXchange`/`PDC` metadata calls if the goal is downloading raw data, not just describing it
`PRIDE_get_projects_for_protein`	Reverse lookup: given a UniProt `accession` (e.g. `P04637` for TP53), returns every PXD project accession that identified that protein. PRIDE's other tools are project-centric and cannot answer this; verified live that a well-studied protein like TP53 returns 30+ project accessions -- pair each with `PRIDE_get_project` for detail

Workflow: PRIDE_search_proteomics(query="<keyword>") → PRIDE_get_project(accession=...) for methods/DOI detail → PRIDE_get_project_files(accession=...) for actual download links. Or, protein-first: PRIDE_get_projects_for_protein(accession="<UniProt AC>") → PRIDE_get_project on each hit to evaluate relevance before downloading.

Verified live: PRIDE_search_proteomics(query="breast cancer", page_size=3) returned real recent submissions (e.g. PXD083320, publication date 2026-08-28) with full instrument/organism/disease metadata already populated in the search response itself -- no separate detail call needed to triage relevance.

Workflow Overview

Query (keyword / species / accession)
|
+-- PHASE 0: Input Resolution
|   Determine search type: keyword, species, or accession lookup
|
+-- PHASE 1: Repository Search
|   Search MassIVE and/or ProteomeXchange based on query type
|
+-- PHASE 2: Dataset Detail Retrieval
|   Get full metadata for promising hits
|
+-- PHASE 3: Result Synthesis
    Compile datasets with metadata, publications, and relevance assessment

Phase 0: Input Resolution

Objective: Determine the query type and prepare appropriate search parameters.

Decision Logic

Accession provided (e.g., PXD000001, MSV000079514):
- PXD accession: call ProteomeXchange_get_dataset and optionally MassIVE_get_dataset
- MSV accession: call MassIVE_get_dataset
- Skip Phase 1, go directly to Phase 2
Species name provided (e.g., "human", "mouse"):
- Map to NCBI taxonomy ID: human=9606, mouse=10090, rat=10116, yeast=559292, zebrafish=7955, fly=7227, worm=6239, arabidopsis=3702
- Use MassIVE_search_datasets with species filter
Keyword provided (e.g., "phosphoproteomics", "breast cancer"):
- Use ProteomeXchange_search_datasets with query parameter
- MassIVE does not support keyword search -- use ProteomeXchange for keyword queries

Phase 1: Repository Search

Objective: Find relevant datasets across repositories.

Tools

MassIVE_search_datasets:

page_size: Number of results to return (integer, max 100, default 10)
species: NCBI taxonomy ID string to filter by species (e.g., "9606" for human)
Returns: Array of dataset objects with accessions (array), title, summary, species, instruments, keywords
Note: No keyword/text search parameter -- filtering is by species only

ProteomeXchange_search_datasets:

query: Optional search filter -- keyword or dataset accession (e.g., "phosphoproteomics", "PXD")
limit: Max results (1-50, default 10)
Returns: {data: [{accession, title, species}], metadata: {source, total_returned, query}}

Workflow

For species-specific search:
- Call MassIVE_search_datasets(page_size=20, species="9606") for species-filtered results
- Call ProteomeXchange_search_datasets(limit=20) for broader listing
For keyword search:
- Call ProteomeXchange_search_datasets(query="keyword", limit=20)
- Review titles for relevance
For comprehensive discovery:
- Call both tools in parallel
- Merge results, deduplicate by accession (PXD accessions may appear in both)

Response Format Notes

MassIVE_search_datasets: Returns a direct array (no {data: ...} wrapper)
ProteomeXchange_search_datasets: Returns {data: [...], metadata: {...}}

Phase 2: Dataset Detail Retrieval

Objective: Get full metadata for datasets of interest.

Tools

MassIVE_get_dataset:

accession: Dataset accession -- accepts both MSV and PXD formats (e.g., "MSV000079514", "PXD003971")
Returns: Object with accessions, title, summary, species, instruments, keywords, contacts, publications, modifications

ProteomeXchange_get_dataset:

px_id: ProteomeXchange identifier in PXD format (e.g., "PXD000001")
Returns: {data: {px_id, title, species, identifiers, instruments, publications, file_count}, metadata: {...}}

Workflow

For each promising dataset from Phase 1, call the appropriate detail tool
Extract key metadata: title, species, instruments, publications (PubMed/DOI), modifications
For PXD accessions: prefer ProteomeXchange_get_dataset for file count; use MassIVE_get_dataset for richer summary/keywords

Key Fields to Extract

title: Dataset name/description
species: Organism(s) studied
instruments: Mass spectrometer(s) used (e.g., Orbitrap, Q Exactive, TripleTOF)
publications: PubMed IDs and DOIs for associated papers
modifications: PTMs studied (from MassIVE only)
file_count: Number of raw files (from ProteomeXchange only)
keywords: Topic tags (from MassIVE only)

Phase 3: Result Synthesis

Objective: Compile and present dataset results in a structured format.

Report Format

# Proteomics Dataset Search Results
**Query**: [original query]
**Date**: YYYY-MM-DD
**Repositories searched**: MassIVE, ProteomeXchange

## Summary
Found N datasets matching [criteria].

## Datasets

### 1. [Title]
- **Accession**: PXD/MSV number
- **Species**: [organism]
- **Instruments**: [MS platforms]
- **Publications**: [PubMed IDs / DOIs]
- **Modifications**: [PTMs if available]
- **Files**: [count if available]
- **Summary**: [brief description]

### 2. [Title]
...

## Data Gaps
[Note any limitations in search coverage]

Tool Parameter Reference

Tool	Parameter	Notes
`MassIVE_search_datasets`	`page_size`	Integer, max 100. Default 10
`MassIVE_search_datasets`	`species`	NCBI taxonomy ID as string (e.g., `"9606"` not `9606`)
`MassIVE_get_dataset`	`accession`	Accepts both MSV and PXD formats
`ProteomeXchange_search_datasets`	`query`	Optional keyword or accession filter
`ProteomeXchange_search_datasets`	`limit`	Integer, 1-50
`ProteomeXchange_get_dataset`	`px_id`	PXD format only (e.g., `"PXD000001"`)

Response Format Notes:

MassIVE_search_datasets: Returns direct array of dataset objects (no wrapper)
MassIVE_get_dataset: Returns direct object (no wrapper)
ProteomeXchange_search_datasets: Returns {data: [...], metadata: {...}}
ProteomeXchange_get_dataset: Returns {data: {...}, metadata: {...}}

Fallback Strategies

Situation	Fallback
MassIVE search returns empty	Use ProteomeXchange search (broader coverage)
ProteomeXchange search returns empty	Try broader/simpler query terms
MassIVE_get_dataset fails for PXD accession	Use ProteomeXchange_get_dataset instead
Species taxonomy ID unknown	Search ProteomeXchange by keyword (organism name)
No keyword search results	Try individual terms instead of multi-word queries
Need real download links, not just metadata	Use `PRIDE_get_project_files` -- the only tool here that returns FTP/Aspera URLs
Need "which datasets have protein X"	Use `PRIDE_get_projects_for_protein` -- no other tool here supports protein-first search

Common Species Taxonomy IDs

Species	Taxonomy ID
Human	9606
Mouse	10090
Rat	10116
Zebrafish	7955
Fruit fly	7227
C. elegans	6239
S. cerevisiae	559292
A. thaliana	3702
E. coli	562

Interpretation Framework

Quality Indicator	Good	Acceptable	Caution
Instrument	Orbitrap Exploris/Eclipse, timsTOF	Q Exactive, TripleTOF 6600	Older LTQ, ion trap only
Publication	Peer-reviewed with PubMed ID	Preprint or DOI only	No associated publication
Metadata completeness	Species + instrument + PTMs + summary	Species + instrument only	Title only, no annotations

Interpreting dataset search results:

Datasets with both MassIVE and ProteomeXchange accessions generally have richer metadata; MassIVE provides summaries and keywords while ProteomeXchange provides file counts -- cross-reference both for a complete picture.
Instrument type determines data quality ceiling: high-resolution instruments (Orbitrap, timsTOF) produce higher mass accuracy and more reliable quantification than older ion trap platforms.
A dataset lacking a peer-reviewed publication may still be valuable, but its experimental design and processing pipeline cannot be independently verified -- weight such datasets lower in meta-analyses.

Synthesis questions to address in the report:

Do multiple independent datasets for the same organism/condition show consistent protein identifications, or do discrepancies suggest batch effects?
Is the instrument platform appropriate for the analysis type (e.g., DIA requires high-resolution; TMT requires MS3 or calibrated MS2)?
Are the reported PTM types and species consistent with the user's research question, or is additional filtering needed?

Limitations

MassIVE: No keyword/text search -- only species-based filtering via species parameter
ProteomeXchange: Limited metadata in search results (no summaries or keywords); get details via Dataverse_get_dataset
No full-text search: Cannot search within dataset descriptions or abstracts across repositories
No download via MassIVE/ProteomeXchange/PDC: those tools retrieve metadata only, not raw data files. PRIDE is the exception -- PRIDE_get_project_files returns real FTP/Aspera URLs per file, verified live
Rate limits: Both APIs may throttle under heavy load; keep page_size/limit reasonable
Coverage: ProteomeXchange is the most comprehensive but may lag behind individual repositories for very recent submissions

Integration with Other Skills

Skill	Relationship
`tooluniverse-proteomics-analysis`	Use retrieved datasets as input for MS data analysis
`tooluniverse-protein-modification-analysis`	Find PTM-specific datasets to complement iPTMnet annotations
`tooluniverse-multi-omics-integration`	Discover proteomics datasets for cross-omics integration

References

MassIVE: https://massive.ucsd.edu
ProteomeXchange: http://www.proteomexchange.org
PRIDE: https://www.ebi.ac.uk/pride
ProXI API: https://github.com/PRIDE-Archive/proxi-schemas

About this skill

When to Use This Skill

COMPUTE, DON'T DESCRIBE

KEY PRINCIPLES

Domain Reasoning: Dataset Quality Assessment

Core Repositories Integrated

PeptideAtlas: Peptide-Level Observation Evidence

Cancer Proteomics via PDC

PRIDE Archive: Full-Text Search, File Downloads, and Reverse Protein Lookup

Workflow Overview

Phase 0: Input Resolution

Decision Logic

Phase 1: Repository Search

Tools

Workflow

Response Format Notes

Phase 2: Dataset Detail Retrieval

Tools

Workflow

Key Fields to Extract

Phase 3: Result Synthesis

Report Format

Tool Parameter Reference

Fallback Strategies

Common Species Taxonomy IDs

Interpretation Framework

Limitations

Integration with Other Skills

References