Initial grooming

Discussion Points:

• Items to review Loader issues
  • 
  • 
  • 
  • 
  • 
  • 
  • 
  • 
  • 
  • 
  • 
  • 
  • 
  • 
     

Decision Points:

• 
  • Kim has a work around for the browser.
    
    • He is basing it on the length of the version.
  • This would still be useful to everyone else.
  • Priority 2.
• 
  • Now that indexes are separated into their own directories and in the DB, we should be able to perform multiple loads at the same time.
  • Related to LEXEVS-1413 and LEXEVS-1157.
  • Priority 2
• 
  • Would like a decent message that the SAB is incorrect and the tables should be cleaned up.
  • Look into checking the SAB file first by parsing it and verify it is correct.  If it's invalid, stop.
  • Priority 1
• 
  • Related to LEXEVS-2253 and LEXEVS-1157.
  • Priority 2
• 
  • We initially agreed to increasing the length from 250 to 1000.
  • Tracy agrees that the above solution will still work.
  • Priority 3
• 
  • This can be closed as not an issue anymore.
• 
  • These warning issues are a lot of noise.  It would be good to not surface these warnings.
  • Priority 3
• 
  • LexEVS 612 - Clean DB Script. 
    
    • If LexEVS 612 is working, it would satisfy the issue. 
  • This cleanup should be done at the end of the load.
  • Priority 4
• 
  • We are not sure if this is still an issue.  We will need to investigate
  • Priority 2
• 
  • Currently working on.
  • Priority 1
• 
  • Related to LEXEVS-1413 and LEXEVS-2253.
  • Priority 2
• 
  
  • Preferably, remove old tag (if exists) and add the tag to selected coding scheme version.
  • Priority 1
• 
  • This would be useful.
  • Priority 1
• 
  • The method should not return null, It will always return a Boolean value.
  • This should be handled on the OWL2 loader.
  • Priority 3