Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: removed the Custom Namepsace registry information as it on the RDF best practises page now

...

Code Block
fcrepo.streaming.parallel:false

If you are running Fedora on a multiprocessor machine you can level parallel processing across single requests by turning this option on.   Parallel processing of streams can boost the retrieval speeds of the RDF associated with objects with large numbers of inlinks (ie dependent objects with memberOf associations).  Enabling this option in conjunction with increasing with cacheSize parameter in your repository.json file can boost retrieval speeds significantly.

Skolemizing to Hash-URIs

Code Block
fcrepo.bnode.hash-uri=<true|false>

With this property set to 'true', Fedora will skolemize incoming blank nodes to hash-URIs (with UUID fragments) on the base URI to which the request was addressed. By default this feature is turned off for backwards compatibility.


Allowing user updates to certain server managed triples 

You can relax certain restrictions on updating some server managed triples using the following setting:


Code Block
fcrepo.properties.management=relaxed


For details please refer to the following article: How to allow user-updates to certain server managed triples.

Custom Namespace registry

This optional feature allows an administrator to provide a list of custom namespace prefixes that will override the default prefix registry. The custom namespaces are loaded on start-up via a YAML file.  The namespaces can be modified while Fedora is running.  Changes may take a few minutes to take effect.

Below is a sample YAML namespace configuration file, custom_namespaces.yml.  The example contains a single custom namespace for the sake of clarity; you may list as many as you like.

Code Block
awesome: http://example.com/awesome/

Fedora can activate the file by using the -Dfcrepo.namespace.registry system parameter, either on the command line or by adding it to the list of other params that provide paths to other configuration files:

Code Block
mvn jetty:run -Dfcrepo.namespace.registry=/my/fedora/path/custom_namespaces.yml

Once Fedora is running, checking the available namespaces should return the list of custom namespaces and not the system generated namespaces:

Code Block
curl -ufedoraAdmin:fedoraAdmin  http://localhost:8080/rest/

# Status 200
# @prefix premis:  <http://www.loc.gov/premis/rdf/v1#> .
# @prefix test:  <info:fedora/test/> .
# @prefix memento:  <http://mementoweb.org/ns#> .
# @prefix rdfs:  <http://www.w3.org/2000/01/rdf-schema#> .
# @prefix webac:  <http://fedora.info/definitions/v4/webac#> .
# @prefix acl:  <http://www.w3.org/ns/auth/acl#> .
# @prefix vcard:  <http://www.w3.org/2006/vcard/ns#> .
# @prefix xsi:  <http://www.w3.org/2001/XMLSchema-instance> .
# @prefix awesome:  <http://example.com/awesome/> .
# @prefix xmlns:  <http://www.w3.org/2000/xmlns/> .
# @prefix rdf:  <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
# @prefix fedora:  <http://fedora.info/definitions/v4/repository#> .
# @prefix xml:  <http://www.w3.org/XML/1998/namespace> .
# @prefix ebucore:  <http://www.ebu.ch/metadata/ontologies/ebucore/ebucore#> .
# @prefix ldp:  <http://www.w3.org/ns/ldp#> .
# @prefix dcterms:  <http://purl.org/dc/terms/> .
# @prefix iana:  <http://www.iana.org/assignments/relation/> .
# @prefix xs:  <http://www.w3.org/2001/XMLSchema> .
# @prefix fedoraconfig:  <http://fedora.info/definitions/v4/config#> .
# @prefix foaf:  <http://xmlns.com/foaf/0.1/> .
# @prefix dc:  <http://purl.org/dc/elements/1.1/> .
...

Suppose, you later decide that "awesome" namespace was not required. Edit the file /my/fedora/path/custom_namespaces.yml to remove the "awesome" namespace line, save the file and wait a moment or two, then check the namespace output again:

...

More information on this feature can be found at the Best Practices - RDF Namespaces page.