A little while ago, I added COinS (ContextObjects in Spans) to our SFX menu pages. I have been asked by several people about the motivation of this, since it would seem that the user would know if fulltext was available to them at this stage.
So, imagine one of our users is at an SFX menu for another institution. Normally, they’d be, well, screwed. If COinS are enabled in the menu, however (and now we’ve proven this is pretty darn simple), they could use WAG the Dog or Dan’s bookmarklet or Greasemonkey extension (he has them for GT) and get to our fulltext subscription.
Another use case is GT Library’s web designer. Heather is a GT employee (of course), so she access to all of our resources. Being an FSU student, she also has access to their collection. Imagine Heather getting a GT SFX menu for an article that we don’t have available in fulltext. By using her bookmarklet, she could then see if that article is available from FSU, without having to manually look for it herself. If FSU implemented COinS in their menus, then it would work both ways. With GALILEO opening up SFX for the entire state, one has to assume that all of our users could potentially belong to more than one library community (GT and ATL/Fulton Public Library, for example), each with their own subscriptions.
Anyway, it’s quite cool to see (quasi-)real world examples of how COinS would work.