Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "NGI community interactions"

From EGIWiki
Jump to navigation Jump to search
Line 1: Line 1:
== Preparation ==
== Stage 1: Preparation ==
When we try to answer the question of "What should be captured about the conversations that NGIs have with scientific communities?", we should consider a number of aspects:  
Before we could answer the question of "What should be captured about the conversations that NGIs have with scientific communities?", the members of the VT should answer:  
# How much would your group, your NGI like to know about the conversations that other NGIs have with user communities?  
# How much would Your group, your NGI like to know about the conversations that other NGIs have with user communities?  
# What kind of questions would your NGI like to answer using this information? (e.g. Who are the potential users for workflow systems? Are there teams working on using e-infrastructures for fire simulation? Who are working on some type of integration of HPC and EGI cluster resources? etc.)
# What kind of questions would you like to answer using this information? (e.g. Who are the potential users for workflow systems? Are there teams working on using e-infrastructures for fire simulation? Who are working on some type of integration of HPC and EGI cluster resources? etc.)
# What would your NGI be able and be willing to share with other NGIs about conversations with user communities?
# What would your NGI be able and be willing to share with other NGIs about conversations with user communities?


Finding the right balance between "tell us everything" vs "zero administration" is important for the successful uptake of the process within the NGIs.
Please add your answers here:
Italy:
#
#
#
Portugal:
#
#
#


== Info to capture ==
== Info to capture ==

Revision as of 16:31, 9 December 2011

Stage 1: Preparation

Before we could answer the question of "What should be captured about the conversations that NGIs have with scientific communities?", the members of the VT should answer:

  1. How much would Your group, your NGI like to know about the conversations that other NGIs have with user communities?
  2. What kind of questions would you like to answer using this information? (e.g. Who are the potential users for workflow systems? Are there teams working on using e-infrastructures for fire simulation? Who are working on some type of integration of HPC and EGI cluster resources? etc.)
  3. What would your NGI be able and be willing to share with other NGIs about conversations with user communities?

Please add your answers here: Italy:

Portugal:

Info to capture

Here is the 0th draft of "what should be captured about conversations that NGIs have with scientific communities". This will evolve as members of the VT gather answers to the above three questions:

  1. Who talked to who, where and when?
    1. Names and affiliations from both sides (NGI and scientific community)
    2. Event where the discussion/interview took place
  2. What is the scientific discipline, project, group that the interviewed person represents?
  3. How much and what sort of potential do you see for a fruitful collaboration with the person and the group he/she represents?
    1. For your institute
    2. For your NGI
    3. For EGI as a whole
  4. Would the involvement of other NGIs into the discussion facilitate the collaboration?
    1. If yes, what sort of NGIs are we looking for?
  5. Any other remark


Storage, sharing, processing

Ibergrid works on the setup and configuration of a CRM system (Customer Relationship Management). This system should support the information collection process defined by this VT. The development of the process runs in parallel with the setup of the CRM and Ibergrid has a representative in the VT to ensure that the requirements and possibilities about the CRM are communicated.

Additional remark: Another, already active Virtual Team project collects contact information about ESFRI projects: VT_ESFRI_Contact_List. Contact information about ESFRI projects can be represented by a tree graph where the nodes at the first level of a graph represent the ESFRI projects; nodes at the second level represent the institutes that participate in the ESFRI projects; nodes at the third level represent the personal contacts who were contacted by the local NGIs. Information about converations among NGIs and ESFRI members can be attached to the third-level nodes.