orderBy is used in the GET request (and others), but the same information is represented by 'sortColumn' in the corresponding JSON response.
Example:
GET /collectionobjects?orderby=ProjectNumber,InventoryDate&limit=100&offset=0
JSON response:
...
"sortColumn": "ID",
...
Suggest using orderBy in both HTTP request and in JSON response.
Also decide on whether to use camel-case or not, and use the same in both.
Example. HTTP request:
GET /collectionobjects?orderBy=ProjectNumber,InventoryDate&limit=100&offset=0
orderBy
is used in the GET request (and others), but the same information is represented by 'sortColumn' in the corresponding JSON response. Example:GET /collectionobjects?orderby=ProjectNumber,InventoryDate&limit=100&offset=0
JSON response:
Suggest using
orderBy
in both HTTP request and in JSON response. Also decide on whether to use camel-case or not, and use the same in both.Example. HTTP request:
GET /collectionobjects?orderBy=ProjectNumber,InventoryDate&limit=100&offset=0
JSON response:
NB Should check for other examples of this kind of inconsistency..