This would be something really useful for a user, but maybe is better implemented in another script, on top of this generic uws-client?
With CosmoSim's (Daiquiri's) UWS implementation, one can easily filter by the tablename, since it is given in the full job list. For any other parameter, one needs to send not only one request to the job list, but also one request per job to get the details. This can take quite some time and maybe it's a bad idea.
The main problem is that it depends on the UWS-service which parameters are available.
But users do want to search for the ids of jobs with a tablename like 'test-*' or with a service-specific parameter in a specific range or a certain tablename in the sql-query. I would expect a list of jobids returned (together with some details) which can then be used for e.g. deleting all these jobs or looking up further details.
One more thought: at least we could do some filtering for error-messages, since "errorSummary" is included in the uws-schema. And filter for start/endTimes, these are also standardized.
This would be something really useful for a user, but maybe is better implemented in another script, on top of this generic uws-client? With CosmoSim's (Daiquiri's) UWS implementation, one can easily filter by the tablename, since it is given in the full job list. For any other parameter, one needs to send not only one request to the job list, but also one request per job to get the details. This can take quite some time and maybe it's a bad idea.
The main problem is that it depends on the UWS-service which parameters are available. But users do want to search for the ids of jobs with a tablename like 'test-*' or with a service-specific parameter in a specific range or a certain tablename in the sql-query. I would expect a list of jobids returned (together with some details) which can then be used for e.g. deleting all these jobs or looking up further details.
One more thought: at least we could do some filtering for error-messages, since "errorSummary" is included in the uws-schema. And filter for start/endTimes, these are also standardized.