NIH | National Cancer Institute | NCI Wiki  

 Attendees

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

De Coronado, Sherri    

NIH/NCI    

Safran, Tracy

NIH/NCI   x
Ong, Kim L
ISx
Lucas, Jason R
ISx
Bauer, Scott  Mayox
Stancl, Craig
Mayox
Endle,  CoryMayox
Peterson, KevinMayox
Wynne, Robert    NIH/NCIx
Tran, Tin    NIH/NCI [C] x
Carlsen, Brian (NIH/NCI) [C]x
Wong, Joanne   

Kuntipuram, Kumar

 

x

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
293JasonCheck into Mayo being designated a trusted site2015.06.03  done

Progress

  
Scott
  • Sprint 15
  • On going Support
Cory
  • Sprint 15
  • On going Support
Craig
  • Sprint 15
  • Agile Admin

Agenda

Sprint Status

Current Sprint - Sprint 15 (October 15, 2015 - October 28, 2015)

LexEVS S13-500 Agile Development - Sprint Status#SprintStatus-Sprint15

Sprint Planning

Issue Prioritization

Recent LexEVS Related Bugs and Features (within last week)

Key Summary T Created Reporter P Status Affected Version/s Fix Version/s
Loading...
Refresh

 

Recent CTS2 Service Related Issues (within last week)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

 


Issue Grooming

Prioritize JIRA issues (fix version 6.4)

Key Summary T Created Reporter P Status Labels
Loading...
Refresh

 

 

Sprint Deliverables - Updates

  • 6.3.x
  • Lucene
Lucene build - Cleanup script is broke. 
Build practice is out of date, discuss single jar vs zip file

The build is currently broke.  The artifact built does not run due to the new lucene jars and their manifest files. 

The dev team will need to consider if we need to change the process to create a zip file, rather than a jar.

The dev team is suggesting breaking the build up into multiple jars.

This new multiple jar approach would break current users of the single jar.  Users would need to update their classpath.

TODO: Add two groups to work with on the NCI team to the Face to Face agenda.  How will this affect NCI users?

TODO: Mayo dev team to come up with a proposal on how to migrate to the new jar structure.

VPN and network evaluation

Craig is still waiting to hear back from the Mayo/NCI IT.

TODO: Craig will follow up with IT to get an update.

Horizontal Coding Scheme searchesTODO: Craig will add this to the Face to Face topics.
Face-Face Planning

December 8 - 10 on-site.

There is a wiki link for agenda topics: LexEVS 6.3 and 6.4 Technical Face-To-Face Meetings

TODO:  NCI team to add additional information to the topics for the Face to Face meetings.

Search queries - accessing the database opposed to the Lucene index only

  • Update
Scott noted that unless you set the resolve flag in the query, it does not go to the DB.

LEXEVS- 970

  • OWL2 Issue breakdown update

Scott was able to load the thesaurus locally without any errors.

TODO: Scott to work with Gilberto and review a load with restrictions.

Gilberto noted the following:

  • He is not seeing any relationships for biotin (code CHEBI_15956) on his load.
  • Role Relationships not displayed for code (OBI_0100061)
  • has associated axiom (fol) (IAO_00100000) (the declaration of the property) -
    • Do we have this data in LexEVS db? 
    • Once we have this in the DB, can the TERM browser render this properly?
  • information content entity - has curation status
  • entity - editor note: annotation on annotation name is not rendered
LexEVS Meeting next week (2015.10.28)

The Mayo team will be out next Wednesday.

The NCI will cancel the meeting.

The Mayo team will end the existing sprint and start the next one

Questions around how NCI uses sorting mechanisms

We are re-implementing how we are restricting coded nodes.

We are are seeing some differences in sorting when doing multi coding scheme index searches.

If you do a union query across multiple code systems.  Each code system has it's own index.  Scoring is done on a each index.  This is causing a junit ordering test to fail.

We will need to see how this works with real data.

MedDRA 18.1

If the CUI is left blank will it cause a problem?  We don't think so.

JIRA Issues

Recent LexEVS Related Bugs and Features (within last week)

Key Summary T Created Reporter P Status Affected Version/s Fix Version/s
Loading...
Refresh

Recent CTS2 Service Related Issues (within last week)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

6.4 LexEVS Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

6.4 CTS2 Service Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Project Plan Changes

#DescriptionDue DateResourcesNotesRisksMitigation
 None     
       
       

 Planned Activities

Area of InterestDetails
  
  
  

Risks, Issues, Dependencies

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

 

 

 

  • No labels