NIH | National Cancer Institute | NCI Wiki  



Safran, Tracy

Wynne, Robert    NIH/NCI [C]x
Bauer, Scott  Mayox
Stancl, Craig
Endle,  CoryMayox



To understand current status of the value set loading script.


Discussion Points: 

  • Status of testing the original script for loading Value sets
    • Tracy mentioned that the load that was supposed to load all value set definitions crashed and never completed.
    • Scott mentioned that the script runs and creates over 1000 threads.  This may be part of the problem.
  • On Dev, OWL2 load failed for Tracy (mentioned above)
  • On Data QA, Tracy used the regular API to load one at a time.
  • Tracy/Rob mentioned that they never tried the load using OWL1.
  • Tracy kicked off the value set script during the meeting
    • This is running against OWL2 on DEV.
    • The value set definitions loaded.
    • The resolved VS crashes soon after it starts (some resolved VS were loaded)
  • Scott suggested that he would try the value set load and resolution scripts on DEV at NCI.
    • Tracy agreed that would be good.
    • Scott will remove all value set definitions and resolutions prior to starting the script.
    • He will then load value sets, then attempt to resolve them.
  • Value Set load issues
    • lexevs-2716 - This is a production issue.  Scott should look at this one soon.

Decision Points:

  • Scott  will run the value set load and resolution scripts on DEV at NCI.
OWL2 Discussion

Discussion Points:


  • We then discussed some OWL2 questions:
    • Scott confirmed with Tracy/Rob that there no complex properties (embedded html) in OWL2.
    • Scott asked, if we have a property that is null, should we:
      • log a warning and continue (entire entity will not load)?
      • log error and stop?
    • Rob suggested this should break the load.  This should log the error as well.  This is for the NCIT load.
  • OWL2/Protege Dates
    • New version of Protege at beginning of April for OWL2
    • April 24th would be first OWL2 PROD Load.

Decision Points:


Value Set Issues Identified during 2016.12 Technical Face-To-Face

2016.12 Technical Face-To-Face Prioritization List


  • No labels