We’ve been using LibAnalytics for a few years, but Springshare has a new and improved version we decided to upgrade to this summer: LibInsight. LibInsight offers some features not found in the older tool, like automatic harvesting of COUNTER data through the SUSHI protocol (yes, that sentence is a real thing and not something out of an episode of Dr. Who), integration with LibApps, and unlimited datasets.
I’ll be taking over the technical administration of LibInsight, since I already manage all the other Springshare tools. A lot of you are using LibAnalytics to enter data, and many of you come from bookmarks you’ve saved in your browsers to specific data entry forms. All of these URLs will change when we migrate, so we’ll have to do some updating. Here are more details about the upcoming migration:
I had also planned on migrating to 360 Link 2.0 (for the third summer in a row), but frankly, the tool just has too many problems. tl;dr: we’re not migrating to 360 Link 2.0 this year. (We have never planned on using the 360 Link 2.0 sidebar (PDF), which is an absolute mess. Our plan was to use the static pages, which, incidentally, were copied from our 360 Link 1.0 redesign. Go figure.) The accessibility issues alone are enough to shut down the migration. It has enough problems that once again I saw our only solution was to create a script that completely rewrites the entire page to give semantic, accessible HTML as well as an intuitive, flexible design. And since I already have a nicely working script that gives us everything we want, the added features of 360 Link 2.0 (basically, index-enhanced direct-linking) just doesn’t justify the amount of work it would take to get the tool up to snuff for our users. So, we’ll take a look again next year. When I asked last summer about improvements to the non-sidebar pages, I was told that since most customers use the sidebar, they weren’t planning on putting any more resources into the non-sidebar pages. We’ll see if that changes in the future. I sure hope so! (Or not. 360 Link Reset works very well.)
On Wednesday, August 23rd, we’ll be pushing the eJournal Portal 2.0 live. I wrote the other day about the Journal Finder migration and asked for feedback (and included instructions for testing). I’ve heard from a few folks, but fully 33% of the respondents are currently in Australia on sabbatical, so I’m hoping to get a few more Michigan-based folks to take a look.
As always, let me know if you have any questions!