Child pages
  • Coordinating Fedora Instances
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

We want to run more than one repository, at least one for cataloging/testing use and one for production use. Will Cowan thinks it may be useful to keep one centralized repository for the master metadata and periodically export that data to one or more production repositories.

Fedora will eventually have built-in support for federated repositories.

Tentative plan:

  • All data is ingested to the "development" repository.
  • As each collection is finished, its contents will be exported, and imported to the production instance.
  • Periodically, an incremental update will be run to sync the development

Big questions:

  1. Are we preserving the data in the "development" repository or the "production" repository?
    1. What kind of load will the preservation system put on our server? Is this load better suited to the dev server or the production server?
    2. Does the dev server have enough space to store everything?
  2. Is it possible to "update" objects on the production server and maintain version history for these updates only?
  3. Is it better to do incremental updates per collection? Or over the entire repository? Does it hurt to have "junk" data in the production repository?
  • No labels