…example (private university)...
Solution to handle library vendor validation During Summer 1999, began testing Ezproxy as replacement for locally written URL-rewriter program we’d been using since 1996. Out of the box, it handled vendors using IP-validation. Chris Zagar of Useful Utilities added features to support scripted logons to vendors like (New) FirstSearch and Cambridge Scientific Abstracts, to support HTTP-based username/password scenarios (Hoover’s Company data), and to support multiple ID files so that we can assign different permissions to different classes of patrons. Currently, we are able to support all our vendor validation scenarios using Ezproxy. (Many of our e-journal links still point to the old program, because we haven’t had time to change 600+ URLs.) In February, the Ezproxy log showed app. 230,000 “fetches” (this count includes every graphic element, etc. on every page, so the page count would be much smaller).