Page History

• NCIt Browser - merge work
  • 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 morningCompleted - acceptable?

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?
  • Working on research of Windows options
    SQL file and related indexes?
    
    • NCIt
    • GO
    • Meta subset
    • Mapping
    • Value Sets
• How to keep data updated enough to be relevant?
• Kim is working on a Windows laptop - Windows 10 Enterprise
  • 8GB RAM? 16GB?

• Update to Vue3 continuescomplete

• Kim has started testing - working?
• Meta extension wrapped into lexbig.jar
• performance issues?

• Stage - they might need hand holding
  • Tracy met with Chuck on Tuesday and walked through some configsChuck provided list of URL's to test

• Corretto testing completed on Dev, being implemented on QA
• app-stage2.nci.nih.gov

• Timeline security driven?
  • Corretta only extends us to 2026
• EVS Explore/Stardog stack timeline to be ready to take over
• Possibility of making EVS Explore more visible??
  • No timetable and no expressed interest

• Remote API / URI Resolver schedule for shutdown this month.
  • Ticket for shutdown on Dev - this week?

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

• 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