Actions Reference
BioMapper provides 25+ self-registering actions for biological data processing. All actions follow the 2025 standardizations for parameter naming, context handling, and type safety.
Data Operations
Protein Actions
Metabolite Actions
Chemistry Actions
Quick Reference
Data Operations
Action |
Description |
|---|---|
|
Load biological identifiers from CSV/TSV files |
|
Combine multiple datasets with deduplication |
|
Apply filtering criteria to datasets |
|
Export results to various formats including CSV, JSON, and Excel |
|
Apply Python expressions to transform data columns |
|
Enhanced expression-based data transformation |
|
Parse and extract identifiers from composite fields |
Protein Actions
Action |
Description |
|---|---|
|
Extract UniProt IDs from compound reference fields |
|
Standardize protein accession formats |
Metabolite Actions
Action |
Description |
|---|---|
|
Nightingale NMR platform matching |
|
AI-powered semantic matching |
|
Vector-based metabolite matching using HMDB embeddings |
|
Fuzzy string matching for metabolite names |
|
RaMP database integration for metabolite mapping |
|
Progressive multi-stage semantic metabolite matching |
Chemistry Actions
Action |
Description |
|---|---|
|
Match clinical test names using fuzzy string matching |
Integration Actions
Action |
Description |
|---|---|
|
Upload and sync results to Google Drive with chunked transfer |
|
Enhanced Google Drive sync with improved error handling |
Usage Example
name: protein_processing_workflow
description: Complete protein data processing and export
steps:
- name: load_source
action:
type: LOAD_DATASET_IDENTIFIERS
params:
file_path: "/data/ukbb_proteins.csv"
identifier_column: "uniprot"
output_key: "source_data"
- name: extract_uniprot_ids
action:
type: PROTEIN_EXTRACT_UNIPROT_FROM_XREFS
params:
input_key: "source_data"
xref_column: "protein_refs"
output_key: "extracted_data"
- name: normalize_accessions
action:
type: PROTEIN_NORMALIZE_ACCESSIONS
params:
input_key: "extracted_data"
accession_column: "uniprot_id"
output_key: "normalized_data"
- name: filter_results
action:
type: FILTER_DATASET
params:
input_key: "normalized_data"
conditions:
- "confidence > 0.8"
output_key: "filtered_data"
- name: export_results
action:
type: EXPORT_DATASET
params:
input_key: "filtered_data"
file_path: "/results/processed_proteins.csv"
2025 Standardizations
- Parameter Naming
All actions use standardized parameter names:
input_key(notdataset_key,data_key)output_key(notresult_key,target_key)file_path(notfilepath,input_file)
- Context Handling
Actions use UniversalContext wrapper for robust context handling across different execution environments.
- Type Safety
Actions inherit from TypedStrategyAction with Pydantic parameter validation and structured results.
- Performance
All actions are audited for algorithmic complexity to prevent O(n²)+ performance issues.
- File Loading
Uses BiologicalFileLoader for robust parsing with automatic encoding detection and biological data optimization.
Strategy File Locations
Strategy YAML files are located in src/biomapper/configs/strategies/ and organized by:
Entity Type:
prot_*,met_*,chem_*,multi_*Source-Target:
ukb_to_hpa,arv_to_kg2cApproach:
uniprot_v1_base,semantic_v1_enhanced
Example: prot_ukb_to_hpa_uniprot_v1_base.yaml
—
## Verification Sources Last verified: 2025-08-22
This documentation was verified against the following project resources:
/biomapper/src/actions/ (comprehensive action implementations - verified 25+ registered actions)
/biomapper/src/actions/registry.py (global ACTION_REGISTRY and @register_action decorator system)
/biomapper/src/actions/typed_base.py (TypedStrategyAction base class with Pydantic models)
/biomapper/CLAUDE.md (2025 standardization requirements and architectural patterns)
/biomapper/src/configs/strategies/ (YAML strategy file organization and examples)
/biomapper/pyproject.toml (project dependencies and package structure)