LexEVS Meeting Minutes - 2014.10.01

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Scott to work with Gilberto to determine what is needed for OWL 2 requirements

on hold

on hold

on hold

on hold

open

Scott: DEV Deployment, SNOMED load, Kim's Issue

• Deployment week - successful deployment on QA and Stage. Overall, this was successful because of access to all the teams involved.  Identified issue with URI resolver - currently being fixed.  
• New focus on Kim's issue - hope to get it resolved soon.
• Bring SNOMED to focus once URI resolver is complete.  

Cory: Project Closure, 6.2 Documentation

• 6.2 Documentation
• 6.2 Project closure documentation
• 6.2 Final process tasks
• CTS2 Service had issues in entity query.  This is fixed and can go up tiers.  Once loaded, Tracy to reindex.  Cory will let her know.
• AMIA Poster

Craig: Project Plan Updates, Contract updates, Project Closure

• 6.2 Documentation
• 6.2 Project closure documentation
• 6.2 Final process tasks
• Finalized MOD 4 contract.

Nothing new.

We can drop this off our list.  

Will create a new project plan for Mod 4.

We will consider a 6.3 deployment in the Dec 2014 timeframe.

We will consider a 7.0 deployment (new features)

LexEVS 6.2 QA Issues (redeployed as 6.2) - will be redeployed (prefer at same time)
 

LEXEVSCTS2-26 - Entity query matchvalue parameter is being ignored
URIRESOLV-3 - Update implementation to a PreparedStatement based query
 

LexEVS 6.3 Issues (Dec 2014 release)
 

LEXEVS-641 - OWL2 loader uses VersionIRI, but doesn't have a wide enough column
LEXEVS-614 - OWL2 associations and annotations on associations.
LEXEVS-583 - OWL2 data: restrictions on a class using datatype properties
LEXEVS-595 - Need a Method to Identify OWL Resources in an Unstructured environment
LEXEVS-586 - OWL2 chained properties
LEXEVS-598 - TreeService getTree method can fail when the root node code appears in multiple namespaces.
LEXEVS-667 - TreeService getTree method fails on remote call when the root node code appears in multiple namespaces.
LEXEVSCTS2-21 - Value Set resolution fails when a value set name is more than a particular number of characters.

And Lucene Updates that do not require a model change. 

Consider additional value set related items.  (team to identify/create JIRA items)

LexEVS 7.0

Lucene Changes that require a model change.
TBD

Additional Tasks
AMIA Poster
NCI Planning Day

General feeling is that the week went well.  Teams were able to focus on tasks when needed.  Ability to move things up tiers without QA complete was helpful and allowed things to move much faster.   It was good to have Scott on site instead of trying to fix issues remotely.  Will consider this process for future large deployments (possibly 7.0).

Not displaying a hierarchy.  Appears that the treetops RELS are not being loaded. 

5.1 -> 6.0 -> 6.1 changes may have effected treetops.   

First, load the content using the 5.1 loader to verify the load is correct.  Then we can determine what is missing and what is expected in the 6.1 loader.  

Joanne and Brian will load again using the 5.1 loader.  Then provide what is expected and other details for Scott to look at the problem. 

Priority and timetable to be evaluated once triaged.