1. Service Cloud for INTI
Université de Franche-Comté – GRDI
University of Pécs – Research Team on TD & ICT
Péter ÁCS Ph.D. – Csilla FILO
21-23 Mars 2012 – Tours France

2. Territorial Intelligence Service Cloud (TISC)
Why Cloud
?
Like a crossway with signposts.
In the Cloud we can found:
Application directory
Participants directory
2

3. Problem
We have participants from several institutions participating
is several projects in time and in space. These collaboration
points are overlaps each other.
We have a lot of different applications different service
providers.
We would like:
• Use existing solutions
• But stable connectivity points
• Flexible in supporting organizational complexity
• Projects, institutions, …. 3

4. The TI portal is a public space
4

5. TISC is behind the portal for participants could have access to a “Cloud”
5

6. TISC for users has 6 important basic function
• Shows palette of the accessible services (and give access as it is
possible)
• Give search possibility for information about other participants
individuals and institutions
• Give possibility to keep up to date the users own data
• Manage other users and institutions, status, rights and identification
and data depending on the rights of logged in user (distributed
management of the data)
• Decision making support for groups (projects, institutions, groups)
• Publicly of participation
6

7. Inside TISC the users have a list of services available
7

8. One of the tools to integrate is
The new CooSpace from DEXTER
New document management, scheduling, alerts, and more…

9. Project coordination tool in CooSpace – (Summer)
Working modes:
• Planning project
• Managing project
Planning phase
• Tasks (content, schedule, resources)
• Views (Gantt, pert, task list, resouce list) & export
Managing phase
• Tasks (responsibilities, deliverables (definitions), deadlines,
progress indication)
• Views (Gantt, pert, task list, resouce list, plan & real
comaration) & export
Super-project view (Tasks-are projects.)

10. Project coordination tool – simple structure
Super-project
Task
Project (Sub-project)

11. Users can participate in projects can have
relation to institutions and can be member of
any group
11

12. How the users will be in the cloud?
A.)
1. The user having the appropriate right creates user (Sets the:
name, e-mail, password, home group)
B.)
1. The user having the appropriate right creates user
(Sets the: name, e-mail, home group)
2. E-mail verification: Password setup e-mail. A letters asking user
to give a password and agree the participation. (This e-mail sets the
email address verified as well.)
12

13. How the users will be in the cloud?
C.)
1. The user having the appropriate right creates user
PROPOSITION (Sets the: name, e-mail, home group)
2. The appropriate group (based on the home group assignation)
decide on this proposal. (E-mail goes to participants of the
decision, to ask them to decide.) According to a decision method,
the process ended, on decision or deadline.
3. In the case of positive decision. E-mail verification: Password
setup e-mail. A letters asking user to give a password and agree
the participation. (This e-mail sets the email address verified as
well.) 13

14. How the users will be in the cloud?
D.)
1. The user create the own registration at
the public surface. (The proposed user is
going to created in the default group
assigned for.)
2. The appropriate group (based on the home group assignation) decide
on this proposal. (E-mail goes to participants of the decision, to ask
them to decide.) According to a decision method, the process ended, on
decision or deadline.
3. In the case of positive decision. E-mail verification: Password setup
e-mail. A letters asking user to give a password and agree the
participation. (This e-mail sets the email address verified as well.)
14

15. Automatizms
We would like to distribute the management task to keep the
data live.
• If a user become member of a project, institution or group and it entails
that they will automatically receives the applications and access
assigned for.
• If a user become member of a project, institution or group the group
manager automatically receives possibility to keep update the
participation data.
• If the user changes the password in TISC, it will be relevant
automatically for all application.
• If user membership decision took place, the membership is getting
real, no further operation needed.
• If the user changes the contact data, it will be available for other
participants immediately
• We use translation if it is available. (If not we use the original text.)15

16. Aspects of TISC
TISC has two aspects providing services:
16

17. For applications it is an LDAP service for authentication
17

18. Application integration levels
• Registered application. Application described, and listed, linked for
the assigned or all users. (No authentication, no further integration)
• Authentication level integration. The application is described and
listed, linked for the assigned or all users. The application using
LDAP to authenticate the users (The authorization could takes place
using web service or LDAP group membership.)
• SSO (Single sign-on) level integration. The application is described
and listed, linked for the assigned or all users. The link passes the
session of the users to another application. No re login required. (The
authorization could takes place using web service or LDAP group
membership.)
18

19. For management it is statistics, information about usage and
participants from all over the word
19

20. Objectives
From the point of view of INTI it is a directory of
participants, but it is also tool structuring the participation.
One person can be member of different
projects, organization units, groups.
These relations could be used for:
• Make public information transparent
• Offering services available for groups
• Get contact with each other individually
• Communicate with the help of tools integrated
• To decide on membership and registration
• To decide on general purpose proposals
• Keep update a member and membership data. 20

