NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Key

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

...


SYSTEMS
EVS transition to virtual machines

STATUS: As decided from last week, we will wait to switch STAGE from on prem to VM once PROD VM is ready; so we can switch both PROD and STAGE at same time .

Systems

BACKGROUND: 

On Friday Sept 29th, we were asked to deploy a banner on public-facing websites if the government was shutdown. There was confusion about who was reponsible for which pages - and how to do it quickly (especially if systems groups goes to bare-bones support level. While the government was not shut down, we still want the ability to handle it better in the future.
 
OBJECTIVE
:

 to be able to update public-facing pages with banners quickly and efficiently, with Consistent styling desired for all sites - in case the need ever arises again (in case of another shutdown/emergency/etc)


ACTION:

  •  Build responsibility list for public facing pages (Jason Lucas compiled the list) thumbs up 

Application

URL

Developer/POC

Term Browser

https://nciterms.nci.nih.gov/

Guidehouse/Kim Ong

Metathesaurus Browser

https://ncim.nci.nih.gov/

Guidehouse/Kim Ong

Term Suggestion Application

https://ncitermform.nci.nih.gov/

Guidehouse/Kim Ong

EVS Explore

https://evsexplore.semantics.cancer.gov

WCI/Brian Carlsen

EVSRESTAPI (Swagger Page)

https://api-evsrest.nci.nih.gov/swagger-ui/index.html

WCI/Brian Carlsen

EVS website

https://evs.nci.nih.gov/

Clint Malone?

Report Exporter

https://evs.cancer.gov/report-exporter

Mayo/Andrew Moore

LexEVS CTS2 docs                          

https://lexevscts2docs.nci.nih.gov

Mayo/Tracy Safran

LexEVS CTS2 Landing Page

https://lexevscts2.nci.nih.gov/lexevscts2/

Mayo/Tracy Safran

EVS Semantic Integration Platform

https://sip.evs.cancer.gov/evssip/

ESI/Ye Wu


ACTION:


LEXEVS UPDATES

Planning

  • Complete Report Exporter refactoring and dependency updates

    • (see EVSREPEXP-475 -> 483)

  • RMI Retirement - in progress

    • Update test script
  • Examine feasibility of Java 17
  • Miscellaneous bug fixes
    • Investigate ERROR messages (both reported by Jason Lucas, and catalina.out  

and Focus


Completed Sprint - Sprint 212 (Sept 4 - Sept 29)  – Burndown Report

Current Sprint  - Sprint

LexEVS Sprint Status

Completed Sprint - Sprint 212 (Sept 4 - Sept 29)  – Burndown Report

Current Sprint  - Sprint

213 (Oct 2 - Oct 27) LINK TO Jira Sprint 213

  • EVSREPEXP-491 resolve branch-download list not being displayed on chrome browser (now FIXED)
  • EVSREPEXP-433 Security issue: set-value vulnerability
  • For the month of October 2023, the Mayo group is planning to:

    • Complete Report Exporter refactoring and dependency updates

      • (see EVSREPEXP-475 -> 483)

    • RMI Retirement - in progress

      • Unfortunately, I do not have a detailed update at this time, other than there are efforts to update the test script. I believe that the the RMI is turned off on STAGE, and the test script would test other components to verity that there are no unseen side-effects.

    • Improvements, Refactoring Code Debt, Feature development:
      • LEXEVS-5341 Update Spring to Spring 6
      • LEXEVSCTS2-453 Update CTS2 welcome with digital sytle requirements (header, footer, etc)
    • Examine feasibility of Java 17
      • BACKGROUND: a small number of LexEVS components (aka dependencies) are being phased off of java 8 (or are no longer being supported on java 8).  We ideally want to use a current version of those components (dependencies). IF the current version of that component is only supported on Java 14 or later (just as an example), then we would have to migrate the ENTIRE LexEVS stack to Java 14 or later. (Note that the current Java version is Java 21 LTS, and the most popular non-LTS version is Java 14). So there is a risk that a vulnerability is found in the older version of the component/dependency and we would have to either migrate everything quickly to a new version, or not use that component (which might not be possible), or shutdown LexEVS entirely. Note that there are certain versions of Java which are "long-term support" versions - meaning that they will be supported for several years beyond non-LTS versions. LTS versions are Java 8,  Java 11, Java 17, and Java 21.
      • OBJECTIVE: find out what would it be like to upgrade from Java 8 LTS to Java 17 LTS.  How hard would it be? How long might it take?
      • LEXEVS-5361- Investigate Java 17
    • Miscellaneous bug fixes (several small bugs that have been identified over time and need to be addressed)
      • EVSREPEXP-491 resolve branch-download list not being displayed on chrome browser (now FIXED)
      • EVSREPEXP-433 Security issue: set-value vulnerability (in progress)
      • LEXEVSCTS2-452 test_associations_
    LEXEVSCTS2-452 test_associations_
      • subject_of call revealed hierarchy bug
      • EVSREPEXP-478 Feedback form is not coming up
      • LEXEVS
    -5341 Update Spring to Spring 6LEXEVSCTS2
      • -
    453 Update CTS2 welcome with digital sytle requirements (header, footer, etc)LEXEVS-
      • 5252 Read an Entity by URI throwing a 302 error
      • LEXEVSCTS2-431
    Service resource does not populate Service name/versionLEXEVS-5361 Investigate Java 17
      • Service resource does not populate Service name/version
      • Investigate ERROR messages (both reported by Jason Lucas, and in catalina.out )

    ACTIONS


    Technical Debt remediation

    LexEVS Code Debt Refactoring

    • Coding complete on lexevs services - except for isolated dependencies
      • The isolated dependencies largely depend on using an updated version of Java (e.g. they are using more current Java versions. Java 21 LTS is the current version.  FYI: the LTS stands for "long-term support". LTS versions are Java 11, Java 17, and Java 21. . they are using more current Java versions. Java 21 LTS is the current version.  The more popular non-LTS Java version is Java 14)
      • Scott is investigating costs and feasibility of Java 17 (see LEXEVS-5361 above)
      • LEXEVSCTS2-447 javax-servlet - on hold, until we update Java 17
      • LEXEVSCTS2-446 spring-boot - on hold, until we update Java 17
    • Work on NCIt Browser - ehcache beta on dev. Kim approves promotion (Scott)
    Report Exporter


    • Discussion Points:

      • Vulnerable dependencies - in progress
        • Red Herring: while Andrew was debugging, was getting "no results" for Concept codes – turns out it was service problems
        • ?
          • Image Modified
        • Improving unit testing remaining
      • Ticket 487 - on Prod
      • Feedback form
        • Need to research approval procedure, Mark was asked to reach out to OCPL
        • Andrew to supply copy of survey form from RE
    ACTION:

    ACTIONS

    on
    • from OCPL on  
    Securitysee JQuery issue under Systems

    Statistics Dashboard

    OBJECTIVE:  
    Complete Migration of Statistics Dashboard from SumoLogic to DataDog by March 2024

    STATUS:

    The queries used in the Statistics Dashboard have been shared with < someone on migration team > (as of Sept 2023).

    They are working on migrating from "SumoLogic" format to DataDog format 

    • SumoLogic Query: 
    • Data Dog Query

    <note: removed images of DataDog vs SumoLogic queries, as they didn't add much to the discussion anyway >

    ACTIONS:

    View file
    namedbm_sd_actions.7ee020748834b8a28b07d02f5e65e6e0.avif.pdf
    height150

    Image Removed
    • etc) 
    Comparison/Mapping Tool
    • On Hold
    AWS Cloud to be in Separate AccountDiscussion Points

    Waiting on AWS team

    Decision Points:

    Team Absences


    Mayo Team - Tracy off Oct 12, 13.  In training Wed, Fri.  Andrew off Oct 27

    MSC - 

    Leidos - 

    QA -

    Gov - 


    EVS SERVICE AND ARCHITECTURE GROUP UPDATES
    EVS Service and Architecture GroupDiscussion Points:

    Will meet next week  



    DATA UPDATES
    Data

    Discussion Points: 

    23-09.d - schedule to deploy to PROD on  

    Will do monthly terminology week starting  

    Then will work on META afterwards

    DECIDED: Data Deployment should continue as planned - no reason to delay.


    BROWSER UPDATES

    Browsernote outage discussion above

    QA UPDATES

    QA

    >We completed Regression Executions for the Monthly DDR for Sep '23 (23.09d) for EVS REST APIs on PRODUCTION .

    >We Executed Sanity Test Sets for LexEVS Data refresh on QA Tier .

    >We have executed Sanity Tests on NCIm,NCIt,TermForm for updated 23.09 Thesaurus deployment  on STAGE Tier and for LexEVS Data refresh on QA Tier.

    >We have completed Progression and Sanity Executions for EVS Report Exporter v1.2.0-RC3 Tag on PRODUCTION Tier (EVSREPEXP-487).

    thumbs up 

    23.09 Thesaurus deployment  on STAGE Tier and for LexEVS Data refresh on QA Tier.

    >We have completed Progression and Sanity Executions for EVS Report Exporter v1.2.0-RC3 Tag on PRODUCTION Tier (EVSREPEXP-487).

    Thanks to Itendra for the helpful updates!

    thumbs up 


    TERMINOLOGIES LIFECYCLE REPORT

    Terminology Updates and Schedule 


    Mark Benson TPM Update

    Everyone is humbly asked to complete NIH Anti-Harassment training as soon.

    • Unless your contracting company tells you otherwise - Please check and verify your status on theNIH HHS.gov Learning Portal to confirm completion.
    • Lyuba and others get lists of people that haven't yet completed - and we can make her life easier if everyone has completed!
    • Decided: You don't have to report your training status to Mark
    TERMINOLOGIES LIFECYCLE REPORT

    Terminology Updates and Schedule 

    Discussion Points: 

    Decision Points: 

    Mark Benson TPM Update
  • Complete Anti-Harassment training thumbs up 
  • Research Scraper attack on NCI Terms Browser

    LexEVS Technical Debt Progress

    ...