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

 

Sana  

...

Sprint Status

 

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

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

DEV Blade - Update
  • Moving up the tiers
  • 6.5.0.1.RC.1 LexEVS Admin

Discussion Points:

Jacob is installing the FINAL versions on QA

  • We are building a new LexEVS Admin (loader) 6.5.0.1.RC.1 .Once built, this will be deployed has been loaded and verified on Dev to test.

Decision Points:

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
  • Cory will create LexEVS 6.5.0.1.FINAL build and will request Jacob to install on DEV and then DATA_QA.

Docker - Next Steps Discussion

Discussion Points:

Decision Points:

  • Cory will set up a meeting with the systems team  There is a meeting set for Monday 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 happensNCI Docker containers.

Decision Points:

Value Set Architecture

  • Update
  • Discuss Definitions
  • Publish Valueset = Yes
  • Hierarchy

Discussion Points:

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

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.

Decision Points:

  • Mayo team to determine if the coding scheme is available while a new entity is being added/registered.
  • There is continued discussion on how to determine value sets and hierarchies.
  • We will look at enhancing the value set API more for better performance.

Decision Points:

  • We agreed to use the term browser definition if it exists, otherwise we will use the entity definition.  This assumes that the information will stay in the scrubbed version of the OWL2 XML.
    • NCI agreed to this.
  • We need to keep the publish value set flag in the scrubbed version of the OWL2 XML..
    • NCI agreed to this.
  • Rob will send out the details on the hierarchy structure and what flags/properties will be there.
  • Kim will need to update to use the modified API in the term browser after Scott makes his changes. 
    • Jason agreed.

CTRP discussion

  • API Requirements
  • Opportunity to use transitive table and/or Graph closure exposed via REST-ful services

Discussion Points:

  • Craig requested that any meeting minutes from the meeting last week be shared with the team.
  • We need to understand the CTRP's project boundaries and requirements for the different teams.
  • There are no action items for the team at this time.

Decision Points:

LexEVS External Users

  • Raphael (Brazil)

Discussion Points:

  • Scott helped this user set up the Remote API. 

LexEVS External Users

Discussion Points:

  • None

Decision Points:

Team Absences

Mayo Team

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

NCI

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

JIRA Issues

Recent LexEVS Related Bugs and Features (within last week)

...