| Excerpt |
|---|
Creating, modifying or deleting objects in the repository generates JMS events. The indexer listens to those events, retrieves the RDF from the repository. The indexer can be configured to process the event in various ways, such as copying the object RDF to a triplestore or indexing in Solr. |
...
If the Fedora Repository is be running at http://localhost:8080/rest/ – you can create, update and delete objects and datastreams using your browser, or using the REST API (see SPARQL Recipes ). Each event will trigger the indexer and be synced to Fuseki (or Sesame), which you can access at http://localhost:3030/ (if you have Fuseki running on its default port).
| Anchor | ||||
|---|---|---|---|---|
|
If you have a repository with existing content that you want to index, or have changed your indexing logic and want to reindex content, you can use the reindex REST API call in the indexer webapp.
...
| Code Block | ||
|---|---|---|
| ||
$ curl -X POST http://localhost:8082/reindex/foo/bar?recursive=false |
| Anchor | ||||
|---|---|---|---|---|
|
In some situations it is desirable to have multiple Fedora repositories all feeding into a single external triplestore. In order to accomplish this, we need to install and setup the three components (Triplestore, Fedora 4 Repository and JMS Event listener/indexer) as follows:
...