Illiad NCIP Plug-in : Set Up Procedure
- Common issues - be sure to set the NCIP responder URL with na03 as the Alma instance portion for the URL
- Testing: Use a live patron's request - as long as they have an ID in ILLiad - if one of their items comes in you can check it in in Alma -
- Make fake ILLiad requests - didn't send them all the way through to OCLC (change the status in ILLiad) - so it doesn't actually go out as a request
- With lending requests, use expired lending requests - the borrowing library won't receive updates from OCLC. Make ILLiad process it as if it was a request - once received, Alma will display the request to logged-in users in Primo under 'requests' in their library account
- When is everyone putting this into production? Each campus will roll out on their owncan decide if and when to roll out. Some campuses may decide not to use the plugin.
- Kirstie @ CSULB - known issues identified:
- when you set up your ILLiad partner to automatically receive, supposed to stop at physically received, but it moves to another weird status, you can manually receive like other ILL requests, or you can have it auto-receive.
- Lender due date is ignored, the CSU+ setting overrides, so desk workers have to manually override the date.
- If you have multiple volumes, no way to account for that, it will only accept the first barcode - can override by going into the request to update the barcodes.
- Once NCIP is installed, at what point does it show up in the user's record?
- should be instantaneous to show up in the user's Primo account under requests once the item is received - when you make the request in ILLiad it doesn't show up right away, it only appears once we receive the item and change the status to receiving it and at awaiting customer contact. It doesn't wait until the user notification is sent. Alma notification is sent prior to ILLiad notification.
Testing resources - see https://docs.google.com/document/d/1yYVWnHAIzGHdBzJjgmdgbhxGJJ4p5tXq-Dg4OkQia_w/edit (Thanks Renaldo Gjoshe (Unlicensed))
Distributing add-ons to multiple clients: https://prometheus.atlas-sys.com/display/ILLiadAddons/Distributing+Addons
- File-share-supplied add-ons install in addition to any locally installed add-ons on the user workstation.
- Versioning is supported through the version parameter in config.xml (of every add-on)
- Enable logging in the ILLiad client when testing - have to run the client as administrator for that to work - under options - turn on debugging
- Challenge to be setting on user ID - that's a setting in your resource sharing partner setup in Alma > Parameters - make sure your user identifier type is selected to match the matching point in ILLiad
- SLO stored user share on ILLiad server that all ILLiad users are part of a windows group that have access to the ILLiad server share storing the add-ons
- Once the client is run as administrator - it brings down the file from the server share and automatically activates it as well
- There's an additional add-on for the new UI to search within the client
Question about a server addon that enables NCIP borrowing and renewals: https://prometheus.atlas-sys.com/display/ILLiadAddons/ILLiad+Alma+NCIP+Borrowing+Renewal, SFSU is exploring but can't seem to get it to work - may query Alma and/or ILLiad listserv
See also: ILLiad Primo New UI Add on: https://prometheus.atlas-sys.com/display/ILLiadAddons/ILLiad+Primo+New+UI+Addon