NIH | National Cancer Institute | NCI Wiki  

Versions Compared

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   x

Safran, Tracy

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

Kuntipuram, Kumar

NIH/NCI [C]

x

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
       
Craig/LarryFollow up with Jose (CTRP) in January 2016 to see if we can assist them and understand their requirements.2015.12.162016.01.31 Open

Progress

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

...

Sprint Status

Current Sprint - Sprint 19 ( December 10, 2015 – December 23, 2015 )

LexEVS 6.4 S13-500 Agile Development - Sprint StatusStatus#SprintStatus-Sprint19

Sprint Planning

Issue Prioritization

Recent LexEVS Related Bugs and Features (within last week)

Jira
serverNCI Tracker
columnskey,summary,type,created,reporter,priority,status,versions,fixversions
maximumIssues20
jqlQueryproject = LEXEVS AND (TYPE = bug or TYPE = "new feature" or TYPE ="Improvement" or TYPE ="Inquiry") AND created >= 2015-12-02 AND created <= 2015-12-16
serverId7954a81f-12da-3366-a0ef-97c806660e7c

 

Recent CTS2 Service Related Issues (within last week)

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

 


Issue Grooming

Prioritize JIRA issues (fix version 6.4)

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

 

Face-to-Face Recap

2015.12 Technical Face-To-Face Prioritization List

We clarified the priorities for each piece of work to be done.  There is now a column to indicate what work will be done during the 6.4 timeframe.

Next steps - We will create JIRA issues for each work item in the list.

CTRP will get back to the EVS group when they have firm requirements.  It was suggested that Craig/Larry will follow up with Jose in about a month to see if we can assist them and understand their requirements.

Tracy brought up the "Path to Root issue" - This is part of the existing transitive closure issue captured in the F2F notes. If this was developed in CTS2 it would be to retrieve descendants and ancestors.  We should also consider how this will work if there are multiple different paths to root.  For example, the thesaurus has many nodes that have 10+ paths to root.  Sherri will send an example of this to the development team.

Tracy mentioned that "Lung Carcinoma" has several different paths to root.

Examples from Sherri of concepts with many paths to root.

  • Colon Serrated Adenocarcinoma
  • Colorectal Neuroendocrine Tumor G2
  • Intracranial Cavernous Hemangioma
  • Localized Non-Resectable Adult Hepatocellular Carcinoma

Other general comments were that the 3 day duration was a good time frame and it was also good to meet with other teams (CTRP and Systems).

OBI issue

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-1386

Scott is trying to determine why the tree extension isn't working for certain cases.  If he cannot determine the error, he may need to work with the term browser team to see if the issue is there.

Jacob was able to open a port for debugging on the DEV system so Scott can do some debugging.

Holiday PlanningThe next two Wednesdays will be cancelled due to the holidays.
LexEVS External Users

Scott helped a user on the forum to get LexEVS installed.  The user was looking at how to get the shortest path between two nodes.

Larry suggested that we request any additional information from the user (what they are using LexEVS for, etc) if they are willing to send this.

...