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.
Comment: Reverted from v. 8

...

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 x
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
CoryAdd link to Maven Opts for end users2016.12.21  

Open

Agenda

Sprint Status

 

Current Sprint -  Sprint 50 (February 16, 2017 – March 1, 2017)

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

  • Report writer team may need to test with Java8

DEV Server Configurations

  • Planning and usage discussion

Discussion Points:

  • Dev
blade for CentOS 7 being created - will be used for java 8, MySQL 5.6 (6.4/5 release)
  • VM (
snapshot) blade server for
  • Mayo
(CentOS 6) pointing to MySQL 5.6
  • Mayo team requested remote API, URI resolver, CTS2 service containers on there as well.
  • ) is set up and we confirmed we can log in
  • Dev Blade - Jacob is waiting for the Mayo Dev team to let him know if tomcat 8 will work
The Browser team will want to test our Java 8 LexEVS release once we install on Mayo Dev

Discussion Points:

  • Scott's tests on MySQL 5.6 show that performance is as good (and better in some cases).
Decision Points:
  • .

Decision Points:

  • Validate that Tomcat 8 works with our Java 8 release.

LexEVS Java 1.8 & MySQL 5.6 Environment

  • MySQL update
  • Cory to confirm with Jacob what version of tomcat 8.x NCI is going to run.

6.4.1.3

Snapshot

FINAL build update

  • Creating 6.4.1.3.FINAL

Discussion Points:

Additional loader enhancements/fixes don't need to go into
  • 6.4.1
.x. They can wait until
.The NCI dev team can use the Java 8 release of LexEVS to
  • branch.

Decision Points:

Value Set Loading Enhancements

Status from Rob
  • Update

Discussion Points:

  • The additional fix from Scott will need to go into the 6.4.1.x release.

    • Rob/Tracy mentioned that testing with the Value Set load script from Scott, was done with OWL2 and never completed successfully
    • .

    Decision Points:

    CTS2 RESTful documentation

    LexEVS Version/Naming Discussion

     

    Discussion Points:

    • LexEVS Software Release Versioning
    • Larry suggested if the release has a major impact on the end user (consumers), then we would increment the major version number.
    • If the user created their own instance of LexEVS, then the versioning would affect them more than just being a consumer of the API. 

    Decision

    Discussion

    Points:

    • The
    Mayo dev team will look into the different query requests and see what options there are
  • Calls to return the results - are there limitations?
  • Filter down - use a programming language to parse JSON and make subsequent calls.
    • team will think about this and discuss again next week.
    CTS2 REST API Discussion

    Discussion Points:

    • End users are not familiar with the CTS2 model and REST API.
    • This doesn't fit well with end LexEVS users as they are not familiar with the CTS2 model.
    • It was suggested that it may make sense to have a REST API that represents the LexEVS Model.
    • Example scenarios:
      • For a given regime concept, give me the associated drugs. (the user knows the relationship)
      • This was available under caCore.
    • Users of CTS2:
      • Bob Kline (CTL), CTRP, Brian Bazilla
    • Tracy created multiple JIRA issues capturing the issues:
      • LEXEVSCTS2-138-144
        • Most of these issues were possible under caCore data services.
    • Larry suggested looking at the UMLS REST interface

    Decision Points:

    • Mayo Dev team will discuss and come up with some possible solutions and report back to the team.

    LexEVS Logical Role Relationship

    • Discussion with Kim

    Discussion Points:

    •  
      Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-2764
    • Kim is questioning the difference between inferred and asserted versions.
    • DEV vs PROD browser - inferred versions for neoplasm are different.

    Decision Points:

    • Kim to provide some screen shots/examples of this issue.

    Decision Points:

    • Cory will respond to the team with what is possible with CTS2 REST calls for the given examples.
    CTS2 RESTful API questions

    Discussion Points:

    Decision Points:

    The Mayo team will investigate tools to auto-generate CTS2 RESTful API
    LexEVS External Users

    Discussion Points:

    None
    • Nothing noted.

    Decision Points:

    Proposed Backlog Review Items

    Discussion Points:

    Decision Points:

    Team Absences

    Mayo Team

    • Cory -
    • Scott -
    • Craig - March 6-13

    NCI

    • Tracy
      • March 9-17
    • Rob

      • March 20-24

    JIRA Issues

    Recent LexEVS Related Bugs and Features (within last week)

    ...