2016-09-14 Meeting notes

• No significant task force updates today; everyone's been really busy!

Authentication

• 1 month ago sent out information re: Shib to Project Managers and links to instructions for ID management staff
  • 2 things Ex Libris needed to know: 1) set of test credentials (some campuses don't allow this) 2) need to decide release attribute as match point between Shib & Alma
    • By default, PeopleSoft EmplID is the main identifier for all users (fac, students, staff). Patron load is set up so that PeopleSoft ID is primary ID. By default, shib is set up so that by default EmplID is the match point. Users login with their campus / network username and password. Shib will then send the EmplID identifier to match in Primo.
    • Do you have a lot of users outside of PeopleSoft AND are in the campus directory (e.g., LDAP) you may want your match point to be different. This is likely NOT the case for many campuses.
  • Since last Primo upgrade, Shib auth has not worked; Ex Libris is fixing that now. Hopefully will be fixed as soon as tomorrow.
  • Primary IDs in Alma should become EmplID; campus username can be secondary ID. If your Alma Primary ID is not currently EmplID we'll need to rectify this.

Patron Load

• CO "CMS" group have been working on this project
• Have been working with the Vanguard campuses (Northridge, Fresno, SJSU)
• CO CMS group have developed a batch script and made available for vanguard campuses for testing; may be pushed out to all campuses and made available in a future CSU-wide release. The script includes documentation and instructions that local campus PeopleSoft administrators can set up and run.
• Currently testing when a user account changes that the changes are being picked up by the script and recognized in the exports and ensuring that FTP is functional
• Data is structured slightly differently at each campus. Most of what's needed for Alma is standard across the campuses, but there are a couple of cases of non-standard data, e.g., username and barcode. Many campuses are using the barcode that is NOT the EmplID may not be stored in PeopleSoft or may not be stored in a standard place, so may require some customization (COMR exception) by your PeopleSoft admin.
• Action Item: Reach out to your PeopleSoft administrator(s) to ask about any fields you may want to have in Alma, especially if you are concerned are not standard (e.g., barcode / username). Consult this document for list of required fields.
  • Northridge has a customized barcode number based on the EmplID and Northridge PeopleSoft admin will be adding a COMR exception for extracting / building barcode and extracting userID to place as a secondary identifier in Alma.

XSLT Notices Task Force

Import Profiles Task Force

Emailed to project managers 9/1

If you would like your Item Material Types to more closely match your III IType values, contact Sarina re: her script to Update Item Material Types (GitHub)