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.

VT Intelligence Collection

From EGIWiki
Revision as of 16:52, 23 November 2011 by Sipos (talk | contribs)
Jump to navigation Jump to search

General Project Information

  • Leader: Gergely Sipos, EGI.eu
  • Mailing List: Still to be setup: vt-egi-intelligence-collection@mailman.egi.eu
  • Status: Active
  • Start Date: 10/Nov/2011
  • End Date: Expected to finish before the middle of January 2015
  • Meetings:

Motivation

The conversations that NGIs have with scientific communities should be sharable, searchable, comparable, merge-able in order to

  • know who we (as a community) talk to
  • see the big picture of collaborations between NGIs and scientific communities
  • to identify commonalities and faciliate the reuse of best practices.

Output

The expected output of this project is a process which can be communicated to EGI staff (NGI & EGI.eu) so that when they talk to user communities (informally or at meetings) they record the conversation so that a European wide picture of activity and prospects can be built up. These contacts will be analysed and intelligence obtained circulated back to the NGIs indicating potential new areas for collaborative activities. The process should use the CRM (Customer Relationship Management) system which is currently under setup by the Ibergrid teams in Spain and Portugal. The information gathered by the NGIs through this process can be used by both the NGIs and EGI.eu outside of this VT.

Tasks

  • Define what we (an an NGI, or as a community) would like to know about the conversations of NGIs and scientific communities?
  • Define a storage space to share instructions with the NGIs (Can the CRM be used for this?)
  • Define a storage space where NGIs can capture the conversations with the expected details.

The process should be flexible enough so it can be used in various interview and conversation situations; It should be simple enough so it does not cause an overhead for interveiwers;

Members

  • EGI.eu: Gergely Sipos
  • NGIs: FI, UK, CH, SE, MC, HR, ES, PT, NL, LT, DE, FR, HU, SK,

Resources

  • CRM system: <TO_COME>

Progress

  • Task 1
  • Task 2
  • ...
  • Task N