STORIES OF TOMORROW First prototype of... · STORIES OF TOMORROW Students Visions on the Future of...

STORIES OF TOMORROW

Students Visions on the Future of Space Exploration

Collaborative Project in European Union’s 2020 research and innovation programme

Grant Agreement no. 731872

Call: H2020-ICT-22-2016

Deliverable D4.1

STORIES: First prototype of the System

This project has received funding from the European Union’s Horizon 2020 research

and innovation programme under grant agreement No. 731872

© 2017, STORIES consortium

Ref. Ares(2017)4760046 - 29/09/2017

STORIES of Tomorrow D4.1 STORIES First prototype of the system

STORIES 731872 of 76

Editor Miltiadis Anastasiadis (Motivian EOOD)

Date 29 September 2017

Dissemination Level Internal

Status Final



The STORIES Consortium

Beneficiary

Number

Beneficiary name Beneficiary

short name

Country

1 University of Bayreuth UBT Germany

2 Otto-von-Guericke University Magdeburg OVGU Germany

3 Helsingin Yliopisto UoH Finland

4 Ellinogermaniki Agogi Scholi Panagea Savvaae EA Greece

5 Nucleo Interactivo de Astronomia NUCLIO Portugal

6 Theofanis Alexandridis Kai Sia EE OMEGA Greece

7 Publisto Digital Applications EPE PUBLISTO Greece

8 Motivian EOOD MOTIVIAN Bulgaria

9 Creativitic Innova SL CTIC Spain

10 Societe d´economie mixte d´exploration de

Centres Culturel educative et de Loisirs SEM

SPACE France

11 WRO Hellas WRO Greece

12 University of California UoC USA

13 University of Arizona UAZ USA

14 National Astronomical Observatory of Japan NAOJ Japan

15 Curtin University of Technology CURTIN Australia



Contributors

Name Institution

Miltiadis Anastasiadis Motivian

Apostolos Pagkoutsos Motivian

Nikos Karapanagou Motivian

Ivona Ivanova Motivian

Nikos Papastamatiou OMEGA

Theofanis Alexandridis OMEGA

Ioannis Krommydas OMEGATECH

Andreas Diktyopoulos OMEGATECH

Constantine Abazis PUBLISTO

Giannis Paraskakis PUBLISTO

Jorge Lopez CTIC

Enara Artetxe González CTIC

Legal Notices

The information in this document is subject to change without notice.

The Members of the STORIES Consortium make no warranty of any kind with regard to this

document, including, but not limited to, the implied warranties of merchantability and fitness for

a particular purpose. The Members of the STORIES Consortium shall not be held liable for

errors contained herein or direct, indirect, special, incidental or consequential damages in

connection with the furnishing, performance, or use of this material.

The information and views set out in this deliverable are those of the author(s) and do not

necessarily reflect the official opinion of the European Union. Neither the European Union

institutions and bodies nor any person acting on their behalf may be held responsible for the use

which may be made of the information contained therein.



Executive Summary

This deliverable provides an overview of the stories collaboration platform and authoring

module, that are core in the Stories platform. The description summarizes work performed as

there are other deliverables that detail the work done.

Furthermore it provides an overview of the Stories hardware and software infrastructure that is

used to host Stories platform and enable running of the Stories first prototype in pilot schools in

the European Union. Furthermore the Stories requirements for the infrastructure required at

schools is provided, together with a mail for the help desk that the technical team has set up in

order to support pilot users in all selected schools.



Table of Contents

The STORIES Consortium ..............................................................................................................3

Executive Summary ........................................................................................................................5

Table of Contents ............................................................................................................................6

1 Introduction..............................................................................................................................9

2 Integration Plan ..................................................................................................................... 10

3 Collaboration Platform and API ............................................................................................ 12

3.1 The API .............................................................................................................................12

3.2 The security mechanisms ...............................................................................................12

3.3 The user interfaces .........................................................................................................13

3.4 ILLUSTRATIONS .............................................................................................................13

4 Stories Authoring Module ..................................................................................................... 18

4.1 Adding text to the story ..................................................................................................19

4.2 Adding images to the story ............................................................................................22

4.3 Adding video to the story ...............................................................................................22

4.4 Adding actions to the book assets (images, texts, videos, etc.) .................................23

4.5 Ordering assets ...............................................................................................................23

4.6 Asset inspector and locking items on pages ................................................................24

4.7 Book and page settings ..................................................................................................24

4.8 Preview e-book ................................................................................................................25

5 Analytics server and dashboard ........................................................................................... 26

6 Software tools used for the platform .................................................................................... 28

6.1 Unity3D ............................................................................................................................28

6.2 Autodesk 3DS Max ..........................................................................................................29

6.3 SketchUp .........................................................................................................................30

6.4 Drupal 7 ............................................................................................................................30



6.5 Symfony 2 ........................................................................................................................31

6.6 Doctrine ORM ..................................................................................................................32

6.7 MySQL..............................................................................................................................32

6.8 Apache2 ...........................................................................................................................32

6.9 PHP (v7) ...........................................................................................................................33

6.10 Ubuntu Server Distribution .............................................................................................33

6.11 Jasper reports .................................................................................................................33

6.11.1 JasperReports Server – General Information ............................................................. 33

6.11.2 Jaspersoft® Studio ..................................................................................................... 34

7 Infrastructure Hosting Stories .............................................................................................. 36

7.1 Hardware Infrastructure ..................................................................................................36

7.2 Software Infrastructure ...................................................................................................37

8 School required infrastructure ............................................................................................. 38

8.1 PC specs at schools .......................................................................................................38

8.2 For VR Support (optional - can be one in the entire school) ........................................38

8.3 AR .....................................................................................................................................38

8.3.1 AR Creation Tool ........................................................................................................ 38

8.3.2 AR Player ................................................................................................................... 39

9 Help desk ............................................................................................................................... 40

9.1 Project Management Tools .............................................................................................40

10 Conclusion and outlook ........................................................................................................ 41

11 User manual Annex ............................................................................................................... 42

11.1 STORIES Collaboration platform ...................................................................................42

11.1.1 LOGIN ........................................................................................................................ 42

11.1.2 MANAGE SCHOOLS ................................................................................................. 43

11.1.3 MANAGE CLASSES .................................................................................................. 44

11.1.4 MANAGE USERS ...................................................................................................... 46

11.1.5 MY PROJECTS .......................................................................................................... 50

11.1.6 MY PROFILE ............................................................................................................. 56

11.2 STORIES Authoring Module ...........................................................................................57



11.2.1 Adding text to the story ............................................................................................... 60

11.2.2 Adding images to the story ......................................................................................... 62

11.2.3 Adding videos to the story .......................................................................................... 63

11.2.4 Adding actions to the book assets (images, texts, videos, etc.) .................................. 65

11.2.5 Ordering assets .......................................................................................................... 66

