• Page:
    Admin Portlet —

    An admin portlet is a pre-configured portlet that allows to perform certain administration tasks. See also Further Administration Portlets

    Admin portlets are accessible via the Portlet Explorer for users who have corresponding rights.
  • Page:
    Admin Portlet —

    An admin portlet is a pre-configured portlet that allows to perform certain administration tasks. 

    Admin portlets are accessible via the Portlet Explorer for users who have corresponding rights.
  • Page:
    Data Node —

    A data node is a container for operations producing or manipulating data. Each operation produces a table or a graph. The last table produced by the sequence of operations is the data node's result table. 

    A data node can be based on another data node in the same project, its parent node. If it has a parent node, the parent node's result table is the input of the data node.
  • Page:
    Data Node —

    A data node is a container for operations producing or manipulating data and resulting in a result table. It can be based on another data node in the same TIS Project, its parent node.

    A (non-empty) data node consists of

    • a sequence of operations, and
  • Page:
    Operation —

    An operation applies an operator with some operator settings to a data node. 

    Operations in a data node are aligned in a sequence where each operation manipulates the result of the previous operation. The sequence of operations is shown in the List of Operations in the Homepage of a data node.

    An operation can
  • Page:
    Operation —

    An operation is part of a data node. It applies an operator to this data node. It takes as input zero or one table (the last table produced by the sequence of operations in the data node or the result table of the data node referenced by the data node if the sequence is empty) and some settings, including parameter values. It produces a table or a graph.
  • Page:
    Operator —

    Operators are predefined functions to create or modify tables or  to create graphs in data nodes. An operator is applied to a data node as operation together with its settings. Operations in a data node are aligned in a sequence where each operation manipulates the result of the previous operation.

    An operator is added to a data node using the "Add" button in the rightmost column of a data node's "Operations" tab. See Operation page for details on this tab.
    Legacy operators can be updated using the "Update operation" button in the "Flags" column of the corresponding operator row, or from within the project properties window. See Operator upgrade page for details.
  • Page:
    Operator —

    Operators are predefined functions that manipulate or create contents, usually tables, in data nodes. An operator is applied to a data node as operation together with some general and some operator-specific settings. Operations in a data node are aligned in a sequence where each operation manipulates the result of the previous operation.
  • Page:
    Parameters —

    Parameters allow to set values to manipulate operations from outside of a project (e.g., from the TIS Board). Parameters can take values of primitive data types (e.g., text or a number) available in TIS or values defined by the settings of an operator  (e.g., scaling intervals in the Scaling 8.2 operator).

    Parameters are project-specific, i.e., the scope of a parameter is the project in which it is defined. A parameter from one project is not visible to other projects (however, values can be shared by several projects via TIS Tables).
  • Page:
    Parameters —

    Introduction

    Parameters allow to change values and settings of TIS Projects (general parameters) and of operators (parameters of operators)

    • from outside of the project (e.g., TIS Board) and
  • Page:
    Parent node —

    A data node another data node, the child node, is based on. The parent node's result table serves as input for the child node's first operation.

    See also Update process between data nodes and Data node recalculation modalities.
  • Page:
    Parent Node —

    A data node another data node, the child node, is based on. The parent node's result table serves as input for the child node's first operation.

    See also Update process between data nodes and Data node recalculation modalities.
  • Page:
    Project —

    A project is the largest building block of the TIS Editor. In a project, input data is converted to tables or graphs containing (parts of) this data in a desired format. The conversion is done by operations applying operators.

    The tables in a project are organised in data nodes and folders. A folder contains one or more data nodes. A data node contains a sequence of operations resulting in the data node's result table. 
  • Page:
    Roles —

    A role is a collection of rights. A user assigned a role inherits this role's rights.

    The following table describes the predefined roles of TIS.

    Role
  • Page:
    Roles —

    A role is a collection of rights. A user assigned a role inherits this role's rights.

    The following table describes the predefined roles of TIS.