...
| Call from LTA Client | "OGC API - Processes" operation | Details | Response of query |
|---|---|---|---|
| Product Order Request | /processes/{PROCESSID}/execution | Query type : POST PROCESSID = order-request Input parameters :
| By default returned by service:
Other parameters (can be retrieved through endpoint /jobs/{JOBID} |
Order Status Query (status = completed) Mario : use job result to get all the parameters !! | /jobs/{JOBID}?status=successful | JOBID = order ID returned previously | List of completed Jobs with their ID and following parameters :
use job result to get some parameters ??? |
| Product Staging Notification | Callback mechanism for completed jobs : requires to add a subscriber property in the order request (notification endpoint) | To assess : authorisation for callback |
...
JobStatus value correspondance
| Odata status | OGC API - Processes status |
|---|---|
queued | accepted |
| in_progress | running |
| completed | successful |
| failed | failed |
| cancelled | dismissed |
Process definition
TODO : add a table on Process definition with input and output parameters (as a requirement)
Bulk Product Retrieve
The bulk is defined by a list of products or query filter parameters and a batch size
...
- Create a specific Process for "Bulk Create Request".
- query filter parameters : the process parameters == filters
- list of products : one parameter as a list of product IDs
- BatchOrder List Request : is the result of the "Bulk Create Request" Process
- Create a specific Process for "BatchOrder trigger"
Good to simplify the current way to do bulk (many batch orders to trigger !!)
Trigger all the batches automatically
→ offer the user to automatically execute the batch orders or not (as a parameter of "Bulk Create Request")