| Page Properties | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Field | Data | Notes |
|---|---|---|
| User Identifier type | Primary Identifier (default) or Other Defined Identifier in Alma (Barcode, University ID, etc) | Data from this field must match a unique patron identifier in ILLiad. The default in ILLiad is username. If the defaults cannot be applied to your campus then please view the additional instructions for alternate user identifiers here. |
| Request pushing method | Open URL | |
| URL template | Campus specific Open URL | According to Ex Libris, this is not mandatory. Reference ERM Functional Call from 4/6 |
| Default library owner | Resource Sharing Library or Temp Location | |
| Request Item - Bibliographic record ID type | OCLC Number | |
| Request Item - Default location | Lending Resource Sharing Request | |
| Check-Out Item - Default location | Borrowing Resource Sharing Request | |
| Check-Out Item - Default item policy | Campus defined policy | |
| Accept Item - Default location |
Resource Sharing Library
If you have elected to use the Resource Sharing Library then you must configure both the Open Hours and Terms of Use tables for that library.
...
After all edits have been made to the file, restart Illiad and register the Add-on (see the documentation on activating an Add-On).
Distributing the add-on to multiple ILLiad clients
Atlas provides documentation for configuring ILLiad so that add-on files can be shared by multiple clients:
https://prometheus.atlas-sys.com/display/ILLiadAddons/Distributing+Addons
The add-on can be distributed to all clients and de-activated for those clients that are not using it.
During testing at SLO, the NCIP plugin was deployed once from the server, with its config, and is auto-activated in the everyone's ILLiad client, but it was discovered that the ILLiad client needed to be run once as Administrator in order to write the updated add-on from server share into Program Files (x86)\ILLiad\Addons. (Thanks to Mike Price at SLO for sharing this troubleshooting tip!).
Action log
| Section | Point Person | Expected Completion Date | Last action taken | Next action required |
|---|---|---|---|---|
Articulate the need for the policy (background) |
| |||
Create a Policy Statement |
| |||
Identify and create best practice recommendations |
| |||
Update Response Server URL instruction add new screen shot |
| |||
| Added documentation for distributing add-on to multiple clients | Lauren Magnuson (Unlicensed) |
|