List of what still needs to be done for GridUsageSensorServices

General:

Need to update the documentation, especially the !JavaDocs, for the sake of future maintenance programmers.
GUSS paper needs some more data points and a once-over proofread.

Decide data-archiving policy (i.e. do we want to eventually remove individual packets from database, replacing them with summary records? After how long? What information needs to be in these summaries?)
Formulate reliability guarantees, i.e. safeguard against losing any packets that reach us. I am working on this now; Ravi is going to provide an independent count of the number of packets going to usage-stats.globus.org measured on the router level so we can compare and see if any are getting lost.
Make sure date, IP/hostname formats, field names, etc. are consistent across all tables.
Optimize packet tables for faster queries. (I'm working on this right now.)

Graphing of other component stats besides GridFTP, if there is sufficient interest.
Allowing users to define their own categories of hosts besides the two current default categories ("globus" and "everything") for plotting. Saving custom categories in portal preferences. This would be fun to add, but I want to know if there is a use case for it before I proceed.
More display options: other types of charts besides time-series? Other quantities that could be calculated and displayed? At one point I had a host-to-host graph option, but since we have made the policy decision not to make available individual host information, I removed this option. Again, I would like to know what graphs/quantities there might be use cases for.
Cleanup of some obsolete cruft from the code
Improving portal response time by optimizing database queries on the java side.