Page History

...

• Dates: October 1, 2015 – October 14, 2015 (2 weeks)
• Goal:   
  
  • Demonstrate all previous LexEVS functionality as implemented with the new Lucene and 100% of unit test pass
  • Provide continued support and issue resolution.
  • Provide deployment support.
• Project Roadmap
  • https://wiki.nci.nih.gov/download/attachments/270532635/S13-500%20MOD4%20-LexEVS%20Lucene%20-%20Project%20Roadmap%20-%2020151006.pdf?api=v2
• Agile Board
  • https://tracker.nci.nih.gov/secure/RapidBoard.jspa?rapidView=220&view=planning.nodetail
• Sprint Report (includes issues/deliverables)
  • https://tracker.nci.nih.gov/secure/RapidBoard.jspa?rapidView=220&view=reporting&chart=sprintRetrospective&sprint=428
• Retrospective 
  • 2015-10-14 Retrospective - 6.4 - Phase 3 - Sprint 14
• Artifacts
  • v6.3.0.1 branch
    
    • Git tag: v6.3.0.1.RC1
    • <sftp location>
    • Functionality Summary
    • Git Tag: SNAPSHOT.SPRINT14.2015.10.15
    • <sftp location>
      • LEXEVS-1195 GUI - Filter coding scheme drop down to not display resolved value sets.  This is fixed for all loader dialogs.
      • LEXEVS-1192 Loader - OBI property qualifiers are now being loaded correctly 
    lucene branch
    • • 
        
      Functionality Summary:
      • lbGUI provides drop down lists for a variety of content loading convenience.  These content loading aides typically require a conventional coding scheme.  Since resolve value sets are coding schemes under the covers, these also appear in the drop down lists.  The number of these value sets loaded by some users creates a long list that is unusable under some circumstances.  This snapshot removes the resolved value sets from the list.
      • The OBI source is written in OWL2 format.  It features Axioms that contain references to property annotations also defined in the source.  When these property annotations are defined as owl literals they were being loaded properly.  However most of the annotations were defined as simple IRI's and were not being properly loaded.  This fix corrects that issue and provides test source and Unit tests to track for regression errors. .
        
  • lucene branch
    • Git Tag: SNAPSHOT.SPRINT14.2015.10.15
    • <sftp location>
    • Functionality Summary:
      • Lucene queries on most multi property designations are functioning properly
      • Lucene queries against a non-child status value are corrected.

Sprint 13

• Dates: September 17, 2015 – September 30, 2015 (2 weeks)
• Goal:   
  
  • Demonstrate functionality of some searches being performed in the API and 25% of functionality implemented.
  • Provide continued support and issue resolution.
  • Provide deployment support.
• Project Roadmap
  • S13-500 MOD4 -LexEVS Lucene - Project Roadmap - 20150922.pdf
  • S13-500 MOD4 -LexEVS Lucene - Project Roadmap - 20150929.pdf
• Agile Board
  • https://tracker.nci.nih.gov/secure/RapidBoard.jspa?rapidView=220&view=planning.nodetail
• Sprint Report (includes issues/deliverables)
  • https://tracker.nci.nih.gov/secure/RapidBoard.jspa?rapidView=220&view=reporting&chart=sprintRetrospective&sprint=419
• Retrospective 
  • 2015-09-30 Retrospective - 6.4 - Phase 3 - Sprint 13
• Artifacts
  • Git Tag: SNAPSHOT.SPRINT13.2015.09.29
  • http://cbiit-download.nci.nih.gov/evs/LexEVS/v6.4/lbRuntime_SNAPSHOT.SPRINT13.2015.09.29.jar
• Functionality Summary
  • Search Functions in matching designations for all search algorithms should return results.  
  • Sorting mechanisms seem to be in order according to limited Unit test application.
  • Search API for mapping schemes should be as fully functional as other searches
  • Some property restrictions are working within limitations.  We are still working to fix concept status and property type restrictions – others are not fully tested.
  • Multiple restrictions have limited functionality.  Not fully tested.

...