Gnowsis Documentation
Gunnar Aastrand Grimnes, gunnar.grimnes [ AT ] dfki.de
March, 2006.
Architecture
Gnowis Server is the "invisible" part of Gnowsis, where all the magic
happens. It includes the following components/functionality:
- Four storage repositories:
- ConfigurationStorage - stores gnowsis configuration: user details,
datasources, synchronisation details, etc.
- PIMOStorage - stores the user's PIMO.
- ResourceStorage - stores all the data about a user's resources,
emails, files, contacts, events, etc.
- ServiceStorage - stores data that individual datasources or
services might need to keep track of.
- ApertureDatasourceRegistry - This build on the config store and
provides a nice interface for listing, getting, adding and updating
Aperture Datasource to the Gnowsis Server.
- ApertureSynchroniser - This will spawn a thread to crawl each
datasource - the crawled data is put in the ResourceStorage.
- GnowsisSearch API - this allows sparql, serql and fulltext searching over all the data in gnowsis.
- PIMOService API - this provides functions for dealing with the PIMO, creating and removing classes, occurrences, relations, etc.
- Tagging API - this provides functions for getting and setting tags relating PIMO concepts to resources.
Gnowsis server also comes with some GUI components, these include:
- An installation GUI for creating default configuration files and
installing these in the right place.
- An configuration GUI for adding/removing and configuring
datasources.
- Support for a windows tray icon and mac system menu.
Technical details
All gnowsis repositories use Sesame2 repositories. Inside gnowsis these are availble as Repository objects and as Jena models (See Sesame2Jena).
The repositories that keep the user's data (PIMOStorage and ResourceStorage) are full-text indexed, this is done using Lucene. (See LuceneSail).
Links
Other things to read to learn more about gnowsis-server: