Stream: argonaut
Topic: scheduling / Issue #58 Whether to add a header to Hold re...
argo-scheduling-bot (Jan 27 2018 at 16:21):
Healthedata1 opened Issue #58
As discussed at the Jan Connectathon. Indicating the expiration of a hold would be good for a consistent user experience.
Proposal to add a header to
?holdrequests response indicating expiration time.
(todo: research the proper header type)
argo-scheduling-bot (Jan 27 2018 at 16:21):
Healthedata1 labeled Issue #58
argo-scheduling-bot (Jan 27 2018 at 21:26):
Healthedata1 commented on Issue #58
Understood that client should be obligated to release the hold but if not the server will release it.
argo-scheduling-bot (Jan 27 2018 at 21:28):
Healthedata1 edited Issue #58
As discussed at the Jan Connectathon. Indicating the expiration of a hold would be good for a consistent user experience.
Proposal to add a header to
expiresRFC 7324 requests response indicating expiration time.
(todo: research the proper header type)
argo-scheduling-bot (Mar 19 2018 at 20:49):
Healthedata1 commented on Issue #58
See similar usage in Bulk Data access. - add this guidance to operation(s). and release hold steps as well as state diagrams.
argo-scheduling-bot (Mar 19 2018 at 20:49):
Healthedata1 closed Issue #58
argo-scheduling-bot (Mar 19 2018 at 20:50):
Healthedata1 commented on Issue #58
applied to ig
Last updated: Apr 12 2022 at 19:14 UTC
