Something like this has been on our development path and I agree would be a really great thing for everyone. I'm not sure of the time line but it's something I'd personally like sooner than later so we'll see what we can do.
We've had a few request for LDAP and Active Directory support so we will probably add support for it sooner than later. The good new is that in the next release of Mango we have reworked user permissions to create very flexible user groups. This should help us do a better LDAP integration.
It would be very useful if a static 'time offset' value could be set as a property of data sources and/or points.
The value (entered in milliseconds) would offset the usual timestamp for the point.
This would be most helpful when instrumentation has a fixed delay between the measurement and the reading of that value via its data interface.
For example some panel meters we use seem to be delayed by some seconds, which can make it tricky to diagnose issues.
If you have not already looked into it, you may want to check out the DGLux module, which will allow you to build a report with nice looking charts that show the kind of data you want.
For example I use Mango to read a pulse counter that is attached to a gas meter, then I use DGLux to generate a pretty bar chart that displays a customisable time period and plots the number of pulses recorded, with dropdown menus to change to hours, days, weeks, months etc.
You can also add buttons to your dashboard to easily export data from the dashboard in PDF, PNG or XLS format (though I don't know how you can automate it).
sometimes, the datasources is interrupted because the nework problem or other reason, we can recover acquisition the data during the interrupted times.
now the datasource all save the value runtime(now time),so if we interrupted recover collect the data before,the timestamp is now but not the realy past time. Do have same case? and have some solutions.