11.2.6 Asset inspector and locking items on pages ............................................................... 66

11.2.7 Book and page settings .............................................................................................. 67

11.2.8 Preview e-book .......................................................................................................... 68

11.3 JASPER Analytics Server General .................................................................................68

11.3.1 Add User .................................................................................................................... 69

11.3.2 Add User Role ............................................................................................................ 70

11.3.3 Add new Data Source ................................................................................................ 71

11.3.4 Create new Report ..................................................................................................... 72

11.3.5 Run Report ................................................................................................................. 75



1 Introduction

This deliverable presents the Stories Platform infrastructure – hardware and system software –

and also the basic infrastructure required at each school in order to be able to run the Stories

software. The link for the system platform is accessible through the project portal

(www.storiesoftomorrow.eu) and has the name: STORIES PLATFORM (shown as banner

on the left part of the portal) and with URL: dashboard.storiesoftomorrow.eu that will

point to: 163.172.71.197

Stories platform comprises mainly of: the authoring tool, the collaboration tool, the analytics

engine server, the questionnaires, the 3D objects and AR and VR tools.

http://www.storiesoftomorrow.eu/



2 Integration Plan

The aim of this work is to:

Integrate all STORIES components into a functional environment providing all required

services.

Integrate the supporting networking infrastructures with STORIES functional

components

The work performed and presented in this deliverable forms the test-bed for the trials of the initial and consequently final prototype. The development of the application prototype follows a two-phase process, where the technical infrastructure and the application components will be tested and improved in order to satisfy all end users types in the best way. In this first phase, the technical infrastructure and the application prototype have been integrated and tested during an early application and evaluation phase by the technology providers. It must be pointed out that integration, has been carried within the platform environment, which includes integration of the implemented components between them, integration of the platform components with the selected technologies and integration with the real school environment in terms of technical infrastructure (networking schemes). Separate pilots will be made at different user / exhibition premises all over Europe, thus combining a critical mass of end users and test results.

The STORIES platform follows from the Q-Tales project and consists of the following

interrelated subsystems:

The STORIES Authoring Tool that facilitate the multi-path stories creation, adoption

and modification while at the same time will support collaborative work between students

working together in the same story and interactions between students, teachers and

experts in the domain. The authoring tool will allow for integration of different media,

including 3D objects and Virtual Worlds. The tool will be powered by Unity 3D, thus

supporting a cornucopia of 2D and 3D graphics, including 3D worlds, while it will

incorporate with AR and VR interfaces. As soon as the story is published it may be

viewed by the user through the Story Player. The Story Player may also be used by the

student during the creation phase, in a preview capacity. The Story Player Engine, which

will also build upon Unity 3D infrastructure, will retrieve the story from the STORIES

Repository and will execute the storytelling (browsing of the e-book). Since 3D, AR and

VR features may be included in the e-book, headsets (e.g. Oculus) and game consoles

come into play, in order to provide a unique experience to the user.

The STORIES Storytelling Engine part of the authoring tool that will offer scaffolds and

apps to help students to enrich their stories (pre-defined 3D objects and sounds,

proposed templates for the story presentation, easy to use video editor, text editors,

formulas editors, calculators). Using different techniques (including theatre play,

dioramas, paintings, animations, 3D printing objects, videos) students create and enrich

their story a scene at a time, bringing their ideas to life. Once completed they then use

the STORIES authoring tool to write their story in a variety of visual styles and import the

scenes they have made using different media. Sequencing events in a natural order

promotes understanding and stimulates the imagination, encouraging creativity and

helping pupils to come up with innovative new ideas.

The STORIES Collaboration platform and the Collaboration API of the STORIES

System. The Collaboration Platform contains the main web interfaces available to

students for them to explore the various modules (3D worlds building modules, VR and



AR content modules, Authoring and Player modules) and to coaches to monitor the

students’ progress and engagement with the aforementioned modules. The

Collaboration API is the tool that handles the execution of all the communication

protocols, and the synchronisation and the data transfer among all components of the

STORIES system; it also implements and monitors the main security mechanisms.

The STORIES repository database that will include the rich collection (organised

according to the themes, language, big ideas of science) the of students’ stories

available in EN, FR, EL, PT, FI and DE. An advanced search mechanism will support

easy retrieval according to the users’ queries.

The STORIES Advanced Interfaces that will provide enhanced experiences to the

viewers of the stories. The stories (or part of the stories) will be available through VR

and AR interfaces. Additionally the stories will be available to tablets and mobile devices.

The STORIES Analytics Dashboard Tool that will provide data to the teachers (for

their classes) and to the evaluation team in order to provide evidences for students’

performance on task and their Deeper Learning profiles. Within this technology-based

assessment framework all six deeper learning competences that follow from the

STORIES pedagogical principles will be assessed. Pattern-matching technology will be

used to process the log files and identify the key aspects of a performance

corresponding to the competences. This approach permits fully-automated partial

credit scoring against each of the skills from the framework.

Each of these components/subsystems is a separate information system designed to operate in

a standalone mode and/or in cooperation with the other components. The use of integration in

the STORIES ecosystem is to create value by accumulating, assembling, coupling,

consolidating, and stabilizing all the above components in order to build and deliver the unified

STORIES system. Therefore, the essence and nature of integration is focused on achieving the

intended level of stability, functionality, performance and quality of the STORIES components,

their services, and processes.

Stories integration has passed through several phases of development with the most important

one being the feedback that was received after the 2017 summer school event that was

organized by EA in Athens Greece and a large number of teachers commented on the

integrated platform, its functionalities and interoperability, this providing valuable input to the

technical team in order to bring forward a highly stable STORIES integrated platform that will be

used for the 1st pilot phase in schools in Europe.

In the next sections we provide a brief description of each core component, the technologies

that were used for the STORIES platform and the manual that complements the software

integrated platform and will accompany teachers and students in their usage of the STORIES

platform.



3 Collaboration Platform and API

The STORIES collaboration platform is designed using a fully modular architecture in order to ensure the scalability and the maintainability of the whole ecosystem. By modular design we mean the development of various sub-components that when combined, form a powerful web application. The most important components of the platform are:

3.1 The API

The STORIES ecosystem is comprised -apart from the collaboration platform- of a set of subsystems including the Authoring Module, the AR/3D Content Development Module, Players and Data Components such as Analytics and Business intelligence tools. A RESTful API is necessary in order to ensure the secure communication between the aforementioned components and the Collaboration platform. An architectural style called REST (Representational State Transfer) advocates that web applications should use HTTP as it was originally envisioned. Lookups should use GET requests. PUT, POST, and DELETE requests should be used for *mutation, creation, and deletion respectively. An API that adheres to the principles of REST does not require the client to know anything about the structure of the API. Instead, the server has to provide whatever information the client needs in order to interact with the service. An HTML form is an example of this: The server specifies the location of the resource, and the required fields. The browser doesn't know in advance where and what information to submit. Both sets of information are supplied by the server. This principle is called Hypermedia as the Engine of Application State (HATEOAS).

