02134nas a2200193   4500000000100000000000100001008004100002260000900043100001600052700001600068700002200084700001900106245012100125856004400246300001400290490000700304520161500311022001401926       2026                            d  c20261 aIsto Huvila1 aOlle Sköld1 aDydimus Zengenene1 aLisa Andersson00aWhat a Standard Makes out of a Process? Data-documentation Standards and Their Consequences to Process Documentation  uhttps://doi.org/10.1108/JD-10-2025-0324  a289–3140 v823 aData-documentation standards offer diverse means to represent processes, an aspect of datasets that generally lack adequate documentation for their reuse. This study aims to generate new knowledge of to what extent data-documentation standards cover and conceptualise data-related processes (i.e. paradata).A set of nine major general domain-agnostic research data standards (Data Package, DataCite Metadata Schema, Dublin Core, OAI-ORE, PREMIS CERIF, DDI, PROV, NetCDF) were analysed using close reading of standards documents to identify elements relevant to representing diverse aspects of data-related processes.A review of popular standards shows that they vary in what processes are represented: many focus on curatorial history and a part on capturing selected aspects of processes for enabling specific types of prioritised forms of (re)use of data. Also, the representations vary and range from complex data models to limited attribute data with parallel variation in their forms and granularity. The variations affect the capacity of standards to accommodate different ontological and epistemic perspectives to processes and their features. The findings underline how the choice of a particular standard – and standardisation as an approach for generating process documentation – has major consequences to what aspect of a process ends up being documented and from what perspective, with consequences to the usefulness and affordances of produced descriptions.To the knowledge of the authors, no previous research on to what extend common data documentation standards accommodate paradata exists.  a0022-0418