Hello Andrea,
thanks for your questions. Let me try to clarify a bit more what we have in mind right now.
Executions List
At a first glance I was thinking to the possibility of having some “public” executions, somehow, but digging a bit more on the proposal this does not make much sense.
The new operation should return only the list of available Executions the logged in user has started, except in the case it is an Administrator. In that case he will be able to get the whole list.
StatusInfo Response
Yes, roughly it should return what we see on the GUI, possibly with a bit more information (when/if available) as detailed in the table below
Names
Definition
Data type and values
Multiplicity and use
JobID
Unambiguously identifier of a execution job within a WPS instance.
Character String a
One (mandatory)
Identifier
Unambiguously identifier of a process within a WPS instance.
ows:Identifier
One (mandatory)
Status
Well-known identifier describing the status of the job.
Character String b
One (mandatory)
ExpirationDate
Date and time by which the job and its results will be no longer accessible. c
ISO-8601 date/time string in the form YYYY-MM-DDTHH:MM:SS.SSSZ with T separator character and Z suffix for coordinated universal time (UTC)
Zero or one (optional) Include if available.
EstimatedCompletion
Date and time by which the processing job will be finished.
ISO-8601 date/time string in the form YYYY-MM-DDTHH:MM:SS.SSSZ with T separator character and Z suffix for coordinated universal time (UTC)
Zero or one (optional) Include if available.
NextPoll
Date and time for the next suggested status polling.
ISO-8601 date/time string in the form YYYY-MM-DDTHH:MM:SS.SSSZ with T separator character and Z suffix for coordinated universal time (UTC)
Zero or one (optional) Include if available.
PercentCompleted
Percentage of process that has been completed.
Integer{0…100} d
Zero or one (optional) Include if available.
a) Particularly suitable JobIDs are UUIDs or monotonic identifiers such as unique timestamps. If the privacy of a Processing Job is imperative, the JobID should be non-guessable.
b) The basic status set is defined in http://docs.opengeospatial.org/is/14-065/14-065.html Table 3. Additional states may be defined by certain operations or extensions of this standard.
c) This element will usually become available when the execution has finished (Status = “finished”).
d) Zero (0) means the execution has just started, and 100 means the job is complete. This value is informative only without any accuracy guarantees.
GetExecutions Request
In order to filter and refine the Request, I was wondering about a set of simple Request parameters as depicted in the diagram below
which are better detailed in the table here below
Names
Definition
Data type and values
Multiplicity and use
Owner
Unambiguous identifier of a user within a WPS instance.
Filters out all the jobs not anonymous or not belonging to the specified user.
Character String a
Zero or one (optional).
Identifier
Unambiguous identifier of a process within a WPS instance.
Filters out all the jobs not belonging to the specified process identifier.
ows:Identifier Value shall be one of the process identifiers listed in the ProcessSummary elements in the Capabilities document.
Zero or one (optional).
Status
Well-known identifier describing the status of the job.
Filters out all the jobs with an Execution Status different from the one specified.
String{PENDING, RUNNING, FAILED, CANCELED, FINISHED} b
Zero or one (optional).
OrderBy
One of the OWNER, IDENTIFIER, STATUS.
The Response Document will be ordered accordingly to the value specified. If not value has been specified, the list of Processed will be ordered by Identifier and ExecutionDate.
String{OWNER, IDENTIFIER, STATUS}
Zero or one (optional).
a) It must match one of the usernames available on the Server, if any available. GetStatusesListResponse contents may vary accordingly to security constraints.
b) The basic status set is defined in http://docs.opengeospatial.org/is/14-065/14-065.html Table 3. Additional states may be defined by certain operations or extensions of this standard.
···
On Thu, Jul 12, 2018 at 11:12 AM, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:
Dear lists,
I would like here to ask your opinion about a possible extension/improvement of the GeoServer WPS Service.
The main goal of this proposal is to allow a client to recognize the list of WPS Executions through a simple request to a WPS Operation. What we would like to achieve would be something similar to this:
![image.png]()
The client makes a simple “GetExecutions” request to the WPS Server, in order to get back an XML document containing the list of current Execution Statuses.
Ideally should be possible also to filter the “GetExecutions” request along with simple parameters, in order to refine the output and get back only the executions status we are looking for.
Adding a bit more to this, if AUTHORIZATION headers are sent along with the “GetExecutions” request, the WPS Server should be able, if a security subsystem is available and enable on the latter, of provide also the list of eventually private/protected resources to the client itself.
Part of this proposal is also to review and improve the “lineage” option of the WPS service, allowing a client to retrieve the Execute Inputs values provided to the process Identifier.
Thoughts?
–
==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.
Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead
GeoSolutions S.A.S.
Via di Montramito 3/A - 55054 Massarosa (LU) - Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.
==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.
Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead
GeoSolutions S.A.S.
Via di Montramito 3/A - 55054 Massarosa (LU) - Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.