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
  • One - Identify potential use case communities
  • Two - convene use case communities
  • Make-up of use case communities
  • Responsibilities
  1. Engage and convene

Activities

PreviousStage outlineNextSupporting tools

Last updated 10 months ago

One - Identify potential use case communities

OA governance will maintain an openly published list of existing and potential new use case communities, which will be informed by:

  1. - OA governance will maintain a library of policy analysis of different sectors, and MEL evidence built up from existing use case communities.

  2. OA community input - the OA community can propose potential use case communities through the .

Potential use case communities will be presented to the AEF which will allow:

  • other members of the OA community to .

  • OA governance to prioritise resources and support using a .

Two - convene use case communities

Once a viable use case community has been identified, the following steps will be taken to catalyse it:

For new communities:

  1. Identify stakeholders

  2. Engage with these stakeholders and provide a means for them to register their interest

  3. Hold a kick-off meeting

  4. Agree the governance and accountability structure

Where a community already exists:

  1. Engage with the community to establish their existing model

  2. Identify any stakeholder gaps and, where required, invite targeted stakeholders to join the community and/or provide a means for additional stakeholders to register interest in the community

  3. Hold a scoping meeting to establish points of contact and ways of working

Make-up of use case communities

Use case communities can be made up from:

  • Organisations both within the OA community and/or outside the OA community. Involving organisations from outside the current OA community enables the OA community to grow, which should help it become more sustainable

  • Organisations with fixed/closed membership, or with open membership

  • Organisations in overlap with members of the AEF, W3C or SC or independently

Responsibilities

Policy and evidence library
Use case community suggestion form
register interest where possible
standardised decision-making matrix
Engage and convene responsibility chart
Responsibility chart for the engage and convene stage of the framework. It outlines the activities in the stage, and which of three groups are responsible for them, OA governance, OA community or Use Case Communities. In the first activity, identify potential use case communities, policy research is the responsibility of OA governance, and OA community input is the responsibility of both OA governance and OA community. In the second activity, convene use case communities, identify stakeholders, and engage with identified stakeholders, are the responsibility of both OA governance and OA community. And agree governance and accountability structure is the responsibility of use case communities.