See Best Practices for Decision Pages and Tags for groups
Legend:
| Status | ||
|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Page Properties | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Recommendation
Provide counts of RLF materials held in the Northern and Southern facilities as distinct reporting units for persistent collections.
...
[Possible alternative recommendation, pending AASA-PT discussion:] Taking a hybrid approach, provide the counts necessary to support the various reporting needs that exist in the system. (See Options grid below.)
Impact
Stakeholder group | Impact |
|---|---|
UC Libraries | Determinations around what and how we report are for the most part managed/owned by the UC Libraries (i.e., shared ownership). |
CDL | CDL analysts, who are responsible for constructing report queries at the Network Zone according to templates agreed upon by the UC Libraries, must exclude items based a variety of parameters… |
UCOP | Likely, this specifically pertains to our Risk Management Office, who reports holdings information to our insurer, for compliance purposes. |
Reasoning
We are seeking to reduce unnecessary and duplicative efforts, and better ensure “apples to apples” reporting by shifting Collections reporting to the Network Zone, wherever possible. Identifying means to save our collective time and effort to produce UCOP data will allow us to focus on new reports, and collections data analysis.
...
Additionally, the RLFs are well positioned to manage the item counts to account for Shared Print Collections without inadvertently double counting those items. Our current practice for counting shared print in system-wide statistics essentially double counts those materials.
Background
Current practice is for the UC Libraries RLF holdings have been reported by each campus as part of a Schedule D, which is campus physical holdings by resource type and sub-location.
If RLF holdings are reported by original depositor and Shared Print is included in campus reporting and not treated separately, some holdings will not be reflected in our (individual campus?) reports, such as shared print for licensed content and those WEST holdings submitted by non-UC contributors. (Although Non-UC contributions to SP collections represent a small portion of our holdings, we strive to be comprehensive.) Historically, there has always been overlap between the Shared Print Annual Statistics managed by the Shared Print program and the UC Libraries / UCOP Annual Statistics in that those holdings are reported in both. Campuses (onsite and at the RLFs) report shared print holdings as part of the Annual Statistics and for the Shared Print Statistics. Alma Analytics functionality affords us the opportunity to report our data in several different ways.
Options Considered
These are functionally possible within Alma Analytics.
Options | Pros | Cons |
|---|---|---|
Option 1 - NRLF + SRLF are reported as part of the UC Berkeley & UCLA data exports | The RLFs share an IZ with these 2 campuses. Completion of a Schedule D with the rest of the campus buildings might be easier. | Does not address interest in reporting the totality of all items ever acquired & never withdrawn, regardless of where stored. Does not reflect original depositors' “liability” for lost or damaged materials. Represents a drastic change in data reporting. |
Option 2a - RLFs as distinct reporting units | RLF staff are physically closer to the holdings and greater familiarly with the bibliographic data, so might have more accurate view of what is held. | RLFs are sharing and IZ with a nearby campus, and each party must tease out the appropriate data. If If RLFs aspire to be “One collection, two locations,” this falls short of that. For For ARL reporting the RLFs are not members, despite having collections large enough to qualify as such. |
Option 2b - RLFs as distinct reporting units for persistent items; non-persistent items (Special Collections and non-circulating/restricted materials), reported as part of the campuses’ holdings | For non-persistent items, a distinction needs to be made between processed non-circ items (countable) and unprocessed backlog overflow storage items (not countable). Special collections staff probably are better positioned to distinguish their materials held at the RLFs by using location codes. | Schedule Schedule D would need to reflect all of what is physically located in a building, whether persistent or not. Schedule A reporting would have to distinguish between non-circ RLF holding holdings and everything else. |
Option 3 - Holdings attributed to depositing campus. (Status quo) | On some campuses, there is a political need to report the totality of all items ever acquired & never withdrawn, regardless of where stored. | Not Not all RLF deposits originate with a campus, e.g. items going into a Shared Print collection from the outset, not previously held on a campus. |
Option 4 – Hybrid approach (which combines Options 1, 2a, 3) | There are multiple audiences for the collected data and differing reporting needs. | In the case of constructing a overview of the UC collective collection, some care must be taken to avoid double counting. |
Dependencies
Questions to consider
The committee would like to note that there remains a philosophical question around ownership and how UC might represent our collective collection (shared print, and the persistent, circulating RLF collections). The items that are not shared print don't have a formal agreement around them, but through the persistence policy and the way deposits are set up in the system, they are for practical purposes, also shared print.
Action Log
Action/Point Person | Expected Completion Date | Notes | Status |
|---|---|---|---|
Gather feedback from experts |
| See meeting notes: 2023-04-17 10 am AASA-PT Meeting Notes | |
x | <date> |