Syncing between Fedora and Duracloud
- general requirements
- more control (selection? policies? granularity? frequency?) over sync changesets
- more control over restore (by date? version? object? datastream?)
- flagging Fedora objects as "ready" for sync to DuraCloud
- granularity of sync and restore
- object level?
- datastream level?
- versioning support in sync?
- are objects stored in DuraCloud based on pid, or pid & version-id?
- detecting bit rot
- support for file repair
- local utility for generating MD5 manifest keyed to DuraCloud content-ids?
- provenance support for Fedora/DuraCloud interactions
- premis entry returned from DuraCloud to add to Fedora audit datastream?
Serving Fedora content from DuraCloud
- usecases
- serving video
- send high-bandwidth video to DuraCloud
- convert video to access version
- have local Fedora know about new rendition(s)
- sync from multiple locations
- Fedora object has multiple remote datastreams
{"serverDuration": 109, "requestCorrelationId": "6625e785b7f1c618"}