NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

  • Created by Unknown User (endlecm), last modified on Jul 18, 2018

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Attendees

NameRolePresent
Remennik, LyubovNIH/NCIx

De Coronado, Sherri    

NIH/NCI   x

Safran, Tracy

NIH/NCI [C]x
Ong, Kim L
ISx
Lucas, Jason R
ISx
Bauer, Scott  Mayox
Stancl, Craig
Mayox
Endle,  CoryMayox
Wynne, Robert    NIH/NCI [C]x

Kuntipuram, Kumar

NIH/NCI [C]x
Kisler, BronNIH/NCI [C]x

Agenda

Use Case - MedDRA (LexEVS-3661)

Discussion Points:

  • Import MedDRA into LexEVS and export coding scheme as RDF files and load into StarDog.
  • The LexEVS exporter currently exports to OWL  (not OWL2)
  • Sherri mentioned that Mark Musen has a RRF -> RDF converter that NCI could potentially use

Decision Points:

  • Action Item: NCI agreed to put this issue on hold and see if the direct converter will work for them.
JIRA Issue: LexEVS-3905 - Inconsistent value set URIs are returned by different API methods.

Discussion Points:

Decision Points:

  • Action Item: NCI agreed that this issue should be fixed.
JIRA Issue: LexEVS-3464 - Loader: Sources for Properties are not loaded for Meta Thesaurus

Discussion Points:

Decision Points:

  • Action Item: Scott will finish up and review with NCI team and authors.
JIRA Issue: LexEVS-3616 - Loader: Truncated role qualifiers in Ontology for Biobanking

Discussion Points:

  • LEXEVS-3613 - Getting issue details... STATUS
  • A DB column would need to be increased. 
  • All DBs would need to be reloaded (could be from a dump)
  • This Biobanking load is only loaded on DEV currently, so the upper tiers would not need to be reloaded.
  • The DB definition/model in LexEVS will need to be updated.  
  • This change could be put in a patch.

Decision Points:

  • Action Item: NCI agreed this should be worked on.
Remote API

Discussion Points:

  • Editors, Kim and caDSR are currently using the remote API.  
  • There are serialization issues when changes are made.  This is complicated maintenance.
  • Long term is to sunset the remote api.  
  • Long term - Remote api would need to be replaced by some REST services.

Decision Points:

Browser Requirements

Discussion Points:

  • Browser review will be tomorrow with Kim.

Decision Points:

  • Action Item: Review all of the browsers and determine requirement
Requirements to support Data Commons

Discussion Points:

  • Use Case: Mapping to coding schemes not loaded
  • Use Case: Go from gene to proteins

Decision Points:

Microservices discussion

Discussion Points:

Decision Points:

  • Action Item: Lyuba suggested having a separate meeting to understand micro services and how this might fit in with LexEVS
Face to Face Meeting from last year (2017)

Discussion Points:

Decision Points:

  • Action Item: Bron suggested Mayo team reviewing the minutes and see if there are any important issues that should be followed up on.
  • Action Item: Bron to re-start the API group architecture
  • No labels