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
MoMA have requested that a second verification method (ex. a second drop-down or pop-up window) be added to confirm a users selection from the Processing Configuration field in the Batch Import UI ahead of being able to launch a batch.
MoMA works with two primary processing configs, which are designed to deposit material into two separate storage pools: local and cloud. Their local workflow handles extremely large batches of material at a time (into the 10s of TBs) and deposits into their local storage server, whereas their cloud workflow handles much smaller quantities of AIPs, which are subsequently replicated and the replicas stored with two different cloud providers. Their concern lies in the potential for user error when selecting the appropriate processing configuration and subsequently having large local batches accidentally stored and replicated in the cloud thus incurring large costs and/or increased labour to clean up the error. As such, they have requested that some form of secondary verification be added to the Batch Import UI to reduce user error and ensure the appropriate processing config is used.
The text was updated successfully, but these errors were encountered:
MoMA have requested that a second verification method (ex. a second drop-down or pop-up window) be added to confirm a users selection from the Processing Configuration field in the Batch Import UI ahead of being able to launch a batch.
MoMA works with two primary processing configs, which are designed to deposit material into two separate storage pools: local and cloud. Their local workflow handles extremely large batches of material at a time (into the 10s of TBs) and deposits into their local storage server, whereas their cloud workflow handles much smaller quantities of AIPs, which are subsequently replicated and the replicas stored with two different cloud providers. Their concern lies in the potential for user error when selecting the appropriate processing configuration and subsequently having large local batches accidentally stored and replicated in the cloud thus incurring large costs and/or increased labour to clean up the error. As such, they have requested that some form of secondary verification be added to the Batch Import UI to reduce user error and ensure the appropriate processing config is used.
The text was updated successfully, but these errors were encountered: