Page History

Current Sprint - Sprint 7 8 (June 24July 9, 2015 - July 822, 2015)

LexEVS 6.4 Agile Development - Sprint Status

https://wiki.nci.nih.gov/display/LexEVS/LexEVS+6.4+Agile+Development+-+Sprint+Status#LexEVS6.4AgileDevelopment-SprintStatus-Sprint8

Sprint 8 Planning

Upcoming Sprint - Sprint 8 (July 9, 2015 - July 22, 2015)

Issue Grooming

• Prioritize JIRA issues

LEXEVS-946 -  Associated with this issue, any vocab with multiple name spaces isn't working.

If we were to fix OWL2 to work for any OWL1 load, this would potentially time consuming with all the loads and verification.

Multi-Index Prototype Status

• Results (Scott)

Local XSD Resolution

• Resolution and Priority (Scott)

NCI's concern is that we may have to implement the solution twice with the original plan.

Hierarchy's for these vocabularies hasn't been displayed for a long time.

6.3 Deployment Status

• NCI Maven Mirror Update

We built this service and gave to NCI the war file.  They have deployed to the DEV service.

Cory will verify the service is working as expected.

• (Cory)

OBI Load

• Update and next steps (Scott)

CTS2 Doc Service - NodeJS/NPM versions

• Heroku service life
• Upgrade to latest IO docs

There is an security issue with the current version of node.js and npm that is being used.  When time permits, we will upgrade to the latest versions. 

This will also force us to upgrade IOdocs and the cts2 service configuration file.

We will continue to keep the heroku site running in the meantime.

Discuss new search issues - Status (Cory)

• Jira
  server NCI Tracker serverId 7954a81f-12da-3366-a0ef-97c806660e7c key NCITERM-679

• Jira
  server NCI Tracker serverId 7954a81f-12da-3366-a0ef-97c806660e7c key NCIM-204

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

literalContains is the match algorithm that would need to be used if searching for special characters.

There may be performance hits when using this algorithm.

We could consider using literalContains in the browser only when special characters are entered.

Kim will evaluate the performance of using the literalContains algorithm in the browser.

Scott has implemented and checked in a fix for this issue.

Brian can show us what the load looks like in the SNOMED tool in a future meeting.

We will need to determine what parts to use in the browser now..

Model changes may be needed for some further MRMAP changes.

• NCI Tech Stack (Gilberto)
  
  

VPN and network evaluation

• Update from Gilberto and Jason

External Request

• ?

U of Michigan asked for a list of LexEVS users.