You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Query Product

The following presentation contains a short gap analysis regarding STAC and the AIP of the LTA service:

STAC-AIP-Gap-Analysis.pptx


This table focuses on product properties that should be exposed by AIP instances and that are not currently backed by STAC Core or extensions.

Property NamePossible values / ExampleCommonCommentProposed solution
Online
  • true
  • false




Order extension field order:status:

  • orderable=Offline
  • succeeded=Online

to be stated in the ICD : 

Offline : item with no assets

Online : item with assets





Retrieval functions

Retrieve Product

Queries

Call from LTA Client"OGC API - Processes" operationDetails Response of query
Product Order Request

/processes/{PROCESSID}/execution

Query type : POST

PROCESSID = order-request

Input parameters : 

  • product_identifier
  • priority

By default returned by service:

  • ID of the Order → Job UUID

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=successfulJOBID = order ID returned previously

List of completed Jobs with their ID and following parameters : 

  • Status → status
  • StatusMessage message
  • SubmissionDate → created
  • CompletedDate → finished
  • EstimatedDate →  additionalProperties mechanism ??
  • Priority additionalProperties mechanism ??
  • EvictionDate → additionalProperties mechanism ??


Product Staging NotificationCallback 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 statusOGC API - Processes status

queued

accepted
in_progressrunning
completedsuccessful
failedfailed
cancelleddismissed

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

1st level assumption: not "as is" in the OGC standard.

Ideas

  • 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") 


  • No labels