Attendees
| 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 | x |
| Endle, Cory | Mayo | |
| Wynne, Robert | NIH/NCI | x |
| Brem, Larry | NIH/NCI [C] | |
| Pan, JJ | NIH/NCI [E] | |
| Tran, Tin | NIH/NCI [C] | |
| Ahmed, Shamim | NIH/NC [C] | |
| Haber, Margaret | (NIH/NCI) | |
| Roth, Laura | (NIH/NLM) | |
| Ramani, Vivek | (NIH/NCI) [C] | |
| Carlsen, Brian | (NIH/NCI) [C] | |
| Wong, Joanne | ||
Kuntipuram, Kumar | x |
Action Items
| # | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
|---|---|---|---|---|---|---|
| 64 | Scott | To follow up on URI's on OWL2 with Harold. | on hold | |||
| 72 | Scott | Add release date to Release notes when appropriate | open | |||
| 79 | Cory | complete security requirements | open | |||
| 100 | Scott | Check into source code, namespace application for code queries, javadoc availability for tree extension etc | on hold | |||
| 106 | Craig | Confirm and arrange meeting time for MedDRA review | open | |||
| 113 | Scott | Create JIRA Item for resumeBatch LEXEVS-601 - Getting issue details... STATUS | done | |||
| 114 | Scott | Wrap up release artifacts | done | |||
| 115 | Scott | Add the log notes for URI failover for the URI Resolver to the PTE | done | |||
| 116 | Jason | Contact Jacob about sorting out the URI Resolver issues with the database connections | done | |||
| 117 | Gilberto | Check on the status of the Java 1.7 requirement | open | |||
118 | Scott | Draw up a list of changes to documentation and entry points | open | |||
| 119 | Gilberto | Check on the use of NIH ListServe for forum activity | open | |||
| 120 | Sherry | Check with Ann Wiley about the policy for forums | open |
Progress
| Priorities for the Extension | 2014 extension is signed off on by NCI and should be signed by the end of the day. Represent FDA and CDISC Value sets should be as they want them. How do these requirements fit into CTS2 model. Need to get this done as the highest priority. Suggest using the preferences file to adapt. Current state of Java 1.7 update requirement – should this be a priority. Keep as a high priority probably will become official tech state requirement in March. Need to update the CTS2 Framework to get that up to date with 1.1. The specification was posted last month, a good time to get this done. Value set browser to have NCI value sets represented. CTS2 1.1 implementation and resource requirements to be examined more closely to see how these affect the final implementations. LexEVS Priorities:
|
| 6.1 QA and Deployment (Tin, Jason) | Status: Errors on the tiers differ and QA appears to be working correctly. We'll look at that and workshop the problem on Dev |
| Widget Deployment | Will expose when we have a working external lexevscts2. |
| Meta Loader Error Output | JIRA Item #596. |
| 6.1 Documentation | Status. Will add release documentation when release is current. |
| Forums and user support | What shall we do with these links and support in general. Ask Ann Wiley about the policy. Check the NIH List Serve as a possible issues forum for LexEVS. |
JIRA Issues
| Description |
|---|
| LEXEVS-570 - Getting issue details... STATUS |
| LEXEVS-572 - Getting issue details... STATUS |
| LEXEVS-573 - Getting issue details... STATUS |
| LEXEVS-574 - Getting issue details... STATUS |
| LEXEVS-576 - Getting issue details... STATUS |
| LEXEVS-579 - Getting issue details... STATUS |
| LEXEVS-583 - Getting issue details... STATUS |
| LEXEVS-584 - Getting issue details... STATUS |
| LEXEVS-585 - Getting issue details... STATUS |
| LEXEVS-586 - Getting issue details... STATUS |
| LEXEVS-587 - Getting issue details... STATUS |
| LEXEVS-588 - Getting issue details... STATUS |
| LEXEVS-589 - Getting issue details... STATUS |
| LEXEVS-592 - Getting issue details... STATUS |
| LEXEVS-593 - Getting issue details... STATUS |
| LEXEVS-594 - Getting issue details... STATUS |
| LEXEVS-595 - Getting issue details... STATUS |
| LEXEVS-596 - Getting issue details... STATUS |
| LEXEVS-597 - Getting issue details... STATUS |
| LEXEVS-598 - Getting issue details... STATUS |
| LEXEVS-599 - Getting issue details... STATUS |
| LEXEVS-600 - Getting issue details... STATUS |
| LEXEVS-601 - Getting issue details... STATUS |
Project Plan Changes
| # | Description | Due Date | Resources | Notes | Risks | Mitigation |
|---|---|---|---|---|---|---|
| None | ||||||
Planned Activities
| Area of Interest | Details |
|---|---|
| List of Issues, adjustments | Loaders and smaller issues |
| Continue work on widgets |
Risks, Issues, Dependencies
Risks
| # | Opened Date | Due Date | Description | Likelihood (H, M, L) | Impact | Assigned | Status | Mitigation Strategy |
|---|---|---|---|---|---|---|---|---|
Issues
| # | Opened Date | Description | Impact | Assigned | Status |
|---|---|---|---|---|---|
Dependencies
| Opened Date | Description | Assigned |
|---|---|---|
