NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Old Version 1

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

Saved on

compared with

New Version 2

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   
Fragoso, Gilberto NIH/NCI     

De Coronado, Sherri    

NIH/NCI    

Safran, Tracy

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

Kuntipuram, Kumar

NIH/NCI [C] 

...

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 VM (Mayo) 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.

Decision Points:

  • Cory to confirm with Jacob what version of tomcat 8.x NCI is going to run.
Creating
  • DEV Blade
    • 6.4.1.3
FINAL build update
    • .FINAL
  • Mayo DEV VM
        • 6.
      4.1.3.FINAL
        • 5.0 SNAPSHOT

    Discussion Points:

    Decision Points:

    Value Set Loading Enhancements

    • Load Update

    Discussion Points:

    Decision Points:

    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 Points:

    • The 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:

    Continued Value Set Discussion

    Discussion Points:

    Decision Points:

    AnyURI Designation

    Discussion Points:

    Decision Points:

    Thesaurus Query Role Types Discussion

    Discussion Points:

    Decision Points:

    LexEVS External Users

    Discussion Points:

    • 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

    ...