Page History

Current Sprint - Sprint 6 (June 3, 2015 - June 24, 2015)

Lucene Version

• Scott to provide update on 4.10 vs 5.1

Scott will continue work on implementing the block join prototype with Lucene 5.1 and fix the current errors that are occurring. 

This prototype works in Lucene 4.10.

Sprint 7 Planning

Upcoming Sprint - Sprint 7 (June 2524, 2015 - July 8, 2015)

LexEVS S13-500 Agile Development - Sprint Status

Issue Grooming

• Prioritize JIRA issues

Sprint 7 will start Thursday (2015.06.25) to allow for NCI to assist with issue grooming.

Additional items to work on in Sprint 7:

• Add time for Scott to get block join prototype working with Lucene 5.1.
• LEXEVS-970  
  • Exit criteria - fully backwards compatible.  OWL1 is a subset of OWL2.  Any OWL1 load issues should be fixed in the OWL2 loader.
  • If NCI thesaurus is loaded with OWL2 - we may need to create new jUnits for the OWL2 load.
  • TODO: Gilberto suggested a separate meeting to review junits and how OWL1 loads are different than OWL2 loads.
    • TODO: Craig to create JIRA tasks for this investigation/planning work.
• LEXEVS-946 - This fix would be part of LEXEVS-970.
• LEXEVS-942  - Will start the implementation in Sprint 7 for this issue.

6.3 Deployment Status

• Update from Jason
• FINAL tag

lexevs 6.3 will go to PROD tomorrow. This will run against lexevs CTS2 6.2.

NCI will move lexevs CTS2 6.3 up the tiers.

Deprecate LexEVS 5.1 in July - caDSR may still be relying on LexEVS 5.1.  LexEVS 5.1 will go off line in September.

6.4 Development Environment

• Versioning concerns
• Scheduling updates

LexEVS 6.4 DEV environment will have indexes not compatible with previous versions of LexEVS.  We suggested LexEVS 6.4 will have its own separate containers.

NCI will repurpose old containers on DEV for LexEVS 6.4.

Discuss new search issues

• 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

Rob discovered that any term with an apostrophe doesn't return any results. 

In the GUI, the "contains" doesn't return any results either.

TODO: Mayo to validate if this works in CTS2 Service.

TODO: Mayo will research to determine what matching algorithm will give you back results with an apostrophe.

VPN and network evaluation

• Update from Gilberto and Jason

External Request

• epSOS update from Larry

Mayo to demo LexEVS to see if it fits their needs.