MDS Best Practice Approach - Sample HR Scenario

Question

Thanks for taking to time to read my MDS requirement...just looking for a better way to go about it.
Here is the requirement: 
Every month CEO releases an excel list of approved employment positions that can be filled to the HR.   The HR dept wants to be able to add positions that CEO approves and remove positions that the CEO feels are
no longer necessary.  The recruiting group wants to track/modify this master list of positions per the CEOs discretion and assign employees to potentially each position as people are hired/terminated.
The HR data steward must be able to:
-when a position is filled, must be enabled to assign employees to the positions for org chart reporting
-they need the ability to assign/reassign parent child relationships for any position i.e. the Director Position manages multiple Manager positions which manage multiple Register Clerk positions.
I am new to MDS and am initially not sure how to approach this problem...do I create one entity for 'Positions' and another for 'employees' ?   I'm thinking with that approach I can create employee as an domain based attribute for Position, then
create a derived Hierarchy for the Position parent/child relationships...just wondering if this is a good approach.
Are there other things I should be taking into consideration?  Thanks!

Answer 1

If your Material list document is not excessively long it probably wouldn't be too much overhead to add a few extra columns using the CalculatedColumn action block.  These extra columns, even though the number would be the same for all rows could contain a column for each of your aggregated functions.
Then in your iGrid just set the Column Width for these addtional fields to zero and upon UpdateEvent of the grid you could javascript them from Row number 1 to your desired html elements, etc.