Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Current Sprint - Sprint 11 (August 20, 2015 - September 2, 2015)

LexEVS 6.4 S13-500 Agile Development - Sprint StatusStatus#SprintStatus-Sprint11

LexEVS 6.4 Agile Development - Sprint StatusSprint 11 Planning

• No issued identified by NCI to include in the upcoming sprint.
• Mayo team will assign implementation tasks to the sprint.

Issue Prioritization

Recent LexEVS Related Bugs and Features (within last week)

Recent CTS2 Service Related Issues (within last week)

Issue Grooming

Prioritize JIRA issues (fix version 6.4)

UNICODE Annex #29 Load for C1855

• Scott to discuss

May need to determine an algorithm/analyzer to handle the removal of special chars (punctuation).

Standard analyzer is performing better than expected.

Whitespace junit tests are functioning fine with the Lucene testing framework.

String Analyzer - slight differences - removes capitalization, special chars (ie. exclamation points)

It was suggested that both cases (include/remove special chars) be supported.

Implementation is fine as it now stands. Need to consider an extension for single char searches.

Metadata Index handling

• Scott to discuss

Scott verified what was working and not working.

Successfully implemented removal of metatdata - to be used in the GUI.

Tracy would like to have command line removal - not high priority.

Tracy would like metadata removed when coding scheme is removed. This should be version specific.

Single special character search

• LEXEVS-1131
• Discussion with Kim

Attempting to search on single characters: <, >, and ! 

Will we need to support these kind of queries?  It would be additional work for the DEV team.  Lucene doesn't advise this.

This should be working with the new Lucene work. We will need to test.

These special properties could have their own analyzers for searching.

Chemical name searches

• Updated from Scott

There may be a small set of users that would want to be able to search on chemical names / single characters.

We can provide analyzers for these and store them.

This could be part of an advanced search.  We would match up the query with specific analyzers.

We should consider the potential of SQL injections for this implementation.

HTTPS - Applications Migrating to HTTPS

• LexEVS CTS2 REST Services - via Apache
• LexEVS API Services

The REST service should be fine.  We will just need to redirect in the Apache configuration.

LexEVS service would need to be updated for HTTPS.

TODO:  Create JIRA items and put them in the backlog for after 6.4.

OBI load evaluation

• Update from Gilberto

Tracy suggested just the LexEVS client and it's dependencies be hosted out on Maven.

Other projects at NCI are purely maven projects and would like this as an artifact.

TODO: Mayo to look at making the LexEVS client a Maven artifact.

Do we have the ability to sort the JSON Nodes that are returned.

TODO: Mayo to investigate if we can sort the results.  This should be part of 6.4

Namespace loading issue investigation

• LEXEVS-1033

Latest representation of OBI needs to be reviewed by Gilberto. More time needed to evaluate.

NPO issue was not replicated.

HL7 issue - referred to the notes about the loader. There are no namespaces (JIRA should be created specifically for this issue).

RIM vs MIF loader discussion - not sure when MIF can be used to start loading HL7. Currently, Tracy indicated they are still using the RIM loader. There was never a full evaluation of the MIF loader by Gilberto to determine if can be used in production. NCI to evaluate and decide if MIF can be used.

VPN and network evaluation

• Update from Gilberto and Jason

External Requests

• ?

• Lekha Venugopal (CTEP)

By end of 2016, all applications will need to be using HTTPS.

Mayo team to create JIRA items for backlog. May need to spend some time evaluating as part of 6.4 development.