| Item | Desired Outcome | Time | Who | Notes | Decisions | Actions |
---|
1 | Checkin/quick updates/anything from slack or email | | 1 | All | 2 | (Ops 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?
| 15 | All | Is communication flows diagram completed and published? Done! Awareness of upcoming communications and anything needed? No. Waiting on feedback on the report on Takeaways from meetings with chairs to see if there are actions. Reminder to check off your “done” tasks from the task report. | | |
2 | SILS value props | Awareness of next steps; assign deadlines | 5 | All | Next steps: Ben or Adrian will post a copy of the value props and stakeholders in DOC gdrive in the SILS value propositions subfolder and share the links with Donald along with Adrian’s email. Ben will draft an email to DOC briefly explaining the objective of the value props with links to docs. Share with Donald. Donald will take the value props to DOC for review/edit. Provide a deadline for feedback: one week by 9/18. Co-chairs will share value props with CoUL for approval.(at CoUL meeting in Sep) After value props are approved by DOC and CoUL, Ben will share the value props in a SILS News. And, place the value props document on the SILS Website.
| | |
3 | Basecamp | Revisit our policy on limiting Basecamp as we enter the full implementation phase; document our reasons. Who has access now? IT members Chairs ICs Op Leads
Avoids duplication of many people posting questions on the same issue. Fewer people with accounts means it’s easier to prioritize questions that are time-critical. If we open it, we need best practices for use don’t post questions without checking with co-chairs of your group or your IC you are coming late, your question may have been answered. here’s where to look for the answer first (list of where to check for answers - your group first) Here’s how to set up your notification - daily digest don’t check off something as “done” Ask Ex Libris when it’s time for questions looking ahead; poster should qualify urgency. Use categories to tag by topic.
Limit to only cohort? Do not include local implementation team members who are not in the cohort? Allow ICs to determine who on the local teams should be included. Grant access upon request; we will not add everyone on the project. Go through your chair or IC for requesting an account.
| 3From SILS Chair 9/9 meeting: Task the Ops Leads with creating a “Best Practices” document for BC See 9/8 Ops Leads notes | 20 | All | Immediate next steps this week: Create a decision page (Done! Needs Op Leads review) If we do agree to open up BC a little more, ensure that the limitation that BC access will only be given upon request as needed.
First draft of best practices by Op Leads (In progress in decision page) Share with ICs, PPC, IT, SILS chairs to edit Consult with Marci Confirm where on BC to post the request for accounts
| | |
4 | SILS project blog (recurring) | Is the blog necessary? | 10 | All | Blog has been challenging - finding the time! Is anyone reading it? And is it providing value? If not, delete it? Agreement we are communicating this same information to the cohort effectively and we don’t need it. Interview different groups to create blog posts such as the ICs on how they are organized locally and how it’s going. Ask 3 questions. Do a seasonal series.
| Keep blog space open for groups to blog. | |
5 | Alma Training (recurring) | Update on progress | 5 | Neil | October workshops update - approved schedule? Still waiting to hear from ExL. | | |
6 | (Ops 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?
| 10 | All | | | |
7 | Op Leads feedback on shared gov | Continue work on https://docs.google.com/document/d/1EmIgNjK79ig4wXFEwpbxoblik2dMmmqH8701xhBi5jA/edit# What’s the best way to add to this document? On our own or together? | 20 | | Time-permitting | | |
8 | Communicating about integrations work | Determine approach and who’s involved https://docs.google.com/document/d/1ZU4-h19rqUCBNX-4NS0DI25Is-6ZBI4_hDKB_Kpu_CM/edit# | 15 | | Time-permitting, not urgent | | |
9 | SILS All Chairs meeting (recurring) Note-taking: Lena Facilitating: Christine Monitoring chat: All Track attendance: Lena
Topics for next meeting: Sep 9 Role assignment | 20 | All | 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: Sep 23 | 4 | SILS Service Manager (recurring) | 0 | Caitlin | 5 | | Alma Training 0 | All | Discuss week of 9/14 | | |
10 | SILS Town Hall meeting (recurring) | Update on progress3rd Tuesdays | 0 | Neil | 6 | SILS project blog | Com Leads | Checkin 9/15 | | |
11 | SILS Service Manager (recurring)Items for the blog? | | 0 | All | | 7Caitlin | | | |
12 | Parking Lot | | | | | | |
813 | Wrap up | | 5 | All | Any actions or decisions missed? | | |
914 | | Total | 50/50 | | | | |