NIH | National Cancer Institute | NCI Wiki  

 Attendees

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

De Coronado, Sherri    

NIH/NCI    

Safran, Tracy

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

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
238CorySend out PDF and abstract for AMIA poster.2014.11.12  done
239CraigConfirm Kevin and Harold availability for next week.2014.11.12  done
240TinSend performance spreadsheet.2014.11.12  done
241CoryCreate JIRA issue to track issue regarding NLM CTS2 service authentication issue2014.12.03  

open

242ScottSend email to Kim with NPO information.  2014.12.03  

open

243ScottSchedule OWL discussion meeting with Gilberto, Tracy.2014.12.03  open
244CraigPlan meeting with Tracy to discuss collaborative LexEVS development process2014.12.03  open
       

Progress

EPA Demo

Interested in learning more about distributed vocabulary services.

TODO:  Larry to send out URL for prototype.

Immediate Priorities and Problems (Mayo Team)

Scott:  Starting to work on OWL2, will start look at Lucene.

Cory:   LEXEVSCTS2-21 - Getting issue details... STATUS

  • Pushed fix out to the informatics server.
  • Need to complete junit for testing. 

Craig: Project Plan for 6.3 and 6.4.  Will be reviewing and updating JIRA items. 

 

NLM CTS2 Service UTS Authentication
  • Will look into what's wrong and determine how much effort.
  • Create JIRA issue to track the issue.
Tree Evaluation – Feedback
  • Changes need to be made based on discussion from F2F.
    • Need to be able to navigate to root.
    • Namespaces missing
  • NPO loading needs to use a manifest.
    • Scott to send email regarding NPO
OWL2

Planning to meet to discuss with Gilberto, Scott, Tracy.  Friday PM

Scott to schedule.

Code Contributions

Tracy was able to check in her code. 

Need to coordinate with Scott as there is some parallel work.  Part of the Friday discussion.

May want to share a common plan for working together in this code base. 

TODO:  schedule time to share the plan/process.

F2F followupPlease review comments from Larry.  Craig and team to start planning based on the decisions during the F2F.

Hardware performance discussion

Scott suggested there may be ways to configure things to decrease load time.

Coding scheme metadata could be changed to increase performance (assumption).

 

JIRA Issues

Description
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

#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