Skip to main content

PoolParty Linked Data Frontend Template Guide

Abstract

PoolParty Linked Data Frontend Template Guide

The templates for the Linked Data Frontend reside in the frontendRoot directory that can be found here:

  • /opt/poolparty/data/frontendRoot (Linux)

  • C:/User/poolparty/PoolParty/data/frontendRoot (MS Windows)

Note

Starting from PoolParty 2024 Release 2 only installations on Debian 12 as the tested distribution are fully covered by our SLAs. While we are happy to assist with installation on other distributions, this support is provided on a best-effort basis or through our dedicated Development Support package. Support for new installations on systems running MS Windows has been discontinued from the PoolParty 2024 Release 2.

The basic structure of the templates in a PoolParty installation is as follows:

default

Default template delivered with a PoolParty installation

  • conf.vm ... common settings. Here, common variables and configuration options are defined.

  • vars.vm ... variables used in all templates. Here you can find URI definitions shortcuts.

  • foot.vm ... footer of the template used in all page setups

  • head.vm ... header of the template used in all page setups

  • makros.vm ... set of shared functions that are used in other templates

  • server.vm ... html view of the server page

  • lang

    • de.vm ... German labels

    • en.vm ... English labels

  • js

    • script.js ... collection of java script functions. E.g. showIndex formulates a SPARQL query to collect all concepts of a project, starting with the respective character.

  • project

    • html.vm ... html view of the project

  • resource

    • html.vm ... html view of a resource. Distinction between concepts and concept schemes

    • visual.vm ... visual view of a resource (concept, concept scheme)

    • concept.vm ... view of a concept

    • conceptscheme.vm ... view of a concept scheme

    • map.vm ... covering available languages

custom

Templates in the custom directory overwrite templates in the default directory. Different templates can be defined down to the project level.

To have a different template for a project you have to create a directory for the project in the custom directory named like the projectID of the project.

This only works if the projectID does not contain signs that are not allowed while creating Linux folder names.

For example a projectID like 'project/myThesaurus' would not work because of the '/'.

Summary

  • custom/<projectID>/server.vm overwrites

  • custom/server.vm

and

  • custom/server.vm overwrites

  • default/server.vm

As you can see from the default structure you can have a template per

In this section: