Helpdesk Integration Requirements Group Minutes: 2014 May 22

• Time: 3pm - 4pm
• Rooms: CV-331/AOC-317/GB-137
• Video hub: 192.33.117.12##6519
• Audio: 434-817-6286

Agenda / Minutes

• Review of Action Items from previous meeting: HDIntegrationRequirements2014May08
  • Tim has requested that the requirements be completed in Q3 (by the end of June). Implementation in POP15 is under discussion.
  • New ticket department mockup: PPT PDF
  • Maurizio's account linking demo video: http://www.eso.org/~amchavan/demos/2012-04-20-account-linking/
  • Initiating account linking from NRAO SP. (Kelly)
• Forcing NRAO users to register with ALMA
  • If all ALMA questions must be answered by the appropriate ARC and ALMA questions require an ALMA account, then we either need to force NRAO-only users to register with ALMA (thereby eliminating the NRAO-only category) or we need to restrict ALMA department access for NRAO-only users.
    • I think we are leaning toward forcing NRAO users to register with ALMA. The desired procedure now needs to be defined.
    • ACTION: Gustaaf has agreed to take this on.
• Define procedure for manual account linking
  • Using the demo video from Maurizio as a starting point (SP linking from ALMA has almost been implemented) we need to define the linking procedure.
  • ACTION: Gustaaf has taken this, in connection with the action item above.
• Add to draft use case for user with different email addresses in different SPs.
• Update draft department structure? Use department "groups"?
  • ACTION: Anand will put the group structure in the requirements.
• Next meeting: Friday, 5/30, 11am EDT / 9am MDT ?

Done	Assignee	Description
	Gustaaf	Clearly describe where account linking is required and where it is optional
	Anand	Create use case for user with different email addresses
	Gustaaf	Define account linking procedure w/ mockup
	Anand	Define department structure for all user groups
	-	Define functionality for all classes of users. (Current Venn diagram shows users organized by facility usage; create similar diagram or list showing users organized by differing HD functionality)
	-	Is KB category reorganization required? If so, define structure, create mockup. (Think thru UI: search functionality and categories)