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

RUcore will provide a permanent, open-access digital archive for the information resources originating at Rutgers University. It will include:

• primary source materials (photographs, data sets, digital video and audio, preprints, technical reports, grant reports, etc.)
• Theses and dissertations created at Rutgers University
• Significant special collections from Rutgers University Libraries, including New Jerseyana, materials from the Institute of Jazz Studies, labor collections, and the papers of significant statesmen and politicians from New Jersey.

Learn more about collections...

In addition to collections, over the next two years, RUcore will provide web-based tools that are easy and intuitive to employ, including:

• A web-based digital workflow management system to allow faculty to add resources to RUcore and to customize metadata for indexing the resources.
• A script and indexing page to allow any project to easily add collection searching to a project website, so that project resources housed in RUcore can be searched and displayed from the project website.
• A web archiving toolkit, which will periodically create snapshots of websites, maintaining the website's hierarchical structure, according to a timetable established by the website owner, to provide an historical "audit trail" for the website.
• An Open Archives Initiative (OAI) facility to support sharing resources with other initiatives via harvesting from RUcore.
• An e-journal platform for creating, managing and publishing e-journals.
• Integration with Sakai, for pulling RUcore resources into Sakai courses.
• A SCORM-compliant course management system to create courses and educational resources that can be exported to any SCORM-compliant course management system (WebCT, Blackboard, etc.)
• A concept map utility for clustering RUcore resources into personal collections, based on concept maps.

« Mission Statement

Why build RUcore now? »