Change Details

A first implementation exists. This leverages everything that needs to (scheduler, one-shot task). It's still not complete though since it needs to also deal with origin_metadata.

When a deposit is posted to the deposit server and the client makes it ready (status `ready-for-check`). This triggers an asynchronous loading-check task scheduling (as one-shot task). This can result in deposit ready for load, status `ready-for-load` (when check passes). This triggers an asynchronous loading-deposit task (as one-shot task).

A first implementation exists. This leverages everything that needs to (scheduler, one-shot task). It's still not complete though since it needs to also deal with origin_metadataWhen a deposit is posted to the deposit server and the client makes it ready (status `ready-for-check`). This triggers an asynchronous loading-check task scheduling (as one-shot task). This can result in deposit ready for load, status `ready-for-load` (when check passes). This triggers an asynchronous loading-deposit task (as one-shot task).