KLEKSI features a powerful frontend that allows visitors to search, view, and discover your collection online. The frontend is linked to your KLEKSI environment and installed on your own domain name or website.

As a result, visitors remain within your organization's branding and environment, while all collection data is managed centrally from KLEKSI.

Structure of the frontend
The standard frontend of KLEKSI consists of three main parts:


Overview page
The overview page offers visitors a visual introduction to the collection.

For example, the following can be shown here:

• Featured objects
• Collections
• Recent additions
• Themes
• Exhibitions
• Stories and context information

This page serves as the gateway to the collection.


Search and results page
Via the search page, visitors can search the collection using keywords and filters.

Here visitors can:

• Search by keywords
• Filter by various characteristics
• Sort search results
• Navigating large collections

The search results are updated almost immediately when visitors search or apply filters.


Object page
The object page displays all available information about an object.

Depending on the configuration, an object page may contain, among other things:

• Title
• Description
• Images
• Audio clips
• Videos
• 3D models
• Documents
• Relationships with other objects
• Linked thesaurus terms
• Linked Open Data references

The content of the object page is fully managed from KLEKSI.


Search function with Elasticsearch
The search functionality of the KLEKSI frontend is based on Elasticsearch.

Elasticsearch is a powerful search technology specifically developed for quickly searching large amounts of data.

Instead of searching directly within text, Elasticsearch uses an optimized search index. As a result, search results can be found within milliseconds, even with very large collections.


Advantages of Elasticsearch
Visitors benefit from:

• Lightning-fast search results
• Search suggestions while typing
• Full text search queries
• Support for multiple languages
• Flexible search options
• High scalability

This ensures the search experience remains fast and user-friendly, even with collections of hundreds of thousands or even millions of objects.


Advanced zoom function
KLEKSI supports publishing images in very high resolutions.

This allows visitors to zoom in on images to a detailed level, for example to:

• Brushstrokes to view
• to investigate material structures
• To study details of objects
• Inscriptions or markings to be read

The zoom function uses the same technology as online map services such as Google Maps.


How does this work?
When a visitor zooms in, the entire image is not loaded. Instead, KLEKSI automatically divides the image into small tiles that are loaded only when needed.

As a result:

• Loading times remain short.
• Less data traffic is used.
• Can very large images be viewed smoothly?
• Significantly improves the user experience.

Filter
Visitors can refine the collection using filters. This allows them to quickly find relevant objects without having to manually search through large numbers of results.

Examples of filters are:

• Manufacturer
• Material
• Technology
• Dating
• Collection
• Location
• Object type

Setting a field as a filter
To make a field available as a filter:

1. Go to Object types.
2. Click Edit Structure next to the desired object type.
3. Open the element containing the relevant field.
4. Click on the field.
5. Select Edit Field.
6. Enable the Set as filter option.
7. Save the change.

The field then becomes available as a filter within the frontend.


Manage filter order
The order in which filters are displayed can be adjusted.

• Go to Settings.
• Open the Filter Order section.
• Drag a filter to the desired position.
• Click Save Filters.

The new order is applied immediately to the frontend.


Smart sorting of filter values
Filter values are automatically sorted based on the number of linked objects.

The most frequently occurring values are displayed at the top.

This has several advantages:

• Visitors find relevant options faster.
• Scroll through long lists less.
• Better user experience.
• Higher search efficiency.

As a result, the most frequently used filter values automatically become the most visible.


Supported filter types
Not every field type can be used as a filter.

Currently, KLEKSI supports, among others:

• Text fields
• Selection lists

These field types are best suited for fast and reliable filtering within large collections.


Secured and protected content
When using roles and permissions, parts of the frontend can be hidden.

This allows you to, for example:

• Show exclusive collections to members.
• Restrict research information to researchers.
• Make high-resolution files available only to authorized users.
• Shield non-public objects.

The visibility of collections, objects, media, and supplementary information is fully managed from KLEKSI.

Text to speech
To make collections more accessible, KLEKSI supports automatic text-to-speech functionality.

The title, subtitle, and description of an object can be read aloud automatically.

This provides additional support for:

• People with dyslexia
• People with a visual impairment
• Visitors who prefer listening to reading
• Educational applications

The functionality contributes to improved accessibility and helps organizations comply with modern accessibility guidelines.

Important
The frontend of KLEKSI is directly linked to your collection data. As a result, changes you make in KLEKSI can be automatically published on your website.

Through the combination of powerful search technology, advanced filters, high-resolution media display, access control, and Linked Open Data support, KLEKSI offers a future-proof solution for the online presentation of heritage collections, archives, libraries, and museum objects.

Feedback form
Visitors can leave a comment on a specific object via the frontend. This can be used, for example, to provide additional information, a correction, a question, or other relevant remarks about the object. The visitor enters their details and the comment. In doing so, the visitor can indicate whether the manager or curator may contact them regarding the comment. If permission is granted, the visitor's email address is also sent and made available to the manager or curator. To verify that the comment has actually been sent by the visitor, the visitor first receives an email with a confirmation link. Only after the visitor has confirmed the comment via this link is the comment definitively sent and made available in KLEKSI.

Activate response form
To activate the comment form, go to Application Management in the left-hand sidebar menu and then to Application Settings. Next, open the Frontend tab. Here you can enable or disable the comment form. When enabling the comment form, you specify for which user role the feature should be available. Do you want all visitors to the public frontend to be able to leave a comment? Then select the same role that you have set for the frontend. If you are using the Member Portal module, you can choose to make the comment form available exclusively to logged-in members. To do this, select the role you have set for members.

This way, you decide who can use the feedback form. For example, you can make the feature available to:

• all visitors to the public frontend;
• logged-in members only.

If you link the comment form only to the member role, regular visitors to the public frontend cannot leave a comment.

View comments on an object
The administrator or curator can view the comments left for a specific object within the dashboard. These comments are displayed in the Comments element for the relevant object. This makes it immediately visible which comments, additions, or questions relate to that object.

Overview of all comments
In addition to the comments on an individual object, a separate "Comments" menu item is available in the left-hand sidebar of the dashboard. Here, comments on all objects are displayed collectively in a clear list. This eliminates the need for the administrator or curator to open each object individually to check for new comments. Comments that have been read or handled can be archived. This keeps the overview of active comments organized. Archived comments are not deleted and can be viewed again at a later time by opening the archive.

Set access to comments
The administrator can determine which users within the dashboard have access to the Comments feature. This is configured via the permissions of a user role. For each role, it can be determined whether users are granted read and/or write permissions for comments.

With read permissions, a user can view comments.
With write permissions, a user can perform actions that require edit rights, such as processing or archiving comments.
If a user does not have rights for comments, the Comments feature is not displayed in the dashboard.
In this way, it can be determined precisely per user role who within the organization has access to visitor comments.