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

Support for matching designation search functionality is now in place.

Much of the ground work for other searches is being done at this time as well.

Sprint Planning

• Sprint 12 (September 3, 2015 - September 16, 2015)
• JIRA issues to include

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)

LEXEVS-1143 Load though GUI to be moved into sprint 12.

Single special character search

• LEXEVS-1131

Issue LEXEVS-1131

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.

- was searching on single character items.

Mayo will create a junit for the above case.

We need to determine how some of these search strings are searched on and what the results are.

We need to test how single character alphanumeric searches (case in-sensitive) will work on the file sent from Larry.

The DEV team will set up a set of unit/integration tests.  We will share the results with NCI.

Scott proposed a change to the loads (qualify as chemical name, term type, etc) to handle these special character searches.

We should check to see if there is a pre-built analyzer available for chemical names too.

If we can't find a pre-built analyzer, we could build our own analyzer based on our rules for chemicals.

Take a look at NCIT terms to see how they are structured.

OBI load evaluation

• Update from Gilberto

Gilberto did review this earlier this week.  Tracy will contact Scott on some of the issues they were seeing.

The structure of the vocabulary was in question.

Preferences were used in the manifest file.  Tracy will review these preferences.

NCI was asking what preferences were being used?

Tracy will send the notes to the DEV team.

TODO: Investigate why loading of named instances (individuals) don't appear in the browser.  The GUI isn't displaying them.

TODO: Investigate why restrictions on a class are not being seen either.

Reviewed NDFRT.  Gilberto said it had the same restrictions.

TODO: Investigate NDFRT and why it had the same restrictions.

Metadata Load Issue

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

We could push a loader fix out as part of 6.3 (independent build).

lbGUI and lbValueSet - would like to load multiple value sets in the same window.

We will investigate to see how much work this will be.

TODO: Also investigate a scripting option for loading multiple value sets

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 JasonCraig

External Requests

• Lekha Venugopal (CTEP)

•  https://github.com/lexevs/lexevs/issues/22  (skeusgen)

This user is attempting to dynamically resolve a value set definition via CTS2.  This isn't working as expected.

TODO: Create a JIRA issue to investigate and determine if CTS2 is working correctly or not and how to fix, if needed.