NIH | National Cancer Institute | NCI Wiki  

WIKI MAINTENANCE NOTICE

Please be advised that NCI Wiki will be undergoing maintenance on Thursday, May 23rd between 1200 ET and 1300 ET.
Wiki will remain available, but users may experience screen refreshes or HTTP 502 errors during the maintenance period. If you encounter these errors, wait 1-2 minutes, then refresh your page.

If you have any questions or concerns, please contact the CBIIT Atlassian Management Team.

Versions Compared

Old Version 3

changes.mady.by.user Safran, Tracy (NIH/NCI) [C]

Saved on

compared with

New Version Current

changes.mady.by.user Safran, Tracy (NIH/NCI) [C]

Saved on

Key

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

...


SYSTEMS
Systems

Discussion Points:

  • Status of migration on new QA tier.
    • Archive old server
  • Stage migration status
    • Not yet started
  • Systems new vendors
    • changes impacting EVS?
    • 2 Prod tickets pending for over a week for LexEVS
      • CTS2 deployed succesfully
      • Report Exporter not complete - is AWS so a different team?
  • Semantics URL to be applied to Stage tier - handed to other team, Chuck to chase downStardog license shift to new serverCuong

Decision Points:


LEXEVS UPDATES

LexEVS Sprint Status


Current Sprint - Sprint 203 (Jan 30 - Feb 13 2023)

16X237 Agile Development - Sprint Status#16X237AgileDevelopmentSprintStatus-Sprint203
  • LexEVS CTS2 Service - on Stage, Prod requested
  • Report Exporter - on Stage, Prod requested
  • Vue3 Updates for Report Exporter nearing completion
  • Working on updating browser for Spring 5 - on dev
  • Started working on update of vulnerable dependencies
  • Metrics and other reports due next week
Future Planning

Discussion Points:

 Planning for Mayo team in the coming fiscal year:

  • Java 8
    • implications
  • migration to 11
    • EOL Sep '23
    • Waiting for info on migration deadlines
    • Implications for Tomcat containers
    • JREs available on servers
  • EVS Compare
Technical Debt remediation

LexEVS Code Debt Refactoring

  • Do code inventory for Java migration
    • Work begun on implementation
    • Do code inventory for Java migration
    LoE work to be done - Mark to report
    • Need risk assessment of the work - what is the risk of NOT doing things
  • Vulnerable dependencies
  • Java 8 migration to 11
    • EOL Sep '23
    • Waiting for info on migration deadlines
    • Implications for Tomcat containers
    • JREs available on servers
  • Vulnerability remediation and general updates
  • Other dependencies

CTS2 Mapping/CTS2 Mapping/URI Resolver

Discussion Points:

  • On Stage.  QA verifiedTicket put in for ProdProd, verified

Decision Points:

caDSR Query

Have been asking for other standalone terminologies, expected that they will use CTS2

Statistics Dashboard

Discussion Points: 

Yearly report re-sentNeed 28 day report

  • Google analytics - Retiring GA and going to GA4
    • May need to only update GA, not applications. 
      • Need further experimentation, documentation
      • Per Kim - looks like scripts need to be updated from GA3 to GA4
    • No analytics being collected by EVS Explore
    • Add to Report Exporter and EVS Compare
      • EVS Exporter working
      • Create token for EVS Compare - though it is not ready to gather yet
    • TS to do paragraph on how to migrate

Decision Points:

Comparison/Mapping Tool

Discussion Points:

  • March timeframe
    • Specs document to be put together in March
    • Look at technical debt updates 
    • Java 11

Decision Points:

EVS transition to virtual machines

Discussion Points:

  • Server Migration 2021
    • QA2
      • We are waiting for approval to start using QA2 in earnest, will need to coordinate with team.
      QA
      • URLs repointed
    • Stage 
      • Instance of VM instantiated. Needs configuration. 
      • Blocker: Waiting to hear from Systems on what is needed to progress, if they have configuration information.
      • Followed by Prod then DataQA

Decision Points:

Report Exporter

Discussion Points:

  • Tomcat and Spring Vulnerability noted on the Report Exporter
    • Deployed on Stage
    • Request put in for Prod - ticket in, will follow up: NCI-RITM0415989 (Mark following up)
  • Working on update to Vue3 (JavaScript Framework). EVSREPEXP-451
    • ~ 2 month - Due: Mar 10 (end of sprint 305); on week 7 12 of estimated 16
    • master ticket: EVSREPEXP-442 - Migrate Vue.js version from 2.0 to 3.0
    • Description 8 -
      • On Dev and being regression tested
      • 3 different phases
        • Dependencies updated - complete
        • Squashing errors generated from update - complete
        • Unit testingtesting 
          • bug squashing from this - in progress
          • 8 or 9 issues left
          • Code detection issue requiring details page restructure
  • Look at updating to Java 11 - code inventory work
    • Code inventory complete. Ticket: EVSREPEXP-463

Decision Decision Points:

AWS Cloud to be in Separate Account

Discussion Points

  • No Response as of yet

Decision Points:

Team Absences


Mayo Team - Tracy off 16, 17

MSC -

Leidos - Mark off Feb 14-24

Systems - 


EVS SERVICE AND ARCHITECTURE GROUP UPDATES
EVS Service and Architecture Group

