Issue 18129

trim queries to include only used informations

18129
Reporter: hoefft
Assignee: cgendreau
Type: Task
Summary: trim queries to include only used informations
Priority: Minor
Status: ToDo
Created: 2016-01-06 16:47:21.683
Updated: 2016-01-11 16:55:08.876
        
Description: When querying a resource the response can be quite big. It would be nice if we trimmed these down to the information that we actually use.

An example could be dropdown with people. Currently the response is 1.4 mb. That seems over the top when we are only intersted in an id and the name. This is probably less of an issue if http://dev.gbif.org/issues/browse/DIR-1 is solved]]>
    


Author: cgendreau
Comment: Just explain what you need and we can decide if we add support for fields filtering or another endpoint.
Created: 2016-01-07 16:33:43.514
Updated: 2016-01-07 16:33:43.514


Author: hoefft
Created: 2016-01-08 10:02:36.891
Updated: 2016-01-08 10:02:36.891
        
We have 3 types of autocomplete that we use for building relations. These are people, nodes and participants.

for people we use:
person id
first name
last name

For Nodes and Participants we use:
id
name

Fetching all the data everytime is expensive. For some nodes with relations to 5 people that means that we download 5*1.4mb (as each component is self contained and asks for its own data)
So 304 (http://dev.gbif.org/issues/browse/DIR-1) would also help a lot.
    


Author: cgendreau
Created: 2016-01-11 16:55:08.876
Updated: 2016-01-11 16:55:08.876
        
After adding the concept of "extended" view the size is < 500kb.
After removing the "joins" from the query behind the /person it also takes < 500 ms.