responses.build is a workflow for harmonising physiological response-curve data — leaf gas exchange, hydraulic vulnerability, and fluorescence response curves — from disconnected primary sources into a documented, relational structure.
It is a fork of traits.build, which harmonises single-valued trait data. That engine assumes a measurement is one value for one entity. A response curve is not: it is a set of paired measurements, taken across a driver gradient, that belong together as one identifiable curve. Building AusFizz on traits.build meant encoding the driver, the curve identity, and the instrument settings inside the contexts block — which works, but makes each dataset's metadata large, repetitive, and hard to query. responses.build exists to give response curves a first-class representation instead.
Experimental, and deliberately so. The initial commit is traits.build (develop, commit c2be7f9) with nothing changed but the package's own identity. Databases built with responses.build are byte-identical to those built with traits.build, apart from the engine version stamp — this is verified, and the check is kept as a regression test so divergence stays deliberate and visible.
The response-curve data model is not implemented yet. See PLAN.md for what is decided, what is open, and the compatibility constraints any change has to respect.
responses.build intentionally keeps traits.build's public API — dataset_configure(), dataset_process(), dataset_update_taxonomy(), build_setup_pipeline(), and the rest. A database repository switches engines by changing which package it loads, and nothing else.
Two pieces of upstream identity are kept on purpose, because downstream tooling depends on them:
traits.build, because austraits dispatches on it (print.traits.build).isCompiledBy related-identifier URL https://github.com/traitecoevo/traits.build, because austraits string-matches that URL to decide whether a database is readable at all. It is a compatibility handshake, not a provenance claim.Both are pinned by tests. Changing either requires a coordinated change in austraits; see PLAN.md.
| Repo | What it is |
|---|---|
responses.build |
This repo: the engine |
AusFizz |
The compilation intended for public release, and the source of truth for shared configuration |
ausfizz-private |
Restricted datasets that cannot be released yet, built by the same pipeline and merged on demand |
File issues here for all three, including data issues about the compilations. ausfizz and ausfizz-private are private, and Actions are blocked on private repos across the org, so issues filed there never reach the board; this repo is public, where Actions are unmetered. Everything auto-adds to the AusFizz board (#19), not the family-wide AusTraits board. This repo is public — keep restricted data out of issues.
Splitting the data across two repositories is lossless: building AusFizz's datasets in two groups and binding them with austraits::bind_databases() reproduces every table of a single combined build exactly. The merged object keeps only one metadata block.
# install.packages("remotes")
# remotes::install_github("traitecoevo/responses.build")
install.packages("responses.build", repos = c('https://traitecoevo.r-universe.dev', 'https://cloud.r-project.org'))
Identical to traits.build. From the root of a database repository:
library(responses.build)
build_setup_pipeline(method = "remake", database_name = "AusFizz")
AusFizz <- remake::make("AusFizz")
The data model and workflow concepts are shared with traits.build and are documented in the traits.build book. Read that first. This repository documents only where responses.build departs from it.
responses.build derives from the traits.build workflow. Until it has its own paper, please cite:
Wenk E, Bal P, Coleman D, Gallagher R, Yang S, Falster DS (2024) traits.build: A data model, workflow and R package for building harmonised ecological trait databases. Ecological Informatics 83:102773. https://doi.org/10.1016/j.ecoinf.2024.102773
responses.build is part of the AusTraits family of packages maintained by the AusTraits team. See austraits.org for the project, the data, and the people behind it.
Cross-package knowledge and governance live in austraits-meta — start with its AGENTS.md and the issue & labelling guide.
AusTraits is made possible by contributions from our partner organisations — the University of New South Wales, Western Sydney University, Botanic Gardens of Sydney, the University of Melbourne, the Atlas of Living Australia, and the Australian Government Department of Climate Change, Energy, the Environment and Water — and from our advisory board, data contributors, and past partners.
AusTraits is a co-investment partnership with the Australian Research Data Commons (ARDC) through the Planet Research Data Commons (DOI: 10.3565/nyk4-4r91). The ARDC is enabled by the Australian Government's National Collaborative Research Infrastructure Strategy (NCRIS).
BSD 2-clause, inherited from traits.build. See LICENCE.