 |
 |
Dan et al, I didn't quite understand what you were after when this came up on the list a few weeks ago, but I get it now. Nice work. I would add to your list the OhioLINK OLinks resolver, which will work for pretty much any university in Ohio: URL: http://olink.ohiolink.edu/olinks.php GIF: http://olinks.ohiolink.edu/images/olinks/olinks-54x19.png I do have a question about the scalability of this approach though: are you envisioning that each user would have to tote around their resolver link as a bookmarklet, and that institutions would no longer arrange to pre-configure databases for their users' use? That might make sense for certain high-end users (e.g. those interested in the "Do something else" function), but not for your average user. It seems like this could create more, not less, work for the user. Am I missing out on a crucial detail? Ken At 05:19 PM 02/01/2005, you wrote: >A few weeks back several people were kind enough to add their resolver >information to a list for experimentation with new tools designed to >address the "appropriate resolver" problem. I've set up a simple demo >of one potential use: bookmarklets that redirect openurl links to the >right resolver for a user. > > http://curtis.med.yale.edu/dchud/resolvable/ Ken Irwin [log in to unmask] Reference/Electronic Resources Librarian (937) 327-7594 Thomas Library, Wittenberg University