NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 1

changes.mady.by.user Unknown User (endlecm)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (endlecm)

Saved on

Key

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

...

NameRolePresent
Wright, Larry NIH/NCI   x
Fragoso, Gilberto NIH/NCI     x

De Coronado, Sherri    

NIH/NCI    

Safran, Tracy

NIH/NCI    x
Ong, Kim L
IS x
Lucas, Jason R
IS x
Bauer, Scott  Mayo x
Stancl, Craig
Mayo x
Endle,  CoryMayo x
Wynne, Robert    NIH/NCI x
Tran, Tin    NIH/NCI [C]  x
Carlsen, Brian (NIH/NCI) [C] 
Wong, Joanne   

Kuntipuram, Kumar

  x

Action Items

Scott
 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
64ScottTo follow up on URI's on OWL2 with Harold.   on hold
164CoryCory to add implementation to CTS2 implementations page.2014.04.30  on hold
197ScottDo a gap analysis on what the URI_Resolver logs and what NCI would like to know from these logs2014.6.18  on hold
200Larry/SherryQuery current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's2014.6.18  on hold
207CoryWrite issue against CTS2 OMG regarding the ability to return INACTIVE concepts only.2014.07.30  on hold
210Larry/GilbertoDetermine if there is a need to meet with the CTRP2014.07.30  on hold
212LarryInclude LexGrid XML Export as part of the 5.1 retirement notice. 2014.07.30  

on hold

224ScottURI Resolver - Provide overview of how to access the URI Resolver2014.09.03  

on hold

225ScottURI Resolver - Look at TLAMP and VSAC service to determine usage of URI Resolver2014.09.03  on hold
244CraigPlan meeting with Tracy to discuss collaborative LexEVS development process2014.12.03  on hold
281Try to replicate what CTRP did to break our service (retrieve a tree through CTS2).2015.03.25  on hold
282Mayo TeamLook into implementing graph node in CTS2 for the path to root method (and path to leaf).2015.03.25  on hold
293JasonCheck into Mayo being designated a trusted site2015.06.03  open

...

  
Scott
  • Sprint 6
Cory
  • Sprint 6
  • On going Support
Craig
  • Sprint 6
  • Agile Admin
  • Sprint 7 Planning

Agenda

Sprint Status

Current Sprint - Sprint 6 (June 3, 2015 - June 24, 2015)

LexEVS 6.4 S13-500 Agile Development - Sprint Status#SprintStatus-Sprint6

Lucene Version

  • Scott to provide update on 4.10 vs 5.1

Scott will continue work on implementing the block join prototype with Lucene 5.1 and fix the current errors that are occurring. 

This prototype works in Lucene 4.10.

Sprint Planning

Sprint 7 Planning

Upcoming Sprint - Sprint 7 (June 24, 2015 - July 8, 2015)

LexEVS S13-500 Agile Development - Sprint Status

Sprint Planning

Issue Grooming

  • Prioritize JIRA issues

Jira
serverNCI Tracker
columnskey,summary,type,created,reporter,priority,status,labels
maximumIssues20
jqlQueryproject = LEXEVS and fixVersion=6.4 AND issuetype = Bug AND status = Open
serverId7954a81f-12da-3366-a0ef-97c806660e7c

6.3 Deployment Status

  • Update from Larry

 

Sprint 7 will start Thursday (2015.06.25) to allow for NCI to assist with issue grooming.

Additional items to work on in Sprint 7:

  • Add time for Scott to get block join prototype working with Lucene 5.1.
  • LEXEVS-970  
    • Exit criteria - fully backwards compatible.  OWL1 is a subset of OWL2.  Any OWL1 load issues should be fixed in the OWL2 loader.
    • If NCI thesaurus is loaded with OWL2 - we may need to create new jUnits for the OWL2 load.
    • TODO: Gilberto suggested a separate meeting to review junits and how OWL1 loads are different than OWL2 loads.
      • TODO: Craig to create JIRA tasks for this investigation/planning work.
  • LEXEVS-946 - This fix would be part of LEXEVS-970.
  • LEXEVS-942  - Will start the implementation in Sprint 7 for this issue