Discussion Points:

  • Remote API and URI Resolver retirement
    • Looking at 3 months - April timeframe 
    • Need an announcement sent out ahead of time - Draft sent

Decision Points:


DATA UPDATES
Data

Discussion Points: 

Flat file modified for PT and syn order

  • 23.01e started, being processedreleased - some issues, under review
  • monthly data next week

Decision Points:


BROWSER UPDATES

Browser

Discussion Points:

  • Nothing new for this group

Decision Points: 

  • Spring 5 browser version on Dev
    • properties extension requires update - in progress
    • Expected 2 weeks for app completion
    • Designing ideas for testing in absence of remote API
  • Expect requests from Oberon
  • SPARQL-EVS interface to be discussed off-line

Decision Points: 


QA UPDATES

QA

Discussion Points:  (see chart)

Decision Points: 

  • Regression on RestAPI done for 23.01e
  • Testing done on lastest RestAPI release
  • tag 1.7 EVS Rest and Explore being tested



TERMINOLOGIES LIFECYCLE TERMINOLOGIES LIFECYCLE REPORT

Terminology Updates and Schedule 

Discussion Points: 

Decision Points: : 

Mark Benson TPM UpdateMark Benson TPM Update

Priorities are :

  • lexevs vulnerabilities
  • lexevs java 11
  • lexevs-service vulnerabilites
  • lexevs-service java 11
  • lexevs-service-rest-docs vulnerabilities
    • lexevs-service-rest-docs java 11
    Checklist: LexEVS Code Inventory - Refactoring Checklist.xlsx (Sharepoint)


    LexEVS Spring Migration Progress



    Technical Debt Related Update

    Estimated Effort

    Status

    Ticket

    Code Inventory4 daysComplete
    Lexevs - update "easy" jars2 daysComplete
    Update ddlutils - research and design3 days
    In Progress
    Complete
    Update ddltils - implementations10 daysIn Progress
    Lexevs Unit testing2 days

    CTS2 lexevs-service vulnerability update2 days

    CTS2 unit testing2 days

    QA Lexevs / CTS2

    3 days



    Repair QA issues2 days

    Deployment Lexevs / CTS25 days (elapsed)

    Update LexEVS to Java 11 - research and design4 days

    LexEVS Java 11 implementation5 days

    lucene 9 - research and design8 days

    lucene 9 - implementation15 days

    LexEVS Java 11 unit testing3 days

    CTS2 lexevs-service Java 11 - research and design 3 days

    CTS2 lexevs-service Java 11 implementation3 days

    CTS2 unit testing2 days

    QA Lexevs / CTS2

    3 days



    Repair QA issues2 days

    Update Jenkins1 day

    Deployment Lexevs / CTS210 days (elapsed)

    lexevs-service-rest-docs vulnerability update design2 days

    lexevs-service-rest-docs vulnerability implementation4 days

    lexevs-service-rest-docs unit testing1 day

    lexevs-service-rest-docs QA

    1 day



    lexevs-service-rest-docs deployment4 days (elapsed)

    lexevs-service-rest-docs Java 11 design

    2 days



    lexevs-service-rest-docs Java 11 implementation3 days

    lexevs-service-rest-docs unit testing1 day

    lexevs-service-rest-docs QA

    1 day



    lexevs-system-test design4 days

    lexevs-system-test implementation6 days

    lexevs remaining dependency updates - design10 days

    lexevs remaining dependency updates - implementation20 days

    CTS2 remaining dependency updates - design1 day

    CTS2 remaining dependency updates - implementation3 days

    Unit testing2 days

    QA2 days

    Deployment5 days (elapsed)

    Total Effort (Approximately)104 days

    Technical Debt Related Update

    Estimated Effort

    Status

    Report Exporter vulnerabilities - design4 days
    Report Exporter vulnerabilities - implementation5 days
    Unit testing2 days
    QA2 days
    Deployment5 days (elapsed)

    ...

    01/23/23

    Vocabulary Name

    Local Name

    Version

    Arrival Date

    Loaded to data-qa DB

    Date to Stage

    Date to Production

    Vocabulary Name in LexBIG

    Short Name

    Version identifier

    Date the vocabulary arrived for processing

    		Has the vocabulary been loaded to the data-qa database?

    Approximate date the vocabulary version is scheduled to move to staging

    Approximate date the vocabulary version is scheduled to move to production

    NCI ThesaurusNCIt22.12d12/27/2022yes01/11/2301/17/23
    NCIt-HGNCNCIt-HGNCDec202212/27/2022yes01/11/2301/17/23
    SwissProtSwissProtDec202212/27/2022yes01/11/2301/17/23
    ChEBIChEBIv21701/12/23yes01/19/2301/23/23
    GOGOJan202301/12/23yes01/19/2301/23/23

    to production

    NCI ThesaurusNCIt23.01e01/31/2023yes02/09/232/10/23
    NCIt-ChEBINCIt-ChEBIJan202301/31/2023yes02/09/232/10/23
    NCIt-HGNCNCIt-HGNCJan202301/31/2023yes02/09/232/10/23
    SwissProtSwissProtJan202301/31/2023yes02/09/232/10/23
    ChEBIChEBI




    GOGO




    HGNCHGNCHGNCHGNCJan202301/12/23yes01/19/23




    QA Schedule and Status

    see QA Scheduling and Status

    ...