The current API uses a sheet in the measure_data called "none", corresponding to aggregation level in the report_config of "none". The data is supplied pre-calculated in wide format, which is difficult to do manually because of the differing and irregular x axis dates that will typically be used in rare event charts.
Convert the package to use rare-event data supplied in "event list" form.
This is easier to supply manually, and corresponds to the same method used in other tools (for example the Making Data Count T and G chart tools).
It is also close to the format that data is returned by SQL queries, which is one method for feeding bulk data to this package.
In general terms, "event list" data could (in a future issue) be used to feed data to all measures, and aggregation could be done inside SPCreporter. That is out of scope of this issue.
The current API uses a sheet in the measure_data called "none", corresponding to aggregation level in the report_config of "none". The data is supplied pre-calculated in wide format, which is difficult to do manually because of the differing and irregular x axis dates that will typically be used in rare event charts.
Convert the package to use rare-event data supplied in "event list" form.
This is easier to supply manually, and corresponds to the same method used in other tools (for example the Making Data Count T and G chart tools).
It is also close to the format that data is returned by SQL queries, which is one method for feeding bulk data to this package.
In general terms, "event list" data could (in a future issue) be used to feed data to all measures, and aggregation could be done inside SPCreporter. That is out of scope of this issue.