-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Data Dump Export #101
Comments
This should be available to only admins and heavily rate-limited. |
I think we should discuss this. I can see where non-admin users might want
to do this. Also, it may make more sense to discuss the quantity of data
rather than how it is requested. I think we may have talked at at a team
meeting (much earlier) about having a warning if the size of the file was
larger than some specified value. Doing this would rate limit in a very
primitive way (just for that person and just how fast they can get
data/click) but it might be enough depending on how we do it and what is
needed. Just some thoughts.
All the best,
Steve
…On Thu, Feb 8, 2018 at 8:38 PM, John DiIorio ***@***.***> wrote:
This should be available to only admins and heavily rate-limited.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#101 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA8PttLD3kAMvyPjn0jRroLN6pY6z9Wfks5tS6-_gaJpZM4PWl8P>
.
|
We are about to add timezones to preferences (overall site setting) and to meters (overrides preferences). PR #508 fixes time shifts in graphs by setting everything to web browser local time but the DB does not have time zones with readings. When we dump raw data, the user might want the OED view of time zones (which is the relative time of the day) or the actual time zone that the meter data was collected in. Thus, we should add the meter time zone to the data we dump (maybe as a new column where repeated for as many reading for a given meter). |
There is now a design document for this and it is being done. |
Extend #22 (PR #83) by allowing users to export all available data.
The text was updated successfully, but these errors were encountered: