LexEVS Meeting Minutes - 26 March 2014

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Value Set Module - still making progress.  Coordinating with Kevin on queries across services. 

CTS2 Client UI - Demo at meetings end.

https://www.evernote.com/shard/s89/sh/0fad31fe-ee41-4dac-aec6-0a01d36ce60c/d48e3990d1fbe42b7823ccf46c52f172

Project Plan Updates -

Gilberto suggested skipping Java 1.7 and going to 1.8.

• Need to make sure J.J (systems group) has Java 1.8 available when we go to production
• Wouldn't be available on Dev machines - would need to develop locally
• (Larry) VS enhancements were high on NCI's priority list - big concern
• Larry to look at securing some commitment for next fiscal year to continue development.
  
  • OWL 2 work (Gilberto) asking where it is
  • Loader issues are set for after dev work done and ready to deploy to tiers
  • 586, 583, and 614?  
• Need to estimate these Loader issues and see if it fits in the plan (add to JIRA items list in the plan)
  
  • JJ concerned about Jboss to Tomcat migration.
  • JJ to verify using Java 1.8 in the future.

Vulnerability in current struts version - but we don't use that feature.

• • Used for Grid and distributed services (to display a web page)
  • There was a request that that page not be visible outside the firewall (Tracy)
  • Currently at 2.3.15 and upgrade to 2.3.16.1. - This should only be a patch upgrade.
  • Scott suggested that we should just remove the Struts dependency.
  • The vulnerability was focused on an upload functionality.
  • Tracy - suggested we leave what is out there (it's already protected), otherwise just drop in the updated Struts jar
  • Some Security scan found this (none sure what type of scan) - JJ
  • JJ to determine what type of scan uncovered this issue.
• No additional comments on F2F notes.
  • Larry wasn't sure what belongs in the ARC meeting notes.  
• We can follow up (Hardware,performance, App versions…)

Notes review.  No comments or additions. 

Review what is needed in the ARC meeting - what belongs in that part of notes - Hardware, performance requests.    Team to review. 

Production server needs to be updated and then another scan. 

Can point the CTS2 API page. (Scott)

Need to consider what options are available to provide versions. 

Using coding scheme version to manage (but if several coding schemes, may not get what we need).

Can set up a dedicated time to discuss.   (Kim, Scott, Gilberto(optional))

Gilberto to show the HubZero forum

GitHub - Seems like a better choice

• Tied to project and persisted.
• Could have for multiple projects
• Better for external projects.
• lexevs/lexevs repository would be the master.

Forum would be on lexevs/lexevs

• Julie asked why we are using GitHub instead of NCIP Hub.

Discussed during Tech meeting on Wed morning.  

Decided wasn't used in the past/recently, and could be retired.  

Tracy looked at usage - decided it was declining. 

(Larry) Thought usage was declining when looking at the IP list
As part of 6.1 announcement would not contain Grid services and 6.0 Grid service would retire in 6 months.

Are there rest services that caDSR should be using?    Will they use the same URIs that are provided on browser?  Currently using the URI that defines the value set.