why the object/url has to have the job id in the path?

[IanGoh]

is it a security thing to have the job id, in the object/url response?

{

    "urls": {

        "24168951-9...": {

            "url": "https://data-access-platform-output-prod-iad.s3.amazonaws.com/output/..."

        }

    }

}

Seems more work to get the url since you have to do urls.jobid.url

Or was the reason so you could get multiple jobids back in the same object/url?

[Edina_Tipter]

@IanGoh Good catch! 🤓 It was supposed to be a quick solution but should not be the final. The job ID will not be the same as the resource ID(s)/list of object(s) because as you pointed it out correctly, in the future it could be a use case when we want to return multiple objects not just one as the specification also implies. We'll address and adjust this in our next sprint starting tomorrow.

In sum, you should get the object/url in order to download the resource itself. The Job ID should not be used as s substitute even if temporarily it's the same and easier to get 😉