 |
Page History
...
| Name | Role | Present |
|---|---|---|
| Wright, Larry | NIH/NCI | x |
| Fragoso, Gilberto | NIH/NCI | |
De Coronado, Sherri | NIH/NCI | |
Safran, Tracy | NIH/NCI [C] | x |
| Ong, Kim L | IS | x |
| Lucas, Jason R | IS | x |
| Bauer, Scott | Mayo | x |
| Stancl, Craig | Mayo | x |
| Endle, Cory | Mayo | x |
| Wynne, Robert | NIH/NCI [C] | x |
| Tran, Tin | NIH/NCI [C] | x |
| Carlsen, Brian | NIH/NCI [C] | |
| Wong, Joanne | NIH/NCI [C] | |
Kuntipuram, Kumar | NIH/NCI [C] | x |
Action Items
| Assigned | Description | Date Identified | Due Date | Date Completed | Status |
|---|---|---|---|---|---|
| Craig/Larry | Follow up with Jose (CTRP) in January 2016 to see if we can assist them and understand their requirements. | 2015.12.16 | 2016.01.31 | Open | |
| Scott | Summarize the namespace issue (LEXEVS-1427). This summary should be in the JIRA item itself. | 2016.01.06 | 2016.01.31 | Open |
Progress
| Scott |
|
| Cory |
|
| Craig |
|
...
| Sprint Status | Current Sprint - Sprint 20 ( December 24, 2015 – January 06, 2016 ) LexEVS 6.4 S13-500 Agile Development - Sprint StatusStatus#SprintStatus-Sprint20 Craig reviewed the stories that are planned to be worked on in sprint 21. He also mentioned the Cory will be on this project almost full-time going forward. | ||||||||||||||||||||||||||||||||||||
| 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)
| ||||||||||||||||||||||||||||||||||||
| Face-to-Face Recap | 2015.12 Technical Face-To-Face Prioritization List We clarified the priorities for each piece of work to be done. There is now a column to indicate what work will be done during the 6.4 timeframe. Next steps - We will create JIRA issues for each work item in the list. CTRP will get back to the EVS group when they have firm requirements. It was suggested that Craig/Larry will follow up with Jose in about a month to see if we can assist them and understand their requirements. Tracy brought up the "Path to Root issue" - This is part of the existing transitive closure issue captured in the F2F notes. If this was developed in CTS2 it would be to retrieve descendants and ancestors. We should also consider how this will work if there are multiple different paths to root. For example, the thesaurus has many nodes that have 10+ paths to root. Sherri will send an example of this to the development team. Tracy mentioned that "Lung Carcinoma" has several different paths to root. Examples from Sherri of concepts with many paths to root.
Other general comments were that the 3 day duration was a good time frame and it was also good to meet with other teams (CTRP and Systems). | ||||||||||||||||||||||||||||||||||||
| LexEVS 6.4 Roadmap | Our estimate for phase 4 was originally 60 days. We revised this to about 100 days. This puts our functionality complete date to the end of March 2016. If there is any additional work (CTRP or others), this may potentially push the date out. Scott mentioned that the search extension feature should be completed around the end of January. The search extension is needed by NCI to test the TERM browser. The rest of the search functionality can be tested at this time. | ||||||||||||||||||||||||||||||||||||
Namespace issue
| Scott mentioned that the capability to query from one namespace to another code system is possible. Scott described how the namespace feature will work when traversing into another code system (path to root). Scott and Kevin further discussed this issue and determined that this could be a lot of work to implement more than the narrow path that currently works. Larry suggested that we document and continue this discussion next week when Gilberto is available. Scott will work with Kevin to provide a summary of how this feature works. TODO: Scott to summarize this in LEXEVS-1427. Scott added that this will be released for 6.3 and merged into 6.4. We confirmed with NCI that we don't need to add this to 6.2. | ||||||||||||||||||||||||||||||||||||
| CTRP Planning | We have a list of high level requirements for CTRP that we captured during our F2F meeting in December. We are looking for more detailed requirements for LexEVS planning purposes. TODO: Larry will request more information from Jose. | ||||||||||||||||||||||||||||||||||||
Orphaned Index OBI issue
| Scott is trying to determine why the tree extension isn't working for certain cases. If he cannot determine the error, he may need to work with the term browser team to see if the issue is there. Jacob was able to open a port for debugging on the DEV system so Scott can do some debugging. | ||||||||||||||||||||||||||||||||||||
| Holiday Planning | The next two Wednesdays will be cancelled due to the holidays. | ||||||||||||||||||||||||||||||||||||
added a fix for this orphaned index issue. When the system starts up, the system checks indexes against a registry. Any indexes not found will be removed. We discussed this new functionality with NCI and Tracy agreed that this made sense. | |||||||||||||||||||||||||||||||||||||
| Removal of Windows 32 bit scripts | The Mayo team suggested that we remove the scripts associated for Windows 32. Windows 32 bit systems are not really adequate to run LexEVS. Tracy and Rob agreed that we remove these scripts. We also agreed to remove the Windows 32 bit LexEVS install and everything associated with Windows 32 bit environment. This includes updating the documentation. | ||||||||||||||||||||||||||||||||||||
| Removal of admin script LoadRadLexProtegeFrames | We suggested to remove this script as well and Larry agreed this is no long needed. | ||||||||||||||||||||||||||||||||||||
| LexEVS External Users | Nothing to report | LexEVS External Users | Scott helped a user on the forum to get LexEVS installed. The user was looking at how to get the shortest path between two nodes. Larry suggested that we request any additional information from the user (what they are using LexEVS for, etc) if they are willing to send this. |
JIRA Issues
Recent LexEVS Related Bugs and Features (within last week)
...
