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 11 Next »

Attendees

Not attending

Discussion items

Item

Desired Outcome

Time

Who

Notes

Decisions

Actions

1

Check-in / updates

Information sharing and problem-solving

10

All

TSELG: invited CDL folks will join our next week’s meeting to discuss ETDs.

RMFG: finalized configuration recommendations and are starting to talk about how to update policy documents.

IC/PPC subgroup: Liz, Lynne, and Carlo are meeting with Chris and Gunter to prep for a meeting with high-level Ex Libris staff. The focus is on how to improve support during test load and cutover.

DCFG: Not much to report this week. We drafted a Q/A for the FAQ.

AEFG: Group is reviewing configuration recommendations and working on MVP document. High priority item re: fiscal close planning for FAQ and subsequent discussion through SILS migration timeline lens. Identifying need for a systemwide general session to discuss [roughly scheduled for spring]. Additional action item to coordinate with Discovery on Configuration form related to IP ranges for campus/library on Fulfillment tab - on action list but not yet started as of 1/15.

Discovery: Gathering and synthesizing feedback from local discovery teams re: Search Profiles that will help Discovery FG decide what recommended scopes we want to have for test load. Also collecting facet usage analytics from non-VG Discovery FG members to help us provide a suggested list of facets for campuses to consider using.

Fulfillment: Working on filling in the Fulfillment Configuration Form. The group voted on (Test) Harmonization of Loan Periods and Blocks in the UCs Automated Fulfillment Network and will be voting next Thursday on (Test) UC Network Patron Linked Account Shared Fields

PSELG: met on Monday and decided to summarize our findings on our decision page

2

Configuration forms

Approve the configuration decisions new to test load

(Test load) Configuration Form - This will be sent to ICs when ready

  • Discovery only just got info on configuring Primo VE. By next week will be able to add the configs they’re recommending to the table. Ok to add to the table even if there is no decision page to support it yet.

  • [from chat] So for IP piece - & Josephine - if I craft some revised language I can run by you, and if we need to connect on a quick Zoom call the first part of next week we can. Still piecing together the intricacies of this part of config. UW has an application of how this looks in Primo (ex. for their Health Sciences library, Tacoma branch, etc.).

  • Remind existing Alma libraries to review the config form after the environment is delivered to align with the the configurations for test load

Use different colors when adding anything new to the config form table

3

MVP

Share the experience using the MVP document

Discuss the progress of transferring information on Systemwide work to MVP document

10

Xiaoli

MVP document

  • Local campuses MVP includes being able to check out a book; FG focus would be on system-wide issues such as whether a patron borrow from another campus.

  • The MVP is part of what will be tested. Possibly by late spring?

  • [from chat] this spreadsheet could be shareable in 2-3 weeks.

  • Original goal was to be able to communicate out what the MVP would look like, but part of being able to determine that is through testing. Would we share this document widely knowing that it is a living document? Would that generate too many questions?

  • [from chat] Would an FG focused drop-in Q&A (like a brown bag) be a useful way to handle this?

Systemwide work - running brainstorm

4

Training material

What types of training material each FG group have in mind?

20

All

  • Here’s an example of what Internal Training Subgroup members have provided - https://docs.google.com/spreadsheets/d/1xyXgybBTRCNFEieY4DYWYhNl2WV5egCVqJMaujDkqQM/edit?usp=sharing

  • What’s the training for the front line folks? That will be part of end-user outreach

  • FGs will note when workflows are campus specific vs. when there is one approach to performing a task

  • FGs could provide standardized training for consortial workflows, not daily workflows

  • Add documentation links to the Work Inventory if you have them

  • [from chat] FGs might also want to review the revamped Essentials training since some of that is supposed to be better than the old stuff and might be ok for some basic functions

FGs should look at the UCR list on the training Work Inventory for best practices

  • FGs that want to share their testing plans can share an update at the Feb TH.
5

PM Update

Awareness of procedure for requesting special meetings

https://docs.google.com/document/d/1N9mip1f5Tb_c4NqAZ_BAxgSUlhl2uFpnDMRGuX0K2FI/edit#heading=h.s9xgvrgbbzzl

List of meetings on Basecamp

5

Christine

6

Homework

7

Parking Lot

  • January 2021: Testing continuity of service: https://docs.google.com/document/d/1A5dr_sFqBLPwuBwpqLg1mplQBwcPqwoIWrG9nwvimEg/edit

  • For January: CDL shared services

    • Who from CDL should PPC liaise with?

    • Can CDL create a list of shared services that they will be providing? Would like to create a document that could be shared with cohort.

    • What services is CDL currently doing? What services will CDL be providing in production?

  • March: Revisit FAQs after test load opens

8

TOTAL

45/90

Future agenda items

  • No labels