Skip to content
This repository was archived by the owner on Jun 13, 2025. It is now read-only.

Home

Jump to bottom
haup_ca edited this page Oct 27, 2016 · 37 revisions

The Knowledge Finder allows the classification and indexing of any documents as well as web-based searching for information. Not only full texts are processed but also metadata. These are extracted from the data connections. Possible connections are: SVN, WebDAV, XML, databases, flat files.

So called crawlers are used to extract the metadata from a data source. The crawler uses the interfaces of the corresponding technology of the data source of which the metadata is to be extracted. Has a set of metadata in addition to the metadata attributes a reference to the full text document, the crawler evaluates this reference and importes the related documents. A metadata record is retrieved by the crawler, stored in the Knowledge Finder and prepared for indexing per data entry. The crawling is an offline activity, which is typically ran once a day due to the enormous amount of data in many projects. Then the data can be indexed.

The indexer now processes the metadata and full texts from the respective data sources and writes them into an inverted index. As part of the metadata indexing a metadata model is used. This flexible model represents the structure of the metadata and is used to process the metadata during the indexing and the search process. Each metadata attribute is treated individually in the indexing phase and stored as a separate value in the index. This allows quick filtering of records by metadata attributes. This procedure enables the user interface the display of facets filter based on the metadata attributes. The indexer does its work as well as an offline activity.

After indexing, the search engine can access the index and search the respective databases. For this purpose, this component runs alongside the actual search through the interaction with the user. Here, the processing of the query, the relevance determination, and presentation of results will take place. To perform the search, this component first transformes the information needs of the user in an appropriate form of representation. Subsequently, a search and the subsequent ranking is performed. Recently the search engine presents the result set within the user interface. To generate the facets, the search engine also uses the metadata model .

Unlike KnowledgeFinder I, this project adds a visualization of the meta data and provides an interactive user interface for navigating through the knowledge.

Main End-User Features

The KnowledgeFinder II project provides a base software which is adaptable to different use cases. It provides a list of features which can be easily modified to fit the current need. The Frontend - User Documentation throws light on the following topics

  • Full-text search

  • Visual Data Exploration

  • Menu navigation

For more information see Complete documentation

Subsystems

This project is divided in three modules to facilitate the adaptation and configuration for the differents instances and new requirements.

  • Data import

  • Frontend

  • Liferay Webservice

Clone this wiki locally