Stakeholders

• Jenny Watson and the ILLiad team - primary customers of the data import

• Cari Roberts / DAD - need to be kept informed of changes

• CID - current primary owner of the data import

• Fred Reiss - historical owner of the data import workflow

Data From Merick

We get a pair of user data files shipped over via ftp from merick to our primobb VM on prem. These files are:

• lib_emp.txt - A XML document containing employee (Faculty/Staff) metadata.

• lib_stu.txt - A XML document containing student metadata.

and land in /home/merickftp each day.

ILLiad-user-management scripts

Our ILLiad user import is run by cron each Monday at 6am on syslog.prod.nor.internal

The production import runs from /srv/illiad-user-management-prod/, based on code located at https://github.com/OULibraries/illiad-user-management

A test version of the same scripts, pointed at our test ILLiad server, is located at /srv/illiad-user-management-staging/ . This version isn’t configured to run automatically.

The user management script depends on the following files data files:

• lib_emp.txt - See above. Copied from the primobb vm when user management runs.

• lib_stu.txt - See above. Copied from the prombb vm the primobb vm when user management runs.

• cat2s - A text file containing departmental pipe-delimeted metadata. Manually updated as needed.

• cat3s - A text file containing degree/major pipe-delimeted metadata. Manually updated as needed.

The script works by reading current user data from ILLiad into a local SQLite database, importing the updates from the XML files, and then calculating what updates to perform.

NOTE User deletes are currently disabled.

After completion, an email noting SUCCESS or FAILURE will go out to stakeholders.