4.2.2. Creating views

Structure → WissKI Entities and Bundles → Views → + Click Add View
It is also possible to define your own views if you want to create lists based on special filter criteria:

For "View Settings" and Show: Select "Wisski Entitiy".
A view can be created as a page or block or both. In the following example a page is selected (in a block the list would appear directly in the block):
Check "Create a page" under "page settings".

Then the following field appears:

Select the desired display format here under "page display settings", e.g. "Unformatted List", "Table", etc. The format can also be changed afterwards.
In addition, a check mark can be set at "Create a menu link". The link to the view will then appear at the selected position. If necessary, the menu link can also be selected or changed afterwards. The following options are available:

Under the settings there is a preview, which updates itself after each change.
Important: First the filter criteria should be selected!

Title The title that is displayed when you click on the view.
Format Here you can change the display format. Under Settings the settings for the respective format are made.

Important: The field "Entity ID" should never be removed! But it can be hidden by selecting the field and checking "Exclude from display"!
The paths to be displayed in the view are specified here. The order in which the fields are displayed can also be set here. You can also display the title, i.e. the title defined by the title pattern of a bundle/group.
Important: All fields must originate from the same bundle/group!

Set references from the field of the view to the corresponding records:

  • If the link is to be set to the data record in question via the title:
    Select the field -> Rewrite results -> Check "Output this field as a custom link" -> Link path: /wisski/navigate/{eid}}/view?wisski_bundle=enter corresponding bundle ID
    z. B. /wisski/navigate/{{eid}}/view wisski_bundle=bab2e96b12847b3c7a424e3cb331d7dd
  • If you want to link to a record from other fields:
    Example: The bundle/group on which the view is based is "Work". In the bundle "Work" there is a field "Collection", which also has its own bundle.
    • 1. if the field "Collection" should refer to the bundle "Work":
      Select field -> Formatter -> "Plain text" -> Check "Link to Wisski Entity".
    • 2. if the field "Collection" should refer to the bundle "Collection":
      Select field -> Formatter -> "WissKI Link Formatter".
Filter Criteria

The bundles and paths/contents by which the filter is to be performed are entered here.

  1. Define 1st bundle:
    Add -> Check Bundle/Group -> Add and configure filter criteria -> select: Operator "Is equal to" -> Check the relevant bundle/group -> Apply
  2. Set further filter criteria:Add -> Check the relevant path (the paths are sorted by bundles/groups) -> Operator: Select filter criterion -> Value: Specify value -> Apply
    For example, "Personal data" was selected as bundle, further filter criterion: Only painters should be displayed.
    Add -> Check "Personal data -> Occupation" -> Operator: Is equal to -> Value: "Painter".


Meaning of the operators:

  • Is equal to: The value must exactly match the field entry.
  • Is not equal to: The field entry must not match the specified value. Only data records for which the field is filled are taken into account.
    → Can also be used as "Is not empty". For this, enter a value that never occurs, e.g. "%".
  • Contains: The value must occur somewhere.
    → Attention: The query is very slow!
  • Starts with: The field entry must begin with the specified value.
    → is faster than "Contains
  • One of: Works like "Contains", but: Here you can enter several comma separated values. The query is made according to the scheme "Value 1" OR "Value 2".
    → Attention: The query can be very slow!
Sort Criteria The paths according to which the sorting of the display is to be structured are specified here.
Page Settings
  • Path: Part of the URL, e.g. /example_page
  • Menu: The menu link can be specified or changed here if necessary.
  • Access: Here you can set access restrictions for individual permissions or user roles.
Header Here, for example, the hit list can be displayed (tick at "Result summary") or an introductory text can be inserted (tick at "Text area").
Footer → same selection as "Header".
No Results Behavior Display with a hit list of 0 → same selection as "Header
If the entry remains empty, the page remains empty, apart from the title.
Pager Here you can set how the result navigation works, how many hits are displayed per page, etc.



Use AJAX Better select "No".
Caching Switch off in case of doubt if the view has problems loading.
CSS class Here you can apply self-defined CSS classes to the view, e.g. to change distances, etc.


Example: View in display format Geofield Google Map

Example: View in Table Display Format with Introductory Text