Intota – Kate Howe tracked down some estimated times for solving our biggest issues in Intota:

• Truncated list of providers when we try to add resources in the Overlap Analysis tool.  This is a showstopper as it seems to make it impossible to use the tool.  We both make fairly frequent use of Overlap Analysis.  Kate:  The truncated list of providers bug was fixed this sprint and just passed QA today.  should be released in the next few weeks.
  
  
• Notes in the knowledgebase updates – Lola stated that this is on the roadmap for Q2 this year, so it may not be an issue for long.  We would probably count this as a showstopper if it remains un-fixed.  Kate – Fix in progress right now.
  
  
•  Slow loading of the list of licenses - while not an absolute showstopper, this is pretty bad.  We are in the early stages of a major project to add and update our license data in RM.  This slow load occurs any time Intota is loading a list of licenses.  We could encounter this hundreds of times a week during the project.   This is mostly concerning in that we expect the response time in a cloud environment service to not be significantly affected by the size of the data set at the scale we are working with.  A library with 1000 licenses shouldn’t really see a different response time than a library with 10 licenses when we are working at cloud scale.  Kate – Amy, the product manager will put this in the queue to review and see if there is a bug if it’s not already there. 

What else do we need to know to be able to decide if/when to move to Intota? – i.e. Cornell needs to test Assessment before we are willing to pay for it.

Assuming these items are reliably fixed:

*** - Columbia could be ready to move forward by end of June. 

*** - Cornell

• Get a round of check in with e-resources staff. - Liisa
• Test License terms API? - Jesse with ???
• Test Assessment, and/or get Proquest to not charge for it - Jesse
• Jesse to get Xin and others up to speed

Licenses –

360 Link – Let’s figure out what we need to learn about Link 2.0, then we can dig into these questions at our next or a future meeting.

• Http/https security issues - Penn sent info to Breck and Joyce - Joyce will check with Penn for update.
• Resources that rely on cookies - can report to Proquest any resources that do not work properly with side-bar.  These will be configured to go direct to full resolver screen.
• Jesse will pursue calls with PQ to discuss these issues and for beta partner update.