FSter xml “condition” tag

This tag is part of the visualization policy, it is used in file and folder content objects to define which RDF objects they have to show.

Schema

The following schema is the conditions part of the FSter schema
Download FSter configuration schema: FSter.xsd

Overview

Conditions can be:

• applied to the current object, when we use the self_conditions tag (i.e., in file and folder);
  
• applied to the enclosed content objects, when we use the inheritable_conditions tag (i.e., in folder, static_folder and set_folder);
  
• inherited from parents;

Each condition is the part of a SPARQL select query and it is composed by:

• a metadata attribute that is an RDF predicate in the query;
  
• a value attribute that is an RDF object in the query,
  Note: The value can contain strings, metadata from the current content object ($self{metadataName}) and metadata from the parent content object ($parent{metadataName}); when metadata is a subject we can use /subject (e.g., value="ThisIsTheMime-$self{nie.mimeType}AndTheParentSubject$parent{/subject}")
  
• an operator attribute that is additionally applied to the query as a filter (can be is or isnot, the default is is)

Example

The following example shows how to create a folder for each music artist (subject) in the RDF repository and to show inside it the list of files by that artist
Download conditions_example.xml