Thanks for identifying the problem Sachith. To be precise potentially there are many subset variations of interested fields in the Experiment Data which different gateways will be interested in the same usecase or different usecase. We cannot scale by providing different functions for each of these scenarios.
On Fri, Mar 14, 2014 at 11:25 AM, Sachith Withana <[email protected]>wrote: > Hi all, > > Almost all gateways have a requirement of retrieving the experiment > summaries of all the experiments . The fields that are required differ > based on the gateway. > > For Example: > CIPRES requires : Experiment name and status > Some gateways requires the Experiment name with the inputs only. > > But right now the getAllExperiments() method returns the list of all the > Experiments with all the experiment related attributes filled ( the whole > Experiment Model). > > It's costly to get the whole Experiment objects from the API rather than > getting the required few attributes. > > Any suggestions on how we could achieve this? > > One suggestion would be to have a getAllExperiments method with the > parameters as a list of required fields of the Experiments and return only > those fields. > > -- > Thanks, > Sachith Withana >
