-
The Language Processing Framework enables ATLAS Content Management System to automatically process the textual information of the content items and thus help both the content user and providers to find relevant information quicker and more precise.
Six language processing chains (LPC) are supported in the scope of the ATLAS project - Bulgarian, English, German, Greek, Polish and Romanian.
This chapter of ATLAS technical documentation describes the anatomy of a LPC and provides guidelines how additional languages can be integrated in ATLAS.
-
The ATLAS system database contains information about the different domains handled by a single ATLAS instillation, accounts, data and domain registrations.
-
iViewer is a collective name for a group of plugins, responsible for rendering i-Publisher's business objects. More precisely, there are plugins for handling the HTTP requests and others for rendering the requested page.
-
ATLAS stores the definitions of the web sites and text-mining functionality in a relation database. Each domain has a separate core ATLAS database, so that data from different domains is completely separated.
This chapter describes the main database concepts used in the ATLAS core database.
-
This chapter enlists the language independent processing tools used by more than one LPC.
-
The chapter introduces the approach, chosen for the machine translation functionalities, in ATLAS.
-
The chapter briefs the reader about the automatic text categorization tasks, enlists some of the most popular approaches and describes, on a theory level, how the training and classification tasks are solved in ATLAS.
-
The chapter introduces the main concepts and approaches in the field of automatic text summary generation. Furthermore, it outlines the approach, chosen in ATLAS.
-
The chapter enlists the main components and prime functionalities provided by the ATLAS system.
-
The chapter provides information about the components integrated in the Bulgarian LPC.
-
The chapter enlists the currently integrated and adapted classification algorithms in ATLAS.
-
The chapter provides information about the components integrated in the English LPC.
-
The Atlas import export functionalities allow the reusing of important system entities such as widgets, content types and even whole sites.
-
Files (attachments) in ATLAS are stored in a separate data store. Currently, we are using PostgreSQL database to manage the contents of the binary files.
-
The chapter provides information about the components integrated in the German LPC.
-
The chapter provides information about the components integrated in the Greek LPC.
-
Overview of the i-Librarian web site basic components and how it is build
-
The chapter describes the common procedure for installation, configuration and starting an ATLAS component.
-
The chapter show how automatic translation is integrated in the Atlas system. Moreover, it lists the details and configuration of the machine translation providers.
-
The building blocks of content in a website are the content items. Each content item belongs to exactly one content type. The content item comprises of the following components: approval step, categorisation, properties, relations, history, revisions, selection.
-
Each website in Atlas is built of pages, like all ordinary websites.
-
The chapter provides information about the components integrated in the Polish LPC.
-
The purpose of this document is to help navigate through the major features of the Atlas system and act as a basic manual to help the user undarstand the concepts, resources and tools involved in the system.
-
The chapter provides information about the components integrated in the Romanian LPC.
-
HTTP requests in the Atlas system are handled by different servlets.
-
The chapter introduces the main concepts and approaches in the field of automatic text summary generation. Furthermore, it outlines the approach, chosen in ATLAS.
-
-
This section describes the base architecture of Atlas system.
-
The chapter depicts the main components and classes, which participate in the content item's approval mechanism.
-
This chapter describes technical and implementation aspects of the categorization module built in ATLAS.
-
There are some common properties, which all Atlas business objects posses - id, name, description and inserted, updated and deleted timestamp.
-
The content model component is a complex entity, which comprises of the following sub-components: content types, property bundles, properties and relations.
-
An overview of the EUDocLib web site basic components and how it is build using Atlas i-Publisher service
-
An incoming HTTP request is usually converted to a system request object and kept in TreadLocal.
-
Atlas is a component based system. The components are divided based on business logic and each represents a set of plugins, which correspond to the layers described in the previous section. The various plugin types are described in the next section.
-
This chapter enlists the required components which ATLAS depends on.
-
The document describes the technical aspects of the Atlas system - architecture, components, used technologies, key features, database structure.
-
This chapter describes the ATLAS summarization module.
-
ATLAS stores the text mining annotations in a separate database. A PostgreSQL relational database is used for storing the unique annotations per languages.
-
Widgets are page's building blocks. There are 24 types of widgets, each with designed to display different kind of content.
-
Aliases in Atlas are business objects implementing the com.tetracom.atlas.urlalias.api.IAlias interface.
-
The chapter describes the deployment specifics of all ATLAS components.
-
The chapter describes the functionalities and components, which are used to perform categorisation and data mining of a content item.
-
Each component in the Atlas system is a set of plugins. Most of the components have an identical structure.
-
This chapter contains diagrams of the sequence of actions and main participants involved in the building and using of a classification model.
-
The document is intended for people, who would like to get acquainted with the structure and components of the Atlas system. Moreover, this paper provides a base for future contributions to the system.
-
Some of the business objects, especially the pages and the widgets, are renderable, i.e. they are convertible to HTML.
-
Important phrases are divide into 7 groups according to their weights and displayed in a a tag cloud.
-
The actual content of the text mining annotations is stored in high-performance Lucene indexes. This chapter describes the structure of a text mining index and the main queries run.
-
Users and groups are a key part of the Atlas security concept.
-
Datasources and selections allow the Atlas user to apply a filter to the content they want to show on a website.
-
This chapter describes how the ATLAS technical documentation is organized.
-
The components in this chapter allow the tracking of changes, performed on a content item. They also enable the revertion of the content item to one of its previous versions.
-
The navigations are primary mechanism for moving around a website.
-
This chapter shows how a user request is handled in the Atlas system and which the general dependencies are between the plugin types described in the previous sections.
-
The stubs component is responsible for acquiring and providing the content for the list widget renderer in Atlas. Moreover, all backend operations related to grouping, sorting, paging and filtering of the content items are performed in this component.
-
This chapter gives a brief introduction to the ATLAS project - its goals, the challenges it addresses and the suggested solutions. More information about the ATLAS project can be found at http://www.atlasproject.eu/
-
The approval procedures(approval chains) in Atlas allow the user to specify the content items, which can be used in public websites.
-
The sitemap defines where the links from a certain widget will lead to.
-
The site cache service stores the HTML of the requested page.
-
Themes in Atlas contain mainly CSS style files and images used by the renderers. Nevertheless, they may contain different entities like templates and color scheme definitions. Themes contain undetermined number of files that are stored as one archive zip file.
-
With the access log funtionality various statistics of a website can be tracked by a statistics site.
-
The site search functionality determines which of the content types (and which of their properties) used in the selected website will be indexed by the search service.
-
“Site users” are called the users in certain website created by i-Publisher.
-
This chapter describes the cross-lingual information retrieval ATLAS sub-component.
-
The chapter outlines the processes for storing data from ATLAS and retrieving search results in ATLAS from the Nebula5 sub-system.
-
The chapter describes how CLIR is integrated in the Atas system.