2021-06-30 Com Leads (A&B only) Meeting notes

Attendees

  • @Ben Alkaly (Unlicensed), Com Leads

  • @Adrian Petrisor, Com Leads

Discussion items

Item

Desired Outcome

Time

Who

Notes

Decisions

Actions

Item

Desired Outcome

Time

Who

Notes

Decisions

Actions

1

Editorial Calendar

Update calendar and Review draft

15

All

 

 

2

Aug. 2 TH Brainstorm

 

10

All

Possible roundtable topics:

  • What aspects of Alma/Primo are most transformative for our Libraries, from your perspective?

  • Highlights and kudos, MVP and how decisions were made and a couple of examples of decisions

  • Farewell to Melvyl: Bring in somebody key to that project to reflect?

  • Scale back from 60-90? - Yes

  • Reinforce Open Q&A

    • Encourage advance submissions

    • Identify Q&A panel in areas of: Alma expertise (IC?), Primo expertise (Discovery?) and training (IT)

  • UCLS Pop Quiz

    • ~5 questions that reinforce “need to knows”

 

 

3

Know Bugs/Public page

Review PM Notes

0

All

  • Caitlin taking lead

 

Done?

4

June SILS Town Hall

Finalize

5

All

  • Chairs points: align w/ notes

  • Discovery: NEEDED

  • ELs: in deck

  • Reflections: Need to build in Canva
    Roles

  • Ben: Tech

  • Adrian: MC

  • Lena: Chat

  • Christine: PM Update

 

 

5

Escalation Path

Discuss feedback from DOC

5

Adrian

First, DOC would like to thank you for writing your May 20, 2021 message, “Escalation template for patron complaints after go-live.” At our June 1, 2021 DOC meeting, some questions were raised as DOC discussed this further. I volunteered to share the gist of DOC’s response with the two of you on behalf of DOC.

 

There was some confusion caused by this message not going to the ICs or the End User Outreach Group before it went to DOC and CoUL. It was not clear if you sent it to DOC as a heads up before it went out more widely, or if the ICs and EUOG were left out of the loop. Some DOC members feel that if the intention is to share this message more broadly, it would be better for it to come to local campus cohorts via their campus IC rather than their campus DOC representative given the current implementation structure is now a well-oiled machine. Can you please share more context with us to help us better understand your intentions? For example, it is not clear if you are looking for any specific actions from DOC in regard to this message. DOC members were not exactly sure if this was an FYI sharing or if more is expected.

 

There was also a question as to whether or not the SILS communication team would be drafting any talking points that campus people might use as they respond to complaints. For a random example, could the communications team offer talking points for responding to a question such as, “Why is UC Library Search so much slower than the old catalog?”

 

 

6

New risk assessment subteam

 

 

 

 

@Adrian Petrisor to serve on sub-team!

 

7

Wrap up

 

0

All

A

 

 

8

 

Total

50/60

 

 

 

 

Work in Progress:

Com Leads

  • SILS Communications Calendar

  • Local implementation teams interviews in blog (see Local group structures from April 2020) - Ben will draft interview questions

  • Communicating from project to local groups (where to document this?)

  • Blogs

  • Virtual town hall for cohort

  • Virtual town hall for all (start early Nov; quarterly)

  • Celebration milestones and what’s involved

  • Communicating the value of SILS

  • Communicating about integrations work to ensure staff resources are available/ready (Adrian + Todd Grappone)

 

The SILS mission is to transform library services and operations through innovation and collaboration. The future is shared!

Question? Contact AskSILS-L@ucop.edu