![]() |
Page History
...
Name | Role | Present |
---|---|---|
Wright, Larry | NIH/NCI | x |
Fragoso, Gilberto | NIH/NCI | x |
De Coronado, Sherri | NIH/NCI | x |
Safran, Tracy | NIH/NCI | x |
Ong, Kim L | IS | x |
Lucas, Jason R | IS | x |
Bauer, Scott | Mayo | x |
Stancl, Craig | Mayo | |
Endle, Cory | Mayo | x |
Wynne, Robert | NIH/NCI | x |
Tran, Tin | NIH/NCI [C] | x |
Carlsen, Brian | (NIH/NCI) [C] | |
Wong, Joanne | ||
Kuntipuram, Kumar |
...
Sprint Status | Current Sprint - Sprint 10 (August 06, 2015 - August 19, 2015) 6.4S13-500 Agile Development - Sprint StatusDiscussed the analyzers - for the most part, we are using off the shelf analyzers from Lucene. Larry suggested testing chemical (ID) C1855 to query and see if the analyzer works correctly. Without additional analyzers, we do not have internationalization searches. Mayo team is also working on concurrency with our LexEVS indexes. | ||||||||||||||||||||||||||||||||||||
Sprint Planning | LexEVS 6.4 Agile Development - Sprint Status Issue Prioritization Recent LexEVS Related Bugs and Features (within last week)
Recent CTS2 Service Related Issues (within last week)
LEXEVS-1110 - Will be implemented in our Lucene work LEXEVS-1108, 1111 - lower priority Issue Grooming Prioritize JIRA issues (fix version 6.4)
| ||||||||||||||||||||||||||||||||||||
Namespace loading issue investigation | NPO - Attempted to recreate the error, but could not. OBI - Scott loaded this on DEV (tomcat j) for NCI. We are waiting for feedback from NCI on the load and the hierarchy. HL7 - Scott loaded with our loader (not the legacy loader that NCI uses). Found namespace issues. | ||||||||||||||||||||||||||||||||||||
6.3 Deployment Status | Question on any status on how to extend/automate the appscan testing on the CTS2 service RESTful interface. | 6.3 Deployment Status
| DNS changes may happen this Thursday or Friday. If there are issues reported with the DNS switch, it will be switched back to the LexEVS 6.2 URL. | ||||||||||||||||||||||||||||||||||
VPN and network evaluation
| No updatesThere was a discussion last week. Jason hasn't heard anything back yet. | ||||||||||||||||||||||||||||||||||||
External Request
| NoneNothing. | ||||||||||||||||||||||||||||||||||||
Working with Coding Schemes | When dropping a coding scheme, validate that the index is removed and make sure we test that the metadata.xml file is updated accordingly as well. When updating an index, make sure that the metadata.xml be updated correctly. Administration of loading metadata in the GUI is cumbersome. The last loaded value set is at top (or bottom) of the list and hard to find (page through) - in GUI and CLI. Resolved VS and Mappings are loaded as coding schemes. They would like a list of just coding schemes, or resolved value sets, or mappings. This type could be captured in the index. | ||||||||||||||||||||||||||||||||||||
HTTPS - Applications Migrating
| By end of 2016, all applications will need to be using HTTPS.
| Sprint Demos | It was suggested that if there was test code to deploy or demos to show at the end of the sprint, we should do that during this weekly meeting
|
JIRA Issues
Recent LexEVS Related Bugs and Features (within last week)
...