2017-04-13 Meeting notes

CO Systems Projects update

• • Alma Shibboleth
    • Waiting on CO identity management config instructions, still in progress
    • Contingency plan to start with one campus and set up instructions based on that campus configuration
  • Alma Financials Integration
    • Still in progress, much is set up and being tested at San Jose
    • Documentation / Getting Started Guide will be sent out for testing for a few other campuses to test
  • Course Reserves search hosting (San Marcos app/LMS TF)
    • Re-prioritized deliverable for LMS TF
      • Down the line, will be working toward a possible LTI/LMS integration
    • Will be set up for each campus
    • Later, branding/customizations options will be available
    • San Marcos app

• Test examples:

  http://pxfulpaq01.calstate.edu/sanjose/

  http://pxfulpaq01.calstate.edu/dominguez/

  http://pxfulpaq01.calstate.edu/longbeach/

  
  

  • URL redirect for link resolution

    • • https://developers.exlibrisgroup.com/blog/Alma-link-resolver-set-it-and-forget-it

      • Will be a redirect in place for SFX

      • Could be additional capability to set a generic base URL that would persist with base URL resolver changes (for migration and for future)
      • Dave will be providing info to listserv w/plans for redirect for Xerxes
      • SDSU hosting 'permalink bootcamp'
      • Sacramento set up redirect to search bib ID in Primo
  • Renorms break Primo permalinks - important to remember that Primo permalinks may not be 'permanent'

  
  

Patron Load Troubleshooting and Testing Best Practices

• • Patron Load: Known Issues & Enhacements

• CSU HR split upcoming - the CMS script for the extract was designed to be adaptable to run two queries - one for students, one for HR
• Handling auxiliaries
  • In CMS program setup, mapping table to POI types
  • if you don't map POI, they are put into retiree
  • Can put in enhancement request
• Who are visiting scholars?
  • • Professors on campus to visit, do research, or help teach - not having expiration dates for short-term visitors like visiting scholars may be problematic
    • Should put in enhancement request
• Do general community users need to be part of a standardized user group?
  • No, user groups for community borrowers can be determined locally

ISAPI intercepts traffic to ILLiad server and redirects to login script

Must be able to install ISAPI filter on ILLiad server to use script

• Example shared login script authenticates against LDAP, could be configured for other auth protocols
• Sends the username to the Alma user API script then pulls back data from Alma (active, patron type, other values)
• Auto-creates ILLiad accounts

Will San Marcos be interested in bringing in user data from Alma via API into ILLiad, rather than on login?

• Not at this time, but is possible via API or by analytics

Log issues in the GitHub repo

All