Comment 1 for bug 1379355

The data necessary for this plot already exists for Helioviewer.org user-generated movies. We currently record the 'timestamp' that the movie was added to the `movies` table, as well as the 'reqStartDate' and 'reqEndDate'. Additionally, we record the 'startDate' and 'endDate', which are the bounds of the frames that are actually returned, but the request start and end date are slightly more interesting.

Unfortunately we do not currently capture this data for JHelioviewer (JPX movie generation). We do currently keep track of a timestamp each time a 'getJPX' API request made by JHelioviewer. We could add a table to the database that is populated with 'reqStartDate', 'reqEndDate', 'startDate', 'endDate', 'timestamp', ' dataSourceString', and 'dataSourceBitMask' that gets added to each time a 'getJPX' API request is logged. For performance reason, it may be better to do an 'INSERT LOW PRIORITY' query. While the 'timestamp' column would be set to 'NOT NULL DEFAULT CURRENT_TIMESTAMP', we would want to explicitly insert the timestamp at which the query is generated. Otherwise, the value of CURRENT_TIMESTAMP may be inaccurate due to the 'LOW PRIORITY' optimization.