The API includes a set of endpoints. Endpoints are URLs that perform a single action on an Entity in the database. The API receives a call from an external component. External components are those that are not hosted in the same application context i.e. mobile applications on a given endpoint. Then the API forwards the request to the appropriate controller to handle it. Depending on the type of the request (GET, POST, PUT, DELETE), the controller executes the appropriate action on the target entity. The API responds to the client with a predefined response object as a part of a mutual agreed protocol of communication. In illustration 1 below we see an example of how the API communication protocol gets information for a selected user through an endpoint. We can easily identify the URL “/api/v2/user/1” which means that the external component requests from the API to fetch (GET request) from the 2nd version of the API (“/api/v2”) to iterate the user entities and return with information about the user with ID: 1 (“/user/1”). The JSON formatted response contains the information required to fully describe the user object requested. In Illustration 2 we can see an example of an error response generated by the API so that the external component can show the appropriate error message to the user. The API also includes an API documentation for the developers of external components to be able to understand the communication protocols and the various endpoints that the API includes.

3.2 The security mechanisms

In order to successfully transfer secure data between various components, a set of security mechanisms have been implemented. The first security mechanism is the required authentication of users using both credentials in the collaboration platform and Oauth tokens in the API.

OAuth is an open standard for access delegation, commonly used as a way for Internet users to grant websites or applications access to their information on other websites but without giving them the passwords. This mechanism is used by companies such as Google, Facebook,



Microsoft and Twitter to allow the users to share information about their accounts with third party applications or websites.

Generally, OAuth provides clients a "secure delegated access" to server resources on behalf of a resource owner. It specifies a process for resource owners to authorize third-party access to their server resources without sharing their credentials.

Designed specifically to work with Hypertext Transfer Protocol (HTTP), OAuth essentially allows access tokens to be issued to third-party clients by an authorization server, with the approval of the resource owner. The third party then uses the access token to access the protected resources hosted by the resource server. The second security measure is the delegation of access rights and the advanced ACL (Access Control Lists) that grant access on resources in the application depending on the access provided to the system in a hierarchical way. To be more specific each user group in the system delegates from another group with the root user group being the super user.

With the implementation of the aforementioned ACL the access on a resource is lifted up in the hierarchy of the groups (i.e. the access on a project acquired by a student by ownership when creating the project is lifted up to the teacher and the school headmaster without leaving the sandboxed area of a school). With the Digital Rights Management (DRM) the advanced access control lists and the Oauth token mechanisms we can ensure the security of the entire platform.

3.3 The user interfaces

The interfaces of the STORIES platform follow the best UX practices and have been implemented to help the students navigate through the various pages while allowing the teachers and the headmasters to manage their classes, accounts, projects, episode and assets.

3.4 ILLUSTRATIONS



4 Stories Authoring Module

The Stories Authoring Module is integrated in the collaboration platform and is it accessible

when the student clicks “Author” at the right of each episode.

After clicking “Author”, the loading screen appears.

If it is the first time the authoring tool is opened, the cover page of an empty e-book appears

(white area in the center of the screen).

On the top menu all the main functionality of the tool can be found.

On the left side menu bar are some shortcuts for some features of the main menu

(preview, save, undo, redo and delete the selected asset).

On the right side menu bar is the page manager where the user can move through

book spreads, add new spreads, rearrange and delete spreads.



There are also some shortcuts for navigating in the authoring tool:

The scroll bar of the mouse can be used to zoom in and zoom out.

With shift and scroll the user can zoom in and zoom out smoothly.

With Alt and left mouse click the user can move the page left and right.

There are several tasks that the user can do through the authoring tool and for some of them

there is the need the authoring tool to communicate live with the collaboration platform through

its API.

The main tasks are described in the following chapters.

4.1 Adding text to the story

The user can add text to any of the e-book pages. The users is able to resize, modify and style

the text she/he wants.



The user is also able to copy/paste text from other sources: To do that must paste the text to the

right side text box (point 1), then click import button in the text editor (point 2).

The user can style specific words inside the text. Spelling is also automatically checked for

errors and problematic words are marked with red color.



Text can be resized inside the page.



4.2 Adding images to the story

The user can add an image to any of the e-book pages. The user is able to resize and rotate the

image. There is a panel available that connects with the collaboration platform and presents

thumbnails of the images uploaded from the user for the specific episode. Double clicking on the

image places it on the current book page.

Additionally buttons helps the user to easily fit the image to the left and right page.

Button stretches the image to the container box size.

If the user or any of the team wants to add a new image to the e-book, first uploads it to the

collaboration platform in the specific episodes’ repository and then clicks the refresh button on

the top right of the panel.

4.3 Adding video to the story

Same for video, the user can add video(s) to any of the e-book pages to describe its story.

There is a video container that is added to the page. The user can resize it and move it to the

desirable place using the top menu. Video menu also provides tools for auto play, play loop,

start time, etc. The videos are also uploaded to the collaboration platform and then can be used

in the authoring tool.



4.4 Adding actions to the book assets (images, texts, videos, etc.)

Selecting an asset (e.g. image) the user can add actions to it. This is possible from the

“enhance” menu item of the top menu bar. The user can add sound, animation and link to an

external source (URL that opens in new tab).

Adding animation to an asset

Adding a sound to an asset.

Adding a link to an asset

4.5 Ordering assets

All assets in a page can be ordered so to appear one over the other. The user selects

the object and uses the ordering buttons to move these assets backward and forward.



4.6 Asset inspector and locking items on pages

Clicking the button on the bottom of the e-book spreads at the right menu, the

user can see all the assets used in the current pages. Through this can directly delete

some of them not used, find hiding elements behind other assets and also lock some of

them to avoid moving them accidentally when adding more assets to this pages.

4.7 Book and page settings

From workspace menu item in the top menu bar the user can set a background image for the

entire e-book as well as background images for the specific pages in a spread. Additionally

through “playlist” item the user can add sounds to the specific spread that start playing on page

turn (e.g narration).

Extra options are offered to the user to select if the page background should override book

settings meaning that if there is a book background the page background will be visible.



For the playlist, click add new to select the preferred sound from the sounds selection

panel.

4.8 Preview e-book

Clicking on the preview button, the user can view the e-book created.

Using the Stories logo, or the back button the user can return to the authoring environment.



5 Analytics server and dashboard

The STORIES analytics server and dashboard are used in order to analyze and evaluate

students’ performance based on data collected while designing their STORIES story telling

scenario. The Analytics server cannot be fully tested since there are no data so far and the

deliverable is submitted prior to have the STORIES pilots at schools.

The Stories BI Platform can be reached through a web browser. Authorized users can enter the

Platform by giving their credentials.

The analytics server is part of the overall STORIES platform and below are some screens from

