Page History

Sprint Status

Current Sprint -  Sprint 33 (June 23, 2016 – July 6, 2016)

• Cory built and delivered artifacts for RC.1
• Scott is working on OWL2 Loader issues
• Cory is working on HL7 Loader issues

Dev - RC.1

• Status of Deployment and Verification

This deployment will be done through the PTE and Anthill Pro process.

TODO: Mayo team needs to set up an ARC meeting for LexEVS 6.4.

• There are questions about the new lucene indexes and running LexEVS 6.3 in parallel and with LexEVS 6.4. We will also need separate URLs for LexEVS 6.3 and LexEVS 6.4.
• The Mayo team will need to verify/update the LexEVS 6.4 ARC document.
• The Mayo team will then ask Sarah Elkins on the process to request an ARC meeting.

NCI team will run user acceptance tests (from Tin) against the lexevs LexEVS API. They donNCI doesn't need any additional resources from the Mayo team at this time.

After LexEVS is deployed, Tin will update the URLs from his test suite to hit the DEV deployment and test his scripts.

NCI will test LexEVS 6.3 and LexEVS 6.4 side by side to make sure they both work together.

Planning for QA deployment and beyond

OWL2 Loaders - planned time with Gilberto

We have time set up for the next several Fridays (Gilberto, Rob, Tracy, Scott, Deepak, and Cory) to review OWL2 loader changes.

There are several other cardinality use cases that are not in scope for this issue. They will need to be discussed before they can be addressed.

These issues will be discussed at the meeting set up during the next several Fridays.

We will also need to discuss how OWL fits into LexEVS in the future.

HL7 Loader issue - create issue for the flipped internal code and entity code.

• Jira
  server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-2016

LexEVS External Users

• Updates - Javadocs issue - upper and lower case mismatch on linux

  • Jira
    server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-2015

The javadocs is are working as designed.

When the javadocs are created, the filename convention is to be lowercase. Any camel case filenames will therefore break.

One possible solution is to create a specialized doclet to create camel case file names/paths.

A couple other possible work arounds may be to do the following:

• Place a note that this doesn't work on linuxLinux. This note would be placed where we post the javadocs.
• Host them on the wiki

This The return type is a Boolean type, which can return a null.

If the property name is the preferred name, Rob thought it would use that property.

Tracy suggested that the Thesaurus should have a preferred name.

Rob will create a JIRA issue for this.

• Kim created this TreeServer issue:

  • Jira
    server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-1999

Mayo Team

• Craig - June 30th, July 1st, July 4th
• Cory - July 4th
• Scott - July 4th
• Deepak - July 4th