Summary: We need to extend our data pipeline to gather metrics that align with our current OKRs around impact and infrastructrual sustainability. This includes tracking indicators of usage, growth, federation, and community uptake. Our existing tooling can support this — the work is primarily in identifying and implementing the specific metric gathering mechanisms and calculations. For example, we may already track triples but not the date an instance was first created — in such cases, the task involves designing the method to gather and store that data in the first place.

Why This Matters: This work will enable us to better evaluate our strategic success, provide insights for iteration, and report out transparently to our communities and stakeholders. It will also help us sustain and prioritize work based on real-world usage and needs.

Scope:

• Add logic and/or configuration options to our pipeline to gather additional metrics
• Ensure outputs are accessible via existing dashboards or exports
• Build each metric to be versionable and modifiable as definitions evolve

Definition of Done:

• All child tickets closed
• Metrics implemented or refined based on feasibility feedback
• Documentation updated to reflect data sources and calculations
• Confirmed output is available and accessible within the core tool (no need to duplicate paths, as a new dashboard is in development), and baselines are captured and stored

Dependencies:

• Core data tooling (already in place)
• Metric-specific definitions (captured in child tickets)

Next Steps:

1. Create child tickets for each metric we want to track
2. Prioritise based on OKR delivery dates
3. Begin implementation and feasibility review