NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Old Version 5

changes.mady.by.user Bauer, Scott (NIH/NCI) [C]

Saved on

compared with

New Version 6

changes.mady.by.user Bauer, Scott (NIH/NCI) [C]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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
IS x
Lucas, Jason R
IS x
Bauer, Scott  Mayo x
Stancl, Craig
Mayo x
Endle,  CoryMayo x
Wynne, Robert    NIH/NCI x
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   

Kuntipuram, Kumar

  x

 

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   open
79Corycomplete security requirements   open
100ScottCheck into source code, namespace application for code queries, javadoc availability for tree extension etc   on hold
106CraigConfirm and arrange meeting time for MedDRA review   open
117GilbertoCheck on the status of the Java 1.7 requirement   open

118

ScottDraw up a list of changes to documentation and entry points   open
119GilbertoCheck on the use of NIH ListServe for forum activity   open
120SherryCheck with Ann Wiley about the policy for forums   open

...

6.1 QA and Deployment (Tin, Jason, Scott)Status: Proposed we install index on stage.  Could do as a onetime workaround.  Should wait for Stage move to Production.  Will wait till the current data set is moved up.  Common Index is large and unwieldy.   IRA Item to be created. (Tracy)  Tracy and Scott to work out some requirements for testing indexes on Stage.  
Meta Loader Error OutputJIRA Item #596.   
6.1 DocumentationStatus.  Report on entry points etc.  Noted the Links that are release related have not been updated.  We will switch to the 6.1 in symbolic link to LexEVS landing point.  
JIRA Item for Value Set convenience methodJIRA #590#590  Currently we need to pass coding scheme to server to return the property to find out if it's a value set.  None are tagged as Production.   
Forums and user support (Gilberto and Sherry)   
Code coverage reports and QA JUnit documentation  (Tracy)   
DataQA inclusion in PTE's   
Priorities for the ExtensionRevisit

LexEVS Initial Estimates:
(1) Resolved value set export and required format (representation) (FDA, CDISC)
4 weeks
Performance of Hierarchial Search (graphDB)
(4) Lucene Update
16 weeks
Need to consider network drive access.
Importance of updating to latest Lucene code.  
(2) Java 1.7 Update
4 weeks (assuming no major issues)
Feedback from Bulk Loader (Synchronized Content)
(3) Upgrade to CTS2 1.1 Framework
3 weeks
CTS2 API, CTS2 Widgets, documentation
CTS2 Implementation Expansion
Additional LexEVS match algorithms to be exposed in matchAlgorithm.
(3) VSMC Integration with LexEVS value sets.
4 weeks
Resolved Value Sets in LexEVS
CTS2 1.1 (resolution) - need to understand implications.  
Requires updates to VSMC client
(1) JIRA Issues
?? weeks
Need to determine what JIRA items are important for resolution.  

 

May want to move VSMC before Java 1.7. 

  
Contract Wrap-up   

 

 

 

JIRA Issues

...