De Coronado, Sherri
|Ong, Kim L ||IS||x|
|Lucas, Jason R ||IS||x|
|Pan, JJ ||NIH/NCI [E]||x|
|Tran, Tin||NIH/NCI [C]||x|
|Ahmed, Shamim||NIH/NC [C]|
|Ramani, Vivek||(NIH/NCI) [C]|
|Carlsen, Brian||(NIH/NCI) [C]|
|#||Assigned||Description||Date Identified||Due Date||Date Completed||Status|
|64||Scott||To follow up on URI's on OWL2 with Harold.||on hold|
Provide an email update to NCBO, NLM, and Mayo with current activities and what has been built.
|155||Kumar||Verify that funds can be extended through Oct.||2014.04.30||on hold|
Scott to work with Gilberto to determine what is needed for OWL 2 requirements
|164||Cory||Cory to add implementation to CTS2 implementations page.||2014.04.30||on hold|
|170||Scott||Update the ARC dates to include range of dates for each tier.||2014.05.14||open|
|185||Gilberto||Create Jira for OWL 2 Annotation issue in the API.||2014.05.28||open|
|187||Scott||Create JIRA item for removing CTS2 Java API.||2014.06.04|
|188||Craig||Add task to remove CTS2 JAVA API to the project plan||2014.06.04|
|189||Craig||Update and send out latest project plan on Thursday afternoon.||2014.06.04||done|
|190||Cory||Commit UI changes and update informatics||2014.06.04||done|
|191||Scott||Send performance spreadsheet to larger group||2014.06.04||done|
|192||Scott||Capture issues with Agile we may have||2014.11.04||open|
|192||Scott||Investigate logging or monitoring capabilities of URL Resolver||2014.11.04||open|
|193||Craig||Send out updated Project Plan||2014.11.04||open|
|194||Craig/Scott||Send a list of Known Common Value Set Client issues to Larry||2014.11.04||open|
|Immediate Priorities and Problems (Mayo Team)|
Scott: MySQL 5.5 - Tomcat verification testing, Loader testing.
Craig: Project Plan Updates
|Goals and performance document (Larry)|
Document that captured a performance document that was submitted to justify better hardware. Also include a basis for target performance. After review, there was followup required. Will require ongoing discussion and refinement of the document going forward.
JJ asked if there was a timetable to address performance concerns. The goal is that in the 6.2 time frame, plan to have adequate hardware and consistent hardware from Dev to Prod. This timetable would lead to Sept 2014. This performance will need to be included in the project plan - include creating performance profiles of 6.2 on DEV hardware on Shady Grove and then evaluate performance at that point and determine what else would need to be done. Additional work would need to be prioritized against the currently planned tasks at that time.
|Agile adoption Schedule|
Currently looking at all aspects of process - including updates of terminologies. Agile approaches still being decided. EVS will be a good product to evaluate approaches.
Would like to have common education to provide a definition of how we will run the project with Agile. This will ensure that all teams/groups will understand what aspects of Agile will be in this process.
Provide an initial analysis of how Agile could work in LexEVS environment that could feed requirements to the formal process.
Risks on Mayo's side - small development team that is required to develop and also address immediate issues/concerns. Typical agile sprints are focused and limited to defined sprint. Moving forward, do we need to support agile and the existing expectations of support? Need to consider such expectations. TODO: Scott to capture issues/concerns that we may have.
Project plans to start reflecting agile in the September time frame.
|caDSR and Value Set and other URIs (Weekly Status)|
URI format was agreed. No additional news. One concern was if the old URIs are being used by anyone. Need to look to see if the URI resolver has logging. TODO: Scott to determine if there is logging.
|Tech Catalog Review||No additional comments. If there are concerns, send them onto Gilberto and JJ.|
|Dev DRT request||Possibly going to use STAGE server for Dev. Jacob is going to follow up regarding the request.|
|GitHub, build workflow||Discuss when Gilberto is back next week.|
|Forum Links on GitHub (Scott)|
Recently received a forum posting from the old VKC forum. Realized the readme was linking users to the VKC forum. We can fix the readme, but now that we need to modify the files and push to NCIP channel, we need to figure out how we would make the change and push to both channels.
Will need to discuss with Gilberto next week.
|Project Plan||Craig to send out updated plan.|
|Value Set Client - Sharing Link|
List of value set client - NCBO, TLAMP issues. Scott and Craig to provide list of any existing issues.
There will be an NLM demo. Want to include lessons learned.
|LEXEVS-570 - Getting issue details... STATUS|
|LEXEVS-573 - Getting issue details... STATUS|
|LEXEVS-579 - Getting issue details... STATUS|
|LEXEVS-586 - Getting issue details... STATUS|
|LEXEVS-594 - Getting issue details... STATUS|
|LEXEVS-597 - Getting issue details... STATUS|
|LEXEVS-598 - Getting issue details... STATUS|
|LEXEVS-599 - Getting issue details... STATUS|
|LEXEVS-605 - Getting issue details... STATUS|
|LEXEVS-606 - Getting issue details... STATUS|
|LEXEVS-607 - Getting issue details... STATUS|
|LEXEVS-608 - Getting issue details... STATUS|
|LEXEVS-609 - Getting issue details... STATUS|
|LEXEVS-612 - Getting issue details... STATUS|
|LEXEVS-613 - Getting issue details... STATUS|
|LEXEVS-615 - Getting issue details... STATUS|
|LEXEVS-616 - Getting issue details... STATUS|
|LEXEVS-617 - Getting issue details... STATUS|
|LEXEVS-618 - Getting issue details... STATUS|
|LEXEVS-619 - Getting issue details... STATUS|
|LEXEVS-620 - Getting issue details... STATUS|
|LEXEVS-621 - Getting issue details... STATUS|
|LEXEVS-622 - Getting issue details... STATUS|
|LEXEVS-623 - Getting issue details... STATUS|
|LEXEVSCTS2-2 - Getting issue details... STATUS|
|LEXEVSCTS2-3 - Getting issue details... STATUS|
Project Plan Changes
|Area of Interest||Details|
|VSMC definition||Need a dialog defining module use around ResolvedValueSets|
|Update LexEVS CTS2 Service to CTS2 1.1||Need deployment tests|
|Work on a variety of EVS JIRA Priorities||Scripting, convenience methods, tree extension namespace issues|
Risks, Issues, Dependencies
|#||Opened Date||Due Date||Description||Likelihood (H, M, L)||Impact||Assigned||Status||Mitigation Strategy|