21. What we have done
(Before 2011 december)
• We have discussions on functionality
• We have the revisions of strategic plan
• We database plan (now revision V5)
• We web service environment installed (one switch missing)
• We have database and LDAP server installed (It was ready before the
project)
• We have the application (nor ready) version installed
• We have an environment for development
• We have program architecture designed and implemented
• We have login functionality imlemented (using LDAP)
• We have the list application implemented
• We have a list of user functionality partly implemented
• We have the geolocation data
21

22. Current tasks
We make structural, background development for the
quick future development
• General form design and handling engine.
(Development of one form and backgroud logic takes an average 2 days. After this
development it will be devided into two stage 10-20 minutes to design. 30 minutes to
implementation. For raise this efficiency we put some woking days in it without
eyecaching result.
Place for application release
http://mshe-web.univ-fcomte.fr/tisc/
Place for application development
http://tisc.uhisoft.hu/index.php

23. Next tasks
For the first release
• User management with invitation principles
• Geolocation data trasformation
• Group handling
• Institutions, projects, other groups
For the next release
• Application management
• Other user cretion methodes
• Confoirmation
• Proposal Longer term future release
• Registration • Statistics for management
• Decision making on membership • Puting participants and projects on map
• E-mail notification • General purpose proposal and acceptance procedure
• Documentum (CV) management possibilities
• Translation and translationmanagement • Publication database for TI
• Firther user communication possibilties
23

24. Thanks to the team
Team members:
Peter Uherkovich (Pécs Univ)
Mattieu Latroy (MSHE),
Hélène Tisserand (MSHE),
Pierre Gerardin (UFC)
Also for suggestion:
Jean-Jacques Girardot (UFC)
Cyril Masselot (UFC)
Philippe Signoret (UFC)
24

25. Extension plan
The project call: (SROP-4.2.2.C-11/1/KONV)
Supporting the Research of the Forward-looking Information and Communication Technologies
and ensuring the a new generation of related IT professionals
UNIVERSITY OF PÉCS (RD&ICT)
Proposal has two objectives connected to TISC:
RD&ICT has other objectives in the proposal for research and organization purposes:
conferences and human resource for research .

26. It is a part of a big project at the Univerity of Pécs
Az Információs Társadalom
reakcióinak modern kihívásaihoz
jelenségeit leíró komplex
eszközökkel történő alkalmazkodó
adatbázisok létrehozása
modellezése innovációk
Előrejelzett reakciókhoz való alkalmazkodási kényszer
Elkülönült gazdasági Hosszú távú
adatbázisok összekapcsolása, adattárolás
Mintabeli információ dúsítása
adatbányászata
(mikroszimuláció, outlier-
Módszer-fejlesztési kihívások
szűrés, bayes-i modellezés) Árvíz-modellezés
Térségfejlesztési kutatói
adatbázis létrehozása, felhőbe Logikák és játékelmélet
Pénzügyi-gazdasági
regisztrálása Helyzet-alapú modellezés kockázat előrejelzés
Ontológiavezérelt intelligens Szövegbányászat és logikai
Hálózati
platform építészeti-néprajzi reprezentáció ReALIS
médiaarchívumok
adatbázis eléréshez rendszerben
újfajta szervezési
Szemantikus technológiák lehetőségei
Terminológiai virtuális
alkalmazása könyvtári
tudásközpont létrehozása Multi-homing a jövő
területen
internetében
Elkülönült adatbázisok Digitális megosztottság
összekapcsolásának komparatív analízise Virtuális laboratórium
adatvédelmi aspektusai a hatékony IKT
oktatásért

27. What does it mean Edu-Id integration?
Two aspects of integration (We are interested in both)
There are several federations in the world …

29. What does it mean Edu-Id integration?
Currently the french version is:
The federation Éducation-Recherche
Where CNRS is also identity provider like many other organization
sibboleth
https://federation.renater.fr/en/index
The hungarian version is:
Hungarian Research & Education Federation
simplesaml
PTE is also indenty provider in the Hungarian federation
http://www.eduid.hu/

30. What we should do for join the integration?
The technology is known
• We need agreement on to accept federational authentication
information
• We need to have an angreement on to serv authentication for
usres not registered in the federation.
We have to plan and implement the coding
(That is what we aimed in our project proposal)

31. The other objectives is statistics
We are going to develop statsitics based methodologies for recognition
cooperation patterns in the network, and via this becomes possible to
suggest possible collaborators. The benefit of this work is best if we
have a lot of participants form all over the word. This research and
development is about a future perspectives.

32. Partnership
We need partners expressing their interest in this development project.
....

33. Thank you the attention!