Last modified by marissadiazpier on 2022/05/13 14:15
From version 11.1
edited by marissadiazpier
on 2021/11/17 11:58
Change comment: Uploaded new attachment "1637146688078-285.png", version {1}
To version 12.2
edited by marissadiazpier
on 2021/11/17 12:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,7 +2,7 @@
2 2  (((
3 3  (% class="col-xs-12 col-sm-8" %)
4 4  (((
5 -= SLU IN EBRAINS =
5 += SLU In EBRAINS =
6 6  
7 7  (% style="text-align:center" %)
8 8  [[image:1637145734843-998.png]]
... ... @@ -15,23 +15,37 @@
15 15  = What can I find here? =
16 16  
17 17  * (((
18 -Tools and contacts for Expanding the EBRAINS Community.
18 +SLU description.
19 19  )))
20 20  * (((
21 -SLU rol description.
22 -)))
23 -* (((
24 24  SLU objectives, reach, goals, and activities.
25 25  )))
26 -* Tools for the identification of the community’s needs
23 +* Tools for the identification of the community’s needs.
24 +* Tools and contacts for Expanding the EBRAINS Community.
27 27  
28 28  SLU GOALS
29 29  
30 30  * Help EBRAINS development teams into transforming scientific needs into technical requirements.
29 +*
31 31  
32 32  (SLU) Activity:
33 33  
33 +(% style="text-align:center" %)
34 +[[image:1637146688078-285.png]]
35 +
34 34  * The SLU act at the interfaces between different WPs’ work plans, and those between Science and Infrastructure activities.
37 +* (((
38 +Find the best way Helping showcases with process definitions and diagramatic tools.
39 +)))
40 +* (((
41 +Making possible the interaction between technical teams and scientific teams.
42 +)))
43 +* (((
44 +Profiling needs and guidance for integrated workflows
45 +)))
46 +* (((
47 +Using knowhow and past experience of user cases to improve service integration.
48 +)))
35 35  * Structure and trigger cross-Service Category (SC) developments foreseen around self-contained projects, to enforce comprehensive solutions that respect the principle of service composability, i.e., to systematically bring the EBRAINS services together in a range of typical and specific contexts.
36 36  * Asist selected projects to prioritize functional connections of key services.
37 37  * Support the development of workflows spanning the breadth of neural data, models, and functions, highlighting the holistic perspective.