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

Kuntipuram, Kumar

NIH/NCI [C] x
Haber, MargaretNIH/NCI

x

Sana  

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
      

...

Sprint Status

 

Current Sprint  Sprint 57 (May 25, 2017 – June 7, 2017)

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

DEV Blade - Update to 6.5.0 RC 5
  • CTS2  Build/Testing
  • Moving up the tiers

Discussion Points:

  • Jacob is installing the FINAL versions on QA
  • We are building a new LexEVS Admin (loader)
  • The latest CTS2 Service is on Dev as a release candidate version.
  • 6.5.0.FINAL LexEVS Remote API is on Dev, ready .1.RC.1.
    • Once built, this will be deployed on Dev to test.

Decision Points:

  • Kim to test the remote API on DEV when the data is loaded.
  • Tracy will test the CTS2 service on DEV
  • Cory will request Jacob to install the FINAL version of the LexEVS admin and CTS2 on DEV

    NCIt load

    • Extraneous spaces issue/review

    Discussion Points:

    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-3042
    • Scott reviewed his code fix and noted that the human readable rendering still has extra white space.
      • This is an issue for the browser and how it parses the OWL2.
       

    Decision Points:

    • Scott will add an additional fix to remove extra white space.

    Docker - Next Steps Discussion

    Discussion Points:

    Decision Points:

    • Next sprint, Cory will update the lexevs test scripts to pull the stored versions of software from NCI Nexus server.
    • The next step would be to look at making deployable containers in Docker.

    Decision Points:

    • set up a meeting with the systems team to discuss creating Docker containers that are deployable on the NCI Dev tier.
    lexgrid.org Migration

    Discussion Points:

    • We will plan on migrating lexgrid.org to a new DNS Thursday and Friday.
    • This may affect builds/loads while the migration happensScott is investigating and testing what the exact changes need to be for updating the DNS.

    Decision Points:

    Value Set Architecture

    • Update

    Discussion Points:

    • Scott is currently working on this.  There is a plan to have a meeting next week to review the current work.
    •  We had a meeting earlier this week with the NCI team.
    • Scott reviewed his prototype
    • A couple of issues were identified:
      • Definitions expressed in the xml file don't line up with the published source in the OWL.
      • Hierarchies - (TVS in the un-scrubbed version) doesn't line up in the code to define the hierarchy.
    • We need to come up with a plan before we continue.

    Decision Points:

    •  Scott will follow up with the NCI team to understand where to get all of the definition and hierarchy.
    Decision Points:

    CTRP discussion

    • Possible nightly data builds

    Discussion Points:

    • We will be meeting with a whole new group of CTRP developers this afternoon.
    • The Mayo team found that there are several authoring junit tests that are not being run with our overall tests.
      • We ran them locally and found that most of the tests were successful.
    • CTRP would like to create new terms and have them available right away. 
    • We will need to start capturing requirements from CTRP and then determine where this fits in for priority discussed that CTRP may need nightly data builds.

    Decision Points:

    • Scott will provide links to CTS2 documentation on how to make changes to the dataMayo team to determine if the coding scheme is available while a new entity is being added/registered.

    LexEVS External Users

    Discussion Points:

    • The LexEVS team is planning on working with the ASU team to set up repositories in the next sprint.None

    Decision Points:

    Team Absences

    Mayo Team

    • Cory -  June, 5,6
    • Scott -
    • Craig -

    NCI

    • Tracy
    • Rob June 16,19
    • Kim

    ...