Update on Cornell RM Implementation – Where are we at?-
Serials Solutions Client Center response time – See Bob’s message text below. I believe we can do some kind of response time check without being too distracted form other work, but let’s discuss our options and make some plans.-
- Seems to be slowing down more regularly.
- Things to test: Each staff, once per day perform and time the following tasks:
- Look up admin login
- Attach a license
- Track a new title
- Set up call with Serials solutions to discuss test methodology and express our concerns. - Joyce will do Monday
- Update Bob/Xin with plan - once we have a methodology plan.
- Everyone - add items to the list above that seem to take longer than appropriate or send to Jesse/Liisa/Joyce/Susan.
CE – Our CE module is built. Let’s discuss how we should move into using it. A few points, but far from all:
- A variable to consider is that SeralSolutions will begin migrating customers to the Intota platform later this year. CE functionality is not available in Intota platform, yet.
- It may be worth looking at Intota in relation to the Client Center response time issue.
- It may be a stronger statement to push for CE functionality in Intota if we are truly using CE.
Support for being on bleeding edge (i.e. sooner move to Intota) is low. No support for CE functionality, not sure if existing functions are there, yet.
Decision: Continue CE plans as they are. Watch Intota development and push for CE functionality.
Bob's message:
I believe SerialsSolutions response time (at least in the client center) has degraded to the point where we need to take more formal action.
I've noticed slow response frequently over the last few months on the rare occasions I use the client center. Just now, I decided to measure response time but gave up – a couple of commands got response in 30-45 seconds (already terrible); two others were still running after 3 minutes. These were not esoteric queries, but searches for specific databases and requests to display the information.
I realize today may be unusually bad, but I've seen enough to believe there's a serious problem. I'd like to request that we do a formal time test at intervals over the next week or so: run standard searches and commands at intervals (maybe 3 times a day) and record response times.
Once we see the results, we can decide on an appropriate approach to SerialsSolutions. We're paying them a lot of money, and slow response must be costing us a lot in terms of lost productivity. Meanwhile, we're expressing deep concern about the potential for slow response in Alma.
If others agree, may I ask that the 2CUL E-Resources team coordinate such a test? In order not to further slow productivity, we might use staff with some familiarity with the system but not primary
users as testers. Let me know what you think.