Documentation
Documentation for BOLD Forensics is organised in four layers: using the workbench, the subsystems and analytical methods behind it, the programming interfaces, and platform administration. A shared reference section holds the data standards, lookup tables and release notes that every layer relies on.
Pages are being written layer by layer. Each is marked as available, as held elsewhere, or as planned.
Start from your role
-
Technician
Registers specimens, uploads sequences and attaches evidence files.
-
Project manager
Sets up projects and datasets, decides who can see them and reviews completeness.
-
Analyst or reviewer
Runs analyses, interprets reports and prepares or reviews expert statements.
-
Platform administrator
Creates accounts, maintains reference lists and oversees the work on the platform.
-
Developer or integrator
Connects other systems to the platform or builds new analytical methods.
Formats
- How-to
- Video walkthrough
- Workflow animation
- Screenshots
- Reference
Status
- Available
- Elsewhere
- Planned
Layer 1: Using the workbench
How work is organised, how to get data in, and how to run analyses and prepare statements. Written for people new to the platform.
For technicians, project managers, analysts and reviewersGetting started
What the workbench is, your account, and finding your way around.
Projects, datasets and access
The containers that hold records and decide who can see them.
Records and evidence review
What a record holds and the views for checking it against its evidence.
Adding specimens and sequences
Getting records into the platform, in bulk or one at a time.
Attaching evidence files
Photographs, documents, chromatograms, fingerprints and notebooks, stored with the record.
Running analyses
Choosing records, configuring a method, and reading the report.
Expert statements
Statements prepared from a record for use as evidence.
How the platform handles your data
Access, logging and retention as they are implemented.
Layer 2: Subsystems and analytical modules
The services behind the workbench, what each analytical method computes, and how new methods are built.
For analysts, laboratory managers, technical reviewers and developersHow the platform fits together
The services, how data moves between them, and how they trust each other.
Record store and search
Where records live and how they are searched and summarised.
BioStor file storage
How evidence files are typed, processed and kept.
Analysis service
How jobs are queued, run and returned.
Analytical methods
One page per method: purpose, inputs, the parameters actually applied, outputs and limitations.
Identification engine
The public identification service and its reference libraries.
Method validation and quality
What is known about each method's performance and limits.
- Software, versions and citations
- Known limitations of the methods
- Validation studies
Building new analyses
Creating a method from the template module and running it within the platform.
Layer 3: APIs
Programming interfaces for each service, with authentication, conventions and worked examples.
For developers and systems that connect to the platformGetting started
Which API to use, how to authenticate, and the conventions they share.
- Which API to use
- Authentication
- Conventions and errors
Endpoint references
Generated from each service.
- Workbench API
- Data API
- Analysis API
- BioStor API
Webhooks
Notifications BioStor sends when processing finishes.
- BioStor webhooks
Recipes
Worked examples for common integrations.
- Submit an analysis and collect the result
- Upload a file and attach it to a record
- Load specimen records in bulk
- Search and export records
Layer 4: Administration
Creating accounts, maintaining reference lists and overseeing the work on the platform, using Platform Management.
For platform administratorsAccounts
Who administers the platform and how accounts are created and managed.
People and institutions
The registries that statements and records draw on.
Reference lists
Markers, primers, geography and taxonomy.
Projects and datasets
Administering recordsets across the platform.
Oversight
Watching the work that flows through the platform.
Reference
Material every layer refers to.
Data standards
The Barcode Core Data Model and the forensic extension.
- Barcode Core Data Model (BCDM)
- BCDM forensic extension
- Field dictionary
- Controlled vocabularies and validation rules
- Darwin Core crosswalk
- Upload templates
Quick reference
Tables to look things up in.
- Access levels at a glance
- File types and limits
- Upload and job statuses
- Glossary
Help and updates
- Release notes
- Frequently asked questions
- Support
- System status
Platform operations
Guides for the people who install and run the platform are kept separately and are not published here. They cover installation and environments, deployment, server hardening, backups and restore, monitoring, and network allowlists.