Facets for enaio® fulltext

enaio® 10.10 »

Full-text hit lists also contain an area with facets – dynamic filters that can be used to restrict the hit lists based on properties.

The following hit properties are specified in the facets area:

Object type/application/edited/editor/created/creator

The number of hits with that property is specified for each property.

Hits are assigned to applications using groups of MIME types. This data is stored in database tables and can be customized for specific projects.

Users can activate/deactivate basic facets in enaio® client via their user-specific settings and activate list catalogs and date fields as additional facets for each object type. These facets are shown in a full-text hit list of the object type.

Configuring Facets

Facets for the 'Edited' and 'Created' basic parameter fields and facets for date fields of object types can be configured.

Configurations are optional; without configuration the following settings are used by default:

This month/Last month/This year/Last year/More than one year ago

For example, a breakdown into quarters can be configured.

It is configured with the custom-aggregations.json configuration file under \services\service-manager\config\.

The aggregations-cfg-example.json file is installed in this directory using quarters by default. This file can be customized and saved as custom-aggregations.json.

Further information can be found in the Elasticsearch documentation.

Configuration File

The configuration contains a definition range and an assignment range.

Definition range:

"definitions": [  
{ "names": [

Facet names for the interface

Names for languages are optional.

Without language versions: "name": "1. Quartal dieses Jahres"

{ "language": "de",
"name": "1. Quartal dieses Jahres" },
Label for German
{ "language": "en",
"name": "1st quarter of this year" },
Label for English
{ "language": "fr",
"name": "1er trimestre de cette année" }
Label for French
],  
"key": "firstQuarter_thisyear",
"from": "now/y",
"to": "now/y+3M-1s"

key: Technical name for assignment

from: Beginning of the time period

to: End of the time period

Time periods may not overlap.

},  
{ "names": [ Additional facet definitions
...  

 

Assignment range:

"assignments": [  
{ "objectType": 262152123, Specification of the object type using the internal type designation
"dateRanges": [  
{ "fields": [ "datum1", "angelegt" ],  Specification of one or more fields using the database names
"rangeKeys": [ Time periods for the specified fields
"thismonth", "lastmonth",
"thisyear", "lastyear", "older" ] 

Specification and order of the technical names of the time periods

Objects that do not fall into a time period are not listed within the facets.

},  
{ "fields": [ "datum2" ], Specification of one or more fields using the database names
"rangeKeys": [ Time periods for the specified fields
"thisyear", "lastyear", "older" ]  Specification and order of the technical names of the time periods
}  
...  

 

Likewise, an assignment of time periods to the basic parameter fields 'created' and 'modifytime' can be performed without specification of the object type. These assignments then apply to all object types for which no assignment is configured.