If we only include child job ids, clients will have to make (n + n*m) requests to display job status (n = top-level jobs, m = average number of child jobs). Options for clients to display job details:
- Include child job objects. This could get big for jobs with lots of children, so probably not great.
- Include title or description of executing child jobs. This would be preferable.
- Indicate the ids of the child_jobs that are executing, so the client doesn't have to poll all the children to get detailed status.