Page History

...

Attendees: Kim, Cory, Scott, Craig, Jason, Larry, Tin, Rob, Tracy

Discussion: Coding Scheme Search and Indexing

...

• OWL2 Loader

  • Jira
    server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-586

    
    
    • Used to support inferencing.   GO and OBI may have this already.
    • Examples include - hasUncle, hasFather, etc.
    • Gilberto to provide examples and we can discuss during future meeting.   
    • http://www.w3.org/TR/owl2-new-features/#F8:_Property_Chain_Inclusion

  • Jira
    server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-1160

    
    
    • This is related to OWL2 and should be considered part of OWL2 changes.
• MedDRA Loader
  • LEXEVS-339 (MedDRA loading into LexEVS)
    • This can be closed since we have a MedDRA loader.  

  • Jira
    server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-1169

    
    
    • This does not impact the load.
  • Need to create JIRA for "Semantic Type" missing
  • Need to provide comparison of MedDRA loads to understand what is missing.  May decide to not pursue based on what is identified.  
• HL7 Loader

  • Jira
    server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-584

    • This has nothing of value and can be closed.
  • 
    

    Jira
    server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-1037

    • Scott noted that coding schemes should be loaded as separate coding schemes.    Historically, we've loaded as a single coding scheme.  There are varying views on how it should be loaded.  There are approximately ~200 coding schemes and most have few concepts in them.  
    • Namespaces need to be fixed - Scott asserted that there is no supported coding scheme (additional metadata)
  • Gilberto described that on HL7 webpage, you can view the coding scheme and the branch/structure.  It is desired to provide that structure.   
    • We should look at what HL7 provides and determine what needs to be done.
• Process Automation
  • Tracy described the sequential loading of content (GO, ChEBI, etc).
    • This manual loading happens monthly.
    • There are 5 manual steps.   
    • Propose a way to provide the loader a version and as a result it would build a manifest object.
• Additional JIRA items

  • Jira
    server NCI Tracker jqlQuery project = LEXEVS AND status in (Open, "In Progress", Reopened, "On Hold") AND (description ~loader OR summary ~loader) serverId 7954a81f-12da-3366-a0ef-97c806660e7c

    • This list needs to be reviewed by the group to determine if there are additional loader considerations.   If there are JIRA items that are no longer needed, they should be closed.
  • Scott brought up the issue around a failed load and table locking.   
    • This issue is related to 5.5.  
    • LexEVS should be aware so it can fix the problem.   
    • One option would be to update 5.6 or MariaDB.
    • JIRA item needs to be included.  

  • Jira
    server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-234

    
    
    • This should be considered in project backlog.

  • Jira
    server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-347

    
    
    • Tracy noted this would be difficult as the indicator varies based on the source.
    • Scott suggested an evaluation would need to be completed to understand the methods used to indicate deprecated concepts.  
    • It was suggested to focus on specific coding schemes - instead of a general approach.  Priority should be for OWL2.
    • This should be considered in project backlog.

  • Jira
    server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-459

    
    
    • Tracy - currently there is a script to load all the value sets (load value set definition).  
      • Propose that the VS could be added to a directory and point the script at the directory to load the value sets.
      • This will be further discussed during the Value Set Editor discussion.

  • Jira
    server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-535

    
    
    • This issue can be removed.
    • CLAML loader is no longer used.  All JIRA items around CLAML can be closed.

  • Jira
    server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-464

    
    
    • This is part of the older OWL loader.
    • This may have been resolved in OWL2.
    • The OWL to loader is no longer the focus.
    • No decisions made.  
• It was noted that we should do a complete review of the JIRA backlog (ON HOLD) issues.    Most issues associated to OBO may be closed after review. 

Attendees: EVS Group

• Reviewed 2015.12 Technical Face-To-Face Prioritization List with the group.
  
  

Attendees: Tracy, Rob, Tin, Cory, Craig

• Scott presented the loader tutorial.

{scrollbar:icons=false}

...