Alerce query fails with error from tom-demo-dev

[rachel3834]

Describe the bug
Running an Alerce query (query 10, Galactic Bulge query) from tom-demo-dev's UI produces the following error:
400 Client Error: BAD REQUEST for url: https://api.alerce.online/ztf/v1/objects/?count=false&order_by=None&order_mode=None&page=1&page_size=20&ra=17.5&dec=-27.0&radius=60

To Reproduce

1. Go to tom-demo-dev, click Alerts
2. Run the Alerce query labeled 'Galactic Bulge' (10 in list)

Expected behavior
I expect the query to return a list of targets or an empty list indicating there were no targets found.

Desktop (please complete the following information):

• OS: MacOS Ventura 13.1
• Browser Chrome

Additional context
Would be nice to fix, but not super urgent.

[rachel3834]

Actually, looks like Alerce queries are failing because they have changed their query string requirements; I'm getting the same error if I submit the query from a test TOM.

This makes it higher priority

[rachel3834]

More debugging info. The Alerce query form I am submitting sends the following query to Alerce:
https://api.alerce.online/ztf/v1/objects/?count=false&order_by=None&order_mode=None&page=1&page_size=20&ra=295.3245&dec=40.186667&radius=120
(I'm doing a simple cone search on these coordinates)

The specific errors produced are:
{"errors": {"order_by": "Column used for ordering The value 'None' is not a valid choice for 'order_by'."}, "message": "Input payload validation failed"}
{"errors": {"order_mode": "Ordering could be ascendent or descendent The value 'None' is not a valid choice for 'order_mode'."}, "message": "Input payload validation failed"}

These two key words appear to be the problem in my query. According to the Alerce API documentation both of these parameters accept a range of set values but cannot be None.

These parameters also don't appear to be essential, I suggest the parameters simply be removed from the query string, or use default values of:
order_by: oid
order_mode: ASC

[jchate6]

Is this issue still live?