technologies e.g. from the fields of document
analysis and language processing.
2 FABEGG SYSTEM
ARCHITECTURE
The FABEGG system consists of different
components. The most important ones for the
underlying paper are on the one hand the component
that allows construction of a document repository by
a company or a governmental authority. We will
stretch the possibility to insert forms into the
repository and hence, refer to this component as the
forms front-end hereafter. The second component is
the one that enables the use of the repository and
will be referred to as user front-end in the following.
The document insertion is organized as follows:
A governmental authority feeds documents and
forms into a document and template repository via
the FABEGG forms front-end. For the discussion
within this paper we mainly focus on the insertion of
forms that are part of processes within the authority.
The FABEGG forms front-end allows the authority
to enhance the forms with metadata that is necessary
to process them later on. Furthermore, it allows
adding metadata to support visual impaired users to
understand and to process these forms.
The FABEGG user front-end builds on this
information to present documents. The user can scan
a document to process and he will then have
different modes of access to it. For example the
document can be displayed in certain colour
combinations, in an enlarged mode or it can be read
to the user (cf. section 5).
In the next sections we will describe these two
components in more detail.
3 FORMS FRONT-END
FABEGG provides an interface to insert forms or
general documents into a repository. This repository
can be used like an information centre for a
company or a governmental institution where
relevant information can be found and downloaded.
In the following we focus on the insertion of forms
that are usually presented to the citizens as printed
documents. For digital forms a similar procedure is
possible.
In order to guide a blind or visual impaired user
through the form a set of help texts can be associated
with the document. This comprises text to explain
the general processing steps of the form as well as
help texts for each field to explain the user the kind
of information that is expected to complete a field.
To enable the forms recognition step from the
digital image a set of anchors is associated with a
document or form. In general, anchors are areas
where certain content is expected or which have
special features that allow identifying the form or
the form template, respectively in the repository.
4 DOCUMENT
REPRESENTATION
Documents and templates are contained in the
document repository. The information that is
necessary to process a document is stored in an
XML-format that is partially depicted in figure 3.
The left-hand side of the figure shows an excerpt of
a form, which students have to maintain during a
practical phase of their education.
In this example there is one anchor, namely the
word “Laufzettel” in the headline of the document.
When this anchor is found the upper left-hand corner
of the surrounding box of the anchor will serve as
origin for the positions of the fields in the document.
Then completion of the form can start. The
information for the relevant input fields is stored in
the XML-format file, which is partially depicted on
the right-hand side of figure 1. Here, the definition
of the data fields is shown in some detail. For each
field the distance to the anchor is given and
additional information like a field id and a fieldname
is also available. The element <FieldValue>
contains the corresponding value filled in the form
on the left-hand side. This value is determined at
runtime when the particular form template is
processed. The FABEGG system will try to read the
text at the specified position in the document. In a
first step the text read can be checked for syntactical
correctness. In this case the system can check the
text whether it coincides with the type given in the
<FieldType>-Element. The function that should be
used is specified in the <ValidateFunc>-Element
referring to a function called “Check4ValidName”
in our example.
5 USER FRONT-END
The user interface consists of a camera unit,
speakers, and a display. The camera unit enables
easy document handling and fast document capture.
IMPROVING ACCESSIBILITY TO BUSINESS PROCESSES FOR DISABLED PEOPLE BY DOCUMENT TAGGING
287