Page Comparison

1:00-1:10

Welcome & New Member

John Wenzler

Welcome Andrew Carlos, East Bay, as the new Discovery Committee Chair

1:10-1:2530

Updates

John Wenzler brandon dudley (Unlicensed) David Walker

• Brandon’s Status going forward

• Ex Libris Contract Renewal Date

• New Policy Page on Confluence

• Committee Membership Changes

• Other Updates …
  

1:30-1:25:40

Functional Committee Reports & Goals

All

Acquisitions (LInda)

• The Acquisitions Committee continues to ask campuses to make changes/additions and improvements to this Google Doc. as they update their contact information. It has really evolved now that it is more accessible. This was a carry-over project from the past Acq/Erm group. https://docs.google.com/spreadsheets/d/1AXiVA0DSBgeu7ESthkQf5TJslEtYVqnbOp7NcZ3KY9E/edit#gid=0

• We have made plans to do an TS Open Forum on “Alma to PeopleSoft Financial Integration “ that will involve demonstrations from three different campuses: San Marcos, Pomona and San Jose. We just finalized a date it will be November 7th.

• We have done our introductions/goals/concerns and the PS integration was the 1^st thing we wanted to work on. We also want to look further into encumbrances. However we know both of these issues are a campus decision. We just want to be a source of information.

Analytics & Assessment (Brian)

Analytics & Assessment will be focusing on usage stats this year during the transition to COUNTER5. Along with curation guidelines for existing and migrated data we will be evaluating SUSHI utilization across the system with an eye toward developing reports for evaluating usage on a broad basis. We will continue to update and develop established reports and dashboards as needed while providing targeted assistance via Slack.

Resource Management (Israel)

Report:

• Committee members who presented, or moderated, at the Summer Meeting: Lia Ryland (San Francisco), Mark Braden (Los Angeles), Julie Moore (Fresno), and Israel Yanez (Sacramento).

• Other presenters in the Resource Management track: Pam Anan (Pomona), Luiz Mendes (Northridge), Samuel Barber (Fullerton), and Patrick Flanigan (San Diego).

• With input from the NZ Management Group, the committee has decided to ask campuses to localize records that do not comply with the language of cataloging policy. Israel will present on how to identify problem NZ records, and how to run an unlinking job at the next TS Open Forum, 9/12.

• An issue arose recently that may not have been widely known. There is a collection discovery issue in Primo for shared environments (i.e. consortiums). When a campus creates a collection (not to be confused with an electronic collection) in Alma, there is currently no way to localize discovery in Primo. Consequently, all campuses who have enabled collection discovery in Primo would see every Alma collection across all campuses. If there is more expressed interest among the CSU campuses in implementing Alma collections, we may seek to encourage Ex Libris to make this feature work for consortiums. Ex Libris documentation: Managing Collections.

• The committee reviewed the Council of University of Wisconsin Libraries (CUWL) technical report on their recent cooperative technical services pilot. While the CSU does not have a central tech services staff that would mirror the CUWL, the Resource Management Functional Committee members feel that we can still think of ways where we can benefit from centralized efforts in the area of resource management. The goal is to focus on collaboration.

Goals:

The committee will continue to support resource management staff across the CSU by reviewing best practices and policies as needed, and providing direct assistance upon request. The committee will support the work of, and collaborate with, the NACO funnel project, the NZ Management Group, and the Release Notes group. We plan to start thinking strategically about how we can work more collaboratively and effectively as a consortium in the area of resource management.

ERM Committee (Dolly)

• Conduct an inventory of all ERM information (confluence, slack, listserv, etc), organize that information, and create a maintenance schedule.

• Investigate how we can address accessibility of databases as a consortia.

1:40-2:15

2019/20 Priorities

All

Before the meeting, each member will write two paragraphs on their takeaways from the Northridge Meeting: Paragraph 1) Goals and Objectives for my functional committee: Paragraph 2) Goals and objectives for the Steering committee. We’ll discuss.

Potential Steering Committee Priorities

• ULMS Policies – Clarifying approval process? Clarifying whether campuses are required to implement. (Linda)

• Harness our collective power to encourage Ex Libris to take functionality for consortiums into account when developing new features. (Israel)

• Continue to work collaboratively and effectively across functional areas. (Israel)

• Salesforce cases with developmental fix planned but not addressed within a year (Dolly)

• Identify and encourage publishers/access providers to work with Ex Libris to add or improve their collections/metadata to the knowledgebase. (Dolly)

• Clarify process for adopting policies and getting feedback on them (John)

• Identify areas of possible CSU-Wide Collaboration (John)

• Evaluate add-ons to the ULMS such as Leganto and Esploro for broader adoption (John)

2:15-2:30

Agenda Setting

John Wenzler

List of topics to cover in future meetings