| Item | Desired Outcome | Time | Who | Notes | Decisions | Actions |
|---|
| 1 | Announcements/Updates | | | | | |
|
| 2 | Review Release Notes | | 10 | Team | | | |
| 3 | Broader Security Updates | | 5 | Team | | | |
| 4 | Team Charter | | 10 | | | | Will discuss charter when more members are present. Gem will start with a first draft of filling in the charter and get comments in the next meeting. |
| 5 | Review Acknowledgment of Data Privacy and Security Responsibilities for Authorized Users of UC Alma Environments | Determine Next Steps | 30 | Group | How do we want to approach this? Anything we need to work on before this? Can we answer OT’s question, “Does the current data privacy form cover the use of patron data from all UC institutions and not just the home institution for appropriate business use?”
| | |
| 6 | Next Meeting | | 10 | | No December Meeting Next Meeting January 28 | Add standing agenda item for any security updates/news that we might need to be made aware of? Add standing agenda item for 10 minute (+/-) reporting of review of release notes shared in a Google Doc. Gem and Adrian volunteered to report back to the group next month.
| | |
| 7 | Wrap up | Review actions and decisions | 5 | Group | | | |
| 8 | Parking Lot | Capture important topics for future discussion | | | How quickly must Ex Libris disclose a security incident to us? According to p.31 of our contract, Ex Libris should inform us no later than 2 business days after they “reasonably believe” a breach has or may have occurred of non-public information. How should this group work with Siren?
| | |
| 9 | | Total | x/x | | | | |