 |
Page History
...
| Time | Item | Who | Notes |
|---|---|---|---|
| Action Items | see below | ||
| Monthly status reports | November MSR missing December MSR missing Kudos for February status report | ||
| Invoices | Oct-Dec 2017 invoice has been approved Jan 2018 invoice has been approved | ||
| Out of office | Ulli out of office from March 21, returning April 9. Meeting on March 29 will take place as scheduled. | ||
| Email report form | Requester email now included in email. Email gets send to 5 people including meeting organizaer. Samarth is the primary repsonder and will request information from other people as needed. Admin can see an Issues tab in the challenge app where they keep track of the issues. Challenge organizer has also access. GUI has been developed, backend development to follow this week. | ||
| ISBI 2018 | Team is assembling a lessons learned document about things users noted regarding case assosciation and randomization. | ||
| Website | Create a website that explains what a challenge is and who to contact for help, including phone line and email Will be tied into the TCIA application process | ||
| Incoming Help desk requests | ISBI has generated requests for help, data conversion, technical issues tracking is mostly done by email evaluating systems that could be used for tracking - ongoing
| ||
| Procedure questions | How are help desk requests received? How are help desk requests logged? How are help desk requests tracked? Who responds to the help desk requests? How is a "responder" assigned to the help desk request? How are answers tracked? Who closes an issue? Should we track user satisfaction? How to track user satisfaction? Workflow Response time
| ||
| Means to request help | phone, email, ticketing system | ||
| Means to provide help | email, answer on phone, chat, WebEx, Bomgart | ||
| Supported Challenges | see new table | ||
...
