So, the term is rolling, and no one is dead yet, including the instructor who took up eight hours of three different consultants' time tutoring her in making recordings only to decide that she would use one of the Lecture Capture enabled conference room 'studios' instead, "thanks anyway". And that was a very close one.
But today, today I may have slain someone, and I'm not sorry at /all/.
Someone from Perusall (collaborative annotation tool) popped up in Boss's inbox saying that we have so many instructors using Perusall now, isn't that great, and this is usually when they start negotiations for a site license; is she the person to talk to?
Background: Perusall is installed at root, in our Canvas instance, and any instructor in the Uni can activate it in their course with no restrictions. This is specifically because Perusall, three years back, suggested doing so and promised they were and would remain a free tool, subsidized by their sweetheart deals with textbook publishers.
So I saw red, told Boss I'd deal with it, and promptly forwarded the email to central IT's software licensing group, with a note that they were the unit who could talk about whole-university site licensing, and also, just incidentally, that if they were exploring licensing they might want to compare features and price points on Hypothes.is, the other annotation tool I know some instructors use; that either tool would work just as well for all the use-cases I know of, if we have to pick one. And then I dropped a note to the Harmonize rep that if they can push up text-annotation in their development queue, I could write a /very/ convincing sole-source argument for adopting them instead of Perusall.
*smiles sweetly and coldly*
NO ONE tries to shake MY College down for license money, buddy, not and walks away after.
But today, today I may have slain someone, and I'm not sorry at /all/.
Someone from Perusall (collaborative annotation tool) popped up in Boss's inbox saying that we have so many instructors using Perusall now, isn't that great, and this is usually when they start negotiations for a site license; is she the person to talk to?
Background: Perusall is installed at root, in our Canvas instance, and any instructor in the Uni can activate it in their course with no restrictions. This is specifically because Perusall, three years back, suggested doing so and promised they were and would remain a free tool, subsidized by their sweetheart deals with textbook publishers.
So I saw red, told Boss I'd deal with it, and promptly forwarded the email to central IT's software licensing group, with a note that they were the unit who could talk about whole-university site licensing, and also, just incidentally, that if they were exploring licensing they might want to compare features and price points on Hypothes.is, the other annotation tool I know some instructors use; that either tool would work just as well for all the use-cases I know of, if we have to pick one. And then I dropped a note to the Harmonize rep that if they can push up text-annotation in their development queue, I could write a /very/ convincing sole-source argument for adopting them instead of Perusall.
*smiles sweetly and coldly*
NO ONE tries to shake MY College down for license money, buddy, not and walks away after.