NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

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

...


SYSTEMS
Systems

Discussion Points:  Data deployment at 430 might be delayed due to technical issues.

Decision Points:  Thanks for quick response to downtime yesterday


LEXEVS UPDATES

LexEVS Sprint Status


Current Sprint - Sprint 183 (March 24, 2021 – April 3, 2022)

16X237 Agile Development - Sprint Status#16X237AgileDevelopmentSprintStatus-Sprint183
  • Activities
    • Updates to Spring for LexEVS - working through the DAO and Performance TasksDAO Query Implementation prioritized
    • Working on CTS2 Framework/LexEVS CTS2 Service
    • Batch Testing Recode in ProgressSome external training hours required
LexEVS Spring Updates

Discussion Points:

  • CTS2 - complicated by OSGI so working to untangle that knot
  • Performance/Batch Loading
    • Option - may be able to rely on current loaders and update only the service. Needs testing
    • Need feedback from systems whether this is acceptable, since loaders are not exposed to the outside
    • Need to test loaders by priority - per Lyubov. OWL > LgXML > OBO > RRF > 
  • Ongoing Triage planning
  • Risks to schedule around reduced hours/training/unanticipated recode for batch implementation
  • – no longer a priority
  • Full Query Test and Fix in Progress

Decision Points:  

Meta Tree investigation

Discussion Points:

  • Nothing new to report

Decision Points:

CTS2 Mapping/URI Resolver

Discussion Points:

  • On Hold

Decision Points:

Statistics Dashboard

Discussion Points: 

  • Approved a refresh/Sumo is working on replay of April.  Requested back to January.
  • Waiting for Data Refresh

  • Data Replay finally complete
  • Need to keep contact with Manish to make sure those aren't lost again

Decision Points:

Comparison/Mapping Tool

Discussion Points

  • On Hold

Decision Points:

EVS transition to virtual machines

Discussion Points:

  • Server Migration 2021
  • Stage server online but not configured
  • QA needs to be double checked for URL validity

Decision Points:

Team Absences

Mayo Team

  • Scott - July 26th - August 2nd
  • Tracy - September 20th through October 1st.

Leidos

  • Mark June 27 - July 1


Vulnerability testing



EVS SERVICE AND ARCHITECTURE GROUP UPDATES

EVS Service and Architecture Group

Discussion Points: 

Need to start discussion of retirement of NCITerms/LexEVS structure

  • Likely August timeframe to start this discussion
  • Decision Points:


    DATA UPDATES
    Data

    Discussion Points: Released this morning, Wed 29, rather than Monday the 27th. 

    Decision Points:


    BROWSER UPDATES

    Browser

    Discussion Points:   Derived Logical algorithm that he will distributeLooks like they were running a netsparker on prod and it brought browser down yesterday evening. Chuck brought it up more quickly.

    Decision Points: 


    QA UPDATES

    QA

    Discussion Points: Completed 1.6 into feature set. Working on EvsExplore 1.7.

    Decision Points:  No release candidates lately



    TERMINOLOGIES LIFECYCLE REPORT

    Terminology Updates and Schedule 

    Discussion Points: 

    Decision Points: 

    ...

    05e 0531060306May202205/31/202206/07/2206/06/22

    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.06d

     06/

    29/2022

    yes07/05/2207/06/22
    NCIt-HGNCNCIt-HGNC05/31/2022yes06/03/2206/06/22




    SwissProtSwissProtMay2022yes06/03/2206/06/22




    ChEBIChEBI




    GOGOJun20226/6/2022yes06/08/22




    HGNCHGNCJun20226/6/2022yes06/07/2206/08/22




    MED-RTMED-RTJun20226/6/2022yes




    QA Schedule and Status

    see QA Scheduling and Status

    ...