Indexer view for diving into external MRV data

[gautamp8]

Problem definition

External sensors and systems often generate data points at frequent intervals — in some cases, every 15 minutes, 24/7. In real-world deployments, the number of such systems can reach hundreds or even thousands. Similar challenges arise when policy logic (e.g., calculations) requires the use of historical data, as these datasets may span decades of measurements.

These scenarios create significant challenges in terms of data comprehension and traceability, since Guardian currently lacks convenient tools for manipulating and displaying such large datasets.

Requirements

1. Ability to receive documents containing or referencing large sets of tabular data via external interfaces.
2. Ability to display large datasets in a tabular format.
3. Ability to display large datasets in chart form.
4. Ability to trace specific individual or grouped values through their usage and transformations in the policy (i.e., where they were used and what they influenced).
5. Ability to trace data for a specific ID or sensor across historical datasets and display them as time-series charts.
6. All of the above capabilities should be available in both Guardian and Indexer.

Original definition

For VM0033 and Metered stoves methodology, stakeholders(VVB, Registry) need a way to drill down into data sent by external systems.

To be specific -

1. Metered meth requires every stove data to be sent to Guardian, we use external data block to receive and later manipulate it to output a monitoring report on regular frequency. VVB needs a way to sample few stove IDs and check the trace of data from start to finish.

2. For VM0033, Kanop(external MRV provider) will be sending sea level rise data on regular basis to guardian. There needs to be a way to present it on indexer in best way possible.