Page History

in progress

done

Provide an email update to NCBO, NLM, and Mayo with current activities and what has been built.

open

Craig Project Plan Updates

Scott:  CTS2 6.1 Service Deployment, 6.1.1

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

Struts update,  CTS2 Service Updates - Value Set Modules and CTS2 1.1 Based Framework

• 6.1.1 Struts update - Scott generated testing reports and need to give those to Tin.  
• CTS2 6.1 Service Deployment - URLS are pointing to stage.
• 1.1 Based Framework - updates based on code review and issues identified (search and value set coding scheme and version).  
• UI and CTS2 deployment - planning to get configured over the next week.   Testing distributed mode for CTS2 services.  
• There will be documentation/code sample changes for the 1.1 based CTS2 framework services.  
• Scott working on remaining Junits for the Struts update (6.1)
• 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. 
• Do all jUnits need to be 100% clean, 508? and scans up the tiers?   
• Can 6.0 users migrate to 6.1?  Larry suggested it should work this way, but not sure what this all affects.
• Scott is currently using Java 1.6.0_65.  
• Scott to send version of Java to NCI team.
• Struts update is on NCI Dev now.  Jason will request an app scan on it.
• Mapping Issue - issue with some client code.  Issue went away when Tracy went to a local API.
• Issue on searching with maps in distributed.
• JIRA issue to be created by Kim.
• VS Module work - still working on.
• Resolved VS fix on formal name works (JIRA item)

Cory:  CTS2 Client UI, Informatics Deployment

• NLM services (
• Able to resolve value set entries in the client.
• Starting to work on the 1.0 service (NLM) utilizing the existing transforms. 
• Common way to retrieve VS entries
  Researching libraries to to XML and XSLT transformatio

• based)  and transforming to the 1.1 based client.   This is complete.   Next need to incorporate the NLM authentication.
• Search has been included in the client to allow users to search on value set names. 
• Informatics configuration is planned and hope to have deployed in next week or 2. 

Craig: Project Plan Updates

• Add JJ to the project plan list
• Schedule meeting with Sherri, Larry, Kumar, JJ to discuss project plan and roadmap. 
• Tech Stack and associated dependencies.  Identified by JUnits once components are upgraded.  

• No updates this week

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)
• Agreed that we will move to 1.7.

• Will provide more details during planning meeting.  

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.

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.   

NCI to report on follow up    

•  There was a problem going directly against the API.
•  Look at this again when we evaluate Lucene
• lbConfig.prop to be updated to 800,000  NCI/Tracy to put in a ticket to do this.      
  Scott to discuss with Kevin what type of memory increase this may be or other issues it may cause. 

JIRA item done discuss priority

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

• Issue with the contains search. 
• Issue with the search extension.

• This is after the VS module work.  And during the Lucene investigation.        
  
•   Scott to look at the analyzers for this. 

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.    

• Scott checked with Kevin about the proposal for Tracy to change to 800K.  Kevin said this is defaulting to 1000 in Lucene - anything above that is undefined.   No idea how things will perform.  Tracy did test on Data QA by incrementing 100k at a time.  
  
• Tracy will continue to evaluate - better than having it fail for the user. 
  
• Scott could evaluate as well, but this is lower priority for now.  NCI will evaluate now. 
  

• Provide an email update with current activities and what has been built.   (Larry)
• No interest in monthly (at this time).
• Face to Face could be discussed.  (June/July or September)

• Not an immediate task.  Users should be able to move from LexEVS 6.0 to LexEVS 6.1.  If LexEVS 6.0 were to get shut down, then this could come back as a higher priority. 

• Updated and available here: LexEVS 6.1 Design Document - Detailed Design - CTS2 REST Services#DetailedDesign-CTS2RESTServices-5URIResolution

• Tracy cannot get that to load - Mappings.   Tracy to send Scott the details and he can take a look. 

• ISO Country and Region codes in Meta and retrievable via advanced search.  Need to figure out how to make available to FDA users - possible REST call that would pull out content and return via a REST call.   Would use CTS2 LexEVS services to pull this content.   Can currently can do an advanced search.  
• If created as a Value Set, then possible to use CTS2 resolved value set services.   
• NCI will continue to look at this.  Can provide weekly updates.

• 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.  (Need a JIRA Item for this)