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 Next »

 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
Wynne, Robert    NIH/NCIx
Brem, Larry  NIH/NCI [C]   
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

  

 

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
64ScottTo follow up on URI's on OWL2 with Harold.   on hold
72ScottAdd release date to Release notes when appropriate   done
129ScottFurther testing on Production around the breaking value set   done
130ScottUpdate 227 for flag for exceeding max clause count   open
131ScottCheck the database to make sure the MOA value set entries are there   done
132ScottFix the value set name truncation by the end of the week   done
133ScottTalk to Harold about value set versioning   done

Progress

Immediate Priorities and Problems (Mayo Team)

Value Set Module - still making progress.  Coordinating with Kevin on queries across services. 

CTS2 Client UI - Demo at meetings end.

https://www.evernote.com/shard/s89/sh/0fad31fe-ee41-4dac-aec6-0a01d36ce60c/d48e3990d1fbe42b7823ccf46c52f172

Project Plan Updates -

  
Struts Security Update (Jason)Vulnerability found in Struts.   Currently used in the grid and distributed services (only to display web page).  This page has been requested to not be available outside the firewall.  Currently at 2315 and upgrade to 2316.1.  Would be good to remove our Struts dependency.   The vulnerability was focused on an upload functionality.    Create a JIRA item to track the need to remove Struts.  Immediately - leave what we currently have (already protected).   If that doesn't satisfy, then drop in new jar.   The issue was found during another security scan.    JJ will follow up on the scan.  May need to follow complete deployment process.   
Face To Face Followup

Notes review.  No comments or additions. 

Review what is needed in the ARC meeting - what belongs in that part of notes - Hardware, performance requests.    Team to review. 

  
6.1 Deployment

Production server needs to be updated and then another scan. 

Can point the CTS2 API page. (Scott)

  
Resolved Value Sets from different Coding Scheme versions (Kim)

Need to consider what options are available to provide versions. 

Using coding scheme version to manage (but if several coding schemes, may not get what we need).

Can set up a dedicated time to discuss.   (Kim, Scott, Gilberto(optional))

  
JIRA or GitHub for forum (Jason)Gilberto to show the HubZero forum  
Retiring Grid Services

Discussed during Tech meeting on Wed morning.  

Decided wasn't used in the past/recently, and could be retired.  

Tracy looked at usage - decided it was declining.  Will make the announcement with the 6.1.

  
caDSR and Value Sets

Are there rest services that caDSR should be using?    Will they use the same URIs that are provided on browser?  Currently using the URI that defines the value set.  

  
Value Set UI Demo   

 

 

 

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
LEXEVS-602 - Getting issue details... STATUS
LEXEVS-603 - Getting issue details... STATUS
LEXEVS-604 - 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

Project Plan Changes

#DescriptionDue DateResourcesNotesRisksMitigation
 None     
       
       

 Planned Activities

Area of InterestDetails
VSMC definitionNeed a dialog defining module use around ResolvedValueSets
Update LexEVS CTS2 Service to CTS2 1.1Need deployment tests
Work on a variety of EVS JIRA PrioritiesScripting, convenience methods, tree extension namespace issues

Risks, Issues, Dependencies

Risks

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

Issues

 #Opened DateDescriptionImpactAssignedStatus
      
      
      

Dependencies

Opened DateDescriptionAssigned
   
   

 

 

 

 

  • No labels