LogoLogo
  • Introducing the framework
    • Context
    • Definitions
    • Development of the framework
    • Who is the framework for?
  • Framework overview
    • Framework at a glance
  • Engage and convene
    • Stage outline
    • Activities
    • Supporting tools
  • Understand and plan
    • Stage outline
    • Activities
    • Supporting tools
  • Develop
    • Stage outline
    • Activities
    • Supporting tools
  • Learn and publish
    • Stage outline
    • Activities
    • Supporting tools
  • Implement
    • Stage outline
    • Activities
    • Supporting tools
  • Appendix one - Engagement protocol
    • Prioritisation matrix
    • Support tiers
    • Interaction process map
  • Appendix two - Governance and accountability structure guidance
    • Governance and accountability structures
  • Appendix three - MEL framework
    • Overview
    • Step by step guide
  • Appendix four - Data requirements framework
    • Data requirements framework
  • Appendix five - Use case template
    • Problem statement template
    • Use case prioritisation decision-making matrix
  • Appendix six - Funding model guidance
    • Funding model guidance
Powered by GitBook
On this page
  • Step 1: Data analysis
  • Step 2: Planning and prioritisation
  1. Appendix four - Data requirements framework

Data requirements framework

PreviousStep by step guideNextProblem statement template

Last updated 10 months ago

This is a guidance document to help use case communities define the data required to achieve their SMART objectives, as defined through the .

Step 1: Data analysis

The first stage in defining your data requirements is to understand what data you have, and what data you need, to meet the objectives you have defined. This will enable you to undertake a gap analysis to identify the gaps or missing information required to fulfil your goals. Gaps that may be identified include:

  • Data doesn’t exist (data would need to be created or collected)

  • Data isn’t shared (data exists, but is siloed)

  • Some data is shared, but not to the desired degree (quality, granularity, timeliness, etc.)

  • Data is shared, but is not as useful as desired

Activities you may wish to undertake include:

You may find it helpful to use the found within the OA Modelling Opportunity Data Specification, and any user research collected during the process of .

Step 2: Planning and prioritisation

The second stage in defining your data requirements is to plan and prioritise. This stage should involve creating an outline of the steps needed to bridge the gaps identified during your data analysis. Potential solutions could include:

  1. Creating new, or improving existing, datasets. Consider:

    • Data sources and collection methods - evaluate the feasibility, costs and time restraints associated with each data source

    • Data quality and critical data elements (CDEs) - refer to the and

  2. Developing new, or adapting existing, technology. A ‘data technology’ is best described as any tool – hardware or software – that enables us to collect, access, use or share data more easily and effectively. . Consider:

      • Is the data already being published through either a bespoke or third party system?

      • Does a bespoke system need to be developed, or will you use an existing third-party system?

      • Where will the data be used?

      • Does a bespoke system need to be developed, or will you use an existing third party system?

  3. Refining the existing OA specifications, or creating new bespoke extensions to the existing specifications -

  4. Improving data skills and literacies -

MEL framework
Creating a data ecosystem map
Creating a data inventory
data model diagram
identifying and prioritising use cases
OpenActive Data Quality Reporting Framework
Government Data Quality Hub’s guidance
ODI - Data Landscape Playbook - Build or improve technologies
Publishing data
Using data
OpenActive W3C Community Group
ODI - Data Landscape Playbook - Assess data skills and literacies