This Confluence wiki site, maintained by DuraSpace prior to the recent merger with LYRASIS, will transition from the duraspace.org domain to the lyrasis.org domain on Saturday, Nov 16 beginning at approximately 7pm ET. A period of downtime of 2-3 hours is expected. After the transition, this wiki will be available at https://wiki.lyrasis.org/. All links to duraspace.org wiki pages will be redirected to the correct lyrasis.org URL. If you have questions prior to or following the transition please contact: wikihelp@lyrasis.org.
Page tree

Archived

If you are looking for the last documentation in the 4.x series, see 4.7.5. Looking for another version? See all documentation.

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

« Previous Version 3 Next »

Fedora Repository (fcrepo4)

Browser Interface

The application can be accessed through the browser interface for demonstration purposes of the repository's basic functionality. Once deployed (see Deploying Fedora 4 Complete Guide) navigate to either http://localhost:8080/rest using the one click install or http://localhost:8080/<war file name>/rest using the tomcat or jetty servers.

REST API

The primary way for applications to work with a Fedora 4 repository is through the RESTful HTTP API.

  • The Fedora 4 HTTP API is generally a RESTful API. HTTP methods like GET, PUT, POST and DELETE are implemented on most resource paths. The API also relies heavily on content negotiation to deliver context-appropriate responses, and a HATEOAS-driven text/html response (providing a decent GUI experience on top of the repository).

Indexing Message Listener

In tandem with the main fcrepo4 webapp is the fcrepo-jms-indexer-pluggable webapp.  It can be configured to listen to the Fedora JMS topic, retrieve messages including pid and eventType, look up object properties, execute transformations, and pass this output to external applications providing search and triplestore functionality.

JMS Indexing Helper App

To support the differing needs for sophisticated, rich searching, Fedora 4 comes with a standard mechanism and integration point for indexing content in an external service.  This could be a general search service such as Apache Solr or a standalone triplestore such as Fuseki or Blazegraph

Frameworks

Hydra and Fedora 4

Error rendering macro 'excerpt-include'

No link could be created for 'Hydra and Fedora 4'.

Islandora and Fedora 4

Extending Fedora 4

Authorization Modules

Federation Connector

Storage Policy

Contributing to Fedora

Fedora is built with the contributions of developers just like you.  If you've found a bug, or have a feature you want to add, we would love your help.  Our Guide for New Developers includes links to our project resources (source code, issue tracker, mailing lists, etc.) and our Git workflow.

Maven Build System

 

  • No labels