Data-as-a-product: A framework for collaborative data wrangling
summary
A reproducible framework called daapr packages data wrangling into versioned, shareable “data products” and is actively used at Bristol Myers Squibb across exploratory analyses, with some repos showing commits since 2022. It versions code via Git/GitHub, environment via renv, and data via pins, uses derivation functions and optional targets pipelines, currently supports RDS/QS and remote boards, plans parquet support, and reports successful collaborative reuse with reader/writer/owner onboarding roles and documented credential and Git workflows.
AI-written summary · about
chapters (18)
- 0:00Reproducible data wrangling
- 1:09Ad hoc analysis challenges
- 2:35Data products for analysis
- 3:36DAAPR framework overview
- 4:19Versioning everything
- 5:48DAAPR workflow steps
- 7:14Derivation code in DAAPR
- 8:21Data product object structure
- 9:28Versioning and deploying products
- 10:32Iterating on data products
- 11:14Collaboration in repos
- 12:22Adoption barriers
- 13:26DAAPR onboarding roles
- 14:48Proving framework success
- 15:11Adoption roadblocks
- 16:55User troubleshooting
- 17:16DAAPR resources and future
- 18:41Q&A
related talks
24mMake data central feature
20mModernizing the Data Science Toolkit of a 40-year-old Market Research Company
22mData as a Product: Transforming Analytics for Business Success
25mUnpacking The Data Product Experience So Far
16mProduct Eyes – Seeing Data In A New Light To Build Valuable Products
39mData Mesh: Why, What and How
24mData Versioning Explained the Open Source Way
30mData Products 101: From Data Chaos to Clarity
