You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
embargo status will update any time that the sample gets new tempo data (initial delivery date needs to be be correct, always reflect the earliest delivery date. i.e., if sample tempo data is recovered with an even earlier delivery date than what is currently stored in smile then this value needs to be updated to reflect that as well as the embargo date) replaced/captured by Tempo model updates + protobuf definition changes #1385
During import, Tempo model will resolve the values for the:
initialRunDate
embargoDate
accessLevel
A daily process will check if embargo date has lapsed and update accessLevel accordingly.
Proposed Tempo model changes:
protobuf change: emarbgo status --> accessLevel
The text was updated successfully, but these errors were encountered:
Add process/event handler that periodically checks for changes to embargo status and pub changes to tempo-cbio pipeline
frequency for status updates: daily
refactor tempo model to also store earliest sample delivery date and embargo statusreplaced by Tempo model updates + protobuf definition changes #1385embargo status will update any time that the sample gets new tempo data (initial delivery date needs to be be correct, always reflect the earliest delivery date. i.e., if sample tempo data is recovered with an even earlier delivery date than what is currently stored in smile then this value needs to be updated to reflect that as well as the embargo date)replaced/captured by Tempo model updates + protobuf definition changes #1385During import, Tempo model will resolve the values for the:
A daily process will check if embargo date has lapsed and update accessLevel accordingly.
Proposed Tempo model changes:
The text was updated successfully, but these errors were encountered: