NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
      

Agenda

ASU Team

  • Overview and Discussion

Discussion Points:

Decision Points:

Sprint Status

 

Current Sprint  Sprint 58 (June 8, 2017 – June 21, 2017)


16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint58
LexEVS REST Services

Discussion Points:

Goals of REST API from CTRP and others

  • Much simpler format with just thesaurus content
    • Harmonized with the REST (JSON) output with the CTS2 service.   This will make it compatible with users of both CTS2 output (JSON) and this REST service.
    • Is there an easier REST API to put on the top of CTS2?
  • There are current users of CTS2 REST service, so we need to make sure any API changes will have a similar format.
  • EntityDescription vs RDF label - how do we harmonize the data.
  • CTS2 is generic.  The NCI team is suggesting going to a more specific (RDF OWL) model for a thesaurus API.
    • Current SPRARQL REST calls to StarDog returns JSON (OWL2 model).

Decision Points:

  • Tracy requested from the LexEVS team: mapping to/from lexgrid↔OWL.
  • Kim will share with the Mayo team the output/format he has from SPRARQL REST calls to StarDog. 
  • Mayo team will see if anyone in our group has triple store expertise that may be able to answer questions from NCI.
     Tier Deployment - Update
    • Tier Deployment
      • Data deployment
    • 6.5.0.1.FINAL LexEVS Admin testing

    Discussion Points:

    Decision Points:

    Docker - Next Steps Discussion

    Discussion Points:

    • lexevs-system-test Docker script is pulling Docker images from the internal NCI Nexus server. 
      • Working with systems team on configuring this withing Jenkins the server.
    • On Monday we discussed with the systems team what it would take create a lexevs deployable container as a prototype on a Dev server.
      • The systems team is a few months out on this work.
      • The Mayo team will start to design and develop Docker images with non-NCI specific software.

    Decision Points:

    Value Set Architecture

    • Update

    Discussion Points:

  • Working on miscellaneous issues on the value set workflow.
  • Moving toward replacing the hierarchy implementation.

  • We will need to understand the current hierarchy structure and how it is handled in the browser.

    Decision Points:

    LexEVS External Users

    Discussion Points:

    Decision Points:

    Craig to set up meeting with ASU and our NCI/LexEVS team.

    Team Absences

    Mayo Team

    • Cory - 6/19 - 6/23
    • Scott - 7/27 - 7/28, 7/31- 8/1
    • Craig -

    NCI

    • Tracy
    • Rob June 16,19
    • Kim
    • Larry - 6/23 - 6/29

    ...