Page History

...

Discussion: Build and Deployment Process and Discussion: Value Set Editor (Authoring)

Attendees:  Cory, Craig, Scott, Jason, Kim, Larry, Gilberto, Rob

• Dev Ops Discussions carried over from earlier this morning.
  
  • Continuous Integration
    • Cory discussed the Continuous Integration Server usage and how it is used by the Mayo development team.
    • There was discussion about how to include CI server functionality to provide value to both the browser team and LexEVS team.  
    • Currently Jenkins is unofficially supported at NCI, but they are supporting what is needed by the project teams.  
    • Mayo does have Travis and Jenkins, but suggests the use of Jenkins.  
    • Jason - there is interest and some value, but limited given few (one) developers.  It was suggested that it would be best to discuss with the Dev Ops group before setting up something else.  
• Value Set Editor
  • Requirements 
    • Ability to maintain collections and sub-collections of value sets
      • https://nciterms.nci.nih.gov/ncitbrowser/ajax?action=create_src_vs_tree&nav_type=valuesets#

...

• • • • Ability to efficiently load the resolved value sets
  • Tracy - Value Set authoring doesn't occur often.  The value set resolution happens every time there is a new version of NCIT.  
  • FDA and CDISC value sets are based on NCIT concepts.
    • Report writer templates are used for individual value sets.
  • Further review of value set workflow (including resolution) is needed to determine requirements and proposed changes.  

Discussion: The Future of lbGUI

Attendees:  Cory, Craig, Scott, Jason, Kim, Larry, Gilberto, Rob

• Current usage of lbGUI:
  • Mayo team uses the GUI to verify loads. (Development)
  • Tracy uses when the admin scripts aren't working.  (Admin)
  • Rob uses to cleanup  (Admin)
  • Gilberto uses to determine if data is loaded correctly. (Data)
• Scott noted that the representation of data in lbGUI isn't always correct.  It is better to look at DB to determine how things are loaded.   
• Technology needs to be updated
  • Usage is becoming unstable 
  • There are several know bugs.  
• The focus should be on expanding the admin scripts and move away from lbGUI.
• Further review of admin workflow is needed to determine requirements and proposed admin script changes and additions.
  
• lbGUI will continue to be minimally supported as needed by the development team.
• Consider ability to provide viewing additional metadata in the GUI.

{scrollbar:icons=false}

...