Page History

• NCIt Browser - merge work
  • Currently merging dependency work with browser updatesCurrent version Kim is working on has Spring 5 updates
    • Waiting for feedback on this
  • There is another branch of LexEVS that has other dependencies updated, much more modest
  Kim will need to reimplement work he has done on main branch
  • He is working on the merge on his own at the moment
  • Ended up with Mayo requested to do the merge. Completed this morning

How will Kim be able to test?

• Suggested option is to create a static set of data for testing the browser
• How would this set of data be delivered?
  • Docker?
  • Central database and package of indexes?
  • SQL file and related indexes?Need minimum set of data requiredB. Carlsen supplied mini-Metathesarus some years ago.
    2 versions in lbTest data sets
    
    • Brian has a newer version a few months old. He has a program to generate it.
    NCIt
    • GO
    • Meta subset
    • Mapping
    • Value Sets
• How to keep data updated enough to be relevant?Testing is functional - this was fixed so needs to be tested.
• Kim is working on a Windows laptop - Windows 10 Enterprise
  • 8GB RAM? 16GB?

• Update to Vue3 continues
  • Still questions on duplicates? 

• Kim has started testing
• Kim says meta extensions need to be made compatible with Spring 5
• - working?
• Meta extension wrapped into lexbig.jar
• performance issuesThree lexevs extensions have been added to the main code base - need inspected
• Have these been merged into the dev branch?
Do they address the issues Kim has found?

• Stage - they might need hand holding
  • Tracy met with Chuck on Tuesday and walked through some configs

• Corretto Java 8 installed on Dev in /usr/java8
  
  • https://docs.aws.amazon.com/corretto/latest/corretto-8-ug/downloads-list.html
  Still waiting on Tomcat to run under Corretto testing completed on Dev, being implemented on QA
• app-stage2.nci.nih.gov

• Timeline security driven?
  • Corretta only extends us to 2026
  • Zulu extends to 2030 - possibility?
• EVS Explore/Stardog stack timeline to be ready to take overCheck the explore time to time to see the progressOn Dev - is down to the low priority vocabularies
• ICD, GO, Meta, NCIt
• Possibility of making EVS Explore more visible??
  • No timetable and no expressed interest

• Keep restarting the tomcat containers but they go back down. 
• Have another engineer brought in to look at it

• Working to get the Tomcat containers set up on QA.
• Corretto installed but another group needs to config it

Report Exporter and Mapping tool are under a project

RestAPI and EVS Explorer are going to be moved into a project, perhaps into the same one as above