| | | | | | | |
|---|
| 1 | SILS Privacy Forms Update | Decide if this needs more discussion or if we can make a decision now regarding the 2nd main bullet point in the notes | 10 mins | Caitlin / Team | From Caitlin’s Email to the OT on 03/29/2022: Complete the retroactive acknowledgement task: ACTION: The DPTF is requesting a confirmation email from each campus Alma admin (or equivalent) affirming the following: Everyone with an Alma account at [CAMPUS] with a role other than “patron” has acknowledged the Data Privacy & Security Responsibilities statement as of [DATE]. The email can be sent to SILS-DPTF-L@listserv.ucop.edu and should be sent as soon as possible. Caitlin will be point person for following up and available for questions as needed.
Confirm that users are acknowledging the form annually: A confirmation email will need to be sent annually. It’s unclear who will take point for data security needs once the current project team concludes, so SILS Operations Team should take point on this for future confirmations.
Caitlin is still in the process of getting emails from all of the campuses for this year As far as OT is confirmed, we need to identify the date by when campuses would need to send these emails, and what email address should they send it to?
| March 30, 2023 will be the date by when folks need to send these compliance emails, and these emails should be sent to the OT listserv | |
| 2 | Proposal for a SILS GitHub from the Discovery OST/SILS Ops Center here | Discuss proposal and determine next steps | 13 mins | Caitlin / Jackie / Team | Tom brought up this topic at the last OT meeting; folks seem to be onboard with this and think it’s a great idea Main guidance that SILS Ops Center would be looking for is account management, and the scope of who they should invite Probably not just Cohort people, probably campus people who aren’t in the Cohort who would want accounts All other tools are Cohort members only, so this would be a change from that
Restriction should be any UC Libraries Staff Member should be able to have an account This will also help campuses who don’t have a dedicated Primo person be more connected Do we have to limit accounts per campus? No, it doesn’t seem like we would have to We would make an organizational account, and people who want to join would create individual accounts, and those individual accounts can be added or linked to the organizational account You can link to companies, it doesn’t seem like there is anything blocking or preventing people from linking to companies There is the option to make things public or private, so that might help Might decide to leave it private for the first month, and once we’ve figured out what we’re doing we can update as needed A person who already has a Github account can be added to an organization
We might just have to let it play out, say it’s limited to UC Library Staff, and if we’re running into issues, we can deal with those issues as they arise
Mostly need to decide who would have access and if we start with UC Libraries Staff, that’s a good start SILS Ops Center would manage this; can verify people’s employment at a UC Library to confirm, and then allow them to join ExL is moving to the next version of AngularJS 1.8; testing to begin for this change in May, live in Production in November A risk would be if anyone makes any changes to the main repo Does OT-SC approve this now, or do we need to take it back to the team to vote on it?
| | |
| 3 | Follow-up discussion regarding Alma NZ concerns | Review and discuss SILS CDL Shared Collections in the Network Zone Project Team: Charge DRAFT and determine next steps | 30 mins | Team | Caitlin checked in with folks last week and everyone she talked to was on board with the idea of the taskforce Caitlin walks through the draft charge with OT-SC Reviewed, discussed, and updated expected weekly time commitment Reviewed, discussed, and updated expected date for completing the work Also discussed how this team would hand off work to other OSTs, based off what they identify while doing their work
Can we bring it to OT as is? Next Steps: Draft charge still needs some more massaging Caitlin will share the draft charge with the folks identified to be on the team, as well as the joint chairs and other stakeholders, and get their feedback; Caitlin will include Tom and Jackie on that email
| | |
| 4 | Build agenda for next OT meeting | Build and finalize the agenda for next week’s OT meeting | 12 mins | Team | | | |
| 5 | Parking Lot | Capture important topics for future discussion | | | | | |
| 6 | | | 65 mins | | | | |