Page History
...
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 | |
Endle, Cory | Mayo | |
Wynne, Robert | NIH/NCI | x |
Pan, JJ | NIH/NCI [E] | x |
Tran, Tin | NIH/NCI [C] | x |
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 | x | |
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 | |||
156 | Scott | Scott to work with Gilberto to determine what is needed for OWL 2 requirements | 2014.04.30 | on hold | ||
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 | on hold | ||
185 | Gilberto | Create Jira for OWL 2 Annotation issue in the API. | 2014.05.28 | open | ||
197 | Scott | Do a gap analysis on what the URI_Resolver logs and what NCI would like to know from these logs | 2014.6.18 | on hold | ||
200 | Larry/Sherry | Query current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's | 2014.6.18 | open | ||
204 | Larry | Plan for August NLM Demo/Meeting. | 2014.07.09 | open |
...
Immediate Priorities and Problems (Mayo Team) | Scott: Loader testing against, Working on JIRA #598
Cory: Working JIRA #'s 531, 371 Craig: Project Plan Updates.
|
| |
caDSR and Value Set and other URIs (Weekly Status)Status if needed | Production now reflects updated URI's Need to know if URI resolver is case sensitive (Scott). URL's are not by definition case sensitive. In general you cannot say you can use either. Proposal: Should go to all lower case. | ||
Dev DRT request | UpdateSsh is now being implemented on Shady Grove dev. Dev and QA to be combined via new Agile approach. QA and developer sit together to develop the test. Once done on Dev, QA is done. Perhaps sprint testing will be done on Dev. Saves data migration. Potential for conflict with data and application testing taking place on the same server. Need to have a plan as to how we will test to potentially take to Systems. Requirements for testing should be different thanks to better resources. Two data base instances might be a good way to manage things. How will we manage documentation of this? Need to have a streamlined test plan/process. JIRA agile may be a good place for this. Other applications are currently trying to create such documentation and may create a standard template for this. We can define exit and entrance values for Dev to QA even though they are on the same tier. Need to create a checklist. | ||
Plans for the future of caCORE webservices. | StatusPerhaps leave this in for this iteration. | ||
Discussion of JIRA #597 | CTS2 Association Graph |
...