NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 2

changes.mady.by.user Unknown User (stanclcr2)

Saved on

compared with

New Version 3

changes.mady.by.user Unknown User (stanclcr2)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
64ScottTo follow up on URI's on OWL2 with Harold.   on hold
136ScottPoint the CTS2 API page to Stage PROD (wiki)   open
139KumarTo do an analysis of the Project plan for budgeting purposes.   open
140ScottUpdate struts jar to 2.3.16   

in progress

149ScottContact Jacob about X11 access on DEV   done
150ScottDocument URI Resolver more thoroughly   open
151ScottJIRA Item to move master to lexevs/lexevs   open

...

Immediate Priorities and Problems (Mayo Team)

Scott:  CTS2 6.1 Service Deployment, 6.1.1 Struts update,  CTS2 Service Updates - Value Set Modules and CTS2 1.1 Based Framework

Cory:  CTS2 Client UI, Informatics Deployment

Craig: Project Plan Updates

  
caDSR and Value Set and other URIs

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

  (Weekly Status) Tech Stack Notes

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.    		  
    Continuing Development through next fiscal year (Larry)

    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.    		  Struts Security Update (Jason)Status (see above)  6.1 Deployment

    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)    
    Max clause count issue .

     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. 
    		  
    Discuss search issues around forward slash / in contains search

    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. 
    		  
    Mapping Index issues

    Discuss Stack Trace and report on updating of browser code

    • see above
    		  
    URI Resolver Documentation
    • 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.    
    		  
    (update)

      

    		  
    NCI, NLM, NCBO and Mayo Planning (Monthly Meetings, Face to Face) GitHub
  • 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)    		  

     

     

     

    JIRA Issues

    Description
    Jira
    serverNCI Tracker
    keyLEXEVS-570
    Jira
    serverNCI Tracker
    keyLEXEVS-572
    Jira
    serverNCI Tracker
    keyLEXEVS-573
    Jira
    serverNCI Tracker
    keyLEXEVS-574
    Jira
    serverNCI Tracker
    keyLEXEVS-576
    Jira
    serverNCI Tracker
    keyLEXEVS-579
    Jira
    serverNCI Tracker
    keyLEXEVS-583
    Jira
    serverNCI Tracker
    keyLEXEVS-584
    Jira
    serverNCI Tracker
    keyLEXEVS-585
    Jira
    serverNCI Tracker
    keyLEXEVS-586
    Jira
    serverNCI Tracker
    keyLEXEVS-587
    Jira
    serverNCI Tracker
    keyLEXEVS-588
    Jira
    serverNCI Tracker
    keyLEXEVS-589
    Jira
    serverNCI Tracker
    keyLEXEVS-592
    Jira
    serverNCI Tracker
    keyLEXEVS-593
    Jira
    serverNCI Tracker
    keyLEXEVS-594
    Jira
    serverNCI Tracker
    keyLEXEVS-595
    Jira
    serverNCI Tracker
    keyLEXEVS-596
    Jira
    serverNCI Tracker
    keyLEXEVS-597
    Jira
    serverNCI Tracker
    keyLEXEVS-598
    Jira
    serverNCI Tracker
    keyLEXEVS-599
    Jira
    serverNCI Tracker
    keyLEXEVS-600
    Jira
    serverNCI Tracker
    keyLEXEVS-601
    Jira
    serverNCI Tracker
    keyLEXEVS-602
    Jira
    serverNCI Tracker
    keyLEXEVS-603
    Jira
    serverNCI Tracker
    keyLEXEVS-604
    Jira
    serverNCI Tracker
    keyLEXEVS-605
    Jira
    serverNCI Tracker
    keyLEXEVS-606
    Jira
    serverNCI Tracker
    keyLEXEVS-607
    Jira
    serverNCI Tracker
    keyLEXEVS-608
    Jira
    serverNCI Tracker
    keyLEXEVS-609

    ...