2020-05-01 IC-SC Meeting notes

eDate

May 1, 2020 11-12pm

Attendees

  • @Carlo Medina (Unlicensed) , co-chair

  • @Bill Hackenberg (UCLA) (Unlicensed)

  • @Caitlin Nelson

  • @Tom Bustos , co-chair

Not attending

Future agenda items

Discussion items

Item

Desired Outcome

Time

Who

Notes

Decisions

Actions

Item

Desired Outcome

Time

Who

Notes

Decisions

Actions

1

Check-in / Update

Report any major changes in availability / circumstances

5

SC

 

 

 

2

IC / ILSDC / Patron Data assessment

Understand how we think it’s going / risk assessment

10

 

ILSDC - (Tom) - good communication, on top of questions and gaps.

Patron Data - (Carlo) search for co-chair continues, but otherwise looking good!

  • GF: depends on patron database decision (below), can share best practices for patron data cleanup.

  • CN: throw co-chair decision to the group itself

ICs overall: doing well!

COVID-19 risk mitigation: ICs have been asked to strategize around what the MVP really is, and estimate timeline, in case of loss of workforce.

 

 

3

Scheduling

understand next steps

15

SC

Do we cancel Monday’s meeting for the IC group? It was supposed to be an ExL day. Do we tell people they have time back? Do we talk about other stuff?

Tent Decision: let’s use Monday for going over the Decision Questions.

What does next week’s agenda look like? 2020-05-07 Meeting notes

 

 

4

Handling questions and issues

Create a plan for how the IC will review and start answering questions

30

SC

SO that ILSDC question form spawned a LOT of interesting info!

Patron data: big question is if we do a big patron database or not → Decision page

Triage:

  1. Someone has to read and understand the question

    1. All ICs?

  2. ICs delegate.

    1. ICs → FG

      1. IC sends the problem / decision over to the PPC

    2. ICs keep

      1. ICs create a small subgroup (where appropriate)

  3. Delegated groups fleshes out problem with supplemental questions, tease out the pros/cons = analysis.

    1. Delegated group takes ownership of the Decision page.

    2. Deadline - can you make a recommendation? OR how much more analysis. → dependencies section!

    3. Reaching out to stakeholders.

  4. Recommendation stage:

    1. someone recommends

    2. someone decides.

 

 

  • How do we organize ourselves so it’s not a free-for-all?

    • Get things on Decision pages with background - perhaps add Dependencies as a template section?

    • Break into subgroups who report back?

  • Deadlines? Timeline

    • ICs need to be aware of when do you need this answer?

    • Balace internal timelines against ExL milestones.

      • If someone needs an answer just before the deadline that’s one thing; but if they need more time to do some work that’s another.

      • Effort factor need to be clearly called.

  • How can we handle the number of questions that might hit us?

    • DELEGATE! This is what the FGs are for.

  • When do we start asking our own questions?

    • Do we need the migration checklist before we can start posing questions?

Other…

PPC agreed with this triage process. Works for them! Send issues over to the SILS-PPC-L listserv. (5/1)

@Greg Ferguson create a Decision page for “Patron Database” issue and get started documenting that. (Fulfillment/ILL decision?)

 

5

Other / Homework

 

 

 

 

 

 

6

 

TOTAL

60 / 60

 

 

 

 

 

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

Question? Contact AskSILS-L@ucop.edu