Syncing between Fedora and Duracloud

  1. general requirements
    1. more control (selection? policies? granularity? frequency?) over sync changesets
    2. more control over restore (by date? version? object? datastream?)
  2. flagging Fedora objects as "ready" for sync to DuraCloud
  3. granularity of sync and restore
    1. object level?
    2. datastream level?
    3. versioning support in sync?
      • are objects stored in DuraCloud based on pid, or pid & version-id?
  4. detecting bit rot
    • support for file repair
    • local utility for generating MD5 manifest keyed to DuraCloud content-ids?
  5. provenance support for Fedora/DuraCloud interactions
    • premis entry returned from DuraCloud to add to Fedora audit datastream?

Serving Fedora content from DuraCloud

  1. usecases
    1. serving video
      1. send high-bandwidth video to DuraCloud
      2. convert video to access version
      3. have local Fedora know about new rendition(s)
    2. sync from multiple locations
      1. Fedora object has multiple remote datastreams
  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.