|#||Assigned||Description||Date Identified||Due Date||Date Completed||Status|
|Area of Interest||Details|
Sent an email to Mark Goodwin about the Mayo trusted site access and the Term Browser “Monitored” AppScan on Monday.
Submitted two new JIRA items:
Need a decision on where this functionality is going to go to start creating trackers and scope document.
Spoke with QA Team about the automated testing LOE. He said that there is some level of hard coding of data values but did not think the maintenance of it would be substantial. I told him it might be a good idea to get the Tech group back together once they have examples of each of test case to see how the data is being handled. Kim should also provide an overview of what he is doing. QA team also recommended putting the code out somewhere so other can review.
Was able to get a preliminary development schedule for 2.7 release. Right now we are looking at development completing early September but still needs some tuning to make sure it is accurate. There are some dependencies I need to follow up on. However this is still a significant release.
|Meta Download Validation App|
|Term Suggestion Form|
|NCITERM-669||View in Hierarchy - Sibling concepts showing up twice.|
Identified a method for removing redundant nodes from the child node list.
|NCITERM-671||Disable hyperlink of association entities returned by the simple search API.|
The search extension API returns all matched entities of all entity types (including both concept and association entities). Submitted a feature request to the Mayo team to allow search be restricted to concept entities only.
|NCITERM-660||UI Testing Utility.|
Modified the code to set the column width on the Relationship tab properly to accommodate the possible long role and association names; for example, Gene_Product_Sequence_Variation_Encoded_By_Gene_Mutant (See NCIt Code C98301).
|NCITERM-672||Remove all relationships between association and concept from the Relationship tab|
Identified the code that needs to be modified to meet the feature request.
|View In Hierarchy: When viewing a concept in Zebrafish, clicking on the View In Hierarchy link does not bring up the Zebrafish Hierarchy Tree.||Performed trouble shooting and found that the tree extension API throws exceptions on a Zebrafish test case. Informed the Mayo team of the finding|
|Area of Interest||Details|
|Report Writer||Develop Project plan for 2.1 release.|
|Term Browser 2.7 Release||Scheduling the release and start development.|
Risks, Issues, Dependencies
|#||Opened Date||Due Date||Description||Likelihood (H, M, L)||Impact||Assigned||Status||Mitigation Strategy|
|04/10/14||Deployments have been taking long periods of time. There is a lot of overhead getting through the iters||H||H||Speaking with members of the QA team to find ways to streamline the testing/deployment process||Finding ways to better integrate the development and QA team. Spoke to EVS Tools TPM requesting the correct communication channels.|
|7/17/2014||Deployment of software, even small upgrades, have been a lengthy process.||This especially affects smaller releases in which there are security or bug fixes.||The Agile practices migration have been put on hold for now.|
|09/10/2014||Getting the environment in place for the Mayo trip to NCI.||Need to get each of the environment (DEV,QA,Stage) in place before the Mayo trip on September 22nd. We are currently one week behind. The impact is that the Mayo developer will be onsite to work on the deployments and the tiers will not be in place.||Currently we only have the DEV environment setup for the LexEVS API>|