Skip to content
Go to file

Latest commit

* Add membership triples to responses. Add default DirectContainer properties when not supplied

* Add basic ITs for verifying that membership is present for the head version of resources with a DirectContainer

* Fix date precision mismatch between membership index and memento timestamps. Add more membership ITs, move some from FedoraLdpIT. Block duplicate membership properties on DCs

* Remove get membership queries for situations in which no tx is present. In practice, they are never used since GET requests use short lived transactions

* Enable a few more tests

* Fix test failures

* Switch to returning timestamp instead of string when adjusting timestamps for membership ranges. Extend delays between versions to avoid flapping

* Remove second index datetime index for mariadb

* Additional indexes for date ranges. Separate update queries per db

* Remove extra indexes

Git stats


Failed to load latest commit information.


**PLEASE BE ADVISED:** this branch (master) is currently the main branch for 6.0 development. It is a work in progress! While it will build and any unignored tests will pass, the code-base is not currently in working order and will not compile into a functioning application. Any pull requests for the current production release should be made against the `5.x-maintenance` branch.

Build Status

JavaDocs | Fedora Wiki | Use cases | REST API |

Fedora is a robust, modular, open source repository system for the management and dissemination of digital content. It is especially suited for digital libraries and archives, both for access and preservation. It is also used to provide specialized access to very large and complex digital collections of historic and cultural materials as well as scientific data. Fedora has a worldwide installed user base that includes academic and cultural heritage organizations, universities, research institutions, university libraries, national libraries, and government agencies. The Fedora community is supported by the stewardship of the DuraSpace organization.

Technical goals:

  • Improved scalability and performance
  • More flexible storage options
  • Improved reporting and metrics
  • Improved durability


The current web-deployable version of Fedora can be downloaded from the Duraspace website or from Github. These artifacts can be deployed directly in a Jetty or Tomcat container as described in the guide to deploying Fedora.


Contributions to the Fedora project are always welcome. These may take the form of testing the application, clarifying documentation or writing code.

Code contributions will take the form of pull requests to this repository. They also require a signed contributor license agreement on file before a pull request can be merged. New developers may wish to review this guide as it explains both the process and standards for test coverage, style and documentation.

Getting help

There are two community mailing lists where you can post questions or raise topics for discussion. Everyone is welcome to subscribe and participate.

Many of the developers are available on the #fcrepo IRC channel, hosted by

In addition, there are weekly technical calls which anyone may join.

Building and running Fedora from source

System Requirements

  • Java 11
  • Maven 3.6.3
$ git clone
$ cd fcrepo
$ MAVEN_OPTS="-Xmx1024m -XX:MaxMetaspaceSize=1024m" mvn install

The compiled Fedora war file can be found in ./fcrepo-webapp/target. This can be deployed directly to a servlet container as described in the deployment guide.

If deployed locally using a war file called fcrepo.war, the web application will typically be available at http://localhost:8080/fcrepo/rest.

There are two convenient methods for testing the Fedora application by launching it directly from the command line.

One option is to use the "one click" application, which comes with an embedded Jetty servlet. This can be optionally built by running:

mvn install -pl fcrepo-webapp -P one-click

and can be started by either double-clicking on the jar file or by running the following command:

java -jar ./fcrepo-webapp/target/fcrepo-webapp-<version>-jetty-console.jar

By default, a Fedora home directory, fcrepo, is created in the current directory. You can change the default location by passing in an argument when starting the one-click, e.g.:

java -Dfcrepo.home=/data/fedora-home -jar fcrepo-webapp-6.0.0-SNAPSHOT-jetty-console.jar

An alternative is use the maven command: mvn jetty:run

$ cd fcrepo-webapp
$ MAVEN_OPTS="-Xmx512m" mvn jetty:run

For both of these methods, your Fedora repository will be available at: http://localhost:8080/rest/

Note: You may need to set the $JAVA_HOME property, since Maven uses it to find the Java runtime to use, overriding your PATH. mvn --version will show which version of Java is being used by Maven, e.g.:

Java version: 1.8.0_31, vendor: Oracle Corporation
Java home: /usr/local/java-1.8.0_31/jre

To set your $JAVA_HOME environment variable:

export JAVA_HOME=/path/to/java

If you have problems building fcrepo with the above settings, you may need to also pass options to the JaCoCo code coverage plugin:

$ MAVEN_OPTS="-Xmx1024m" mvn"-XX:MaxMetaspaceSize=1024m -Xmx1024m" -Djacoco.agent.ut.arg="-XX:MaxMetaspaceSize=1024m -Xmx1024m"  clean install
You can’t perform that action at this time.