Allow API to Add, Remove, and Update records in the UserValidation table
Stanford U is locally hosted and has a custom job that imports users directly into the Users table. This job will update users based on any change event triggered in the Registrar's database. It creates many users that never end up using ILLiad. We would like a standard method of creating a process that pushes users into the UserValidation table and can update users, regardless of their being in the Validation table or in the Users table.
Justin Kovalcik commented
California State University, Northridge has a similar issue. Currently custom coding attempts to pull data from the Ex Libris Alma User API to insert into the User table of the ILLiad database. It would be very helpful if the Customization Manager included fields (similar to Innopac or Symphony) for the Ex Libris' Alma User API for the Web Interface. This would hopefully enable user data to be pulled or updated from the Alma User API for the ILLiad system when a patron logs in. I am unsure if Stanford uses Alma or a different ILS; however, the idea of expanding Web Interfaces in Customization Manager to include other API for user data collection would be terrific. I would specifically request the Alma User API; however, the ability to point to an API and enter info to tell the system what to pull out of the API and store into the ILLiad database would be great.