2015-11-30 Vanguard PeopleSoft Integration Notes

• Attendees: Library Staff, IT & HR from Northridge, Fresno, and San Jose

• Transforming current patron loads to meet the new system needs

Timing: Early test phase (January)

Full test phase (Summer 2016)

Cut-over to production (May, June 2017)

• Do campus IT / HR have time to devote to generate a sample file of patrons by end of January? (Yes, all campuses agree)

What's involved

• Starting now:
  • Download patron xml sample
  • Create sample patron xml with 1-2 patrons
  • Load patron xml to sandbox
  • Troubleshoot errors
  • Confirm that sample is good
• Starting in Late January:
  • Create full patron xml for full load
  • Load full xml to Alma institution
  • Once confirmed success, have user test logging into Primo
  • Confirm end-to-end Primo login success

Fresno - SQR (method for running a report) that runs out of PeopleSoft; generates a CSV file

Northridge - SQR that generates a CSV file

We need automated extract that is FTP'd to a secure location on a daily basis (overnight)

What can be centralized? - right now each campus has its own PeopleSoft instance

For initial test, each library will generate an XML formatted sample file that contains the fields that are currently exported.

For most campuses, some portion of auxiliary users in PeopleSoft

CHRS - Common Human Resources System - in the future, everyone will have a common HR System

• First Name and Last Name
• Email Address
• PrimaryID / UserID (Shibboleth/Network login name)
• Barcode
• Physical Address (Required for INNReach libraries)
• Expiration Date (Ian Chan (Unlicensed) can provide information about how terminated users are removed / expired from the system)
  • Should this be rolling (e.g., 6 months from today, etc.)?