Page History

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 Status

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)

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.

VPN and network evaluation

• Update from Gilberto and Jason

External Requests

• Lekha Venugopal (CTEP)