| 2 | Check in: Campus form to determine what/how to exclude Special Collections & Archives from Alma Analytics reporting for UCL/UCOP annual stats | 10m - Danielle | Confirmed: We are excluding special collections and archives from Alma Analytics reporting, so that each campus can report these holding data locally (to then be submitted centrally, to created updated totals). Deadline: Tuesday, May 09 eod to submit the form.
| | |
| 3 | Revised UCL/UCOP annual statistics: Prototypes for Review → Specifically, let’s prioritize outstanding questions/details that need to be confirmed before we submit our recommendations to SILS-LG (so long as we know it’s possible, the specifics of implementing reports can continue to be built out as we submit our deliverable). | 30m - Michele, Chan, Danielle, Daisy | (Michele, Chan, Ellen and Danielle met to chat about prioritizing outstanding questions/details – here’s our proposed list) Goal: Prioritize outstanding questions/details that need to be confirmed before we submit our recommendations to the SILS Leadership Group. Outstanding questions/details for AASA-PT (in scope to the PT, for Network Zone reporting) Special Collections (what to exclude and how) Work underway (Being handled/explored through the SC&A form).
DDA (if/how to remove DDA from NZ and IZ); currently DDA is included in the AA holdings report (Schedule A - Electronic Portfolio); ACRL asks institutions to exclude DDA for their submissions, though numerous UC campuses opt to include. Withdrawn by modification date for FY Course reserves circulation (print) - ARL excludes Course Reserves in circ counts Data anonymization processes are based on campus-set schedules. Does data anonymization interfere with associating annual circulation data (circs, course reserves) with specific user groups? Still need to determine - are course reserve circs isolated by location name or by item policy? Potentially differs by campus.
Groupings of libraries or locations (to represent reporting units) Being handled offline, between Daisy and AASAPT representatives where their campus reports their data by defined groupings
Title-level reporting (new, not part of standard UCL/UCOP reporting): Should deduplication happen within format but not across? I.e., Dedup within print materials; dedup within electronic. Documentation of alignment and re-use of stats for ACRL & ARL Renaming sheets/schedules
Still TBD, but does not need to be “done-done” by submission date to SILS-LG Final formatting of NZ reports to campus (for the time being) Updates and new approaches entirely (e.g., not having multiple sheets in a workbook; not using Excel at all and instead using an API-driven website or Visualization) would be a longer-term project - needs assessment should happen first, to understand what folks need/want.
Establishing process/workflows as part of annual stats to: affirm variables/parameters don’t need to change for reporting (spring); and give campuses an opportunity to review/affirm NZ outputs; etc.
Outstanding questions/details for SILS-LG (and higher up) How to report the RLFs? Schedule A-print; Schedule D Status quo approach (by original depositor)? Could do Schedule A-print by original depositor Could do Schedule D by RLF institution (though each ‘original depositor’ campus is still responsible for replacing the material in question)
Or by RLF (as distinct institutions)?
How do we want to reflect shared print holdings (campus and RLF based)? Status quo for UCL/UCOP stats has SP included as part of campus reporting (not reported distinctly, save for “total SP” - which represents a portion of the total already reported by campuses). Recommendation to begin developing policy and guidance around data-sharing that leans towards sharing as a default; can have exclusion categories that require campus permissions (e.g., all user data is anonymized (already status quo); financial data requires permission before accessing from NZ, etc.)
| Decision: For DDA holdings, we will report them as a distinct count (e.g., electronic holdings less DDA; and DDA only) Decision: For DDA, AASAPT will have a recommendation for each campus to consider using Alma Analytics auto features for DDA (which will simplify reporting and should make DDA management easier, though some human monitoring/intervention is still required locally on the management end when the auto features are enabled). For creation of a new dedup/title-level report, we should conform with ARL and dedup within formats (print, electronic, microform) but now across.
| |