Deployed on Stage.  Waiting for CTS2 service to be deployed before LexEVS 6.3 goes to PROD
  • .

6.3 CTS2 Deployment Status

  • Update from Jason
  • FINAL tag

lexevs Jason created ticket to deploy 6.3 CTS2 service to DEV

Todo: send note to Jason on what can be tested for 6.2 CTS2 Service against 6.3 LexEVS service on QA and STAGE.

will go to PROD tomorrow. This will run against lexevs CTS2 6.2.

NCI will move lexevs CTS2 6.3 up the tiers.

Deprecate LexEVS 5.1 in July - caDSR may still be relying on LexEVS 5.1.  LexEVS 5.1 will go off line in September.

6.4 Development Environment

  • Versioning concerns
  • Scheduling updates

LexEVS 6.4 DEV environment will have indexes not compatible with previous versions of LexEVS.  We suggested LexEVS 6.4 will have its own separate containers.

NCI will repurpose old containers on DEV for LexEVS 6.4.

Discuss new search issues

  • Jira
    serverNCI Tracker
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyNCITERM-679
  • Jira
    serverNCI Tracker
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyNCIM-204

Rob discovered that any term with an apostrophe doesn't return any results. 

In the GUI, the "contains" doesn't return any results either.

TODO: Mayo to validate if this works in CTS2 Service.

TODO: Mayo will research to determine what matching algorithm will give you back results with an apostrophe

CTS2 Documentation Service Deployment

  • Update from Cory
We will wait until 6.3 CTS2 service is deployed and then use the 6.3 CTS2 URL in the documentation service

.

VPN and network evaluation

  • Traceroute update from Cory
Cory did traceroute on NCI VPN and without VPN to test performance of network.  This information was passed on to
  • Update from Gilberto and Jason
No updates.

External Request

  • epSOS update from Larry

Mayo to demo LexEVS to see if it fits their needs.

 

epSOS team indicated times that would work for them to meet.  Mayo and NCI will now work on times that will work with us.

Request from consulting company that has a client that wants to look at a terminology service for SNOMED.  They want a reply within a week.  Larry will reply that LexEVS is free/open source and minimally answer the questionare.

JIRA Issues

Recent LexEVS Related Bugs and Features (within last week)

...

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = LEXEVSCTS2 AND created >= 2015-06-10 17 AND created <= 2015-06-17 24
serverId7954a81f-12da-3366-a0ef-97c806660e7c

...

Risks

# Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation Strategy
         
         

Issues

 #Opened DateDescriptionImpactAssignedStatus
      
      
      

Dependencies

Opened DateDescriptionAssigned
   
   

 

Action Item Backlog

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
64ScottTo follow up on URI's on OWL2 with Harold.   on hold
164CoryCory to add implementation to CTS2 implementations page.2014.04.30  on hold
197ScottDo a gap analysis on what the URI_Resolver logs and what NCI would like to know from these logs2014.6.18  on hold
200Larry/SherryQuery current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's2014.6.18  on hold
207CoryWrite issue against CTS2 OMG regarding the ability to return INACTIVE concepts only.2014.07.30  on hold
210Larry/GilbertoDetermine if there is a need to meet with the CTRP2014.07.30  on hold
212LarryInclude LexGrid XML Export as part of the 5.1 retirement notice. 2014.07.30  

on hold

224ScottURI Resolver - Provide overview of how to access the URI Resolver2014.09.03  

on hold

225ScottURI Resolver - Look at TLAMP and VSAC service to determine usage of URI Resolver2014.09.03  on hold
244CraigPlan meeting with Tracy to discuss collaborative LexEVS development process2014.12.03  on hold
281ScottTry to replicate what CTRP did to break our service (retrieve a tree through CTS2).2015.03.25  on hold
282Mayo TeamLook into implementing graph node in CTS2 for the path to root method (and path to leaf).2015.03.25  on hold