18: This is supported by the Gateway/Bridge specs. How it is actually implemented in the DDP may vary.

19: When versioning updates are added to Gateway/Bridge specs this will be supported. As with row 18, DDP implementation of the delete action may vary.

20: This is supported by the Bridge (List Deposited Content + Delete Content) but is not supported by the Gateway because there is no way to ask for the list of deposited content. This same functionality (list deposited content) would be needed to perform a complete restore, as noted in previous use cases. There has been some discussion of updating the Gateway Audit endpoint to allow for retrieving details about content/versions, but that endpoint is currently specific to a single object, so wouldn't be ideal for asking a broader question about all objects. It's worth considering if a new call should be added to the Gateway spec.

21: The Bridge deposit process deals exclusively with files. Any metadata for an object/work coming from the repository would need to included in a file by either the repository or the Gateway. Once versioning is in place in the Gateway/Bridge specs, updates to an object/work/filegroup would be considered a new version. How this looks in the DDP may vary depending on how/if the DDP supports versioning.

22: Once versioning is in place in the Gateway/Bridge specs, this will be supported.

24: This capability is not directly supported by either the Gateway or Bridge spec. On the Bridge, size information could be included in the List Deposited Content response or in the Get Audit History response. We haven't specified what would be in the audit history (considering it an implementation detail), but if we want to guarantee that specific information is captured and included for all objcts, that should be added to the spec. If we want to include size in the List Deposited Content response it will need to be determined how the Gateway would expose that listing to the repository (as discussed in item [20] above, there is not currently a call to request a deposited content list from the Gateway). Being able to provide sums for admin sets or collections would clearly need to happen within the repository, as neither the Gateway or Bridge are aware of these concepts.