Page History
...
Sprint Status | Current Sprint - Sprint 16 (October 29, 2015 – November 11, 2015) | ||||||||||||||||||||||||||||||||||||
Sprint Planning | Issue Prioritization Recent LexEVS Related Bugs and Features (within last week)
Recent CTS2 Service Related Issues (within last week)
Issue Grooming Prioritize JIRA issues (fix version 6.4)
| ||||||||||||||||||||||||||||||||||||
Sprint Deliverables - Updates
| Lucene build - Cleanup script is broke. | ||||||||||||||||||||||||||||||||||||
Build practice is out of date, discuss single jar vs zip file | The build is currently broke. The artifact built does not run due to the new lucene jars and their manifest files. The dev team will need to consider if we need to change the process to create a zip file, rather than a jar. The dev team is suggesting breaking the build up into multiple jars. This new multiple jar approach would break current users of the single jar. Users would need to update their classpath. TODO: Add two groups to work with on the NCI team to the Face to Face agenda. How will this affect NCI users? TODO: Mayo dev team to come up with a proposal on how to migrate to the new jar structure. | ||||||||||||||||||||||||||||||||||||
VPN and network evaluation | Craig is still waiting to hear back from the Mayo/NCI IT. TODO: Craig will follow up with IT to get an update. | ||||||||||||||||||||||||||||||||||||
Horizontal Coding Scheme searches | TODO: Craig will add this to the Face to Face topics. | ||||||||||||||||||||||||||||||||||||
Review decision regarding the single jar vs. a zip file | |||||||||||||||||||||||||||||||||||||
VPN and network evaluation | |||||||||||||||||||||||||||||||||||||
Face-Face Planning | Face-Face Planning | December 8 - 10 on-site. | There is a wiki link for agenda topics: LexEVS 6.3 and 6.4 Technical Face-To-Face Meetings TODO: NCI team to add additional information to the topics for the Face to Face meetings. | ||||||||||||||||||||||||||||||||||
Search queries - accessing the database opposed to the Lucene index only
| Scott noted that unless you set the resolve flag in the query, it does not go to the DB. | ||||||||||||||||||||||||||||||||||||
LEXEVS- 970
| Scott was able to load the thesaurus locally without any errors. TODO: Scott to work with Gilberto and review a load with restrictions. Gilberto noted the following:
| ||||||||||||||||||||||||||||||||||||
LexEVS Meeting next week (2015.10.28) | The Mayo team will be out next Wednesday. The NCI will cancel the meeting. The Mayo team will end the existing sprint and start the next one | ||||||||||||||||||||||||||||||||||||
Questions around how NCI uses sorting mechanisms | We are re-implementing how we are restricting coded nodes. We are are seeing some differences in sorting when doing multi coding scheme index searches. If you do a union query across multiple code systems. Each code system has it's own index. Scoring is done on a each index. This is causing a junit ordering test to fail. We will need to see how this works with real data. | ||||||||||||||||||||||||||||||||||||
LEXEVS- 970
| MedDRA 18.1 | If the CUI is left blank will it cause a problem? We don't think so. |
JIRA Issues
Recent LexEVS Related Bugs and Features (within last week)
...