Install this Trifid plugin using:
npm install @zazuko/trifid-entity-renderer
And then add in the config.yaml
file the following part:
plugins:
# […]
entity-renderer:
module: "@zazuko/trifid-entity-renderer"
config:
# ignore some specific paths
ignorePaths:
- /query
Specify the path where the handlebars template is located:
plugins:
# […]
entity-renderer:
module: "@zazuko/trifid-entity-renderer"
config:
path: file:./some-path/your-template.hbs
Under the hood, this plugin uses rdf-entity-webcomponent, that accepts the same configuration options.
Add any of these options under the config section:
plugins:
# […]
entity-renderer:
module: "@zazuko/trifid-entity-renderer"
config:
compactMode: false
technicalCues: true
embedNamedNodes: false
You can configure if the plugin needs to perform any rewriting on the result to the SPARQL queries.
You can use the following configuration option rewrite
and set it to one of those value:
-
auto
(default value): if thedatasetBaseUrl
configuration value is defined (globally or at the scope of this plugin), then it will behaves as if the value was set totrue
, else likefalse
-
true
: rewrite the result of the SPARQL queries by replacing thedatasetBaseUrl
value with the current domain. -
false
: this will disable the rewriting mechanism. This is useful if your triples are already matching the domain name where your Trifid instance is deployed.
Using SPARQL it is possible to define some redirects.
This plugin can follow those redirects and render the final resource, if the followRedirects
configuration option is set to true
.
The default value is false
.
plugins:
# […]
entity-renderer:
module: "@zazuko/trifid-entity-renderer"
config:
followRedirects: true
redirectQuery: "…" # Select query used to get the redirect target ; needs to return a row with `?responseCode` and `?location` bindings.
The default redirect query supports http://www.w3.org/2011/http#
and http://www.w3.org/2006/http#
prefixes.
-
resourceExistsQuery
: TheASK
query to check whether the resources exists or not -
resourceGraphQuery
: The query to fetch the actual triples of the resource -
containerExistsQuery
: TheASK
query to check whether the container exists or not -
containerGraphQuery
: The query to fetch the actual triples of the container -
resourceNoSlash
: The handler will also check if there is a resource with a URL ending with a slash before running the container logic. Set this option to true to disable the resource exists query. Useful if you know there are no triples with container URLs.
npm run example-instance
And go to http://localhost:3000/ to see the result.