Please see the attached chart for a full explanation of how database authentication at OPLIN works.
First, the vendor has to be able to do authentication based on IP address only. This usually isn't a big issue; we've only run into one small vendor out of the hundreds that libraries subscribe to that couldn't handle it in some way.
Second, we need a generic link to the resource, that is, it doesn't have any information in the URL that is specific to any one library. We keep a database of generic links here at the office, which lets us add database links to your locally purchased databases tab (at http://oplin.org/databases) pretty quickly, since the same link will work for any library.
Lastly, you just need to give the vendor your OPLIN proxy IP address. All the authentication in the world won't save us if the proxy IP address doesn't have access. OPLIN proxy IPs always start with 66.213.41 and have a 4th octet of whatever their FSCS is. For example, Ada (OH0001) is 220.127.116.11. We will try to set up authentication for anything that you request.
Technically, you don't, unless the database vendor does not allow access from outside a library building, because patrons at the branch can just authenticate to the Ohio Web Library databases as if they were at-home ("remote") users. If you want your patrons to have seamless, in-library access, however, and to have their usage of the databases automatically added to your library statistics, we have to give the vendor an unchanging, static IP address they can associate with your library.
If you have further questions, please contact OPLIN Support.
|Flowchart of OPLIN database authentication||21.38 KB|