Is there a way to link to restricted resources without inserting the proxy link, and still providing access?
Here's what I know from my past library experience:
If you have restricted resources and don't include a way to authenticate the appropriate users, you're not restricting the resource. That may be fine for some resources - for example:
- some databases allow for visitor use while on campus/in the library vs. student/faculty/staff use only (in the case of an academic library), card holder use only (in the case of a public library), or employee use only (in the case of a corporate library);
In this case, IP recognition (set up with the vendor) is all the database needs to know that the appropriate users are using the database, so you don't need a proxy prefix on the link unless you'd like people to be able to access the database from off campus or outside of the library/company.
If you'd like to provide access off campus or outside of the library/company, you'll need a way to authenticate the appropriate users - like a proxy server.
- some databases may be free on the web, so authentication is unnecessary.
There are some resources, however, that always require authentication because of contract restrictions (students/faculty/staff, card holders, or employees only). In those cases, you'd need to have some sort of authentication method, like a proxy server, in order to insure that only the appropriate users are accessing the database.
If anyone else has other ideas/methods, please post comments!