Pushing Patron Data to Millennium Using Patron Update

Pushing Patron Data to Millennium : Using Patron Update Web Services Marie Martino, Moraine Valley CC Library

What is Patron Update Web Services? ➔ API that allows you to access patron data through a website or Web-enabled application ➔ Enables custom (non-Innovative) applications to assist in maintenance of patron data in Millennium's database MVCC uses it to create and maintain internal patron accounts

Maintaining Patron Accounts: ➔ Patron data comes from Colleague (college business system), a. k. a. the “master database” ➔ Anyone employed at the college or registered for a class “automagically” has an account created and maintained for them in Millennium ➔ No manual loads necessary ➔ Fully automatic process ➔ “Real-time” sync / full sync for backup

Main PUWS Set-Up Considerations: Need to select a viable match point for patron records between databases

Create data mapping between the fields from the college database and the fields in Millennium (and programmer will need to map these to the various elements of the Patron Object in their coding).

When creating the patron, PUWS uses the _p or default patron record template, so set accordingly.

Establish your business rules beforehand. Consider what data gets pushed/inserted/overlayed/deleted and what are the criteria (triggers) for each action in each data field? Examples: ● Set student patron expiration date to 3 weeks after the last term of enrollment. ● Don't over-write library staff PTYPE (25). Otherwise manage role changes. ● Manual deleting of data only. Partially set criteria based on fines/fees. This data is not synced between library & ERP.

Be prepared to test and tweak til you get it it right! Helps to anticipate the ‘weird’ scenarios beforehand.

Our Set-Up ➔ Consists of Colleague, Millennium, PUWS & a custom-made app ➔ App = a command line. exe file written in C# ➔ Happens “behind the scenes” ➔ Fully automatic ➔ Runs on Windows servers ➔ Uses Task Scheduler for a full sync (M-F) and real time sync

● Colleague data is always the master db ● App requests Colleague data ● Colleague sends data (list) ● App goes through PUWS to compare (read) data in Millennium db ● If they do not match, App updates (writes) newer Colleague data via PUWS

Project Requirements ➔ A skilled programmer on staff ➔ PUWS product ➔ Custom application developed by your staff programmer ➔ Adequate patron record allotments ➔ Patron data clean-up beforehand ➔ Bibtemp file increase to accommodate sync

Find More Info iii Tech Docs site: http: //techdocs. iii. com/patronws_patron_data. shtml

Questions for You Sierra – Read/Write Patron APIs? Same capabilities? What cool projects are you doing with the Patron API?

Questions for Me? Thanks! Contact: martinom 43@morainevalley. edu