Although access to an IntBook may be restricted
by an optional authentication layer, the installed book
can be readably available for generic usage. Inputting
the book URL into the browser starts the user inter-
action. The IntBooks web-application is responsible
to deliver all the content and multimedia assets to the
user browser, also providing the turn page function-
ality to the book. The generated content that initially
could be supplied in the form of a L
A
T
E
X document,
is now readable and has been transformed, for exam-
ple, into Adobe Flash format. The server is also re-
sponsible to choose the most suitable output format,
according to the browser capabilities.
For more sophisticated IntBooks, the server de-
livers a web-service for variables storage where the
client application can read and optionally write. This
functionality is configured as part of the IBK file. The
IntBook’s example TexMat (see Section 7) makes in-
tensive use of this functionality, making it a highly
responsive environment to user interaction (e.g. al-
lowing randomly generated exercises).
4 RICH USER INTERACTION
The basic user interaction for every IntBook layout
is the page turning functionality. But this can be a
little limiting to the content that can be delivered. To
warp this, a read/write link is available for the client-
side delivered content, enabling conditionality linked
to the smallest user interaction. This way during user
interaction with the book, let’s say a particular page as
a multiple choice survey, and the next question would
only appear after the previous is correct, using this
read/write link, the client application could check if
the answer was correct and record every answer the
user would give.
Implementing a similar functionality with page
refreshing would drastically increase band-width re-
quirements, create a not so smooth user interaction,
and would probably break page navigation. This is
a relevant characteristic to maximize the user expe-
rience and intended for quizzes, pools, surveys, ex-
ercises, tests, etc, and it’s achieved through storable
variables on the server. It enables the application to
“remember” the user, and the user to review all of his
past answers.
These server variables are strong-typed and de-
clared in the IBK file. During installation on the
server the variables are allocated for a per user instan-
tiation and changes to these variables are logged for
usage by reporting tools.
5 AGGREGATION AND
RE-USABILITY
In this topic we simply use the classical idea of “re-
use, not repeat”. IntBooks can also be viewed as a
collaborative system, where a particular book can be
built from fragments of other books or from other en-
tire books. Different authors may work, for exam-
ple, in different books, in different formats and merge
everything in a uniform book. Obviously, the author
dependencies are kept during all the process. Since
the IBK format is a format for fragmented content,
entire chapters can be imported from book to book.
Because disciplines have similar chapters, concepts
are interconnected. Since some courses are created
from the merge of two intensive book courses and not
all information is relevant, re-utilization is a key fea-
ture. Avoids content repetition and guarantees that an
explained concept has only one meaning across the
various books. The mechanism that manages frag-
ments also incorporates bridges to some web reposi-
tories (e.g. for extracting L
A
T
E
X source from Planet-
Math).
This linking between books is dynamic, so when
a chapter or concept is improved with examples, the
other books using that source are also improved. As
future work we plan to improve the search engine that
allow authors to find and link published contents of
other IntBooks into their own books.
6 USER MANAGEMENT
As in most e-learning platforms, there is a trend to
mimic the organizational hierarchy of an institution.
In a learning environment there are the obvious stu-
dent and teacher roles, and as in any user-based plat-
form there are the typical administrator and manager.
The IntBooks platform is no exception, and it re-
quires a centralized, delivering and control system.
The created authentication, authorization system, was
molded as an institution library, makes only sense, be-
cause our object of development was centered on the
book. An institution may have various libraries (sets
of books) and books may be categorized. A teacher
assigns a book to his teaching class (set of users),
and all the students (users) can start using it. This
might appear to be a complex system, but it’s also
very scalable. It can be as simple as an administra-
tor uploading the books, and creating user accounts,
and it’s ready for usage. Using teachers role, enables
decentralized management of users and permissions.
This role is also meant for accessing the students data,
and statistics collection. The administration system
CSEDU 2009 - International Conference on Computer Supported Education
306