View Source

Table of Contents:

Introduction

This integration is currently in development, and will provide a web-based UI for performing backups and restores to/from DuraCloud.

Scope:

Low-level storage options supported:

Web-based utility that does not require a sysadmin to run
Backups:
- 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:
- Frequency: On-demand and schedulable
- Selection:
  - User-supplied PID(s)
  - By date range
  - By DuraCloud item path
- 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.
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)

More TBD - extrapolating from discussions and meeting notes thus far

TBD - basic screen mock-ups