Decisions:
N/A
Action Items:
| Summary | Description | Responsible | Due Date |
|---|---|---|---|
| ECSS: Submit PCR for Proposed additional metric QMA-141 - Getting issue details... STATUS | Question to ECSS: How many months would it have taken PI's team to complete work without ECSS support? MB follow up with NWD and RR regarding proper language for the Metric | Marques Bland | 31 May 2017 |
| ECSS: Gateways needs to track demographic information of users. QMA-142 - Getting issue details... STATUS | Gateways does not capture demographic information. Gateways has had a large increase in users, but we're not capturing that information. | Marlon Pierce | 31 May 2017 |
Notes:
- Additional metric:
- Adding the metric for how much time saved by the PI is a good metric to keep track of, but we have to continue massaging out the correct language.
- Risk
- ECSS Affiliates- we're not sure the impact this will have on ECSS with the number of projects coming in. It's not a PY7 risk because we're adding it prior to PY7
- KPIs
- Number of project completed
- Is there a way to quantify the requests? How many do we not support?
- We should report out the number of projects that ECSS takes on but never went anywhere.
- Number of project completed
- Discuss number of projects initiated metric during ECSS-MGMT meeting.
- Publications
- JT: some discomfort that we generated our own metric that isn't a standard metric for impact of various publications.
- Gateways does not capture demographic information. Gateways has had a large increase in users, but we're not capturing that information. Perhaps talk to Cipres to pilot something to capture the information.
- It would be hard for CEE to advertise gateways if there's no data coming from it.
- if Gateway users move to using XSEDE In-common logons, then Gateways would have access to more demographic data.