Page tree

Old Release

This documentation covers an old version of Fedora. Looking for another version? See all documentation.

Skip to end of metadata
Go to start of metadata
RDF support is a core feature of Fedora 4, used as the primary data format for the REST API.  A triplestore is not bundled into the repository itself.  Instead, Fedora 4 sends events when the repository is updated, and the Indexer copies RDF from the repository to an external triplestore to keep it in sync with the repository.  This pattern, which is also used for search functionality for the same reasons, allows maximum flexibility about what triplestore to use, and removes the overhead of keeping the triplestore in sync from the core repository functionality.

In order for resources to be indexed in the triplestore, they must be flagged as "Indexable". See documentation under External Search for how to mark resources for indexing.

Triplestore Setup

Instructions for how to setup the triplestores currently supported by the JMS indexer: Fuseki and Sesame.  Other triplestores that support SPARQL Update may also work, but have not been tested.

Indexer Configuration

Creating, modifying or deleting resources in the repository generates JMS events. The indexer listens to those events, and retrieves the RDF from the repository.  The indexer can be configured to process the event in various ways, such as copying the resource RDF to a triplestore or indexing in Solr.

SPARQL Recipes

This page provides detailed steps for creating repository content via the REST API, and SPARQL queries to demonstrate that content has been synchronized to an external triplestore.  For more details on setting up triplestore sync, see External Triplestore.  Much more information about the REST API is available at: RESTful HTTP API and Another Take on the REST API .

  • No labels