the module:

Login function



Sample report from 1st questionnaire

Results from questionnaire

Sample data to test the BI-Analytics Server



6 Software tools used for the platform

This section details the list and a description of all software tools that have been used for

developing the Stories Platform. None of the users is required to have any of these tools, since

they are all integrated in the Stories Platform that runs in the technical partners’ premises.

The collaboration platform was developed in PHP using the Symfony 2 MVC Framework. The

core database -the database that is responsible for the functionality of the entire collaboration

platform- is a MySQL Ver 14.14 Distrib 5.7.19. The Object Relational Mapper (ORM) used for

the communication between the PHP code and the database is the Doctrine Project. The

Application Programmable Interface (API), which is used for the secure data transfer and the

synchronization of the various components, is also written in PHP using a Symfony 2 MVC

framework and complies with all the architectural guidelines and best practices of a RESTful

API. The entire application -Collaboration Platform + API + MySQL Database- is deployed on a

Linux (Ubuntu 16.04_LTS-server) server configured to support the selected architecture and

equipped with an Apache2 web server, a MySQL server and PHP7.0.

The authoring tool was developed with the Unity software platform and related tools. The portal

was developed with Drupal open source software platform and related tools and the analytics

server was developed using the Jasper reports software framework.

6.1 Unity3D

A free version of the software is used to compose the models as elements of a system for

interaction. It is for experiences, applications, games in general.

The game engine of Unity is used to create simulations for mobile devices and consoles. It is

adaptable to 2D and 3D graphics operating through programming. The features are as follows:

UX/UI can be manipulated. Assets and Textures can be added and played through. The

software is used to experimental and platform-specific topics, navigation and path finding are

also issues to respect. The modes for developing 3D or 2D projects can be determined

according to the specific cases given.

Main topics in the program are regarding: Graphics, Physics, Scripting, Multiplayer and

Networking, Audio, Animation,Timeline, UI, Navigation and Path finding, Services, Virtual

Reality, Open-source repositories, Asset Store Publishing. Also Platform-specific, Experimental

and Legacy Topics.

The installing and getting to the initial settings as a basic use of the program continues with

passing through the various asset workflows. Firstly, importing it directly into the assets and

then follows guiding the file into the Create section.

The Gameplay is using the Scenes, Game Objects, Components sections in order to add

interactivity and play through reading the input information.

The Unity can be used for adjusting the settings of an application in order to make a scan of a

barcode for instance or an image to create the augmented version of any model incorporated so

far. Moreover, it allows low polygon modelling to be composed in an environment and guided

through it.



6.2 Autodesk 3DS Max

Mesh and polygon modelling has been used in order to create low size models. An open source

demo version has been used.

The navigation and managing through the scenes in 3DS Max is as follows: Dragging and

Dropping throgh the MAX Scene Files, Mesh Inspector usage. Main particulars are regarding:

Workspaces , State Sets , Containers , Groups and Assemblies , File-Handling Commands ,

File-Handling Utilities , Scene Explorer, Scene States, Schematic Views.

For the operating system: Microsoft® Windows® 7 (SP1), Windows 8, Windows 8.1, and

Windows 10 Professional operating systems are possible with the program. Autodesk

recommends the latest version of the following web browsers for access to online supplemental

content:

Microsoft® Edge

Google Chrome™

Microsoft® Internet Explorer®Mozilla® Firefox®

Regarding hardware the required specifics are:

CPU: 64-bit Intel or AMD multi-core processor

RAM:4GB or 8 as recommendation

Three-button mouse as a pointing device

On 3DS Max characters are created, also areas can be easily modified and manipulated

through terrain polymodelling techniques.

The toolbars are as follows: Main toolbar; The Ribbon;Scene Explorer; Viewport Layouts;

Status Bar controls;Viewport label menus;Quad menu;Time Slider;Viewports;Command

Panel;Animation controls;Viewport Navigation;Slate Material Editor;Rendered Frame

Window. For further information can be found at knowledge.autodesk.com.

The documentation set for 3ds Max resides primarily online. (Two exceptions for offline users

are noted below.) Most documents are available from the Start menu>Programs

>Autodesk>program folder>Help folder, as well as from the Help menu within 3ds Max and the

Additional Help dialogue.

The Asset Browser provides access from your desktop to design content on the World Wide

Web. From within 3ds Max you can browse the Internet for texture samples and product

models. This includes bitmap textures (BMP, JPG, GIF, TIF, and TGA) and geometry files

(MAX, 3DS, and so on).

Productivity gains when the work is reduced by combining geometry from scenes or other

programs. 3ds Max supports this technique with the Import, Merge, and Replace commands.

Moreover, sharing of scenes and objects with others working on the same project using XRef

functionality is possible. The program supports plug-ins, image maps, models from other

programs, rendering images and animations, and saving and opening scene files by default.



6.3 SketchUp

The initial modelling started with mainly for objects of bigger size than the objects themselves, in

particular the landing sites. The free version of SketchUp Make has been used.

Regarding terrains, free imagery from NASA online directory has been the starting point for the

Mars contours and shaping of the sites.

It is used to create 3D models of buildings, furniture, interiors, landscapes, and many more. The

interface of the program is customizable to easily create settlements, housing, interiors,

landscapes, etc. The content is shareable and it is possible to walk trough animations, scenes,

printouts. Modelling for 3D printing is also in the features. The file extensions are adaptable to

other programs or can be converted in order to do so.

Another positive feature of SketchUp is that it can operate with the Google Platforms such as

Google Earth, for instance. Models can be located, as it also currently contains Mars as such

position.

Regarding exporting and importing models, Cad and pdf are possible to adapt. Visual creativity

is motivated as texturing can be added.

Compatibility is as follows: An internet connection is required to install and authorize Sketch Up

and to use some of the features and Microsoft Internet Explorer 9.0 or higher. Minimum

Hardware as recommended:

1 GHz processor

4GB RAM

16GB of total hard-disk space

500MB of free hard-disk space

3D-class video card with 512MB of memory or higher and supports hardware

acceleration. Please ensure that the video card driver supports OpenGL version 3.0 or

higher, updated.

The software allows creating specific workflow from a template a custom. The defaults help for

work discovery and renders graphics to an acceptable standard. Drawing 3D models, Creating

keyboard shortcut.

The Free version of SketchUp allows .dae/collada/ extension; digital elevation models/ DEM

fiels/ .dem, .ddf, kmz files /Google Earth/ .

The terrain modelling requires adjustment of hidden lines and usage of Sandbox tools. Other

downloadable plug-ins are also free of charge and useful for further investigation and shaping of

the models, rendering, as well.

6.4 Drupal 7

The Portal www.storiesoftomorrow.eu is built on Drupal technology which is a solution for

content management that’s balances well flexibility and simplicity. In most cases if a solution is

http://www.storiesoftomorrow.eu/



