Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Item

Desired Outcome

Time

Who

Notes

Decisions

Actions

1

Assemble

  • Start recording

  • Assign Note taker

Note taker - Susan Boone

5



2

Special Collections data

How is each campus counting special collections data

10

All

by title? by item? linear feet?

campus-owned stat: reporting determined locally

UCB and UCLA: title count by collection

3

Timeline for Stats

 Discuss/confirm timeline for new eR NZ data

  •  timeline for building

  • AASA-PT initial review

  • AASA-PT socialization and campus review

Non eR NZ data (campuses affirming those data); submitting non-ILS data

  • Some campuses have requested an extension until Sept. 27; do others need an extension?

Overall timeline:

  • Proposed timeline
    week of 09/23: DN begins building out the new report (pending AASA-PT endorsement to pursue this)

  • week of 10/07: DN aim to distribute to the team

  • Due week of 10/14: Team has one week to review and provide feedback

  • Week of 10/14: Finalize build for this new comparison report

  • Week of 10/21: Share with campus colleagues, ~2 weeks to review (by end of Oct)

  • AASA-PT finalize detailed statistics and UC Libraries annual stats summary by late November or early December

15

Daisy/Danielle/All

eResources numbers drop difficult to analyze/verify because the numbers were run differently YOY.

UCSD: narrative very helpful; approved stats

UCI: future consideration NZ activators/managers of eResources (CDL) have a. role in reviewing data and title duplication

UCB: re-running data by Collection Name will help identify drops due to cancellations, for example. Re-run with more filters very helpful

UCSC: can verify physical data; rerun for eRes is helpful.

UCD: data acceptable, ready to move forward as is

UCM: rerun re-run will give more details to understand drop.

UCLA: data rerun re-run helpful; question about the logic of current exclusions (OA)

UCSF: rerun re-run for eRes is helpful.

4

Mockup of new eResources data file

Is this helpful for campuses?

Is it unnecessary?

Any edits to the design?

What would campuses like to see/remove?

20

Daisy/Danielle

revised output tracks exclusions, includes export by Collection Name for data verification.

Timing of running Alma Analytics appears to impact results.

Daisy will re-run data mid month and beginning of month for collection-level eRes numbers review;

5

Wrap up

Review actions and decisions

5

6

Parking Lot

Capture important topics for future discussion

7

Total

55

...