Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 8
Next »
Attendees
Discussion items
| Item | Desired Outcome | Time | Who | Notes | Decisions | Actions |
|---|
| 1 | Checkin/quick updates/anything from slack or email | | 10 | All | Weekly Ex Libris meetings, pros and cons of inviting the whole cohort using the SILS-Cohort listserv? Currently we are inviting the ICs, SILS Chairs (one member from each group), IT. Are we OK with keeping link sharing on? Benefits? Risks? (Peter is investigating if we can limit link sharing to “viewer” and “commenter” only and disable “editor”. When will fall Alma training be posted to IT Confluence space?
| | |
| 2 | Internal Training - new co-chairs and PM work | Review PM role for IT/EUOS in the post-TOC world. What onboarding is needed for new co-chairs to ensure they are fully empowered to lead and have everything they need? | 20 | All | | | |
| 3 | Training, IC, PPC, SSM | Is anything blocked or behind schedule? What deliverables are coming in the next week? Any decisions, consultations or approvals needed in the next week? Do you need anything?
| 0 | All | | | |
| 4 | SILS All Chairs meeting (recurring) Note-taking: Facilitating: Monitoring chat: All Track attendance:
Post to SILS Chairs slack channel on Monday before meeting: If no agenda items or pressing issues by EOD Monday, we’ll cancel the Wednesday meeting. | Topics for next meeting: Oct 21 | 10 | All | One idea is to ask the the RCTF to come and present about their group (purpose, charge, current work, membership, etc). | | |
| 5 | Parking Lot | | | | Share ExL recording links on Confluence? (would need to get permission from ExL and others) Consider a buddy system for local campus staff (particularly for post-go-live training and other work), pairing a new campus with an existing Alma campus for the local implementation teams. Match by size (student count): Davis, Irvine, Riverside, Santa Barbara, Santa Cruz. Identify risks of not having a buddy system. Post this idea on the Coordinator. Identify times when a buddy is needed, benefits/risks. Premortem checkins - Hold for a future meeting Timeline planning (extend beyond go-live), identify critical path & intense work periods Adrian & Todd are working on integrations communication work Coordinators group: Start with a one-time introduction meeting for Coordinators with IC and PPC; IT co-chairs are in flux right now. Intent is not to have a recurring meeting. Ask ICs and PPC co-chairs: What do you see coming up that will need to be coordinated? decisions?
| | |
| 6 | | | 5 | All | Any actions or decisions missed? | | |
| 7 | | Total | 50/50 | | | | |