LaminDB
Overview
LaminDB is an open-source data framework for biology designed to make data queryable, traceable, reproducible, and FAIR (Findable, Accessible, Interoperable, Reusable). It provides a unified platform that combines lakehouse architecture, lineage tracking, feature stores, biological ontologies, LIMS (Laboratory Information Management System), and ELN (Electronic Lab Notebook) capabilities through a single Python API.
Core Value Proposition:
- Queryability: Search and filter datasets by metadata, features, and ontology terms
- Traceability: Automatic lineage tracking from raw data through analysis to results
- Reproducibility: Version control for data, code, and environment
- FAIR Compliance: Standardized annotations using biological ontologies
When to Use This Skill
Use this skill when:
- Managing biological datasets: scRNA-seq, bulk RNA-seq, spatial transcriptomics, flow cytometry, multi-modal data, EHR data
- Tracking computational workflows: Notebooks, scripts, pipeline execution (Nextflow, Snakemake, Redun)
- Curating and validating data: Schema validation, standardization, ontology-based annotation
- Working with biological ontologies: Genes, proteins, cell types, tissues, diseases, pathways (via Bionty)
- Building data lakehouses: Unified query interface across multiple datasets
- Ensuring reproducibility: Automatic versioning, lineage tracking, environment capture
- Integrating ML pipelines: Connecting with Weights & Biases, MLflow, HuggingFace, scVI-tools
- Deploying data infrastructure: Setting up local or cloud-based data management systems
- Collaborating on datasets: Sharing curated, annotated data with standardized metadata
Core Capabilities
LaminDB provides six interconnected capability areas, each documented in detail in the references folder.
1. Core Concepts and Data Lineage
Core entities:
- Artifacts: Versioned datasets (DataFrame, AnnData, Parquet, Zarr, etc.)
- Records: Experimental entities (samples, perturbations, instruments)
- Runs & Transforms: Computational lineage tracking (what code produced what data)
- Features: Typed metadata fields for annotation and querying
Key workflows:
- Create and version artifacts from files or Python objects
- Track notebook/script execution with
ln.track() and ln.finish()
- Annotate artifacts with typed features
- Visualize data lineage graphs with
artifact.view_lineage()
- Query by provenance (find all outputs from specific code/inputs)
Reference: references/core-concepts.md - Read this for detailed information on artifacts, records, runs, transforms, features, versioning, and lineage tracking.
2. Data Management and Querying
Query capabilities:
- Registry exploration and lookup with auto-complete
- Single record retrieval with
get(), one(), one_or_none()
- Filtering with comparison operators (
__gt, __lte, __contains, __startswith)
- Feature-based queries (query by annotated metadata)
- Cross-registry traversal with double-underscore syntax
- Full-text search across registries
- Advanced logical queries with Q objects (AND, OR, NOT)
- Streaming large datasets without loading into memory
Key workflows:
- Browse artifacts with filters and ordering
- Query by features, creation date, creator, size, etc.
- Stream large files in chunks or with array slicing
- Organize data with hierarchical keys
- Group artifacts into collections
Reference: references/data-management.md - Read this for comprehensive query patterns, filtering examples, streaming strategies, and data organization best practices.
3. Annotation and Validation
Curation process:
- Validation: Confirm datasets match desired schemas
- Standardization: Fix typos, map synonyms to canonical terms
- Annotation: Link datasets to metadata entities for queryability
Schema types:
- Flexible schemas: Validate only known columns, allow additional metadata
- Minimal required schemas: Specify essential columns, permit extras
- Strict schemas: Complete control over structure and values
Supported data types:
- DataFrames (Parquet, CSV)
- AnnData (single-cell genomics)
- MuData (multi-modal)
- SpatialData (spatial transcriptomics)
- TileDB-SOMA (scalable arrays)
Key workflows:
- Define features and schemas for data validation
- Use
DataFrameCurator or AnnDataCurator for validation
- Standardize values with
.cat.standardize()
- Map to ontologies with
.cat.add_ontology()
- Save curated artifacts with schema linkage
- Query validated datasets by features
Reference: references/annotation-validation.md - Read this for detailed curation workflows, schema design patterns, handling validation errors, and best practices.
4. Biological Ontologies
Available ontologies (via Bionty):
- Genes (Ensembl), Proteins (UniProt)
- Cell types (CL), Cell lines (CLO)
- Tissues (Uberon), Diseases (Mondo, DOID)
- Phenotypes (HPO), Pathways (GO)
- Experimental factors (EFO), Developmental stages
- Organisms (NCBItaxon), Drugs (DrugBank)
Key workflows:
- Import public ontologies with
bt.CellType.import_source()
- Search ontologies with keyword or exact matching
- Standardize terms using synonym mapping
- Explore hierarchical relationships (parents, children, ancestors)
- Validate data against ontology terms
- Annotate datasets with ontology records
- Create custom terms and hierarchies
- Handle multi-organism contexts (human, mouse, etc.)
Reference: references/ontologies.md - Read this for comprehensive ontology operations, standardization strategies, hierarchy navigation, and annotation workflows.
5. Integrations
Workflow managers:
- Nextflow: Track pipeline processes and outputs
- Snakemake: Integrate into Snakemake rules
- Redun: Combine with Redun task tracking
MLOps platforms:
- Weights & Biases: Link experiments with data artifacts
- MLflow: Track models and experiments
- HuggingFace: Track model fine-tuning
- scVI-tools: Single-cell analysis workflows
Storage systems:
- Local filesystem, AWS S3, Google Cloud Storage
- S3-compatible (MinIO, Cloudflare R2)
- HTTP/HTTPS endpoints (read-only)
- HuggingFace datasets
Array stores:
- TileDB-SOMA (with cellxgene support)
- DuckDB for SQL queries on Parquet files
Visualization:
- Vitessce for interactive spatial/single-cell visualization
Version control:
- Git integration for source code tracking
Reference: references/integrations.md - Read this for integration patterns, code examples, and troubleshooting for third-party systems.
6. Setup and Deployment
Installation:
- Basic:
uv pip install lamindb
- With extras:
uv pip install 'lamindb[gcp,zarr,fcs]'
- Modules: bionty, wetlab, clinical
Instance types:
- Local SQLite (development)
- Cloud storage + SQLite (small teams)
- Cloud storage + PostgreSQL (production)
Storage options:
- Local filesystem
- AWS S3 with configurable regions and permissions
- Google Cloud Storage
- S3-compatible endpoints (MinIO, Cloudflare R2)
Configuration:
- Cache management for cloud files
- Multi-user system configurations
- Git repository sync
- Environment variables
Deployment patterns:
- Local dev → Cloud production migration
- Multi-region deployments
- Shared storage with personal instances
Reference: references/setup-deployment.md - Read this for detailed installation, configuration, storage setup, database management, security best practices, and troubleshooting.
Common Use Case Workflows
Use Case 1: Single-Cell RNA-seq Analysis with Ontology Validation
import lamindb as ln
import bionty as bt
import anndata as ad
# Start tracking
ln.track(params={"analysis": "scRNA-seq QC and annotation"})
# Import cell type ontology
bt.CellType.import_source()
# Load data
adata = ad.read_h5ad("raw_counts.h5ad")
# Validate and standardize cell types
adata.obs["cell_type"] = bt.CellType.standardize(adata.obs["cell_type"])
# Curate with schema
curator = ln.curators.AnnDataCurator(adata, schema)
curator.validate()
artifact = curator.save_artifact(key="scrna/validated.h5ad")
# Link ontology annotations
cell_types = bt.CellType.from_values(adata.obs.cell_type)
artifact.feature_sets.add_ontology(cell_types)
ln.finish()
Use Case 2: Building a Queryable Data Lakehouse
import lamindb as ln
# Register multiple experiments
for i, file in enumerate(data_files):
artifact = ln.Artifact.from_anndata(
ad.read_h5ad(file),
key=f"scrna/batch_{i}.h5ad",
description=f"scRNA-seq batch {i}"
).save()
# Annotate with features
artifact.features.add_values({
"batch": i,
"tissue": tissues[i],
"condition": conditions[i]
})
# Query across all experiments
immune_datasets = ln.Artifact.filter(
key__startswith="scrna/",
tissue="PBMC",
condition="treated"
).to_dataframe()
# Load specific datasets
for artifact in immune_datasets:
adata = artifact.load()
# Analyze
Use Case 3: ML Pipeline with W&B Integration
import lamindb as ln
import wandb
# Initialize both systems
wandb.init(project="drug-response", name="exp-42")
ln.track(params={"model": "random_forest", "n_estimators": 100})
# Load training data from LaminDB
train_artifact = ln.Artifact.get(key="datasets/train.parquet")
train_data = train_artifact.load()
# Train model
model = train_model(train_data)
# Log to W&B
wandb.log({"accuracy": 0.95})
# Save model in LaminDB with W&B linkage
import joblib
joblib.dump(model, "model.pkl")
model_artifact = ln.Artifact("model.pkl", key="models/exp-42.pkl").save()
model_artifact.features.add_values({"wandb_run_id": wandb.run.id})
ln.finish()
wandb.finish()
Use Case 4: Nextflow Pipeline Integration
# In Nextflow process script
import lamindb as ln
ln.track()
# Load input artifact
input_artifact = ln.Artifact.get(key="raw/batch_${batch_id}.fastq.gz")
input_path = input_artifact.cache()
# Process (alignment, quantification, etc.)
# ... Nextflow process logic ...
# Save output
output_artifact = ln.Artifact(
"counts.csv",
key="processed/batch_${batch_id}_counts.csv"
).save()
ln.finish()
Getting Started Checklist
To start using LaminDB effectively:
Installation & Setup (references/setup-deployment.md)
- Install LaminDB and required extras
- Authenticate with
lamin login
- Initialize instance with
lamin init --storage ...
Learn Core Concepts (references/core-concepts.md)
- Understand Artifacts, Records, Runs, Transforms
- Practice creating and retrieving artifacts
- Implement
ln.track() and ln.finish() in workflows
Master Querying (references/data-management.md)
- Practice filtering and searching registries
- Learn feature-based queries
- Experiment with streaming large files
Set Up Validation (references/annotation-validation.md)
- Define features relevant to research domain
- Create schemas for data types
- Practice curation workflows
Integrate Ontologies (references/ontologies.md)
- Import relevant biological ontologies (genes, cell types, etc.)
- Validate existing annotations
- Standardize metadata with ontology terms
Connect Tools (references/integrations.md)
- Integrate with existing workflow managers
- Link ML platforms for experiment tracking
- Configure cloud storage and compute
Key Principles
Follow these principles when working with LaminDB:
Track everything: Use ln.track() at the start of every analysis for automatic lineage capture
Validate early: Define schemas and validate data before extensive analysis
Use ontologies: Leverage public biological ontologies for standardized annotations
Organize with keys: Structure artifact keys hierarchically (e.g., project/experiment/batch/file.h5ad)
Query metadata first: Filter and search before loading large files
Version, don't duplicate: Use built-in versioning instead of creating new keys for modifications
Annotate with features: Define typed features for queryable metadata
Document thoroughly: Add descriptions to artifacts, schemas, and transforms
Leverage lineage: Use view_lineage() to understand data provenance
Start local, scale cloud: Develop locally with SQLite, deploy to cloud with PostgreSQL
Reference Files
This skill includes comprehensive reference documentation organized by capability:
references/core-concepts.md - Artifacts, records, runs, transforms, features, versioning, lineage
references/data-management.md - Querying, filtering, searching, streaming, organizing data
references/annotation-validation.md - Schema design, curation workflows, validation strategies
references/ontologies.md - Biological ontology management, standardization, hierarchies
references/integrations.md - Workflow managers, MLOps platforms, storage systems, tools
references/setup-deployment.md - Installation, configuration, deployment, troubleshooting
Read the relevant reference file(s) based on the specific LaminDB capability needed for the task at hand.
Additional Resources
1---2name: lamindb3description: This skill should be used when working with LaminDB, an open-source data framework for biology that makes data queryable, traceable, reproducible, and FAIR. Use when managing biological datasets (scRNA-seq, spatial, flow cytometry, etc.), tracking computational workflows, curating and validating data with biological ontologies, building data lakehouses, or ensuring data lineage and reproducibility in biological research. Covers data management, annotation, ontologies (genes, cell types, diseases, tissues), schema validation, integrations with workflow managers (Nextflow, Snakemake) and MLOps platforms (W&B, MLflow), and deployment strategies.4category: biology5license: Apache-2.0 license6metadata:7 source: https://skillmd.com/skills/synthetic-sciences/lamindb8 upstream: K-Dense-AI/scientific-agent-skills9 upstream-url: https://github.com/K-Dense-AI/scientific-agent-skills10 upstream-path: skills/lamindb11 upstream-license: MIT12 upstream-relationship: derived13 adapted-by: Synthetic Sciences14 skill-author: K-Dense Inc.15---1617# LaminDB1819## Overview2021LaminDB is an open-source data framework for biology designed to make data queryable, traceable, reproducible, and FAIR (Findable, Accessible, Interoperable, Reusable). It provides a unified platform that combines lakehouse architecture, lineage tracking, feature stores, biological ontologies, LIMS (Laboratory Information Management System), and ELN (Electronic Lab Notebook) capabilities through a single Python API.2223**Core Value Proposition:**24- **Queryability**: Search and filter datasets by metadata, features, and ontology terms25- **Traceability**: Automatic lineage tracking from raw data through analysis to results26- **Reproducibility**: Version control for data, code, and environment27- **FAIR Compliance**: Standardized annotations using biological ontologies2829## When to Use This Skill3031Use this skill when:3233- **Managing biological datasets**: scRNA-seq, bulk RNA-seq, spatial transcriptomics, flow cytometry, multi-modal data, EHR data34- **Tracking computational workflows**: Notebooks, scripts, pipeline execution (Nextflow, Snakemake, Redun)35- **Curating and validating data**: Schema validation, standardization, ontology-based annotation36- **Working with biological ontologies**: Genes, proteins, cell types, tissues, diseases, pathways (via Bionty)37- **Building data lakehouses**: Unified query interface across multiple datasets38- **Ensuring reproducibility**: Automatic versioning, lineage tracking, environment capture39- **Integrating ML pipelines**: Connecting with Weights & Biases, MLflow, HuggingFace, scVI-tools40- **Deploying data infrastructure**: Setting up local or cloud-based data management systems41- **Collaborating on datasets**: Sharing curated, annotated data with standardized metadata4243## Core Capabilities4445LaminDB provides six interconnected capability areas, each documented in detail in the references folder.4647### 1. Core Concepts and Data Lineage4849**Core entities:**50- **Artifacts**: Versioned datasets (DataFrame, AnnData, Parquet, Zarr, etc.)51- **Records**: Experimental entities (samples, perturbations, instruments)52- **Runs & Transforms**: Computational lineage tracking (what code produced what data)53- **Features**: Typed metadata fields for annotation and querying5455**Key workflows:**56- Create and version artifacts from files or Python objects57- Track notebook/script execution with `ln.track()` and `ln.finish()`58- Annotate artifacts with typed features59- Visualize data lineage graphs with `artifact.view_lineage()`60- Query by provenance (find all outputs from specific code/inputs)6162**Reference:** `references/core-concepts.md` - Read this for detailed information on artifacts, records, runs, transforms, features, versioning, and lineage tracking.6364### 2. Data Management and Querying6566**Query capabilities:**67- Registry exploration and lookup with auto-complete68- Single record retrieval with `get()`, `one()`, `one_or_none()`69- Filtering with comparison operators (`__gt`, `__lte`, `__contains`, `__startswith`)70- Feature-based queries (query by annotated metadata)71- Cross-registry traversal with double-underscore syntax72- Full-text search across registries73- Advanced logical queries with Q objects (AND, OR, NOT)74- Streaming large datasets without loading into memory7576**Key workflows:**77- Browse artifacts with filters and ordering78- Query by features, creation date, creator, size, etc.79- Stream large files in chunks or with array slicing80- Organize data with hierarchical keys81- Group artifacts into collections8283**Reference:** `references/data-management.md` - Read this for comprehensive query patterns, filtering examples, streaming strategies, and data organization best practices.8485### 3. Annotation and Validation8687**Curation process:**881. **Validation**: Confirm datasets match desired schemas892. **Standardization**: Fix typos, map synonyms to canonical terms903. **Annotation**: Link datasets to metadata entities for queryability9192**Schema types:**93- **Flexible schemas**: Validate only known columns, allow additional metadata94- **Minimal required schemas**: Specify essential columns, permit extras95- **Strict schemas**: Complete control over structure and values9697**Supported data types:**98- DataFrames (Parquet, CSV)99- AnnData (single-cell genomics)100- MuData (multi-modal)101- SpatialData (spatial transcriptomics)102- TileDB-SOMA (scalable arrays)103104**Key workflows:**105- Define features and schemas for data validation106- Use `DataFrameCurator` or `AnnDataCurator` for validation107- Standardize values with `.cat.standardize()`108- Map to ontologies with `.cat.add_ontology()`109- Save curated artifacts with schema linkage110- Query validated datasets by features111112**Reference:** `references/annotation-validation.md` - Read this for detailed curation workflows, schema design patterns, handling validation errors, and best practices.113114### 4. Biological Ontologies115116**Available ontologies (via Bionty):**117- Genes (Ensembl), Proteins (UniProt)118- Cell types (CL), Cell lines (CLO)119- Tissues (Uberon), Diseases (Mondo, DOID)120- Phenotypes (HPO), Pathways (GO)121- Experimental factors (EFO), Developmental stages122- Organisms (NCBItaxon), Drugs (DrugBank)123124**Key workflows:**125- Import public ontologies with `bt.CellType.import_source()`126- Search ontologies with keyword or exact matching127- Standardize terms using synonym mapping128- Explore hierarchical relationships (parents, children, ancestors)129- Validate data against ontology terms130- Annotate datasets with ontology records131- Create custom terms and hierarchies132- Handle multi-organism contexts (human, mouse, etc.)133134**Reference:** `references/ontologies.md` - Read this for comprehensive ontology operations, standardization strategies, hierarchy navigation, and annotation workflows.135136### 5. Integrations137138**Workflow managers:**139- Nextflow: Track pipeline processes and outputs140- Snakemake: Integrate into Snakemake rules141- Redun: Combine with Redun task tracking142143**MLOps platforms:**144- Weights & Biases: Link experiments with data artifacts145- MLflow: Track models and experiments146- HuggingFace: Track model fine-tuning147- scVI-tools: Single-cell analysis workflows148149**Storage systems:**150- Local filesystem, AWS S3, Google Cloud Storage151- S3-compatible (MinIO, Cloudflare R2)152- HTTP/HTTPS endpoints (read-only)153- HuggingFace datasets154155**Array stores:**156- TileDB-SOMA (with cellxgene support)157- DuckDB for SQL queries on Parquet files158159**Visualization:**160- Vitessce for interactive spatial/single-cell visualization161162**Version control:**163- Git integration for source code tracking164165**Reference:** `references/integrations.md` - Read this for integration patterns, code examples, and troubleshooting for third-party systems.166167### 6. Setup and Deployment168169**Installation:**170- Basic: `uv pip install lamindb`171- With extras: `uv pip install 'lamindb[gcp,zarr,fcs]'`172- Modules: bionty, wetlab, clinical173174**Instance types:**175- Local SQLite (development)176- Cloud storage + SQLite (small teams)177- Cloud storage + PostgreSQL (production)178179**Storage options:**180- Local filesystem181- AWS S3 with configurable regions and permissions182- Google Cloud Storage183- S3-compatible endpoints (MinIO, Cloudflare R2)184185**Configuration:**186- Cache management for cloud files187- Multi-user system configurations188- Git repository sync189- Environment variables190191**Deployment patterns:**192- Local dev → Cloud production migration193- Multi-region deployments194- Shared storage with personal instances195196**Reference:** `references/setup-deployment.md` - Read this for detailed installation, configuration, storage setup, database management, security best practices, and troubleshooting.197198## Common Use Case Workflows199200### Use Case 1: Single-Cell RNA-seq Analysis with Ontology Validation201202```python203import lamindb as ln204import bionty as bt205import anndata as ad206207# Start tracking208ln.track(params={"analysis": "scRNA-seq QC and annotation"})209210# Import cell type ontology211bt.CellType.import_source()212213# Load data214adata = ad.read_h5ad("raw_counts.h5ad")215216# Validate and standardize cell types217adata.obs["cell_type"] = bt.CellType.standardize(adata.obs["cell_type"])218219# Curate with schema220curator = ln.curators.AnnDataCurator(adata, schema)221curator.validate()222artifact = curator.save_artifact(key="scrna/validated.h5ad")223224# Link ontology annotations225cell_types = bt.CellType.from_values(adata.obs.cell_type)226artifact.feature_sets.add_ontology(cell_types)227228ln.finish()229```230231### Use Case 2: Building a Queryable Data Lakehouse232233```python234import lamindb as ln235236# Register multiple experiments237for i, file in enumerate(data_files):238 artifact = ln.Artifact.from_anndata(239 ad.read_h5ad(file),240 key=f"scrna/batch_{i}.h5ad",241 description=f"scRNA-seq batch {i}"242 ).save()243244 # Annotate with features245 artifact.features.add_values({246 "batch": i,247 "tissue": tissues[i],248 "condition": conditions[i]249 })250251# Query across all experiments252immune_datasets = ln.Artifact.filter(253 key__startswith="scrna/",254 tissue="PBMC",255 condition="treated"256).to_dataframe()257258# Load specific datasets259for artifact in immune_datasets:260 adata = artifact.load()261 # Analyze262```263264### Use Case 3: ML Pipeline with W&B Integration265266```python267import lamindb as ln268import wandb269270# Initialize both systems271wandb.init(project="drug-response", name="exp-42")272ln.track(params={"model": "random_forest", "n_estimators": 100})273274# Load training data from LaminDB275train_artifact = ln.Artifact.get(key="datasets/train.parquet")276train_data = train_artifact.load()277278# Train model279model = train_model(train_data)280281# Log to W&B282wandb.log({"accuracy": 0.95})283284# Save model in LaminDB with W&B linkage285import joblib286joblib.dump(model, "model.pkl")287model_artifact = ln.Artifact("model.pkl", key="models/exp-42.pkl").save()288model_artifact.features.add_values({"wandb_run_id": wandb.run.id})289290ln.finish()291wandb.finish()292```293294### Use Case 4: Nextflow Pipeline Integration295296```python297# In Nextflow process script298import lamindb as ln299300ln.track()301302# Load input artifact303input_artifact = ln.Artifact.get(key="raw/batch_${batch_id}.fastq.gz")304input_path = input_artifact.cache()305306# Process (alignment, quantification, etc.)307# ... Nextflow process logic ...308309# Save output310output_artifact = ln.Artifact(311 "counts.csv",312 key="processed/batch_${batch_id}_counts.csv"313).save()314315ln.finish()316```317318## Getting Started Checklist319320To start using LaminDB effectively:3213221. **Installation & Setup** (`references/setup-deployment.md`)323 - Install LaminDB and required extras324 - Authenticate with `lamin login`325 - Initialize instance with `lamin init --storage ...`3263272. **Learn Core Concepts** (`references/core-concepts.md`)328 - Understand Artifacts, Records, Runs, Transforms329 - Practice creating and retrieving artifacts330 - Implement `ln.track()` and `ln.finish()` in workflows3313323. **Master Querying** (`references/data-management.md`)333 - Practice filtering and searching registries334 - Learn feature-based queries335 - Experiment with streaming large files3363374. **Set Up Validation** (`references/annotation-validation.md`)338 - Define features relevant to research domain339 - Create schemas for data types340 - Practice curation workflows3413425. **Integrate Ontologies** (`references/ontologies.md`)343 - Import relevant biological ontologies (genes, cell types, etc.)344 - Validate existing annotations345 - Standardize metadata with ontology terms3463476. **Connect Tools** (`references/integrations.md`)348 - Integrate with existing workflow managers349 - Link ML platforms for experiment tracking350 - Configure cloud storage and compute351352## Key Principles353354Follow these principles when working with LaminDB:3553561. **Track everything**: Use `ln.track()` at the start of every analysis for automatic lineage capture3573582. **Validate early**: Define schemas and validate data before extensive analysis3593603. **Use ontologies**: Leverage public biological ontologies for standardized annotations3613624. **Organize with keys**: Structure artifact keys hierarchically (e.g., `project/experiment/batch/file.h5ad`)3633645. **Query metadata first**: Filter and search before loading large files3653666. **Version, don't duplicate**: Use built-in versioning instead of creating new keys for modifications3673687. **Annotate with features**: Define typed features for queryable metadata3693708. **Document thoroughly**: Add descriptions to artifacts, schemas, and transforms3713729. **Leverage lineage**: Use `view_lineage()` to understand data provenance37337410. **Start local, scale cloud**: Develop locally with SQLite, deploy to cloud with PostgreSQL375376## Reference Files377378This skill includes comprehensive reference documentation organized by capability:379380- **`references/core-concepts.md`** - Artifacts, records, runs, transforms, features, versioning, lineage381- **`references/data-management.md`** - Querying, filtering, searching, streaming, organizing data382- **`references/annotation-validation.md`** - Schema design, curation workflows, validation strategies383- **`references/ontologies.md`** - Biological ontology management, standardization, hierarchies384- **`references/integrations.md`** - Workflow managers, MLOps platforms, storage systems, tools385- **`references/setup-deployment.md`** - Installation, configuration, deployment, troubleshooting386387Read the relevant reference file(s) based on the specific LaminDB capability needed for the task at hand.388389## Additional Resources390391- **Official Documentation**: https://docs.lamin.ai392- **API Reference**: https://docs.lamin.ai/api393- **GitHub Repository**: https://github.com/laminlabs/lamindb394- **Tutorial**: https://docs.lamin.ai/tutorial395- **FAQ**: https://docs.lamin.ai/faq396