Related Topics • INFO: ISO Auto Holding of Received APDU until Shipped APDU is received from Lender • INFO: Changing Note Types for ISO • INFO: Expire Dates and ISO ILL • INFO: Forwarding Requests via ISO ILL • HOWTO: Going Live with Lending or Borrowing Only • See more

Other Support Options • Contact Atlas Systems Phone Numbers, Support Options, Online Help, and more. • Listserv Pose a question to other users.

Page Tools Print this page E-mail this page

Feedback How helpful was this article? 5 Best 4 3 2 1Worst 0 N/A Suggestions:

SUMMARY

In a shared server configuration, it is possible for each site to define their identity for ISO requests independantly of the other sites. This requires some additional records in the Customization and ISOCustomization tables. These two tables allow you to use your own site codes within ILLiad that translate to your ISO values when sending and receiving ISO ILL requests between other servers.

Customization Table key - ISOSystemID

For each site in a shared server configuration, there can be a separate and unique ISOSystemID. For example site LEAFS may identify itself as NHL:TORONTO for it's ISOSystemID, while the site DUCKS may identify itself at NHL:ANAHEIM. Any site not specifically listed in the Customization table will be assigned the first value in the table. So it is a good idea to fill out values for all of your NVTGC fields for this key. Here's an example of the values in your table.

As a note, ISO symbols are generally designed to have the external system as the prefix and then the symbol after it. So for those sites using RLG symbols, your codes would be RLG:NYCX. This means that when you send to other RLG institutions as well, you would need to add addresses for those libraries to your database with the symbol RLG:NYCX etc. where before you were only using NYCX.

ISOCustomization Table key - ResponderId

For incoming messages, you ILLiad's ISO service must match the ResponderId on the incoming request to a site on the shared server (NVTGC). So that if another institution sends an ISO request to NHL:TORONTO, ILLiad on that server knows that that ResponderId maps to the NVTGC site of LEAFS. If you have one site who handles all incoming requests, you only need one value in the table, and the ISOValue would be Default, but most sites will work independent of each other in a shared server environment. An example of the values in your ISOCustomization table would be:

You can not view this table currently in the Customization Manager (this table will be added in a future Customization Manager release), so you would need to add these values through a SQL Script. To add these values to your table, open a SQL Query Analyzer and connect as sa or Windows authentication. In the open script window paste a script similar to the one below. Note the script below is only a sample and you will need to make changes to customize it to your site.

Use ILLData
go
insert into ISOCustomization (ISOType, ISOValue, ISOName, ILLiadName)
values
('RequesterId','NHL:PHILLY','NVTGC','FLYERS')
go