There are things we often do after the getDataSet command is called, such as trimming to a specific range. The getDataSet should have a Jython wrapper which accepts trim=True to mean the data should be trimmed to the timerange. Also, there should be an option to sort the data in time.
getDataSets should also be updated.
A setLayout command is being added at the same time.
See also https://sourceforge.net/p/autoplot/bugs/2582/ and https://sourceforge.net/p/autoplot/feature-requests/823/
See also https://sourceforge.net/p/autoplot/feature-requests/823/ and https://sourceforge.net/p/autoplot/bugs/2582
Specifying trim=tr will implicitly specify the timerange to load as well.
I've also thought it might be nice to constrain the units (like you can with the IDL/Matlab/Python reader), where it will try to convert the data to a specified unit. This makes the code more legible, and future-proofs a script.
Similarly, the data scheme could be constrained. For example, sometimes a server will return data in the form X->Y and sometimes it is a bundle T->[X,Y]. If you don't know the form the data will come in, it would be nice to specify the expected schema. Of course there is not really a good way to identify schemas, just org.das2.qdataset.examples.Schemes.