Versions Compared

Old Version 16

changes.mady.by.user Chris Wilper

Saved on

compared with

New Version Current

changes.mady.by.user Anonymous

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Info
titleSeptember 12th, 2012 - CloudSync v1.1.0 Released!

For downloads, release notes, and more, see CLOUDSYNC11

Panel
titleBGColor#ddddff
titleFedora CloudSync

Overview:

Excerpt

Fedora CloudSync is a web-based utility for backing up and restoring Fedora content in DuraCloud.

This is a community-driven open source project. Want to get involved? Sign up for the mailing list and introduce yourself!

Mailing List:

For development and feature discussion, please see the fcrepo-cloudsync mailing list:

More Information:

Table of Contents:

Table of Contents

Introduction

Excerpt

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

Scope:

  • Any (user-selectable) set of objects or datastreams stored in Fedora.
  • Any externally-managed ("E") datastreams available via http or file URLs.

Low-level storage options supported:

  • All (interacts with Fedora via its APIs)

Status

In-development. The initial goal is to have a deliverable web application with basic selective backup and restore functionality in time for OR11.

Requirements

  • Web-based utility that does not require a sysadmin to use
  • 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)
    • 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)

More TBD - extrapolating from discussions and meeting notes thus far

UI Design

Add/Forget Repositories and Spaces

Image Removed

Copy Object(s)

Image Removed

Select by Query (TBD)

Select by Browsing (TBD)

Related Meeting Notes

...