And when you're on campus the whole chain of redirects and linked pages works based on your IP address without any sort of cookie-based authentication or other interaction?

E.g., the EBSCOhost resolver I have access to is behind an EZproxy login link that requires web-based authentication. I don't know what happens if that link is loaded on campus. Even if EZproxy generally does work automatically on campus, there are almost certainly some resolvers that are behind authentication, so I assume we wouldn't be able to support all resolvers.

If we did do this, it seems like we'd need some translator-like files that could extract the lookup links for individual resolvers, and some community involvement in creating and maintaining those.

I'd also worry that they would break after site changes without any real visibility. Some could be automatically tested, but not ones that didn't work without authentication off campus.

And, finally, getting the rate-limiting right might be tricky. We take some steps in Find Available PDF to throttle requests to individual domains and I believe stop trying a given domain on repeated failure, but here we'd need to send all requests (that failed a publisher lookup, at least) to the resolver, and we'd want to avoid sending too many too fast and also avoid sending hundreds or thousands of requests if it's just not working (e.g., because you're off campus).

So all in all, a tricky problem. But it's an interesting idea, and we have been talking about trying to use OpenURL resolvers more, since we've been getting a huge number of submissions to the directory.