Case Management Window Optimizations:
1.  Implement Threading on Case Save Operations, not through close
button. 
2.  Implement Threading on Case Load Operations (for both View and Edit
Case Windows)
3.  Implement Threading on refresh button of Case manager and case
Edit/viewer
Case Management Window Optimizations:
1. Implement Threading on Case Save Operations (either via Save Button
and also a Save via the Close Button)
Client: implemented swing worker on Case save, close button don’t
execute save action. 
Server: combined duplicate name and abbrev checking through only one
Server traffic to reduce processing time. 

2. Implement Threading on Case Load Operations (for both View and Edit
Case Windows)
Implemented. 
3. Look to optimize other retrieveal operations if possible, maybe cache
certain drop down lists on Summary Tab, etc...
4. Maybe we should cache drop down items on View/Edit Input, Parameters,
and Outputs Windows
Will try to save jobs list in cache, similar as sectors. 

5. Is Editing/Viewing Input, Parameters, and Outputs Windows slow, maybe
we should implement SwingWorker here too.
6. Changing main filter drop-down on Inputs (Sector), Parameters
(Sector), Outputs (Job), and History (Job) Tabs is not correctly
implements threading -- window acts unresponsive during thre table
update
7. Apply similar optimizations to Case View Window?
Implemented SwingWorker on tab (for both Edit and view window)  first
time loading, refresh, drop down menu, and name contain.   Only History
tab is not finished yet.
Merge branch 'master' of https://github.com/ddelvecchio/emf.git
test
SwingWorker: moved GUI related codes outside of doinbackground
Modified Flat File Inventory formats to handle EIS Dataset Shortname
[varchar(20)] in the DATA_SET_ID column (was integer converted to
string)
Fix for Github Issue #10, an OR in the where clause was breaking dataset
versioning.
Merge branch 'master' of https://github.com/ddelvecchio/emf.git
Merge branch 'master' into tempalloc