TimescaleDB vs xportr

xportr applies CDISC metadata — variable types, lengths, labels, formats, ordering — to R data frames and writes the SAS transport files that go into regulatory submissions. Since v0.4.0 the package has had a single entry point, xportr_process(), that runs the whole chain and writes, and metadata arrives as a plain specification rather than a metacore object. The v0.5.0 release in January 2026 finished the cleanup by deleting every deprecated argument left over from that redesign.

The work has moved from building the pipeline to defending it against the ways submission data actually arrives: grouped data frames now raise a warning, date and time variables get class checks, illegal characters are resolved rather than erroring, and xportr_write() warns before a file crosses 5GB instead of producing an unusable artifact. Contributor volume is high and spread across sponsors — Atorus, Roche, GSK and others show up in the PR lists — which is what keeps a validated-context package moving without a single owner.

With deprecations cleared in 0.5.0, the next cycle likely targets more input-shape validation of the kind 0.5.0 started — the grouped-data and datetime-class checks read as the first two of a series. Nothing in these entries points to a new output format.