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 Bauer, Scott (NIH/NCI) [C]

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 [C] x
Ong, Kim L
IS 
Lucas, Jason R
IS x
Bauer, Scott  Mayo x
Stancl, Craig
Mayo x
Endle,  CoryMayo x
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
Scott
CoryRequest DEV VM at NCI.2016.12.072016.12.21
 Open
2016.12.18Closed
JasonRequest Java 8 VM environment build.2016.12.072016.12.212016.12.14Closed
ScottCreate new issue for API for LEXEVS-25102016.12.072016.12.21 Open
Craig

Schedule backlog grooming meeting (Dec 21 at 1:00?)

2016.12.072016.12.21 Open
CraigClose all "on hold" JIRA issues as "resolved - not fixed"2016.12.072016.12.212016.12.20Closed
CoryAdd link to Maven Opts for end users2016.12.21  

Open

ScottCreate new JIRA issue to enhance OBI loader issue LEXEVS-25032016.12.21  

Done

Jira
serverNCI Tracker
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-2586

CorySet up a planning session for Value Set architecture2016.12.21  Open

Agenda

Sprint Status

 

Current Sprint -  Sprint 45 (December 8, 2016 – December 21, 2016)

16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint45

  • Mayo team worked 3 days on CTRP issue.  This may push some stories to the next sprint.

LexEVS Java 1.8 environment

  • Status update: Jason
CTRP Status

Discussion Points:

  • CTRP is able to go production after updates from the EVS team.
    • Jacob increased the max thread pool on tomcat for the CTS2 service.  This seems to have fixed the out of memory issue that CTRP was running into.
  • Mayo team will create stress tests and profile the server to see if there are areas for improvement. 
    • This will need to be prioritized.
  • Craig noted that we and  the external teams should be aware of what services are used.
    • For example, CTRP is using the data services.  These will be removed in LexEVS 6.5.0.

Decision Points:

  • Larry and team will need to prioritize the work to do stress tests and profiling.
    • This work should be done in the next couple of sprints as time permits.
    • If there are areas to fix, Larry/Craig suggested putting fixes into the 6.4.2 release.

LexEVS Java 1.8 environment

Discussion Points:

  • Jason created a ticket to request a Java 8 environment.

Decision Points:

  • Ticket was submitted for VM that contains CentOS 7 and Java 8 for testing
  • The current DEV system would be rebuilt in the meantime with CentOS 7 while we use the VM (above that was created)

Decision Points:

  • We need to do our MySQL 5.6 performance testing prior to upgrading DEV with CentOS 7

6.4.1.3 Snapshot build update

Discussion Points:

  • We will build a LexEVS 6.4.1.3 snapshot when lexevs-2510 is completed.
  • We will also put in a fix for lexevs-2461 and lexevs-2529.

Decision Points:

  • Cory will send out column widths to Rob/Tracy (lexevs-2529)
    • Release Notes
    • There is a Value set fix that is in this release.  We suggest not using the value set load for this snapshot.

    Decision Points:

    Cory to verify that lexevs-2463 is resolved -  value set issue pertaining to loading with PRODUCTION tag.

    NCI Nexus Server Migration Update

    Discussion Points:

    • No updatesPhil is assisting with the Nexus publishing issues with the CTS2 project now.

    Decision Points:

    OBI Load

    Discussion Points:

    • Cory will follow up with Sarah for an update.
    BioMarker Discussion

    Discussion Points:

    • Nothing for the LexEVS team yet.
    • Other discussions and requirements from other teams need to happen first.

    Decision Points:

    OBI Load

    Discussion Points:

    • lexevs-2503
    • Scott was able to reproduce the error based on a preference file from Tracy.

    Decision Points:

    Value set resolution algorithm

    Discussion Points:

    • Kim had a couple of questions
      • Leaf node and transitive closure - how does this work?
      • Value set with no entities - how do you create an XML file for this?

    Decision Points:

    • The value set documentation should be updated with the above answers by the Mayo team.

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

    Decision Points:

    • We will need to create a new JIRA item
      • The properties in the entity description should be prioritized/ranked
    • Gilberto will send the other issue to the OBI team.

    Value set resolution

     

    Discussion Points:

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

    • The top node with no other nodes is considered to be an empty value set
    • If the concept has a target it is not an empty value set.
    • We need to consider the direction of the association. We should not have a self referencing association

    Decision Points:

    Plan Value Set Architecture Session

    Discussion Points:

    • We have discussed using triple stores for managing value sets. 
    • We will need to determine the underlying architecture going forward (lexevs/triple stores)
    • Tracy suggested a micro service to access triple stores for value sets. 
      • This would be just a back end implementation.  LexEVs would still be the front end/API used.
      • The current triple store implementation doesn't provide the same search functionality as LexEVS does.

    Decision Points:

    • Craig to set up a planning session for Value Set architecture.
      • Attendees: Tracy, Rob, Jason, Kim, Cory, Craig, Scott, Kevin
      • Set up meeting after the holiday week. (Week of January 2nd)
    Initial JIRA issue grooming

    Discussion Points:

    Decision Points:

    • Include Jason in the next issue grooming meeting.
    LexEVS External UsersNo updates.LexEVS External Users 
    Team Absences

    Mayo Team

    • Cory - Dec 23, 26, Jan 2
    • Scott - Dec 23, 26, Jan 2
    • Craig - Dec 26 -30, Jan 2

    NCI

    • Tracy
      • Jan 9-17
      • Feb 21-24
    • Rob

      • 12/19

      • 12/23-12/27

      • 1/2/2017

    ...

    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 >=2016-12-07 14 AND created <= 2016-12-14 21
    serverId7954a81f-12da-3366-a0ef-97c806660e7c

    ...

    Jira
    serverNCI Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryproject = LEXEVSCTS2 AND (TYPE = bug or TYPE = "new feature" or TYPE ="Improvement" or TYPE ="Inquiry") AND created >=2016-12-07 14 AND created <= 2016-12-14 21
    serverId7954a81f-12da-3366-a0ef-97c806660e7c

    ...