Weaver: Workflow Execution Management Service (EMS); Application, Deployment and Execution Service (ADES); OGC API - Processes; WPS; CWL Application Package
To better describe the jobs at a glance, the following notation should be used:
urn:<server-name>:wps:<process-id>:<datetime>:jobid:<UUID>
server-name: crim by default or obtained from another setting
datetime in YYYYMMDDHHmmss format (no : to avoid parsing of URN parts), using submitted (job.created) time.
Using this notation, it will be clear directly with the job URN where the execution was accomplished, for which process and at what time. This can become relevant when listing multiple JobID, since the plain UUID does not provide enough information to quickly identify jobs of interest when doing a search. One has to go fetch additional status details for each JobID to better understand what they imply.
Description
To better describe the jobs at a glance, the following notation should be used:
urn:<server-name>:wps:<process-id>:<datetime>:jobid:<UUID>server-name: crimby default or obtained from another settingdatetimeinYYYYMMDDHHmmssformat (no:to avoid parsing of URN parts), using submitted (job.created) time.Using this notation, it will be clear directly with the job URN where the execution was accomplished, for which process and at what time. This can become relevant when listing multiple JobID, since the plain
UUIDdoes not provide enough information to quickly identify jobs of interest when doing a search. One has to go fetch additional status details for each JobID to better understand what they imply.References
JobIdformat in OGC API: https://github.com/opengeospatial/ogcapi-processes/blob/18e8f5c7dc68c0d64062be8fab7a6eb044a8298c/core/openapi/schemas/statusInfo.yaml#L13-L14