...
Differences with current ICD
| Functionality | Operation(s) | BeforeCurrent ICD | AfterFuture ICD | Justification | Alternative |
|---|---|---|---|---|---|
| Returns real priority calculated for requested order | productOrder batchOrder | priority field is returned | priority field is not returned in response | OGC API standard don't allow to specify additional fields in jobStatus response | none |
| Returns estimatedDate information for requested order | productOrder batchOrder | estimatedDate field is returned in order response. Mandatory for productOrder | estimatedDate field is not returned in response | OGC API standard don't allow to specify additional fields in jobStatus response | use "finished" property of Job status. When job completed, "finished" is updated with date of completion. |
| Automatic creation of Batch Orders | bulkCreate | Batch orders processes are created in advance in the bulkCreate step but not triggered. The client has to trigger each of them for execution. | Batch Orders processes are not automatically created. The client has to execute a new process called "batchOrder" | No concept of "process triggering" in OGC API; It doesn't change anything in terms of number of | |
| Setting of FilterParam query parameter | bulkCreate | FilterParam property is a string with the complete criteria | FilterParam property becomes a array of objects. Each object is a criterion for product filtering | Less complexity on client side to define STAC query. The query is built by the service and is compliant | keeping a string |
| BatchOrder query sub-step | bulkCreate | The bulkCreate step don't return the list of Batch Orders but the client needs to send another query to get them. | Job result of bulkCreate process contains the list of batchOrders as an output parameter | simplification of workflow | |
| Notification about process completion | productOrder batchOrder bulkCreate | ||||
| Notification on Subscriptions |
Questions WERUM:
- time to execute "Bulk Create request" : can be long (several mn)
feasible to have a synchronous process wich returns a list of batch orders : No → stick to asynchonous - Are each batch order created when Bulk create : yes and persisted in a DB
...