Page History

Current Sprint - Sprint 13 (September 17, 2015 - September 30, 2015)

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

Issue Prioritization

Recent LexEVS Related Bugs and Features (within last week)

LEXEVS-1194 -Should we (LexEVS) define a default entity type if the source hasn't asserted a specific type?  

Kim is suggesting a convention that LexEVS default the entity type.

A default entity type could be specified in a loader preference file.

TODO - update the JIRA issue with the above comments.

LEXEVS-1192 - Need to look at putting on the schedule to fix in upcoming sprint.

Recent CTS2 Service Related Issues (within last week)

Issue Grooming

Prioritize JIRA issues (fix version 6.4)

Search Algorithm Discussion

• Scoring and ordering results
• Start to document

There are some pre and post operations that after the analyzers are set.  This affects the query results.

We will need to document this and review it with NCI for approval.

There is concern about breaking backwards compatibility with these searches bringing back different search results.

In 6.3 all searches (including literal searches) were case in-sensitive

We should continue to have all searches be case in-sensitive. (exception: code fields are case sensitive)

Algorithm Documentation:

LexEVS 6.4 Search Algorithm Implementation Details

OBI Issue Discussion

CTS2 was not bringing in the sources (qualifiers - complex property).   This will need to be further investigated. 

This can be done in two REST calls.  It would be nice if this could be done in one call.

VPN and network evaluation

• Update from Craig

External Requests

• CTEP

Service URL.  Scott attempted this with 6.0 client code built locally.  This ran for him.

TODO: Scott will attempt to call CTEP to further assist.

November was originally discussed as a time for the face-face even though Lucene is pushed out until around May.

Items to potentially discuss at the face-face:

• Java 8

• update
• Expand the CTS2 REST interface to potentially include associations
• Loader issues with OWL2, MeDRA and HL7

• GUI updates

• RDF Triple Store

• or graph database LexEVS backing
• End-user Value Set editor

Tracy suggested to include a discussion on loaders - how they currently work as well as some useful changes. 

Also, she suggested that there may be some useful changes that could be made to the GUI.

Larry suggested that the value set model that currently

Tracy suggested Loader (current and suggested changes) and GUI.

They do not have an end-user value set editor.  This may be of interest.

Larry suggested value set model that exists doesn't provide all of the functionality they need and that we should discuss our options.

TODO: Mayo to provide a list of topics based on the above and start to circulate.