This use case is for clients to specify fields to return per record, but this burns CPU and also reduces the cachability of a response. Current thinking is to maybe support this use case by defining a streamlined set of fields that represent a smaller record, and then pre-rendering and storing the JSON response (as is done with full records right now).
Candidate fields might include:
ScientificName
DecimalLatitude
DecimalLongitude
InstitutionCode
GlobalUniqueIdentifier
CoordinateUncertaintyInMeters
Other fields to consider: http://calbug.berkeley.edu/data
This use case is for clients to specify fields to return per record, but this burns CPU and also reduces the cachability of a response. Current thinking is to maybe support this use case by defining a streamlined set of fields that represent a smaller record, and then pre-rendering and storing the JSON response (as is done with full records right now).
Candidate fields might include:
Other fields to consider: http://calbug.berkeley.edu/data