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 "CRM Use Case Record ESFRI Data"

From EGIWiki
Jump to navigation Jump to search
Line 1: Line 1:
First use case deals with the recording of information from ESFRI projects. This use case involves mainly two steps, the creation of an account that relates to an ESFRI project and the creation of the individual contacts that constitute the persons that have been already indentified and contacted. This process should be coordinated to avoid creating multiple entries for each entity.
First use case deals with the recording of information from ESFRI projects. This use case involves mainly two steps, the creation of an account that relates to an ESFRI project and the creation of the individual contacts that constitute the persons that have been already indentified and contacted. This process should be coordinated to avoid creating multiple entries for each entity.



Revision as of 09:40, 21 March 2012

First use case deals with the recording of information from ESFRI projects. This use case involves mainly two steps, the creation of an account that relates to an ESFRI project and the creation of the individual contacts that constitute the persons that have been already indentified and contacted. This process should be coordinated to avoid creating multiple entries for each entity.

XXX SOME EXPLANATION ABOUT THE PROTOCOL: WHO CREATES WHAT, WHAT SHOULD BE DONE BEFORE CREATION XXX

Three data structures are used to implement this use case: Accounts, Contacts and Groups. Accounts are used to track ESFRI projects and endpoint information, Contacts are used to associate individual persons to institutions and groups enable setting permissions. Next figure shows an interaction schema among these entities.

XXX FIGURE NEEDS TO BE INSERTED XXX

Account Information

Accounts should have a structure that can deal with all the information relevant for identifying topics, endpoints and contact status. along with the basic CRM account information, other fields are added. The list of fields is the following one:

  • Account Name, XXX
  • Account Number, an automatically generated number.
  • Institution, of each ESFRI contact point.
  • Website, for the institution or specific group represented.
  • Email; Other Email, e-mails from contact points.
  • Created Time, Modified Time, automatic fields with the date of the creation / modification for the account.
  • Type, choosing among entity types, such as Company, International Project, National Project, Non-profit Organization, Other, Research Institute, University.
  • Scientific Discipline, choosing from Biological and Medical Sciences, Education, Energy, Environment and Earth Sciences, Environmental Sciences, Materials and Analytical Facilities, Other, Physical Sciences and Engineering, Research Industries, Social Sciences and Humanities.
  • Project Membership, choosing between ESFRI and Others.
  • Project List, choosing the acronym from an already pre-filled list.
  • Assigned to, which can be either an individual user or a group (e.g. specific NGI).
  • Status, which can be either Active or non-Active.

Along with the information from the account, a description should be included covering three items:

  • Description, with a brief statement on the objectives and scope of the ESFRI project.
  • Potential for EGI use, with a subjective appraisal of the potential impact of its integration in EGI.
  • Interest in e-Infrastructure, describing the interest shown on using e-Infrastructures for their research activities.

EGI CRM UCI Account.jpg

Values of the list categories will be updated in the tool.

Contact Information

Contact define individual persons that are associated to the institution accounts created. As in the case of the accounts, part of the information is general and part is related to the specific case of EGI-CRM. The fields required are the following:

  • First Name, Last Name, with the name and surname of the contact.
  • Mobile, cellular phone for the contact.
  • Title, title or position of the contact in the organization.
  • Email, Other email, main and alternate e-mail contacts.
  • Personal Web Page, URL of personal page, if any.
  • Contact ID, XXXX
  • Account, account of the institution to which this contact is associated to.
  • Created Time, Modified Time, automatic fields with the first and last changes done in the contact.
  • Lead Source, indicating how this contact was obtained (e.g. An Event, EGI.eu, from colleague, Directly contacted contact creator, Internet, Project, Other).
  • Degree of Contact, indicating the frequency of contact (e.g. No contact, Once, Occasional, Regular).
  • Project Membership, choosing between ESFRI and Others.
  • Project List, choosing the acronym from an already pre-filled list.
  • Assigned to, which can be either an individual user or a group (e.g. specific NGI).
  • Status, which can be either Active or non-Active.

Additionally, a field with a textual description should be completed.

Groups Information

XXX MISSING XXX