scieee AI-readable full text Open interactive document viewer

Building Robust Practices for Research Outputs: Supporting Quality and Assessment

Esposito, Alessandra; Ong, Tiffany; Ciula, Arianna

Abstract

Research Software Engineering (RSE) is no longer a hidden force behind scientific discovery—it is a cornerstone of research excellence. As modern research becomes increasingly computational, the role of RSEs has evolved from coding assistants to essential contributors who drive innovation, ensure reproducibility, and elevate the quality of scientific outputs. Departing from the experience of an embedded RSE team in the arts and humanities, this talk explores the dual identity of RSEs: as both enablers of high-impact research and as integral components of human digital research infrastructure. Central to this discussion are two lightweight but powerful tools: the KDL Checklist Document for digital outputs assessment and the Project Release Document (PRD). The Checklist is a practical tool meant for academic colleagues to guide them through a holistic assessment of their digital output when submitting to the UK research evaluation framework (REF). The PRD is meant to be used internally by a KDL project sub-team to ensure the overall suitability of the digital output ahead of its release. These documents are meant to guide the King’s Digital Lab team and its partners through critical development milestones, ensuring that research software and associated outputs are not only functional, but also reproducible, maintainable, and robust. From versioning and documentation to testing and licensing, these tools embed best practices directly into the release process and review of outputs. The talk will also reflect on the difficulties encountered when introducing new practices and how to best socialise them both internally and with partners. By framing RSE as infrastructure, we acknowledge the people, practices, and principles that underpin trustworthy research. This perspective elevates the conversation beyond code quality to institutional and lab or departmental-level strategy— where integrating RSE good practices translates into investment in research reliability, scalability, and long-term impact. A recording of this session is available on YouTube: https://youtu.be/npx6oENLe6U

Full text

Dr Alessandra Esposito Research Software Project manager Building Robust Practices for Research Outputs. Supporting Quality and Assessment Authors: Alessandra Esposito, Tiffany Ong, Arianna Ciula 9 September 2025 - RSECon 2025 Roadmap – What we'll cover How the tools work together Complementary roles in supporting quality and reproducibility. How the tools ensure quality From licensing to accessibility: what high-quality outputs look like. Introducing two key tools Overview of the KDL Checklist Document for digital outputs assessment and Project Release Document (PRD). Why quality assessment in digital outputs matters Understanding the research context and RSE’s evolving role. Lessons learned and Takeaways What we learned and what you can apply. ▪Modern digital humanities research is becoming increasingly computational (software, datasets, digital editions). ▪Digital outputs must meet research domain criteria and digital/software standards. ▪The REF (Research Evaluation Framework) recognises digital outputs as research outputs. ▪But how do we ensure quality, originality, sustainability in these diverse formats in an integrated manner? Matters 1.Why Quality Assessment in Digital Outputs 3 ▪The RSE have a holistic role in research process and production. ▪They are a key part of human digital infrastructure: integrating design and development to co-produce robust research outputs. ▪RSEs as central actors in enabling world-leading research. Matters 1.Why Quality Assessment in Digital Outputs The Dual Role of RSEs 4 1. The Checklist for Digital Output Assessment key 2.Introducing two tools 2. The Project Release Document (PRD) 5 key 2.Introducing two tools 1.The Checklist for Digital Output Assessment Purpose: A practical guide for academic and project teams to evaluate digital outputs for REF submissions. Focus Areas: •Authorship, licensing, editorial context •Technical documentation and versioning •Accessibility and user experience •Sustainability and citability 6 key 2.Introducing two tools 1. The Checklist for Digital Output Assessment Editorial context Are the scholarly intent and scope clear? 1 2 3 Licensing & Ownership Are rights transparent? Technical Robustness Are infrastructure, versioning, and/or APIs adequately documented? Usability & Accessibility Does it comply with WCAG compliance, inclusive design? 4 5 6 Sustainability Is there a plan for long-term hosting/ SLA/ archival planning? Added value How does the output go beyond print or previous digital forms? 7 key 2.Introducing two tools 2. The Project Release Document (PRD) Purpose: An internal tool to ensure readiness before a digital output is released. Focus Areas: •Navigation and UI consistency •Code quality and performance •Security and data handling •Compliance (copyright, licensing) •SEO and analytics readiness 8 together 3.How the tools work ▪External facing ▪Support REF submission ▪Used by researchers and RSEs in preparation for REF submission and/or close to public release ▪Assesses Scholarly value The Checklist The PRD ▪Internal Quality Assurance tool ▪Ensure Development and Design quality ▪Used by RSAs, RSEs and RSDs prior to milestone deployments ▪Check technical readiness When properly embedded in project lifecycles and team practices, they contribute to ensuring quality. 9