Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Info

The following requirements have been extrapolated from discussions with potential users so far. Please feel free to add comments below.

Initial Priorities

  • Web-based utility that does not require command line access
  • Has a REST API for invoking from other services/UIs
  • Backups to DuraCloud:
    • Frequency: On-demand and schedulable
    • Selection:
      • User-supplied PID(s)
      • User-supplied queries involving date ranges and other datastream/object attributes (e.g. custom "ready for sync" flags)
    • Content: Fedora object XML, inline datastreams, managed datastreams, and external datastreams
    • Granularity: Object-level, but provides a flexible way to filter out datastreams/datastream versions.
  • Restores from DuraCloud:
    • Frequency: On-demand
    • Selection:
      • User-supplied PID(s)
      • By date range
      • By DuraCloud item path
      • Via RDF search of Fedora repository (when available)

Longer-Term / Nice to Have

  • Provenance:
    • Provides a standard way to record restore events, or an option to hook into a messaging queue so that they may be recorded as required by the institution (via a custom PREMIS datastream, etc.).
  • Fixity
    • Report on differences between what's stored in Fedora and in DuraCloud
    • Automatic and manual repair of Fedora-DuraCloud inconsistencies
    • Report on Fedora-Fedora inconsistencies (FOXML vs computed, as a built-in service?)
    • Report on DuraCloud-DuraCloud inconsistencies (Stored vs computed, via fixity service)