too simple, it can only be used for a single purpose; if it is too flexible, it may be too difficult for

newcomers to learn.

Drupal is designed to be the perfect content management solution for non-technical users who

need both simplicity and flexibility. It accomplishes this through a modular approach to site

building. Unlike other CMS's, Drupal isn’t a prefabricated toy truck, but rather a collection of

wheels, windshields, axles, frames, etc., that a toy maker can easily assemble. With Drupal, a

maker could create a toy truck, but she or he could just as easily create a toy airplane,

submarine, or robot. For this reason, Drupal may be described as both a content management

system and a content management framework—one unified system that strives to have the

strengths of both, without their deficiencies.

So, whether a site builder is looking to create a news site, online store, social network, blog,

wiki, or something else altogether, it’s just a matter of combining the right modules. The only

limitation is the creator’s imagination.

Drupal is a flexible CMS based on the LAMP stack, with a modular design allowing features to

be added and removed by installing and uninstalling modules, and allowing the entire look and

feel of the website to be changed by installing and uninstalling themes. The base Drupal

download, known as Drupal Core, contains the PHP scripts needed to run the basic CMS

functionality, several optional modules and themes, and many JavaScript, CSS, and image

assets. Many additional modules and themes can be downloaded from the Drupal.org website.

Drupal can also run on other technology stacks:

The operating system can be Windows or Mac OS instead of Linux.

The web server can be Nginx or IIS instead of Apache.

The database can be PostgreSQL or SQLite instead of MySQL, or a MySQL-compatible

replacement such as MariaDB or Percona.

Other operating systems, web servers, and databases can also be made to work;

however, the scripts that the software uses are written in PHP, so that cannot be

changed.

6.5 Symfony 2

Symfony is an MVC framework written in PHP. Its structure is designed to get the best out of the

MVC pattern, whilst maintaining great ease of use. Thanks to its versatility and configurability,

Symfony is suitable for all web application projects.

Symfony is based on the classic web design pattern known as the MVC architecture, which

consists of three levels:

1. The Model: this represents the information on which the application operates--its business logic.

2. View: this renders the model into a web page suitable for interaction with the user.

3. The Controller: this responds to user actions and invokes changes on the model or view as appropriate.

The MVC architecture separates the business logic (model)

and the presentation (view), resulting in greater

maintainability. For instance, if your application should run

on both standard web browsers and mobile devices, you

just need a new view; you can keep the original controller

and model. The controller helps hide the detail of the

protocol used for the request (HTTP, console mode, mail,

and so on) from the model and the view. And the model

abstracts the logic of the data, which makes the view and

the action independent of, for instance, the type of database



6.6 Doctrine ORM

Doctrine 2 is an ORM for PHP 5.4+ that provides transparent persistence for PHP objects. It

fundamentally uses the Data Mapper pattern, aiming for a complete separation between the

domain/business logic and the persistence in a relational database management system.

The advantage of the Doctrine mapper for the programmer is that it offers him the ability to

focus on the object-oriented business logic and worry about persistence only on a secondary

level. This doesn’t mean persistence is downplayed by Doctrine 2. However we believe that

there are considerable benefits for object-oriented programming if persistence and entities are

kept separate.

Entities are PHP Objects that can be identified over many requests by a unique identifier or a

primary key. These classes don’t need to extend any abstract base class or interface. An entity

class must neither be final nor contain final methods; it must neither implement clone nor

wakeup, unless it does so safely.

An entity contains permanent properties. A permanent property is an instance variable of the

entity that is saved into and retrieved from the database by the Doctrine’s data mapping

capabilities.

6.7 MySQL

MySQL is a relational database management system based on Structured Query Language

(SQL). The application is used for a wide range of purposes, including data warehousing, e-

commerce, and logging applications. MySQL is usually used for the purpose of a web database.

By combining MySQL with a scripting language such as PHP or Perl -both offered on our

hosting accounts- it is possible to create websites that will interact in real-time with a mySQL

database to rapidly display categorized and navigational information to a website user.

6.8 Apache2

Apache is the most commonly used Web server on Linux systems. Web servers are used to

serve Web pages requested by client computers. Clients typically request and view Web pages

using Web browser applications such as Firefox, Opera, Chrome, or Internet Explorer.

Users enter a Uniform Resource Locator (URL) to point to a Web server by means of its Fully

Qualified Domain Name (FQDN) and a path to the required resource.

The most common protocol used to transfer Web pages is the Hyper Text Transfer Protocol

(HTTP). Protocols such as Hyper Text Transfer Protocol over Secure Sockets Layer (HTTPS),



and File Transfer Protocol (FTP), a protocol for uploading and downloading files, are also

supported.

Apache Web Servers are often used in combination with the MySQL database engine, the

HyperText Preprocessor (PHP) scripting language, and other popular scripting languages such

as Python and Perl. This configuration is called LAMP (Linux, Apache, MySQL and

Perl/Python/PHP) and forms a powerful and robust platform for the development and

deployment of Web-based applications.

6.9 PHP (v7)

PHP is an extremely popular programming language. Created in 1994 by Rasmus Lerdorf, PHP

has grown in popularity to the extent that today, nearly eighty-two percent of websites use PHP.

Consequently, most of the Web relies on this language to at least some extent. With an

increasing number of people going online -including a rapidly growing number of mobile users

who often rely on relatively slow 3G connections- it is necessary for the servers that empower

the world’s websites to be able to react quickly to user requests. Studies show that forty percent

of people will abandon a web page that takes more than three seconds to load. This proves that

speed is a crucial factor in website design.

Significant changes to PHP have dramatically increased the performance of sites that use this

language. In fact, it is estimated that PHP 7 offers a 100 percent improvement in performance

speed compared to PHP 5.6. This major improvement in speed allows web developers to create

sites that provide interesting and engaging interactive features that still respond to user input as

quickly as modern web users have come to expect.

6.10 Ubuntu Server Distribution

Ubuntu is an open source operating system software for computers. It is one of the distribution systems of Linux, and is based on the Debian architecture. It is usually run on personal computers (PCs), and is also popular on network servers, usually running the Ubuntu Server variant, with enterprise-class features. Ubuntu runs on the most popular architectures, including Intel, AMD, and ARM-based machines. Ubuntu is also available for tablets and smartphones, with the Ubuntu Touch edition.

Ubuntu is the most widely used operating system running within hosted environments, so–called "clouds", since it is the most popular server belonging to the Linux distribution.

6.11 Jasper reports

6.11.1 JasperReports Server – General Information

TIBCO JasperReports® Server builds on TIBCO JasperReports® Library as a comprehensive

family of Business Intelligence (BI) products, providing robust static and interactive reporting,

report server, and data analysis capabilities.

These capabilities are available as either stand-alone products, or as part of an integrated end-

to-end BI suite utilizing common metadata and provide shared services, such as security, a

repository, and scheduling.



