...
We do not recommend that the entire UC Library System store all their licenses in the same drive
Some pitfalls discussed included the fact that campuses may not be able to accurately locate the license of another campus that would meet their needs or find the part of said license without the guidance of the owning campuses staff. Licenses are living document, may be retired or amended and have complex succession tied to multiple products.
A central repository would also require significant bandwidth from campuses to move and rename licenses according to new naming conventions.
If redaction was desired, that would create additional work for campuses.
The team understands that the CDL Redacted License Agreements website (https://cdlib.org/services/collections/licensed/resources/redacted-license-agreements/ ) serves as the central repository for Tier 1 and 2 agreements.
...
Review UC documentation/website in support of new librarians understanding the cross-campus community/eco-system of licensing as a whole. Make listserv information centrally available.
Current listserv is under publicized and hosted at UC Davis rather than CDL: uclr@ucdavis.edu
We recommend centralizing communication about licensing through Slack Community channel (or similar)
We recommend adding interested non-Technical Services staff (including liaison librarians and administrators)
Questions to consider
Who should be included in a Slack channel or listserv
Who should be included in a CKG?
Should listserv be hosted by CDL Shared Collections?
...