Explain that there are gaps in the data #5
The date range reported by querying the schedule table for min(jst) and max(jst) can be a bit misleading.
This commit is contained in:
parent
f0d0e36e9e
commit
bcff8d36af
|
@ -15,6 +15,23 @@
|
|||
</tbody>
|
||||
</table>
|
||||
<div class="row">
|
||||
<div class="column"><b>Date Range</b>: {$min_jst} - {$max_jst}</div>
|
||||
<div class="column">
|
||||
<h2>Historical Note</h2>
|
||||
</div>
|
||||
<div class="column">
|
||||
<p>
|
||||
The recording of schedule data started toward the end of 2023-07-19.
|
||||
It has since been supplemented by the addition of past <a href="segment/?n=au+PAY">au PAY</a> shows which started in 2023-03-29.
|
||||
Note that there are huge gaps of data in between 2023-03-29 and 2023-07-19.
|
||||
There's a lot of missing data that might not ever get backfilled.
|
||||
</p>
|
||||
<p>
|
||||
With that in mind, the first month of solid data collection is 2023-08.
|
||||
Later, when we have monthly breakdowns, you'll be able to see more fairly counted rankings.
|
||||
</p>
|
||||
<p>
|
||||
<b>Date Range</b>: {$min_jst} ‐ {$max_jst}
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
|
|
Loading…
Reference in New Issue