Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Current Sprint - Sprint 22 ( January 21, 2016 – February 03, 2016 )

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

• Sprint

Issue Grooming

Prioritize JIRA issues (fix version 6.4)

• 22 is complete.
• Sprint 23 is being planned.
• Mayo to release the Sprint 22 artifacts and deploy to Dev to enable browser testing.

CTRP Planning

• Update from Larry

• Larry sent a note to request an update from the CTRP team (Jose).
  • Unlikely that CTRP will be able to deliver requirements that will impact the 6.4 release.
  • We should plan to include CTRP in 6.5 planning

No updates from Sherri. 

Gilberto was at CTRP's demo on Monday for their requirements.  He mentioned that there were no LexEVS requirements at this time.

Sherri was wondering if there are any requirements for LexEVS.  Larry commented that there were no requirements for us at this time.

• • .

Value Set Resolution

• Review updates from Rob

• This can be closed. The issue was associated to Max value to resolve and recompilation. (via properties files)
• Changes are on stage and will be promoting to Prod

The properties file for the browser was missing the cache and max value properties.  This properties file needs to be propagated from from DATA_QA to PROD to fix this issues.

• .

6.4 Performance testing

Ability to get and load all of the value sets

Tracy put the NCI value sets out on the SFTP site for Scott. 

Scott will load these value sets on our DEV system.

Scott will be using Java JMH performance harness for performance testing of reading all of these value sets.

This will show the difference between the multi index performance and the single index performance.

Search Extension Testing Requirements

This what is used for text searching. 

We will want to focus our testing on the text searching performance.

Jason mentioned they will test the 6.4 artifacts with the browser scripts.

Production Remote Service not accessible

• Tracy

Scott is waiting to get the PROD logs to investigate further.

Tracy will send the logs to Scott.

• Scott to provide update

• Scott has been working on automation of loading value sets.
• Search extension will be tested over the resolved value sets and over the NCI Meta.
• NCI Team to provide test cases to consider when querying value sets.
• Querying is expected to behave the same way as previous release.

Nexxus Testing

• Delayed and rescheduled for Feb 17

• Toky is going to determine the final date based on Scott's availability.

6.4 Install on Dev

• Update from Cory

• Sprint 22 artifacts to be deployed to Dev this week by Cory

6.4 Artifacts

We have sprint 21 artifacts available for 6.4. 

This release has the search extension features working.

• .

6.3.0.2 RC Testing

with Term Browser

• Finding updates from Jason/Kim

• Kim was to have tested to verify the namespace issue. This has not been done yet.
• Data Dev has this installed and Kim can test.

• Testing has been completed with MySQL
• Larry suggested that we should only test on those that we know are being used (Oracle and MySQL)
• Earlier versions have been tested on the other DBs, but 6.4 should be limited.

VPN Testing

• Updates from Scott and Cory
• Update from Tracy

• Scott and Cory have been testing several times a day on both s2s and software VPN and recording performance status.
• Tracy is not seeing a delay from the office or from home. So any latency would be because of the connection.
• Rob was running eclipse with some initial UI slowness, but things then started performing fine.
• Detailed report to be given on Friday.

• Nothing to note

• TODO: Start deployment tasks at same time as documentation
• TODO: Considerations for 60 day deployment. Schedule a deployment meeting. (include in next weeks meeting)

Namespace Navigation between coding schemes

• Review how this works

Gilberto wanted to review way this namespace navigation works between coding schemes.

The way it is implemented, we can go across coding schemes.  Scott mentioned that there are limitations based on the namespaces.

If there are two coding schemes with the same namespace, this is not supported.

If there are multiple versions of the coding scheme, it will go to the PRODUCTION version.

Scott suggested that Gilberto should come up with a scenario and then we can create a manifest to show how it can be supported.