Page History

Sprint Status

Current Sprint -  Sprint 35 (July 21, 2016 – August 3, 2016)

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

QA Tier Status

• NCI-RITM0031271: New container on QA for the LexEVS 6.4 Remote API
• NCI-RITM0031282: CTS2 AHP on QA
• AppScan

OWL2 Discussion

• LEXEVS-1299 - Supported properties (Kim/Gilberto)
• LEXEVS-1976 - Complex property loader directives
• LEXEVS-1160 - NDFRT Loader - Restrictions on a class not displayed in the browser.

LEXEVS-1299 - do Scott asked if these properties belong in the system as supported properties?

• Scott suggested there is a way to eliminate the duplicates.
• TODO: Scott will create a JIRA item for the work above.

LEXEVS-1976 - Scott suggested the preferences could be updated for this.

• Scott is suggesting keeping the hard coded items and they can be modified via the preference file. This specific parsing has to be "turned on" via the preferences file.
• Gilberto mentioned in OWL2, these values do not exist. They will be pre-floating properties.
• The decision is to leave it in the OWL2 loader. The default is off. It will only be on/available when specifically called in the preferences file.

LEXEVS-1160 - Scott suggested that the browser should add logic to determine what to display.

• Tracy and Gilberto agreed with this.
  

OWL2 Loader build

• Specific 6.4 build with loader fixes.
• Can NCI verify the fixes in this build?

LexEVS using HTTPs - December 31st, 2016 deadline

• Discuss possibility of updating 6.3 or 6.4 for HTTPs for existing customers

There is a an NCI department level requirement that all services need to use HTTPs. If they don't, the current services will be shutdown at the end of December.

We don't want to force end users to migrate to 6.5, if that had the HTTPs fix in it by the end of the year.

Larry suggested that we need to upgrade the existing LexEVS 6.3 and/or 6.4 to use HTTPs prior to the end of the year.

If LexEVS 6.3 was updated and the end user clients have to rebuild their clients, then we should just consider upgrading the clients to the LexEVS 6.4/6.5

The Mayo team will start to investigate and discuss with the NCI systems team.

LexEVS versions - Previous/Deprecated/Retired

• Previous Deprecated LexEVS Installation Packages and Examples

LexEVS 6.3 should be moved to deprecated.

Remove the "Previous" section.

TODO: Cory will make these changes.

• Review column length options

Based on the investigation from Cory, the field is a VARCHAR (250). We can increase the length to accommodate a longer description.

Larry suggested increasing the length to 1000.

Tracy agreed with this.

TODO: Cory will send out an email to confirm everyone agrees with the suggestion from Larry.

LexEVS External Users

• HL7 Loader - content from Meta

  • https://github.com/lexevs/lexevs/issues/42

We think this may be a source issue - loading from RRF.

Brian will look into this issue.

Mayo Team

• Scott - August 1st
  
• Craig - August 24th - 29th