given a job id, hard to find datum and therefore error via http

[seamusabshere]

querying /jobs/X won't give you datum ids, but that's the only way to get errors

[emk]

That's an excellent point! Would Jess be interested in taking lead on this?

[emk]

We might want to add /jobs/$ID/datums or something of the sort, because GET /jobs/$ID is already used internally, I believe.

[seamusabshere]

it might be nice to just inline the datums into the job response

[emk]

@seamusabshere The HTTP REST API is also used internally, and I'd want to make sure that adding extra data to the job response didn't add extra load internally when jobs are actually running. When you have 350+ clients all hitting the db, you need to be careful about this stuff. :-)

[emk]

We should address both this and the other issues discussed in #28 together.