Page History

Craig Project Plan Updates

• Update the plan to include Struts work for both 6.0 and 6.1.
• Include deployment of 6.1.1 and 6.0.?
• Attempt to get waiver for appscan

Scott:  Struts update, Mapping Index and other issues, Value Set Modules

• Scott working on remaining Junits for the Struts update (6.1)
• Scott to send version number of Java to Tin.
• Struts update is on Dev - appscan could be run now.  Jason will make the request.   Possibly use this report and won't need to run on QA. 
• There is a map search issue when searching (distributed).  Kim to create JIRA iteam.
• Will continue to work on the value set modules on once Struts work is complete.   
• Value Sets - Resolved Value Sets - Formal name (Jira ??) is in the current build.  

Cory:  CTS2 Client UI

• Able to resolve value set entries in the client.
• Starting to work on the 1.0 service (NLM) utilizing the existing transforms.  

Harold, Gilberto and others to discuss:

Denise is interested that when publishing caDSR content - she has been asked about the identifirers in caDSR are globally unique.   Denise is wondering what format these IDs should be used. Publishing from caDSR and accessing Value Sets in LexEVS.

 Harold provided a brief overview.  We will provide a copy of the slides.

Ideally, there would be a DNS entry (snomed.info) - however, not confident that id would be supported.

http://id.who.int/icd/release/10/2010/H44.5

Best approach would be to continue to include to discuss during the weekly calls.  

Revisit Java 1.8 update

• Decision to be made in May 2014 regarding 1.8. 
• If can push the 1.7 update, then that would give time to determine availability of 1.8 at NCI.
• However, Scott suggests that we do start update to 1.7 sooner than later.  
• Anticipated 1.8 issues - there are differences in Java that cause compiler issues.  (Tracy)
• Agree that we will move to 1.7.

Kumar  to deliver a project plan analyses.

• Need to have Struts added to the plan.  Craig will do this and provide to Kumar as soon as possible.

Status (see above)

Issues with CTS2

• Scott can return to this issues once complete with Struts.  
• May need assistance from systems team to get access to logs.  (contact Jacob)

 Nci to report on follow up 

• Strategy was to increase max count and verify if would work or not.  Tracy to make the request.  Highest tested was 800k.  Scott to check with Kevin on what effect this max will have on memory/resources.  
  
• Scott to look into breaking up the indexes. 
  
• This issue is against the API directly.   Breaking up the index may not not help in this case.  
  

JIRA item done discuss priority

• This is against the search extension.
• Scott created Jira item
  
•  Consider this as part of the Lucene evaluation. 

Discuss Stack Trace and report on updating of browser code

• see above

• included as part of installation.
• Scott can provide text to describe what the URI resolver is and how it is installed as part of the CTS2 LexEVS Service.
• When updating Data, what needs to be restarted?  (Tracy)  Scott to document this.    

• The lexevs/lexevs was going to be location for issues
• Continued development would be in lexevs/lexevs
• At release time, code would be from lexevs/lexevs into NCIP channel
• NCIP will fork from lexevs/lexevs.