2024-08-06 ACCESS EC Meeting Agenda & Summary

Decisions made during the meeting:

Agenda/Notes

1. Approval of summaries from prior EC meeting @John Towns (5 mins)

   1. 2024-07-30 ACCESS EC Meeting Agenda & Summary

2. Program Milestone Check @John Towns (5 mins)

   1. team will review and provide input

3. Informational Items (10 mins)

   1. RP Forum @Jeremy Fischer

      1. Did not meet this past week

   2. Allocations Stephen Deems/Dave Hart

      1. Talk about Resource Selector and other two tools

      2. Research Advisory Committee - Oct 10 - Laura Herriott working on it

   3. MATCH Shelley Knuth/Alana

      1. finishing up final 1-on-1s - have 2 more left

      2. survey after workkshop in Boston - have @Dina Meek add in newsletter

      3. CCEP - CCEP Workforce Development Funded Workshops | ACCESS Support

      4. 2nd round in Spring

   4. CONECT Tim Boerner/Leslie

   5. MMS Tom Furlani

   6. OpenCI John Towns

      1. Lisa will be reaching out regarding evaluation for the in-person meeting

      2. Continuing to work with Amit Majumdar for his transition into the ACO

      3. Will be having ACCESS at Tapia

      4. Agenda planning group - collecting topics for Sept meeting

         1. Email hold the date and info is out

         2. Sharon - is there a Govt rate? - Lavanya will coordinate food and hotel with them

      5. Who can MC the meeting next week? (no Shawn or John) - Stephen

Misc Topics:

Resource Selector Tool - (Alana)

• Building off Program Milestone Check from last meeting - Getting ready to make some polishing changes as well as updating the AI tool

• Get together to team build on effort - last time Tom G asked find a day and time of when this would be completed

• Jim - ARA has been deployed - SDS is deployed and have moved it to a single service - now have a complete list of info - API calls for people to get to it (and a hidden button to download all the info)

  • Enhancing AI tool - demo at quarterly meeting - demo working on support site that support teams are using now for typical questions- working reasonably well

  • Worked with metrics team that they are collecting info for

  • Getting near point where it is ready for release to ACCESS users

• Products

  • Resource Catalog - one researcher facing catalog - in progress

  • ARA - Resource advisor - released

  • SDS - Software Discovery service - released

• https://docs.google.com/presentation/d/1mulXkrosPYO39Z_VwOH5F8pCkzv_suZxPrb_u3laBoI/edit#slide=id.g21ba5f672e7_0_1

• Will need to de-conflict all this at some point in the future - and these should eventually be all joined together into one tool - how can all this be a “one-stop-shop” tool

  • we are not at a date yet

  • does Stephen D have the right people in the WG meeting to make the decisions on how things will be merged and when?

    • they have uniform agreement on the team for catalog

    • ARA and SDS will be removed from main page and live as part of catalog or can link off to it - we don’t need to necessary move everything to 1 page - linking off would be fine

  • Do we feel like we need a PI meeting to make these decisions? People in the WG are not sure they have the authority to make the final decision

    • This EC meeting should probably be the group making the decision - (Tom G)

  • Should teams be agreeing on data management and what lives behind the tool - is everyone consuming from 1 set of data?

    • yes there is a need to agree on how to procure data and what data to be used

• Meeting on Thursday could probably be the first step toward this - move toward coalesced single solution

  • Need to have representation from RPs on team - Jeremy would be happy to participate but might be able to suggest a couple others - will forward if he can’t

• Backend data sources providing data - and front end tools utilizing that data: the intent is we want one interface - but there can be multiple interfaces for viewing, entering, sorting, etc. - but we want it easy

  • users don’t want to know it is multiple interfaces - they just want 1 bit of software and they should not even know if different pieces of software are doing things - but it should be seamless and look like one piece of software

• RPs have discussed with operation - automated tools that do things and dump out data, but it does not work the way we all thought it should - there are instances of incorrect data - but we may need to invest more time in it - like a quarterly list, so things can be fixed

  • need RPs involved in testing

• Is there a project plan for this with milestones and dates? Discussions are good but a project plan is better - Stephen: will start on that this Thursday

Next EC Meeting: 13th August 2024

EC Meeting To Do Items

Format:

Open

Reference:

Risk Register: https://access-ci.atlassian.net/jira/core/projects/RR/board

Project Change Request: https://access-ci.atlassian.net/jira/core/projects/PCR/board