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:
THIS PAGE IS UNDER DEVELOPMENT!
THIS PAGE IS UNDER DEVELOPMENT!


We should consider a number of aspects when we try to answer the question of "What should be captured about the conversations that NGIs have with scientific communities?":  
== considerations ==
* What would Your NGI like to know about other NGIs' conversations?  
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:  
* What would Your NGI share about conversations? (realisticly!)
* How much does your NGI like to know about other NGIs' conversations?  
* What kind of questions would we like to answer by collecting info about conversations? (e.g. Where are potential users for workflow systems? Are there researchers working on fire simulation using e-infrastructures? Who are working on HPC and EGI integration? etc.)
* What would your NGI share about its conversations with other NGIs?
* Finding the right balance between "capture everything" vs "zero administration" is important for the uptake of the process to be defined.
* What kind of questions would we (as EGI community) like to answer by this information collection? (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.)
* The processes that will be developed by the Virtual Team should be but may not be used by all the NGIs.  
* Finding the right balance between "capture everything" vs "zero administration" is important for the successful uptake of the process within the NGIs.  
 


== proposal ==
Here is the first draft of "what should be captured about conversations that NGIs have with scientific communities":
Here is the first draft of "what should be captured about conversations that NGIs have with scientific communities":


Line 21: Line 21:
# Would the involvement of other NGIs into the discussion facilitate the collaboration?  
# Would the involvement of other NGIs into the discussion facilitate the collaboration?  
## If yes, what sort of NGIs are we looking for?  
## If yes, what sort of NGIs are we looking for?  
# Any other remark?


The
Remark:
Another Virtual Team project will capture contact information about ESFRI projects. 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.


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. 


Scratchspace:


- what degree of contact do you have with each site? none, occasional, regular.  
Additional remark:
- What is the status of collaboration between the NGI and the ESFRI project site (e.g. early discussions, mature discussions, early technical, mature technical)
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.
- What are the plans to strengthen the joint activities with the ESFRI project?
- Any other comment, remark?

Revision as of 15:54, 9 December 2011

THIS PAGE IS UNDER DEVELOPMENT!

considerations

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:

  • How much does your NGI like to know about other NGIs' conversations?
  • What would your NGI share about its conversations with other NGIs?
  • What kind of questions would we (as EGI community) like to answer by this information collection? (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.)
  • Finding the right balance between "capture everything" vs "zero administration" is important for the successful uptake of the process within the NGIs.

proposal

Here is the first draft of "what should be captured about conversations that NGIs have with scientific communities":

  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?


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.