| Item | Desired Outcome | Time | Who | Notes | Decisions | Actions |
---|
1 | Start recording! | Welcome! | 0 | All | | | |
2 | Quick announcements | Awareness of SILS dev slack channel. Need identified by DFG to connect UC Primo developers. Opportunity to bring together other SILS devs including CDL. Let PMs know if you have a developer who will be working on SILS to add to the slack channel.
Related: Jeremy shared a code repository for APIs that CSU is using to share: https://github.com/CSU-ULMS This is an excellent model of sharing APIs and custom coding across a consortium.
| 5 | Lena | | | |
3 | SILS co-chairs update | | 5 | Chris, Günter | |
|
|
4 | Timeline review (recurring) Reminder: Implementation Timeline on Confluence for staff without access to Basecamp. | Awareness of what’s happening / coming soon in the project | 5 | Christine | | | |
5 | MVP | Discuss the following questions: Does the document contain sufficient information which can be easily understood? Who (non-cohort members) would benefit from accessing the document? What’s the best ways to share it? What background information do you think would be useful for the viewers? Are there any items that may be controversial? Are there any items that you think we should draw speciqal attention to? Anything to add? Any systemwide integrations to add?
| 30 | Xiaoli | | | |
6 | Communication Operation Leads update (recurring) | Awareness of communications activities. | 5 | Ben, Adrian | | | |
7 | Flagging any significant issues (recurring) | | 0 | | | | |
8 | Parking Lot Feel free to add a topic to the Proposed agenda topics page on Confluence | Capture important topics for future discussion | | | | | |
9 | | Total | 50/50 | | | | |