NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

 Attendees

NameRolePresent
Wright, Larry NIH/NCI  x
Fragoso, Gilberto NIH/NCI    x

De Coronado, Sherri    

NIH/NCI   x

Safran, Tracy

NIH/NCI   x
Ong, Kim L
ISx
Lucas, Jason R
ISx
Bauer, Scott  Mayox
Stancl, Craig
Mayox
Endle,  CoryMayox
Peterson,  KevinMayo 
Wynne, Robert    NIH/NCIx
Pan, JJ
NIH/NCI [E] 
Tran, Tin    NIH/NCI [C]  
Carlsen, Brian (NIH/NCI) [C] 
Wong, Joanne  x

Kuntipuram, Kumar

 x

 

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
64ScottTo follow up on URI's on OWL2 with Harold.   on hold
156Scott

Scott to work with Gilberto to determine what is needed for OWL 2 requirements

2014.04.30  

on hold

164CoryCory to add implementation to CTS2 implementations page.2014.04.30  on hold
170ScottUpdate the ARC dates to include range of dates for each tier.2014.05.14  on hold
185GilbertoCreate Jira for OWL 2 Annotation issue in the API.2014.05.28  on hold
197ScottDo a gap analysis on what the URI_Resolver logs and what NCI would like to know from these logs2014.6.18  on hold
200Larry/SherryQuery current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's2014.6.18  on hold
207CoryWrite issue against CTS2 OMG regarding the ability to return INACTIVE concepts only.2014.07.30  on hold
209Craig/LarryPlan Techical F2F/AMIA meetings.2014.07.30  

done

210Larry/GilbertoDetermine if there is a need to meet with the CTRP2014.07.30  on hold
212LarryInclude LexGrid XML Export as part of the 5.1 retirement notice. 2014.07.30  

on hold

224ScottURI Resolver - Provide overview of how to access the URI Resolver2014.09.03  

on hold

225ScottURI Resolver - Look at TLAMP and VSAC service to determine usage of URI Resolver2014.09.03  on hold
235Mayo/NCI TeamIdentify additional value set JIRA items to be included in 6.3 release.2014.10.02  on hold
237ScottFinal code deliverables posted to SFTP site and wiki pages updated.2014.10.02  on hold
244CraigPlan meeting with Tracy to discuss collaborative LexEVS development process2014.12.03  open
245Kim/NCIConfirm that the manifest and Tree Jar that Scott put on sftp will work. 2014.12.10  open
246CoryInvestigate if possible to use Apache as a proxy for NodeJS2014.12.10  

open

251CoryInstall NodeJS on NCI server.2014.12.17  

open

251CraigUpdate 6.3 project plan to include 6.2 release activities.2014.12.17  done
       

Progress

Immediate Priorities and Problems (Mayo Team)

Scott: 

  • LEXEVS-623
    • short-term fix
    • should consider updating DAO - could require a larger effort.
  • Support Items
    • Contains Searches - and how they work.
    • James (caDSR) - xml parsing issues. Needed to have client available struts-free.
  • OWL2 Fixes
    • comments below
  • 6.2 Client LEXEVS-675
    • Updated (pulled out things that were not needed)
    • Updated spring generated classes
    • Provided additional documentation.
  • Informatics support
    • comments below
  • Lucene Planning
    • Scott and Kevin have been discussing approach and tasks to be captured in a plan.
    • Considerations given to profiling, more efficient application.

Cory: 

  • CTS2-27 (API Documentation)
    • Documentation is complete (JSON complete)
  • LEXEVS-581
    • Started work.
  • LEXEVS-636

Kevin:

  • Lucene Planning
  • CTS2-28 (Authentication for VSMC)
    • Complete

 

Craig: Project Plan for 6.3 and 6.4

  • Updated

 

JIRA items feedback:  Resume Batch
  • Scott suggests we no longer include in 6.3.
  • Most of the issues we experienced were memory related issues. However, in the new environment, shorter load times, more hardware capacity should reduce the possibility of loads ending.
  • Any changes would need to be down into the spring code.
  • This could be looked at again after we've updated spring.
  • Consider this again for 6.5.
Tree Evaluation – Feedback

Kim will need to provide feedback.

  • Scott to document the use/creation of the manifest. (as part of loader documentation)
  • Manifest on sftp site will load NPO.

 

CTS2 API documentation

Demo and discuss protege server deployment.

  • Example API - note that content may change.
  • Will install on protege server so it could be app-scanned.
  • Either we can provide instructions or get Cory credentials.
  • Gilberto will provide access to the server for Cory.
Shady Grove Deployment

Firewall exceptions have gone through.

Announcements:

  • Browsers
  • Once browsers are confirmed, then the API.
  • Mayo team to prep to get deliverables on the sftp site. LexEVS 6.2 download page. (Scott) (due in 2 weeks)
  • EVS download page needs to be updated to point to the new jars. (Tracy and Rob)
OWL2 Updates

Gilberto and others to review by next Wednesday, January 14.

Scott noted that duplicate relationships should be reviewed and discussed - how should they be maintained (remove the duplicate?)

  • Scott to set up meeting to discuss.

 

Informatics dependencies

JIRA ITEM LEXEVS-686

  • Informatics server was down.
  • Rob noted that something was dependent on informatics for schemas.
  • Scott has prepared a fix that removes that dependency.
    • Schema location changed to local file location.
  • Not part of 6.3 - independent of 6.3.

 

6.3 release planning, also 6.4 (Craig, Scott) 

 

JIRA Issues

Recent LexEVS Related Issues (within last week)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Recent CTS2 Service Related Issues (within last week)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

6.3 LexEVS Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

6.3 CTS2 Service Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Project Plan Changes

#DescriptionDue DateResourcesNotesRisksMitigation
 None     
       
       

 Planned Activities

Area of InterestDetails
  
  
  

Risks, Issues, Dependencies

Risks

Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation Strategy
         
         

Issues

 #Opened DateDescriptionImpactAssignedStatus
      
      
      

Dependencies

Opened DateDescriptionAssigned
   
   

 

 

 

 

  • No labels