...
Gliffy Diagram | ||||
---|---|---|---|---|
|
Delete
Flow
- The Repository manager selects an object to be deleted from preservation storage
- The Repository calls the Gateway DELETE Object endpoint for the object to be deleted
- The Gateway resolves the object into a set of files to be deleted
- The Gateway calls the Bridge Delete Content endpoint with the list of files to be deleted
- The Bridge initiates a delete action for all files in the delete request
- The DDP calls the Bridge List Deletes endpoint on a regular schedule to check for new delete requests
- The DDP performs a delete on each requested file; when all deletes are completed, the DDP calls the Bridge Complete Delete endpoint to inform the Bridge that the delete is complete
- The Repository administrator checks the object status in the Repository; the Repository requests information about the object from the Gateway to provide information.
Gliffy Diagram | ||||
---|---|---|---|---|
|
Restore
Flow
- The Repository manager selects an object to be restored from preservation storage
- The Repository calls the Gateway POST Object Restore endpoint for the object to be restored
- The Gateway resolves the object into a set of files to be restored
- The Gateway calls the Bridge Restore Content endpoint with the list of files to be restored
- The Bridge initiates a restore action for all files in the restore request and creates a directory in Bridge staging storage for the restored files
- The DDP calls the Bridge List Restores endpoint on a regular schedule to check for new restore requests
- The DDP copies each file in the restore request to the specified directory in Bridge staging storage
- When all files have been copied into Bridge staging storage the DDP calls the Bridge Complete Restore endpoint to inform the Bridge that the restored files are available
- The Bridge validates that all file checksums match the checksums provided in the restore request (when checksums are provided)
- The Bridge updates the status of the restore action to "STAGED_FOR_RESTORE"
- The Gateway calls the Bridge Restore Status endpoint on a regular basis to determine if the status of the restore is "STAGED_FOR_RESTORE"
- The Gateway calls the Bridge Get Restored Content endpoint for each file in the restore request and stores each file in the Gateway staging storage
- The Repository calls the Gateway Get Object endpoint and pulls the content into repository storage
- The Repository sends a notification to the Repository manager that requested the restore
Gliffy Diagram | ||||
---|---|---|---|---|
|
Notes
- This flow would be more consistent with the deposit and delete flows if files were references as part of a filegroup/object rather than as independent entities.
...