| Structure |
| Repository Gateway specification - Need to have understanding of what object is, groupings of content and metadata that will be preserved. In OTM API, Bridge doesn't hold that notion. By the time content reaches the Bridge it is just bitstreams. Challenge is that pushes the understanding of the groupings into the Gateway. Is a need for repo to not hold that meaning.
- Manifest approach?
- Adds one request, could potentially be a lot overall
- Agreed on nested identifiers - changes made to docs
- Best practices for DDPs - could pull out practices we can't expect DDPs as a whole to do, but are recommended - OCFL
- Follow same pattern for deletes and restores as we do for deposits?
|