Ensure web application uses lower camel case parameter names across service calls
Summary: Ensure web application uses lower camel case parameter names across service calls
Created: 2013-01-14 16:03:20.187
Updated: 2016-02-08 11:33:56.368
Resolved: 2016-02-08 11:33:56.288
Description: For consistency, we use lower camel case parameter names across all our web services. This is how we have documented our API, and how we want other consumers to use our web services. Please refer to our web services API document here: http://dev.gbif.org/wiki/display/POR/Webservice+API for detailed descriptions of all services.
Unfortunately, our Portal, the first consumer of these web services, does not uses lower camel case. Instead, different pages use different styles. For example:
Occurrence search uses UPPER_CASE (see screenshot)
Species search uses lower_case (see screenshot)
Dataset search uses lower_case (see screenshot)
Therefore, for this issue, please ensure that the Portal uses lower camel case parameter names across all services.
Attachment Screen Shot 2013-01-14 at 3.49.34 PM.png
Attachment Screen Shot 2013-01-14 at 3.54.29 PM.png
Attachment Screen Shot 2013-01-14 at 3.55.58 PM.png
Created: 2016-02-08 11:33:56.365
Updated: 2016-02-08 11:33:56.365
As per [this comment|http://dev.gbif.org/issues/browse/POR-1614?focusedCommentId=18620&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-18620] "All search parameters are accepted case insensitive and ignore underscores. So its legal to use DATASET_KEY=, dataset_key= or datasetKey=
The later is used in the API documentation now."