| | | | | | | |
---|
1 | Checkin/quick updates/anything from parking lot, slack or email | | 10 | All | | Put on agenda for 5/11 SC (can be removed if resolved before then) | |
2 | “This month in SILS” PILOT Start of the month talking points about SILS; release as a SILS News. Workflow: Last week of the month: Ask via SILS Chairs slack channel - what’s your “need to know” (for library staff) for this month to share in SILS News? If you were speaking at a TH, what’s the one thing your group would want to share.(OK if you don’t have anything). Share answer in SILS Chairs slack (meet people where they are.) Com Leads refine it. Ready to go out on the first of the month as a SILS News. Reminder at the SILS chairs meeting.
| | 10 | All | Announce at SILS Chairs on 5/5 (Adrian has already made a request on the #sils-chairs slack channel) Sarah H. gave a brief update to the provost-charged Systemwide Library and Scholarly Information Advisory Committee (SLASIAC), re: UC Library Search. The presentation was very well received - the committee was happy to celebrate the success of the project (under-budget! on-time!), noting the accomplishment given that it's a systemwide technology project. There was also a point of reflection, led by GW, around the fact that we're implementing during the tail end of a pandemic and when campus libraries are suddenly having to re-open (diverting staff time). The response from SLASIAC members was that our communications/outreach might reflect that this is a starting point - that it will enable further campus-based and systemwide integrations and initiatives (in part, reflecting that its an MVP and that more is to come). Cutover dates for the period starting in June until go-live on July 27 were announced on May 6. See the detailed implementation deadline. As part of the SILS Project, Ex Libris will be providing a week-long Primo VE Configuration workshop for all the UC campuses. The training will take place May 17-21, 2021, with workshop sessions spread out across the week. Registration is currently limited to staff responsible for configuration decisions at each campus.
| | |
3 | Editorial calendar (recurring) | | 5 | Ben, Adrian | | | |
4 | SILS Town Hall meeting (recurring) Chairs talking points Copy slide deck for reuse Finalize slide deck Check questions in the queue Confirm several weeks in advance with guest speakers (calendar of speakers) Decisions slide (Review decisions in Com Leads one week before the TH. Ask chairs for a sentence on what is the decision and why it matters and tell them to prepare for Qs.)
| 3rd Tuesdays: 5/18 | 0 | Com Leads | Anything we need to think ahead about? | | |
5 | Town Hall for All Communication channels slide (at each meeting) Q3: 8/2 10:30-noon Roundtable - highlights and kudos, MVP and how decisions were made and a couple of examples of decisions (Com Leads draft questions; Op Leads review questions; Com Leads send final questions by DATE) Post-go-live shared governance?
| Roles: PM update: Slides: MC: Tech role: Ben (mutes/unmutes), advances slides, gives remote control access, and starts recording Moderator Chat: - use Com Leads channel Public chat: sharing links, etc.- PMs Q&A (manage questions): MC will announce questions and push live. PMs will monitor and ping chairs via zoom chat for questions as needed.
| 0 | Com Leads | | | |
6 | Com Leads ongoing checkin | 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 | | | |
7 | Parking Lot | | | | [Talk about in June] Who will manage go-live announcements? What have other consortia done to share go-live announcements? (is this EUOS work or project work?) We will need to set expectations around the time of go-live (morning, noon, later?) Consider: Celebrations/Melvyl retirement: At Aug 8 TH, put a “Melvyl retirement party” section with Q&A with Melvyl creators or quotes on slides. Recognize everyone who was part of Melvyl over the years. Fun interactive poll? Virtual online card you can contribute to. In progress: Patron complaint escalation process message (Adrian). Next steps: draft the email to CoUL to share with their library staff.
| | |
8 | Wrap up | | 0 | All | Any actions or decisions missed? | | |
9 | | Total | 50/50 | | | | |