2019-10-11 Meeting Agenda & Notes
Date & Time
Oct 11, 2019 – 1-2:30 pm.
Zoom
https://csueb.zoom.us/j/531982611
Participants
@John Wenzler
@brandon dudley (Unlicensed) @David Walker @Kevin Phillips (Unlicensed) @Israel Yanez (Unlicensed) @Christina Mune (Unlicensed) @Andrew Carlos (Unlicensed) @Linda Franklin (Unlicensed) @Brian Moore (Unlicensed) @Mike DeMars (Unlicensed) @Joseph Adkins (Unlicensed) @Dolly Lopez (Unlicensed)
September Notes
Discussion topics
Time | Item | Presenter | Notes |
---|---|---|---|
1:00-1:10 | Welcome Agenda Setting | @John Wenzler |
|
1:10-1:30 | Committee Updates | All | Fulfillment:
Resource Management:
The Resource Management Functional Committee’s next meeting is this coming Monday, 10/14/19. Analytics & Assessment
Resource Sharing1. Developed and publicized (via I-SPIE TV) a workflow for dealing with Long Overdue CSU+ loans. We did a study and found that after 90 days overdue a CSU+ loan is extremely unlikely to be returned. We want to be able to inform Collections Development people at the owning library that the book is unlikely to come back and that they can repurchase the book if so desired. The next phase in this project is to connect with the Resource Management Functional Committee to discuss the best workflow for replacing these books while still holding the borrowing patron responsible. Israel should expect to hear from me soon about his initiative. 2. Currently exploring an Alma job that would clean up Resource Sharing request queues of old transactions. However, running the job may have negative consequences for Network Zone analytics. We are still currently exploring whether we should recommend campuses turn on the job or not. 3. We did a release testing session on a recently released Resource Sharing functionality called “Reactivate Request.” During the testing session we noticed that parts of the Alma manual resource sharing request functionality is not working properly, which halted testing. We opened a Salesforce support case about the issue. Testing will resume when case is resolved (or maybe earlier if we find a workaround). 4. Developed a new analytics report that should find items that were Completed but never Received (these are items that “Reactivate Request” functionality would be good for). There was an issue with the report generating some false positives so we are working on weeding those out if possible. 5. One RSFC member has just left the employment of the CSU, but a replacement member was found post-haste. (Thanks Brandon!) 6. Revived the discussion about CalState Walkin users (via I-SPIE TV). Explained why Fulfilment Network (Alma’s pickup and return anywhere system) will not work for CSU+ and why we need an alternative solution for CalState Walkins to use CSU+ at a visited library. This picks up on a discussion we had at the last ULMS Steering Committee Meeting: developing some kind of webform solution to CalState Walkins using CSU+. There is a document that went through the last Steering Committee about CalState Walkins, but it never officially made it out. I will be sending that to ULMS Steering Committee for review and comment.
Discovery
Acquisitions· We are fine tuning the Open Forum “Alma to PeopleSoft Financial Integration” · We are also independently reviewing the “ACQ ULMS Policies”. We will be discussing this during our November meeting to see if there are any adjustments to be made. We understand this due by end of the year. Working on a getting started document sort of like an onboarding document. Current document is ER heavy, so they are bulking up the acq part. This should be complete by the end of the year. The steering committee liked the document and said this could be done for other areas as well. ERMDoing an inventory of all the information that is out there on all our various channels. VPAT (Voluntary Product Accessibility Template) for electronic collections -they are looking at this. |
1:30-1:40 | Survey Results – Steering Committee Priorities | @John Wenzler | See Results
|
1:40-2:00 | Ex Libris Contract Negotiations Surveys | @brandon dudley (Unlicensed) | Surveys to review:
Notes:
|
2:00-2:10 | Confluence Permissions | @David Walker | · We pay for confluence. Usually it is by user count (we currently have a license for up to 100 users). These are editors. Anyone can view the content, but only these users can update or create content. Most of these users are from the ULMS functional groups. Each member has historically been given access. · Other people want to start using confluence. COLD wants each Dean to have an account. · The ScholarWorks and Archives people are also now using confluence. · How do we pay for this? Buy more seats? Too expensive because the education discount has changed. · Ideas: maybe not every ULMS functional committee member should get an account. Move to a just-in-time model where we dole out accounts to those who actually need them. Many committee members liked this idea. · Dave will send out an email to each functional committee head asking them how many seat they need for their committee. |
2:10-2:30 | Clarifying Process of implementing ULMS Policies and Procedures | @John Wenzler @brandon dudley (Unlicensed) | · How and when to get feedback from the communities of practice · What makes the difference between best practices and policies? Some of our documents seem to straddle both. · Couple of issues: how do you enforce policy across the system? (ULMS Police!) and how to you have a unifying policy when all of our campuses are so different? · Once you have a policy, how do you communicate it? · Brian, Brandon, Dolly, and Joe will work on guidelines for functional committee chairs regarding policies and procedures. Communications strategies as well. |
2:30+ | OneSearch Logo | @David Walker | · Community Colleges want to use our logo for OneSearch · Who owns this? Is this a COLD issue? Yes. Dave will take it there. |