Table 1.5 c-1
|
Work package no.
|
2.1
|
Starting date or event:
|
11
|
|
Work package title
|
domusBITae Gate deployment & management
|
|
Activity type
|
MGT
|
|
Partic. No.
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
|
Partic. Short
name
|
ULE
|
UAE
|
UC3
|
CBS
|
HM
|
FUN
|
AAU
|
TUW
|
UB
|
UTI
|
AES
|
CCO
|
SIS
|
SII
|
|
Person-months
|
5
|
8
|
1
|
0
|
2
|
2
|
0
|
0
|
0
|
2
|
0
|
2
|
2
|
5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Objectives
|
|
―
Deployment and upgrading of trial versions of e-Communities using the
domusBITae-CMS for the institutional sites of some representative research centers
in Europe, China and America.
―
Deployment, management and upgrading of the user interface.
―
Providing user-friendly interfaces to the domusBITae modules for the
target community as a major pillar to ensure impacts.
|
|
Description of work (possibly broken down into tasks)
and role of partners
|
|
Unique
participant: ULE
Task 2.1.a: Trial CMS deployment & upgrade
Partners involved:
ULE: 1.5, UAE: 1.5, SII: 1
Task 2.1.b: Trial user interface management & support
Partners involved:
ULE: 3, UAE: 2, UC3: 1, HM: 2, FUN: 2, UTI: 2, CCO: 2, SIS: 2, SII: 4
Task 2.2.c: User interface deployment & upgrade
Partners involved: ULE:
0.5, UAE: 4.5
|
|
Deliverables (brief description)
|
delivery
month
|
|
D2.1.a
|
Trial e-Communities (dB-CMS) launch
|
12
|
|
D2.1.b
|
Initial version launch of the user
interface
|
14
|
|
D2.1.c
|
dB-CMS upgrade
|
25
|
|
D2.1.d
|
User interface upgrade
|
24
|
|
|
|
|
Table 1.5 c-2
|
Work package no.
|
2.2
|
Starting date or event:
|
13
|
|
Work package title
|
Directory
deployment and management
|
|
Activity type
|
SVC
|
|
Partic. No.
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
|
Partic. Short
name
|
ULE
|
UAE
|
UC3
|
CBS
|
HM
|
FUN
|
AAU
|
TUW
|
UB
|
UTI
|
AES
|
CCO
|
SIS
|
SII
|
|
Person-months
|
1
|
0,5
|
0,5
|
0
|
0
|
0,5
|
0
|
3,5
|
0
|
7
|
0
|
1
|
0,5
|
0,5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Objectives
|
|
Deployment,
management and upgrading of the directory module. The direct engagement of
the consortium partners should provide contents into the directory as a means
for gathering community and ensuring early usability of the directory.
Community-driven information (calls, gatherings, publications, events,
academic curricula, research activities) should be gathered and managed.
|
|
Description of work (possibly broken down into tasks)
and role of partners
|
|
ULE:
lead participant
Task 2.2.a: Trial directory deployment
Partners involved: TUW:
0.5, UTI: 1.5
Task 2.2.b: Trial directory management and support
Partners involved:
ULE: 1, UAE: 0.5, UC3: 0.5, FUN: 2, TUW: 0.5, UTI: 5, CCO: 1, SIS: 0.5, SII:
0.5
Task 2.2.c: Trial directory upgrade
Partners
involved: TUW: 1.5, UTI: 0.5
|
|
Deliverables (brief description)
|
delivery
month
|
|
D2.2.a
|
Directory launch
|
14
|
|
D2.2.b
|
Directory upgrade
|
25
|
|
D2.2.c
|
Summary
report of community contributions
|
32
|
|
|
|
|
Table 1.5 c-3
|
Work package no.
|
2.3
|
Starting date or event:
|
12
|
|
Work package title
|
Repository
deployment and management
|
|
Activity type
|
SVC
|
|
Partic. No.
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
|
Partic. Short
name
|
ULE
|
UAE
|
UC3
|
CBS
|
HM
|
FUN
|
AAU
|
TUW
|
UB
|
UTI
|
AES
|
CCO
|
SIS
|
SII
|
|
Person-months
|
8
|
0,5
|
0,5
|
0,5
|
0,5
|
0,5
|
0,5
|
0,5
|
0,5
|
1
|
0
|
1
|
0,5
|
0,5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Objectives
|
|
Deployment,
management and upgrading of the repository module. The direct engagement of
the consortium partners should provide contents into the repository and
review support to its qualification schema, as a means for achieving early scientific
and educational usability and scientific value of the system.
|
|
Description of work (possibly broken down into tasks)
and role of partners
|
|
Lead
participant: ULE
Task 2.3.a: Trial repository deployment
Partners
involved: ULE: 3
Task 2.3.b: Trial repository management and support
Partners involved: ULE:
3, UAE: 0.5, UC3: 0.5, CBS: 0.5, HM: 0.5, FUN: 0.5, AAU: 0.5, TUW: 0.5, UB:
0.5, UTI: 1, CCO: 1, SIS: 0.5, SII: 0.5
Task 2.3.c: Trial repository upgrade
Partners
involved: ULE: 2
|
|
Deliverables (brief description)
|
delivery
month
|
|
D2.3.a
|
Repository launch
|
14
|
|
D2.3.b
|
Repository upgrade
|
25
|
|
D2.3.c
|
Summary
report of community contributions
|
32
|
|
|
|
|
Table 1.5 c-4
|
Work package no.
|
2.4
|
Starting date or event:
|
11
|
|
Work package title
|
Collaborative
& Educational (C&E) Tools deployment and management
|
|
Activity type
|
SVC
|
|
Partic. No.
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
|
Partic. Short name
|
ULE
|
UAE
|
UC3
|
CBS
|
HM
|
FUN
|
AAU
|
TUW
|
UB
|
UTI
|
AES
|
CCO
|
SIS
|
SII
|
|
Person-months
|
0,5
|
1
|
0,5
|
2
|
10
|
11
|
9
|
0,5
|
0,5
|
0
|
0
|
0
|
1
|
0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Objectives
|
|
Deployment,
management and upgrading of the Collaborative & Educational tools. Consortium
partners commit themselves –with respects to its possibilities- to open
collaborative groups, to provide educational- contents and activities, and to convene gatherings using the
e-Venues tools. Together with the repository and glossary contents, this educational
and collaborative assets will constitute the basis for a e-Campus in
informacion studies.
|
|
Description of work (possibly broken down into tasks)
and role of partners
|
|
Lead
participant: AAU
Task 2.4.a: Trial C&E Tools deployment
Partners
involved: HM: 3, FUN: 4, AAU: 3
Task 2.4.b: Trial C&E Tools management
and support
Partners involved: ULE:
0.5, UAE: 1, UC3: 0.5, CBS: 2, HM: 5, FUN: 5, AAU: 4, TUW: 0.5, UB: 0.5, SIS:
1
Task 2.4.c: Trial C&E Tools upgrade
Partners
involved: HM: 2, FUN: 2, AAU: 2
|
|
Deliverables (brief description)
|
delivery
month
|
|
D2.4.a
|
Collaborative tools launch
|
12
|
|
D2.4.b
|
Integrated education tools (e-Campus)
launch
|
14
|
|
D2.4.c
|
e-Venue tools launch
|
14
|
|
D2.4.d
|
Collaborative tools upgrade
|
24
|
|
D2.4.e
|
Integrated education tools (e-Campus)
upgrade
|
25
|
|
D2.4.f
|
e-Venue tools upgrade
|
25
|
|
D2.4.g
|
Summary
report of community contributions
|
32
|
Table 1.5 c-5
|
Work package no.
|
2.5
|
Starting date or event:
|
3
|
|
Work package title
|
Glossary deployment and management
|
|
Activity type
|
SVC
|
|
Partic. No.
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
|
Partic. Short
name
|
ULE
|
UAE
|
UC3
|
CBS
|
HM
|
FUN
|
AAU
|
TUW
|
UB
|
UTI
|
AES
|
CCO
|
SIS
|
SII
|
|
Person-months
|
6
|
1
|
5
|
14
|
1
|
0,5
|
1
|
0
|
1
|
1
|
0,5
|
13
|
2
|
2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Objectives
|
|
The support to the
interdisciplinary glossary –first running in the Glossarium BITri platform-
will be subsequently upgraded with the interdisciplinary glossary module
–developed within domusBITae- and integrated with the domain glossaries. The
research value of the infrastructure is significantly rooted in the
clarification provided by the interdisciplinary glossary and the interoperability
enabled by the interrelated domain glossaries. For this reason especial
effort will be made to provide and manage multi-domain and multi-linguistic
contents.
|
|
Description of work (possibly broken down into tasks)
and role of partners
|
|
Lead
participant: UC3
Task 2.5.a: Interdisciplinary glossary upgrading
Partners
involved: ULE: 2, UC3: 2
Task 2.5.b: Glossary management &
support
Partners involved: ULE:
2, UAE: 1, UC3: 1, CBS: 14, HM: 1, FUN: 0.5, AAU: 1, UB: 1, UTI: 1, AES: 0.5,
CCO: 13, SIS: 2
Task 2.5.c: Domain glossary deployment / upgrading
Partners
involved: ULE: 2, UC3: 2
|
|
Deliverables (brief description)
|
delivery
month
|
|
D2.5.a
|
Interdisciplinary glossary launch
|
12
|
|
D2.5.b
|
Domain glossaries module launch
|
14
|
|
D2.5.c
|
Interdisciplinary glossary upgrade
|
24
|
|
D2.5.d
|
Domain glossaries module upgrade
|
25
|
|
D2.5.e
|
Summary
report of community contributions
|
32
|
|
|
|
| |