Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

9-9:50

Zoom: please see Outlook meeting invite.

📢​ Recording of the meeting: forthcoming, see meeting recordings (please note: Zoom-hosted recordings will be available for 120 days after the meeting 🗓​ , after which they are automatically deleted by Zoom).

Discussion items

Item

Desired Outcome

Time

Who

Notes

Decisions

Actions

1

Start recording!

Welcome!

0

All

2

Quick announcements

0

3

SILS co-chairs update

Awareness of project status in key areas:

  1. Alma/Primo VE response times

  2. Transition Task Force update

Folder: https://drive.google.com/drive/u/1/folders/1lq5pEjMkKWTazRZV7q_wg7Hl38ErhpLc

Team:

  • Donald Barclay, UCM, DOC Liaison

  • Christine Barone, SILS PM

  • Sarah Houghton, CDL

  • Michelle Polchow, UCD

  • Hermine Vermeij, UCLA

  • Lena Zentall, SILS PM

5

GĂĽnter, Chris

Alma/Primo VE response times:

  • Response times appear to be improving

  • Next report is coming 8/30. That report may tell us more because it will come after Merced and Berkeley have begun their semesters.

Transition Task Force:

  • Kickoff was 8/23. First deliverable will be the nomination form.

  • Aiming for nominations to be done in November.

  • Timeline with deliverables is in progress

  • Co-chairs will be Lena and Christine



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

0

PMs

  • December 23 is the last day of phase 4.

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

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

  • Do you have something to share with the cohort and beyond at an Ex Libris Monday Project Status meeting? Let the PMs know.

5

Communication Operation Leads update (recurring)

Awareness of communications activities.

5

Ben, Adrian

6

Offboarding activities

Reminder: final versions are now available of the handoff docs below.

Deadline: December 3.

New: If your group has high priority work that needs to be done in January, flag it: list it as high in Priority, indicate January as the Timing, and provide details as needed in the Notes column.

Schedule your post-mortem when it makes sense to your group but before Dec 3.

5

PMs

  • Let PMs know if you have any questions.

  • (Caitlin) I think we've been focusing on "Cohort" handoffs a lot, but maybe we need to talk about how to support local campus groups and inclusion.

7

Report a problem process

Talk about "what would you like to see improved from our "reporting a problem" procedure (SILS general / Ex Libris)?

30

Claudia & Caitlin

Report an Alma / Primo VE Problem current page.

MVP 2:

  • (Caitlin) New infrastructure for sharing problems among ourselves is forthcoming.

  • (Joe) Reporting to SILS Ops and legacy Resource Sharing team is an artificial split and it would be more efficient for CDL to consolidate these queues.

  • Call out existing mechanisms specifically?

    • slack channels (open only to cohort); not archived

    • UC Alma google group - open to all campuses and is archived.

      • RMFG has that group as a possible reporting mechanism and ask people to use "Resource management" in the subject.

      • I like the idea of having subject line categorization!

      • It's helpful to also allow people to ignore/focus on their area as emails come in

      • subject line categorization helpful to also allow people to ignore/focus on their area as emails come in

      • Alison seconds Liz about bringing some of the subject organizing from slack into the listserv. + 2

      • Liz is right. As discussions move on, we lose access to answers if they are on Slack.

      • The UC Alma google group is a first stop for UC people to discuss issues.

      • Some issues are campus specific.

      • Make subject line understandable and descriptive enough to be recognized. We won’t jump into ontology, controlled vocabulary quite yet.

      • Yes on indicating the module field, etc... (I like distinction btn consultative - email/g-group vs. requesting action=>starting a ticket)

I want to request a new feature or enhancement, or, I want to talk about feature harmonization

  • (Caitlin) Maybe some kind of "new idea proposal" queue for the FGs or their successors? The reason we moved to a SILS is to collaborate.

    • (Lisa) Thinking also on one of Josephine's earlier points re: campuses coming up with an idea that may need more harmonization/consideration - we can re-emphasize areas that are up to local discretion vs. areas SILS groups were looking at harmonization opportunities. (Like not all campus ideas need to come up to SILS/SGTF structure/groups...)

      • possible TH topic??

      • (Caitlin) So I'm hearing two potential action items: (1) brainstorm how to capture new ideas, (2) how to make and reinforce boundaries around local / harmonization tasks. Maybe (3) some polite language around "even if this is a local decisions it's still not time yet"

        • (Rikke) On #3: "Thank you for your suggestion. We're reviewing your input and prioritizing requests. " “

        • (Rikke) “While we review, we ask that you don't make the change for now. We'll get back to you by XYZ date” or 'While we review for impact on harmonization ...”

        • (Lisa) And link or wording that here are things free for local discretion.

        • Caitlin, Josephine, Tom will join the group to brainstorm ideas.

      • Should we have Principles? SILS Harmonization Principles from phase 3: https://libraries.universityofcalifornia.edu/groups/files/sils/docs/SILS_HarmonizationPrinciples.pdf

  • Resources for asking what others have done and what the gotchas are:

    • Include links to email listservs outside UC such as ELUNA CA group, Alma lists, etc.

      • I love the alma listserv but it's a lot to try to keep up-to-date because of how much traffic there is.

Use UC Alma google group for communication among UCs. It’s archived and searchable.

Make subject line understandable and descriptive enough to be recognized. We won’t jump into ontology, controlled vocabulary quite yet.

  • Caitlin, Josephine, Tom will form a group to (1) brainstorm how to capture new ideas, (2) how to make and reinforce boundaries around local / harmonization tasks.
8

Flagging any significant issues (recurring)

0

9

Parking Lot

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

Capture important topics for future discussion

10

Total

50/50

  • No labels