Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Also see: Fedora Asset Definitions, Fedora Resource Index



In order to run a large repository (more than 100k Fedora Objects) while using the ResourceIndex, you must have a 64-bit version of Java running on a 64-bit OS.

Rhyme setup

Connects to Oracle database on ora-iudlu-dev (urania). When we move Fedora to production, we will need to convert to a production database.

Uses port 9090 for service, 9005 for shutdown, and 9443 for redirect. This keeps it from conflicting with any Tomcat instances running on the same machine.

Current test setup (on mallow)

Must fedora-convert-demos to put correct hostname in demo objects.


Demo objext XML is in My Documents\fedora-2.0-src\dist\client\demo\foxml (there is a parallel directory for the METS versions, but it's unlikely that we will use these)

General notes

Start with:

No Format
  fedora-start mckoi

Stop with:
  mckoi-stop username password

Administration tool: {{{
fedora-admin 8080 fedoraAdmin fedoraAdmin


When copying Fedora objects between repositories, Fedora-level references to the local repository are changed. This means that for a datastream that redirects to another object in the same repository, or a behavior mechanism that contains the URL of the local saxon, the machine name and port number will be updated. However, references inside a datastream (like a reference in XSL) will not be updated.

Fedora bugs

Bugs can be reported to Fedora's Bugzilla
user: fedora-bugreport at
pass: bugreport


OAI export works automatically.


However, we will probably devise a separate export system to provide more data (unless recent updates to the OAI provider can meet all of our needs).

Data storage

The XML records that represent Fedora objects are stored in Fedora's objects directory (fedora2_0_objects by default). Underneath this directory, they are organized by a crazy date/time directory structure. Even though they don't have an XML extension, the files are really XML.


If we want to convert from Managed to External content, we can just purge and re-create the datastreams. Of course, this would lose any version information.

Behavior Mechanisms

For a mechanism that simply returns a datastream, put the stream name in parentheses (SCREEN), and reference it as a DATASTREAM parameter passed by URL-REF. For a mechanism that performs some operation, enter the URL of the service, adding any data references in parentheses. If the datastream is simply a short piece of text, you may be able to pass it as a VALUE, but typically you will want to pass it as a URL-REF, in which case the service will actually do the work of retreiving the object.


Wiki Markup
The most frequently used service is Saxon:

Space issues

We are going to initially use Its core stats are: Dual CPU 3GHz each, 6G RAM, 420G usable disk space.


The Fedora project has done some performance testing on a repository with 1 million objects.

Other system limits

How many items can share a PID prefix? A PID is a 64-digit string, so if we use the prefix "iudlp:", we have plenty of options for numerical data. We could even add a collection code, like "iudlp:hohenberger-1214".

Multiple repositories

We will likely want to run more than one repository, at least one for cataloging/testing use and one for production use. Will 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.


Moving data between repositories can be an issue if relationships are present.

Fedora will eventually have built in support for federated repositories.