2021-06-02

Start recording!

Welcome!

0

All

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.

  • Do we want this for UC SILS? Yes. It’s worth considering.

  • How soon do we need it? We can take our time to investigate.

  • Who would create/manage it? CDL as operational home? TBD

5

Lena

On the idea of a shared code repository for SILS developers:

• Joe Ferrie is interested in a shared repo and architecture.

• From Stacy in chat: “I think it would be a great idea to have a GitHub space related to UC Library Search for developers. Seems to be in keeping with the idea of sharing across all institutions.”

• And from Carlo: “My thumbs up is on behalf of Andy Kohler from UCLA who would be on that channel instead of me. And the GitHub as well.”

• And from Lisa: +1 for building mechanisms for collective, collaborative development

SILS co-chairs update

5

Günter

• Cohort members have reported SILS has been a great opportunity to hone skills; it's been a great development opportunity working together!

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

• Awareness of Alma/Primo known issues on Confluence - FGs and ICs should post your known issues here.

• Risk assessment for go-live

  • Out of scope: the transition to ongoing shared gov or CDL as operational center. These require a separate pre-mortem.

  • ICs and WG will each be doing one.

  • We had issues during the test load. Ensure we addressed them. (Yes, ExL documented all the issues with vanguard and test load and asked campuses to ensure these issues are resolved before cutover final load.)

  • No interest from this group.

• See Ex Libris meetings or Basecamp project meetings for other upcoming meeting topics

• June 3: New demo on Work Orders

• June 8: meeting with Ex Libris on Alma/Primo slowness - proposed fix (ICs, PPC, WG)

• Do you have a topic you want Ex Libris to present on? Request a meeting.

• Ask Marci how the meetings after go-live will be used. Can we use them to have demos for workflows like ordering electronic resources using the CZ from start to finish.

Risk assessment not needed for SILS Chairs. (ICs will have their own risk assessment with their local imp teams which will cover most staff.)

MVP

• https://docs.google.com/spreadsheets/d/1gpYQWYpt4GYMLWoVQHrKRlKwY6pMu_2eX78L1C-hPNI/edit#gid=0

• Awareness of simpler version of MVP for sharing widely (with view-only link.)

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 special attention to?

• Anything to add? Any systemwide integrations to add (i.e. should ICs add a tab for systemwide integrations for day 1 and beyond)?

30

Xiaoli

Does the document contain sufficient information which can be easily understood?

• MVP sheet is broken down by FG - one tab per each FG.

• Would the “status” be updated as it changes? Yes, it will be revisited weekly at PPC meetings and updated.

• How can we share what the status is for my institution? Local imp teams have created their own MVPs. The intent of this MVP is systemwide PPC decisions rather than for local imp teams.

• Make it clear what “Day One” means. It means PPC has done their work by Day One, e.g., could involve making a decision. An assumption might be that “implemented by” means it’s in place and working.

  • From Lisa in chat: “I like changing the "Implemented by" header to indicate target date for issuing by PPC vs. implementing at campus level, w/ that variability.”

• Direct readers to their local IC for questions.

Who (non-cohort members) would benefit from accessing the document?

• ICs can determine who should get the document at their campus

What’s the best ways to share it?

• Local IC will share a link to the document with their campus

• Link to it from the SILS confluence home page

What background information do you think would be useful for the viewers?

• Add a read me/background page (tab) to provide context:

  • refer readers to their local IC for questions.

  • note that local imp team may have a different timeline

  • status will be updated weekly

  • represents systemwide PPC decisions and functionality that was agreed upon by all

  • Lisa: I like building in (lightweight) contact info into the doc if it gets separated from context (either on Readme or at top of each tab to go to FG page, etc.).

Anything to add?

• If training documentation is available, link to it in the training hub. RMFG has created some training docs.

  • Add the link and description to column B (Detailed Description).

Communication Operation Leads update (recurring)

Awareness of communications activities.

5

Ben, Adrian

This Month in SILS” is being distributed tomorrow… please post any notables in the Slack thread I started last week… thanks!

Flagging any significant issues (recurring)

0

Parking Lot

Feel free to add a topic to the Proposed agenda topics page on Confluence

Capture important topics for future discussion

50/50