The server exposes comprehensive public interfaces enabling seamless integration with other

applications and the capability to easily add custom functionality.

This section describes functionality of the tool.

The heart of the TIBCO Jaspersoft® BI Suite is the Server, which provides the ability to:

Easily create new reports based on views designed in an intuitive, web-based, drag and

drop Ad Hoc Editor.

• Efficiently and securely manage many reports.

• Interact with reports, including sorting, changing formatting, entering parameters, and

drilling on data.

• Schedule reports for distribution through email and storage in the repository.

• Arrange reports and web content to create appealing, data-rich Jaspersoft Dashboards

that quickly convey business trends.

While the Ad Hoc Editor lets users create simple reports, more complex reports can be created

outside of the Server. One can either use Jaspersoft® Studio or manually write JRXML code to

create a report that can be run in the server.

6.11.2 Jaspersoft® Studio

TIBCO Jaspersoft® Studio is the editing software for TIBCO JasperReports®. It will help users

design and run report templates; build report queries; write complex expressions; layout visual

components like 50+ types of charts, maps, tables, crosstabs, and custom visualizations; and

much more. It integrates TIBCO JasperReports® Server to create powerful report publishing

workflows.

With Jaspersoft Studio you can build documents of any complexity from your data—from print-

ready in PDFs to interactive masterpieces in dynamic HTML, with navigation to interactive

components, like maps and charts that may be inside or outside the report. You can generate

high quality OpenOffice, PowerPoint , RTF, Word, and spreadsheet documents or you can

generate raw CSV, JSON, or XML documents. It's not difficult to build your own custom

exporter to suit any data need.



Using Jaspersoft Studio, users can access different types of data sources, including big data,

CSV, Hibernate, Jaspersoft Domain, JavaBeans, JDBC, JSON, NoSQL, TIBCO Spotfire®

Information Links, XML, or your own custom data source.

It is available as an Eclipse plug-in or a standalone application, Jaspersoft Studio comes in two

editions: Community and Professional. The Professional edition includes additional features, like

access to Spotfire, maps, and advanced HTML5 charts, as well as professional support.

The Community version of TIBCO Jaspersoft® Studio uses the Java Profiler JProfiler tool for

performance analysis and tuning.



7 Infrastructure Hosting Stories

7.1 Hardware Infrastructure

The hardware infrastructure hosting Stories platform is a mix of servers and advanced security

firewalls. Servers are aligned on a 3-tier architecture, entailing database, application and web

based layers.

Development Environment: Production Environment:

The specifications per server and other hardware components is listed below:

Processor

Product Collection Intel® Xeon® Processor D Family

Code Name Products formerly Broadwell

Vertical Segment Server

Processor Number D-1531

Processor performance

# of Cores 6

# of Threads 12

Processor Base Frequency 2.20 GHz

Max Turbo Frequency 2.70 GHz

Cache 9 MB



TDP 45 W

Memory

32 GB DDR4 ECC

Disks

2x 250 GB SSD

Network

Premium Line 300 Mbit/s

Provider AddOns

FTP Backup

DDoS protection

Hardware location:

Development Environment: Production Environment:

Using fake data of registry:

In-House Installation

Using real registry data:

Is installed on the technical

partners premises, following all

necessary compliance of privacy

policy.

7.2 Software Infrastructure

Ubuntu 16.04_LTS-server (64BITS)

WebServer: Apache2

PHP Version: PHP7.0

MySQL Version: Ver 14.14 Distrib 5.7.19

Jasper Reports Server Community Edition 6.4

Drupal 7.54

XAMPP 1.8.3



8 School required infrastructure

8.1 PC specs at schools

For the STORIES platform the PCs the students should have must have the following

recommended characteristics:

They need to have Google Chrome Browser or Firefox browser. Recommended with

current technology available are: Chrome v61 or Firefox v55

64 bit Windows (Windows 10 not 7)

8GB of RAM +

I5 processor +

Graphics card: DX9 (shader model 3.0) or DX11 with feature level 9.3 capabilities(e.g

NVIDIA GTX 750 or AMD equivelant)

8.2 For VR Support (optional - can be one in the entire school)

The equipment needed is: Oculus Rift + Touch(2 controllers). A strong PC with the

recommended configuration as shown in the following link:

https://support.oculus.com/help/oculus/170128916778795/

8.3 AR

8.3.1 AR Creation Tool

Tested independently from the STORIES platform, the AR Creation Tool requires an internet

connection from a regular browser. It has been tested from Windows and Linux PCs in Chrome,

Mozilla Firefox and Microsoft Edge, having the latter presented some problems with video

visualization.

At the moment of writing this document it has not yet been fully tested the integrated version,

although similar results are expected.

The full requirements regarding the browser choice will be distributed among partners in the

User’s Guide document CTIC is preparing for the launching of the AR system.

Regarding the asset types allowed for the AR creation:

.jpg and .png images are allowed

audios must be either .mp3 or .wav

videos can only be .mp4 with H264 codification (this is more an AR Player restriction

because of Android OS’s video reproduction restrictions)

models have to be OBJ uploaded in a zip file that contains the model (.obj) its material if

there is one (.mtl) and textures if there are (.png or .jpg)

https://support.oculus.com/help/oculus/170128916778795/



8.3.2 AR Player

AR Player currently works on Android 4.1 ‘JellyBean’ or above mobile devices, both phones and

tablets.

The quality of the experience will come from the device camera and memory. Slow or old

devices will probably present a slower performance like with any other game or application with

high graphic component.

Beyond having the QR Code to download the AR information and the markers at hand, it

doesn’t require any other configuration from users.

However, its functioning will also be described in detail in the User’s Guide document that will

be distributed among partners.



9 Help desk

In order to fully support schools and the smooth pilot running a help desk has been set up in

order to collect queries, answer to problems and generally support the pilot users in smoothly

using the Stories Platform. The help desk mail is: [email protected] and there is

also a list with names of technical people and telephone numbers that are circulated to pilot

users key responsible personnel so that they can use them for the whole pilot usage period.

9.1 Project Management Tools

