Extend v4 endpoints with more parameters
Coming back to comment #50 (comment 243491), the main idea was to rename the endpoints to a RESTful convention. Nevertheless, this task could be an opportunity to redesign these endpoints to add multiple parameters and enhance performance.
For example, the quick view endpoint can deliver the data it needs (name and status of the job) without doing extra steps (get the wrappers and join information. This endpoint can be generalized to GET /v4/experiments/<expid>/jobs
which RESTfully refers to an endpoint that lists the jobs of an experiment. Initially, it can just read the pkl (fundamental operation that unfortunately cannot be split or reduced) and optionally add more info using parameters like include_structure=true
to return the children and parents, or view=quick
to just deliver name and status to reduce the payload size.
Additionally, further extensions will naturally and intuitively come like PATCH /v4/experiments/<expid>/jobs/<jobname> {"status": "READY"}
to change status.