ILLiad Alma NCIP Integration System Addon
Name | Version | Author | Description |
|---|---|---|---|
ALMA NCIP Integration | 2.0.2 | Atlas Systems | The Alma NCIP Integration system addon allows for integration between ILLiad and Alma using NCIP. This addon uses NCIP v2 calls to the Alma NCIP responder. |
Download
Download zip file:
Release Notes
Release notes are available for Alma NCIP Integration System Addon v1.0.5 and later.
v2.0.2:
Fixed a bug that prevented the value of RequestIdentifierPrefix from being used.
v2.0.1:
Fixed a bug that was converting the pickup locations defined in PickupLocationMappings to uppercase. The pickup locations are now stored in the same case as they are entered in PickupLocationMappings.
v2.0.0:
Fixed a bug that was preventing the value in RequestIdentifierPrefix from being used.
UseRequestIdentifierPrefix setting added to enable RequestIdentifierPrefix setting to allow the option to not use request identifier prefixes. RequestIdentifierPrefix is now prepended to the request identifier when is has a value and UseRequestIdentifierPrefix is set to true. If UseRequestIdentifierPrefix is true and RequestIdentifierPrefix is left blank, the values in DataMapping.Handlers.RequestIdentifier are used based on whether or not the request is library use only. This is a potential breaking change for users with a value in the RequestIdentifierPrefix setting in prior versions of the addon.
v1.0.7:
Fixed an issue where the pickup location pulled from the request would not properly map to the pickup locations defined in the PickupLocationMappings setting if the casing used between the two values differed. The addon will now convert both values to uppercase to perform the match comparison.
v1.0.6:
NCIP problem responses are now properly parsed by the addon, improving the specificity of logged errors for troubleshooting purposes.
v1.0.5:
Fixed an issue introduced in version 1.0.4 that prevented history entries from being added when the addon performed an action on a request.
Configuration
Addon settings are configured in the Manage Addons form.
Depending on your machine's security settings, additional permissions may need to be configured for the addon files after installation. Please see the troubleshooting section below if the addon fails to run after the installation and configuration process.
Settings Validation
As of version 1.0.4, the addon checks the NCIPResponderURL, ApplicationProfileType, FromAgencyId, ToAgencyId, BorrowingUserIdentifer (if BorrowingEnabled is set to true), and LendingUserIdentifier (if LendingEnabled is set to true) settings and displays a message to the user upon client startup if any of those settings are blank. The message is also logged.
Setting Name | Default Value | Type | Description |
|---|---|---|---|
LendingEnabled | true | Boolean | Determines whether lending requests are enabled for NCIP Integration. |
BorrowingEnabled | true | Boolean | Determines whether borrowing requests are enabled for NCIP Integration. |
BorrowingMultiBarcodeEnabled | true | Boolean | Determines whether borrowing requests Barcode fields support Multiple Barcodes. |
ErrorQueueBorrowing | NCIP Errors | String | Defines the name of the queue to which borrowing transactions will be routed if there is an error in processing. |
ErrorQueueLending | NCIP Errors | String | Defines the name of the queue to which lending transactions will be routed if there is an error in processing. |
BorrowingCheckedInFromLibraryRouting | Request in Processing | String | Comma separated list of statuses a request is routed to after successfully checking an item in from the lending library and checking the items out to the customer via NCIP. |
NCIPResponderURL | String | URL for the NCIP Server Responder. | |
ApplicationProfileType | ILL | String | The mapping for the NCIP ApplicationProfileType. This can be a tag or static value. If you would like a different library type for LibraryUseOnly, use "{Custom:GetApplicationProfileType}". |
BorrowingUserIdentifier | {TableField:User.Username} | String | The mapping for the NCIP user identifier sent for borrowing requests. This can be a tag or static value. |
LendingUserIdentifier | {TableField:User.Username} | String | The mapping for the NCIP user identifier sent for lending requests. This can be a tag or static value. |
FromAgencyId | String | Generic From Agency ID string to use in NCIP calls. | |
ToAgencyId | String | Generic TO Agency ID string to use in NCIP calls. | |
UseRequestIdentifierPrefix | false | Boolean | Determines whether request identifier prefixes are used. |
RequestIdentifierPrefix |
| String | Prefix for RequestIdentifier. This should include any separating punctuation such as hyphens or colons. If UseRequestIdentifierPrefix is set to true and this setting is left blank, the values returned by DataMapping.Handlers.RequestIdentifier based on whether or not the item is library use only will be used. |
ItemBarcodeField | String | Defines the transaction field in which the item barcode will be stored. | |
HistoryEntryAcceptItemSuccess | NCIP: Temporary Item created ({barcode}) | String | The history entry made when the AcceptItem NCIP call is completed successfully. Leave blank for no history entry. |
HistoryEntryCheckOutItemSuccess | NCIP: Item checked out ({barcode}) | String | The history entry made when the CheckOutItem NCIP call is completed successfully. Leave blank for no history entry. |
HistoryEntryCheckInItemSuccess | NCIP: Item checked in ({barcode}) | String | The history entry made when the CheckInItem NCIP call is completed successfully. Leave blank for no history entry. |
MultipleBarcodeDelimiter | " " | String | The delimiter that is used to separate multiple barcodes. |
PickupLocationField | {TableField:User.NVTGC} | String | The mapping for the pickup location field. |
PickupLocationMappings |
| String | A comma-delimited list of mappings (i.e., a=b,c=d) which will be used when mapping to PickupLocations from a particular field. Please note that Alma pickup locations are case sensitive, so make sure the pickup location value on the right side of the equal sign is cased correctly. |
Troubleshooting
The ILLiad Alma NCIP Integration addon may fail to run if security settings on the local machine are configured in a way that causes Windows to block loading the addon's files after installation. When this issue occurs, the addon will not run and the following errors will be returned in the ILLiad Client logs:
ERROR AtlasSystems.Scripting.LuaApi.ScriptEnvironmentBase - Script compilation failed for addon Alma NCIP Integration.
ERROR AtlasSystems.Scripting.LuaApi.ScriptEnvironmentBase - Compilation Error: A .NET exception occured in user-code
ERROR AtlasSystems.Scripting.LuaApi.ScriptEnvironmentBase - An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.
ERROR AtlasSystems.Scripting.LuaApi.SystemScriptEnvironment - An addon script error has occurred in a system script. The following error message was returned: An addon script (Alma NCIP Integration) could not be loaded due to an error in the script file(s).
Details:A .NET exception occured in user-codeTo resolve this issue, please unblock the addon files installed on the local machine following the instructions below:
Open the Windows File Explorer and navigate to the folder where the addon files are installed on the local machine (default location: C:\Program Files (x86)\ILLiad\Addons\AlmaNcipIntegration)
Right-click on the first file and select Properties from the menu
Check the Unblock checkbox at the bottom, if present:
Click OK
Repeat for all files in the addon's folder
Once all files are unblocked, restart the ILLiad Client and attempt to run the addon
If the Unblock prompt isn't present or the issue persists after unblocking the addon files, this could mean that blocking performed by an anti-virus software may be causing the issue instead. In this case, the addon files must be whitelisted within the machine's anti-virus software. If the issue still persists after whitelisting the files, please contact support@atlas-sys.com for further troubleshooting assistance.