Table of Contents

• Introduction
• Mission Statement
• What Will RUcore Include?
• Why build RUcore now?
• Trusted Repository: Long-term preservation and access to information
• How does RUcore work?
• The Data Model
• Fedora, the Repository Architecture
• Fedora Metadata
• Information Management Tools and Standards
• Footnotes

The repository architecture is Fedora, [2] an open-source repository application developed by Cornell University and the University of Virginia through a Mellon grant. Fedora-Flexible, Extensible Digital Object Repository Architecture-is supported by a community of developers, including the Rutgers University Libraries, Tufts University, OhioLink, Cornell and the University of Virginia.

At its core, Fedora is a modular, extensible repository architecture that can store, manage, and deliver any type of digital information. Fedora makes no assumptions about the type of digital information it contains. Fedora can support pre-prints, books, journals, data sets, multimedia-anything that a participant considers useful information.

Fedora consists of two core modular service suites, written in web services description language (WSDL):

• Fedora Management Service (API-M): open interface for managing the repository, including creating, modifying, and deleting digital objects or components within digital objects
• Fedora Access Service (API-A): open interface for accessing digital objects and the behaviors (services) associated with them.

Fedora is designed to comply with the emerging information model for digital repositories, the Open Archives Information System Functional Model (OAIS) [3].

OAIS describes the core requirements of a repository that supports access to information for users, as well as the long-term preservation of information:

Fedora provides a suite of services that support the preservation of information, particularly the concatenation of all the metadata needed to manage, preserve, safeguard and make accessible.

« The Data Model

Fedora Metadata »