NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

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

...

EVS Weekly Tech Meeting

Discussion Points:

  • LexEVS
    • LexEVS has been fully promoted to PROD.
    • This is live and Mayo will run through some tests.
  • Browser/Tools
  • Data
    • A number of new codes systems on data qa including CHEBI, NCIt.
    • Url is pointing at the new dataqa which isn't working
    • No new mappings except for a file promotion. 
  • Systems
  • Triple Store/EVS API
    • Counting triples to verify updates

Decision Points:

Sprint Status

 

Current Sprint  Sprint 62 (August 3, 2017 – August 16, 2017)


16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint62
Tier Deployment - Update
  • Tier Deployment
    • Data deployment

Discussion Points:

 6.5 all containers are ready except for the new REST API.  LexEVS deployment is complete.   Will  

Decision Points:

Mayo will do some CTS2 testing, check on the remote java api. 

Decision Points:


Supported Source and Representational Forms - Load Issues on Data Qa

Discussion Points: 

  • Jira
    serverNCI Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyLEXEVS-3222
  • We'll discuss further and along the lines of making this configurable in the preferences.
  • 6.5.0.2  Does load representational forms

Decision Points:

Development Snapshots availability

Discussion Points: 

  • The next LexEVS development snapshot will be installed on the NCI LexEVS dev server.

Decision Points:

LexEVS External Users

Discussion Points: 

Decision Points:

Change to the NCIt namespace

Discussion Points: 

Namespace in CTS2 was used instead of coding scheme when there was a call to the formal namespace.  The result was a namespace not equal to the NCI Thesarus causing failures. 

Decision Points:

The effort going forward will be to avoid as much as possible any new configuration requirements. 

WCAT compliance dates

Discussion Points: 

WCAT compliant requirements must be in place before Jan 18. 

We should schedule a review of all pages before then. 

All current 508 compliant pages are grandfathered in.  Releases after that would have to be WCAT compliant

Decision Points:

We should schedule a review of all pages before the due date

Team Absences

Mayo Team

  • Cory -  8/18, 8/29
  • Scott -  8/18
  • Craig -  8/10 - 8/22

NCI

  • Tracy - 9/5 -9/6
  • Rob -
  • Kim -
  • Larry -

...