Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Discussion Points:

• LexEVS
  
  • CTS2 on-line documentation is running on NCI Prod system. 
    
    • A Update on the ticket that has been submitted for the URL to be accessed outside the firewall.
      Update on the appscan
      • Still waiting on permission to be approved.
    • Lexevs 6.5 AnthillPro migration to Jenkins update
      • The Jenkins workflow on Dev is created. 
      • Jacob will test on Dev and follow up with us.
    • Performance - Browser and LexEVS
      • Indexing and Coding Schemes out of sync?
      • Broken Pipes?
      • Null values for coding scheme queries?
      • QA responsibilities?
      • After the issues in the logs are cleared up, we would like to look at container performance (memory, CPUs, DB access)
    • Browser/Tools
    • Data
    • Systems
    • Triple Store/EVS API

    Decision Points:

Sprint Status

Discussion Points:

• We discussed deploying responsibilities going forward.
• Tracy would be Ok with the Mayo team to deploy the war and admin files in the future.
  • We will need to coordinate with Rob on loads that he does out there.

Decision Points:

• We decided to discuss this issue again next week when Rob is back.

• A new NCIt browser was discussed
   
• Browser performance issues were discussed and owners are looking at their respective issues.

Decision Points:

Discussion Points:

• Kim gave a report on issues he found in the browser logs.
• Owners are making the appropriate updates to there respective issues

Discussion Points:

•  Met on Monday and focused on browser performance issues.
• A meeting is planned for Thursday when Rob and Gilberto are back.
  

Decision Points:

Discussion Points:

• A lot of development time is going into updating the remote API for the asserted value set APIs.
• There are potential security risks associate with RMI.
• There are two users:
  • caDSR - there is no new development for them.
    
  • NCIt browser - uses the remote API for development.
    • There are options for using LexEVS locally for development, including using Docker.
      
   
• Accepting a MeDRA license takes a long time as well.
• The broken pipe issue should be looked at.
• Scott suggested that as part of QA, the browser logs should be scanned on QA and/or Stage to check for errors.
• There may be code paths that the browser is going through LexEVS with that we have not tested.
  
• The new QA tester is starting to take over and picking up the browser tests.

Decision Points:

•  We decided will continue to track the issues better and have a more formal way of categorizing the problems.develop the remote API

Discussion Points:

• 8-10 weeks of LexEVS development left.
• This will include work on the remote API.
  

Decision Points:

• Next week, we can show what LexEVS features will be in the next releaseThe Thursday metting with Bron will discuss this further.

Discussion Points:

• We will discuss next week.

Discussion Points:

• We are discussing a face to face in the summer time frame.

Decision Points: 

• Sherri will determine the best times that work for her and then we will plan around those dates.

LexEVS External Users

Discussion Points:

Decision Points:

Mayo Team

• Cory -
• Scott - June 19th - July 1st
  
• Craig - March 30 - April 6

NCI

• Tracy -
  
• Rob - 
• Bron -
  
• Sana -
  
• Kim -
• Kiruthika - March 26  - March 30th