STORIES technical team has identified Redmine (http://www.redmine.org/) as the STORIES

project management web application tool. The STORIES Project Management features and

scenarios that Redmine is fully satisfying are referred in the following list:

Flexible role based access control

Gantt chart and calendar

News, documents & files management

Feeds & email notifications

Project wiki

Project forums

Time tracking

SCM integration (SVN, CVS, Git, Mercurial, Bazaar and Darcs)

Issue creation via email

Multilanguage support

In the advanced steps of the project, Redmine will also be used as the issue tracking system in order to provide to the teachers and other school responsible personnel and University researchers a direct and fast communication tool with the developers and the technical team. Redmine is an open source project and is released under the terms of the GNU General Public License v2 (GPL).

For documents and code versioning purposes, the technical team identified Apache™

Subversion® (http://subversion.apache.org/): the Apache Software Foundation open source

version control system.

Subversion is universally recognized and adopted as an open-source, centralized version

control system characterized by its reliability, the simplicity of its model and usage, and its ability

to support the needs of a wide variety of users and projects, from individuals to large-scale

enterprise operations. Subversion can be used with a large number of opensurce, multiplatform

versioning clients such as TortoiseSVN (http://tortoisesvn.net/), RabbitVCS

(http://rabbitvcs.org/), Subcommander (http://subcommander.tigris.org/) and many others.

mailto:[email protected]

http://www.redmine.org/

http://www.gnu.org/licenses/old-licenses/gpl-2.0.html

http://www.gnu.org/licenses/old-licenses/gpl-2.0.html

http://subversion.apache.org/

http://tortoisesvn.net/

http://rabbitvcs.org/

http://subcommander.tigris.org/



10 Conclusion and outlook

Stories Platform first prototype version has been developed and installed in a production

environment within the technical partners’ premises. The platform design and implementation

has followed a series of updates and improvements based on users’ feedback, especially from

the summer school demo taken place the summer of 2017 at Marathonas bay in Greece, and

several technical iterations between the technical partners’ team.

The platform will run as from the 9th of October and will last several months – based on the work

performed in each of the pilot schools – and during this period, the technical team will resolve

issues, collect feedback and support pilot running, in order to move afterwards in the 2nd and

final prototype of the Stories Platform.



11 User manual Annex

STORIES OF TOMORROW USER MANUAL

This is the first version of the STORIES OF TOMORROW user manual

11.1 STORIES Collaboration platform

11.1.1 LOGIN

In this section the project’s login form appears where the user must fill in his/her username and

password to login to his/her account. By ticking the “Remember me” box, the user will be

automatically logged in whenever he returns, unless he chose to log out during his/her previous

session. If the user forget’s his/her password, he/she can reset it online.



11.1.2 MANAGE SCHOOLS

In the “Manage Schools” section the user can find all the existing schools and edit them or

create new ones.

In this section, the user can “Add New” schools. In order to do this, the user must fill in the

required fields with the following information:

School Name

School Headmaster

Country



Description

and then press the “Save” button.

In this section, the user can also “Edit” schools by changing any field completed in the previous

form.

11.1.3 MANAGE CLASSES



In the “Manage Classes” section the user can find all the existing classes and edit them or

create new ones.

In this section, the user can “Add New” classes. In order to do this, first he/she must fill in the

required fields with the following information:

Class Name

Class Teacher

School

Description



Furthermore, in this section, the user has the ability to “Edit” class information. To do this, the

user can change any field he completed in the previous form.

In the “Add Students” section the user can add new students and see the students who are

already in this class.

11.1.4 MANAGE USERS



In the “Manage Users” section the user can find all the existing schools and edit them or create

new ones.



In this section, the user can “Add New” users. To do this, he/she must first fill in the required

fields with the following information:

Username

Password

Confirm Password

Account Type (National Coordinator, School Headmaster, IT Administrator, Teacher,

Student)

If he/she tries to proceed to the next step without completing all the required fields, the above

image appears.



In this section, the user must fill in the following information:

Full Name(required)

Gender(required)

Phone Number(required)

Address(required)

City/Town(required)

Country

Remarks



In this step a summary of the information previously submitted appears.

In this area, the user can “Edit” user information. To do this, he/she can change any field of the

following fields:

Username

Email

Address

Phone

Full Name

Country

Description

11.1.5 MY PROJECTS



In the “My Project” section the user can find all of his/her existing projects, and

even “Edit”them. In this section, the user can “Add New” team members. On the bottom of

each box assigned to a team member the following functions are available:

Chat

Assign role to team member

Delete



In the area apearing bellow the team members, the user can create new episodes by clicking on

the “Add New” episodes button and then filling in the required fields with the following

information:

Title

Episode State

Description



or even create a new project by clicking the “Add New” button. After that, a modal pops up and

the user must fill in the following required fields:

Title

Account

Project Icon ( Drop files here or Click to upload)

and then click the “Create Project” button.

On the “View Assets” section, the user can drop files or click in the dropzone area to upload

them.Then, he/she stores the file in the “Project Assets” section. The uploaded files can be

separated into video, images, audio and text files.



The user can view the video or the image or listen to the audio files that he/she has already

uploaded by clicking the “View Video/View Larger/Listen” button, or delete a file by clicking

the “Delete” button.



Back to the “Edit” section, in the “CHAT” area on the right side of the screen, as you can see

in the screenshot bellow, the team members can chat with each other.



11.1.6 MY PROFILE

Here, the user must fill in all the following required fields with his/her information -in the

Personal Info tab:

Full Name

Username

Email

Phone Number

Address

About

and then press the “Save Changes” button.



In the “Change Avatar” tab, the user can drop files or click in the dropzone to upload them, in order to

change his/her avatar.

The last tab is the “Change Password” tab where the user can change his/her personal password by

filling in three fields:

Current Password

New Password

Re-type New Password

and then press the “Change Password” button.

Last but not least, there is the “Logout” button where user is redirected to the Home Page.

11.2 STORIES Authoring Module

The Stories Authoring Module is integrated in the collaboration platform and it is accessible

when the student clicks “Author” at the right of each episode.

After clicking “Author”, the loading screen appears.



If it is the first time the authoring tool is opened, the cover page of an empty e-book appears

(white area in the center of the screen).

On the top menu all the main functions of the tool can be found.

On the left side menu bar are some shortcuts for some features of the main menu

(preview, save, undo, redo and delete the selected asset).

On the right side menu bar is the page manager where the user can move through

book spreads, add new spreads, rearrange and delete spreads.



There are also some shortcuts for navigating in the authoring tool:

The scroll bar of the mouse can be used to zoom in and zoom out.

With shift and scroll the user can zoom in and zoom out smoothly.

With Alt and left mouse click the user can move the page left and right.

There are several tasks that the user can do through the authoring tool and for some of them

the authoring tool needs to communicate live with the collaboration platform through its API.

The main tasks are described in the following chapters.



11.2.1 Adding text to the story

The user can add text to any of the e-book pages. The user is able to resize, modify and style

the text as she/he likes.

The user is also able to copy/paste text from other sources: To do that she/he must paste the

text into the right side text box (point 1), then click the import button in the text editor (point 2).



The user can style specific words inside the text. Spelling is also automatically checked for

errors and problematic words are marked with red color.

Text can be resized inside the page.



11.2.2 Adding images to the story

The user can add an image to any of the e-book pages. The user is able to resize and rotate the

image. There is a panel available that connects with the collaboration platform and presents

thumbnails of the images uploaded from the user for the specific episode. Double clicking on the

image places it on the current book page.



Additionally buttons help the user to easily fit the image to the left and right page.

If the user or anyone of the team wants to add a new image to the e-book, she/he needs to

upload it to the collaboration platform in the specific episodes’ repository first and then click the

refresh button on the top right of the panel.

11.2.3 Adding videos to the story

Same for video, the user can add video(s) to any of the e-book pages to describe her/his story.

A video container is provided that can be added to each page. The user can resize it and move

it to the desirable place using the top menu. Video menu also provides tools for auto play, play

loop, start time, etc. The videos also need to be uploaded to the collaboration platform and then

can be used in the authoring tool.



11.2.4 Adding actions to the book assets (images, texts, videos, etc.)

Selecting an asset (e.g. image) the user can add actions to it. This is possible with the

“enhance” menu item of the top menu bar. The user can add sound and animation as well as

link to an external source (URL that opens in new tab).

11.2.4.1 Adding animation to an asset

Animation panel contains keyframes. The default keyframe is the initial position of the selected

asset (image in this example). To add a new move, the user should:

add a new keyframe,

move the selected image to the destination (new position) (point 1),

add the duration in seconds (point 2), and

save the second keyframe (point 3).

Finally to finish the animation one needs to click the “X” button on the top left of the animation

panel.

11.2.4.2 Adding sound to an asset.

This is possible within the “enhance” menu item of the top menu bar. When the user clicks “add

sound”, a panel appears where she/he can listen (clicking “P” button) to the sound. If the user

selects the sound and clicks “Ok” the sound is added to the selected asset.



11.2.4.3 Adding a link to an asset

This is possible by using the “enhance” menu item of the top menu bar. When the user clicks

“add link”, a panel appears where she/he should enter the link address including “http://”.

Alternatively she/he can copy – paste it like in the text editor menu.

11.2.5 Ordering assets

All assets on a page can be ordered to appear one over the other. The user selects the object

and uses the ordering buttons to move these assets backward and forward.

11.2.6 Asset inspector and locking items on pages

Clicking the button on the bottom of the e-book spreads at the right menu, the

user can see all the assets used in the current pages. Through this she/he can directly

delete some of them not used, find hidden elements behind other assets and also lock

some of them to avoid moving them accidentally when adding more assets to this

pages.



11.2.7 Book and page settings

By using the “workspace” menu item in the top menu bar the user can set a background image

for the entire e-book as well as background images for the specific pages in a spread.

Additionally through the “playlist” item the user can add sounds to the specific spread that start

playing on page turn (e.g. narration).

The user can choose if a page background will override the book background. This is for cases

the student want a page to have different background from the entire book.

For the playlist, click “add new” to select the preferred sound from the sounds selection

panel.



11.2.8 Preview e-book

Clicking on the preview button, the user can view the e-book created.

Using the Stories logo or the back button, the user can return to the authoring environment.

11.3 JASPER Analytics Server General

The Stories BI Platform can be reached through a web browser. Authorized users can enter the

Platform by giving their credentials.



Users can change the Locale of the System and the Time Zone as per their preference.

The BI Platform supports various user roles with different user rights. The JasperServer

administrator can add users, add user roles, create reports, create new themes, create new

Datasources and can perform various administrative tasks on the Platform.

11.3.1 Add User

Addition of new users is being made by the Control Panel of the Platform by selecting Manage

Users



By clicking on a user, the administrator can perform the following actions:

Enable the user

Disable the user

Delete the user

All users can be disabled or deleted except for the jasperadmin who is a built-in Administrator of

JasperReports.

Basic information that is needed to add a new user is:

User name (required)

User ID (required)

Email

Password (required).

11.3.2 Add User Role

Creation of new roles can be performed through the Control Panel by selecting Roles



By clicking on «Add Role…» a pop-up appears where users must enter the Role name and

press OK.

Upon selecting a role from the list of available ones, at the right panel of the Platform, properties

of the Role are presented (mainly it is presented the list of users that have this role).

11.3.3 Add new Data Source

Data sources are various connection profiles to different databases or structured sources where

data is stored.

JasperServer administrator can create a new data source by right clicking to Data Sources

folder and selecting Add Resource Data Source

There are various Data Source Types available, some of them are:

JDBC Data Source

JNDI Data Source

MongoDB Data Source

Bean Data Source

AWS Data Source

Azure Data Source and other

By selecting the preferred data source various information must be filled in to establish the

connection to the Data source. For the JDBC Data Source, below are presented the required

configuration details:



11.3.4 Create new Report

The creation of a new report is being made in two steps. User that has the appropriate right

must make the proper configuration to the JasperServer and he should design the Report to the

JasperStudio.

Configuration of the Report at the JasperServer is being made by right clicking at Reports

folder, then selecting Add Resource JasperReport.

Below is presented the screen where the setup of the report is taking place.



For setting up the Report, following information must be filled in in 5 different tabs:

A.) Setup

Name (required)

Resource ID (required)

Description

The JRXML file (required)

JRXML files are those that define the interface of the report and are deigned at the TIBCO

Jaspersoft® Studio. This tool is the editing software for TIBCO JasperReports®. It helps

designing and running report templates; build report queries; write complex expressions; layout

visual components like 50+ types of charts, maps, tables, crosstabs, and custom visualizations.

It integrates TIBCO JasperReports® Server to create powerful report publishing workflows.

With Jaspersoft Studio users can build documents of any complexity from data sources—from

print-ready in PDFs to interactive masterpieces in dynamic HTML, with navigation to interactive

components, like maps and charts that may be inside or outside the report. Users can generate

high quality OpenOffice, PowerPoint, RTF, Word, and spreadsheet documents or can generate

raw CSV, JSON, or XML documents. It's not difficult for someone to build his own custom

exporter that suits any data need.

By using Jaspersoft Studio, one can access different types of data sources, including big data,

CSV, Hibernate, Jaspersoft Domain, JavaBeans, JDBC, JSON, NoSQL, TIBCO Spotfire®

Information Links, XML, or his own custom data source.



Furthermore, the required fields of the following 4 tabs must be filled in so as to create a new

Report.

B.) Controls & Resources

C.) Data Source

D.) Query

E.) Customization

Upon completing all these steps the Report is ready to be used. Report creator can give

permissions on who can Read-Write-Delete-Execute Only or Administer the Report. These

permissions can be given at user or role level.



11.3.5 Run Report

When entering the platform, users can see the list of Reports that have access to. By pressing

on the Report, this is executed and the results are displayed at the screen.



Users can re-execute the report by pressing the refresh button.

They can zoom-in, zoom-out they can search for data inside the report and navigate through the

different pages of the results.

Users can also export the results of the report in various different formats:

PDF

Excel/ Excel paginated

CSV

DOCX

RTF

ODT

ODS

XLSX/ XLSX paginated

PPTX

STORIES OF TOMORROW First prototype of... · STORIES OF TOMORROW Students Visions on the Future of...

Documents

Transcript of STORIES OF TOMORROW First prototype of... · STORIES OF TOMORROW Students Visions on the Future of...