NIH | National Cancer Institute | NCI Wiki  

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.

...

Sprint Status

 

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

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

DEV Server Configurations

  • DEV Blade
    • 6.4.1.3.FINAL
    Mayo DEV VM
    • 6.5.0 SNAPSHOT

Discussion Points:

  • LexEVS 6.4.1.3.FINAL is loaded on Mayo DEV VM
  • LexEVS 6.5.0 SNAPSHOT will be loaded on DEV Blade with CentOS 7.
    • Jacob has a ticket for this work.
    • We will want a separate DB (MySQL 5.6) for the Blade and the VM Dev instances.

    Decision Points:

    Mayo team will request separate DBs for the Blade and the VM Dev instances.

  • Send note to Jacob.

    • Value Set Loading Enhancements

    • Load Update

    Discussion Points:

  • Scott and team have identified the current issues with the value set failures.
  • Tracy has not had an opportunity to test the mass load script yet.
    • Mayo team will meet with Jason and Kim to discuss value sets architecture tomorrow.

    LexEVS Meeting Minutes - Value Set Architecture Planning Session - 2017.03.02

    Decision Points:

    CTS2 REST API Discussion

    Discussion Points:

    • The Mayo team will look at the new CTS2 JIRA issues created by Tracy.
    • We will determine if our current implementation can accommodate the request.
    • If it can't, can we implement it in CTS2.
    • If that can't be done, we can look at implementing it in a different service.
    • Larry suggested that there should be a simpler REST interface than CTS2.
      • Larry mentioned that they (customers) are coming up with some criteria and examples of what they would like. 
      • They will have some examples/criteria in the next couple of weeks.
      • This may be something like convenience methods or CTS2 extensions.

    Decision Points:

    • The dev team will hold off looking at the existing JIRA issues and see if CTS2 can accommodate this in the next sprint.
    • The dev team will work on the tree extensions instead in this sprint.

    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
    • We will leave this issue open until Kim can verify.

    Decision Points:

    AnyURI Designation

    Discussion Points:

  • There is an example in the OBI OWL2 source.
  • The AnyURI is declared as data type in the annotation property.
    • This doesn't fit into LexEVS model (an association on an association).  The LexEVS API wouldn't handle this well either.

    Decision Points:

    • Scott mentioned that our load will ignore this case
    • Scott will sent a snippet source example to Gilberto.
    Thesaurus OWL2 Source
    Docker - Next Steps Discussion

    Discussion Points:

    • Our loads are now making a lot of calls into the ontology class.
    • This is increasing our Thesaurus OWL2 loads from 1hr to 3-6hrs.

    Decision Points:

    Scott will create a JIRA issue to investigate the new load performance issue.

    Resolving all relationships for a given association

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

    Remote API timeout issue

    • Discussion with Kim

    Discussion Points:

    •  Intermittent socket timeouts from the Remote API.
    • Scott is able to reproduce this issue locallyWhat is the use case for resolving all relationships for a given association.  Also is there a requirement for Enumerations (this is an obsolete interface that does not implement serializable.)  There is a workaround that can retrieve these relationships, but we should discuss implementing a more efficient API call.

    Decision Points:

    Scott will investigate why our system tests are not hitting the same issue.

    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

    ...