Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Scott:

MySQL 5.5 update, Stage Crash, Default Sort

• MySQL updates
  
  • running Junits to confirm upgrade.
  • There are some junits that are causing issues - one is causing locking of the database.   This specific case is against the pre-CTS2 API.
• Stage Crash
  
  • In the logs, Scott noticed that a user might be using the old caCORE API.  After crash - on restart, the server started responding again.
  • Scott will look at the logs a bit closer from site scope. 
• Default Sort
  • Sort is based on scoring algorithm
  • Nothing needs to be fixed, but need to understand how it is sorted and also how to find other sort algorithms. 
  • From LexBIGService can get a list of the sort extensions.  (Scott to send code)
  • There was an email thread with Kevin (Larry to forward to Scott)

Cory:  CTS2 Client UI, Java 1.7

• CTS2 Client UI
  
  • Feedback received from Sherri and Tracy
  • Updates made to the UI (note sent yesterday)
  • IE 11 still has issues with client rendering. 
• Java 1.7
  • Version 1.7 update 55
  • Version 1.7 update 45 - is current at NCI
  • Only requirement is Java 1.7, so the update 55 is okay unless there are
    
    

Craig: Project Plan Updates

• Add OWL2 loader Jira items.
• Update ARC document with dates as they correlate to Tech Stack updates complete.

• Denise and Sherri to get a demo set up in June – Harold to be included.
• No updates.

• Alameda group is already reviewing the data for Tracy.
• 2 different maps are causing the issue. 
• Not seen as a source issue.  
• JIRA item to query on the URI (true identifier) was created by Tracy.
• Would like to have the manifest be used (currently it does not) - needs to be a feature request.   Scott to create Jira item.  Do we still need to consult with the Alameda group
  
  

• Update from Larry
  
  • progress being made - Eric and others understand what is being requested. 
  • Considering an 800GB drive.
    
    • Need to look at where logs could be stored.  If on SSD, it would cause additional read/writes.
• Noted slow load time over network for MySQL 5.5 (Scott)
  
  • Something to keep in mind as we move forward. 
  • Loading to happen local to the DB would be optimal, but may not be practical in the environment. 
• Clarify ARC Deployment Tasks
  • Craig and Scott to update the ARC dates. 

•  Tracy to report on IE version

• Reported by Sherri that value set wasn't resolving correctly.
• Discovered that previous issue (truncating value set names to 50 chars) is causing this issue in the CTS2 Services.   We aren't resolving to the shortened version of the name.