Perhaps the name "Unit Compendium" would be more usefull - I agree that this is not intended to be yet another 'army list'. However this confusion of intent is precisely why it needs to be in a separate folder.
I suggest using a format similar to the NetEA_Army_List_Compendium, but compressing the existing columns slightly to allow the following additional columns
- Source
Typically this will be NetEA where the details are consistent throughout all the different groups.
However, there will be a separate entry for units from E-UK, E-Fr, E-Gdr etc where those groups have different stats, formation sizes or costs.
- Formation size and cost
Typically there is only one entry, though separate entries will provided where appropriate.
- Updates
Again, the list of possible updates is usually consistent, though these will need to be represented by abbreviations.
- Army List
Either "All" to indicate a unit / formation used in all lists of a given race, or an abbreviation of the lists that contain this particular unit / formation
- Status
Several will be needed from "New" indicating something that has just been added, through "Experimental" to "Certified" and "Used". Are there any others?
At present I suggest separate documents for each main Race, effectively mirroring the folders currently in use for Marines, IG, Chaos etc, though obviously this could be provided in a single document. Elsewhere, (probably at the top), there will need to be a preamble regarding the intent of the document, version number date etc together with an index of the various abbreviations used and their meaning.
However, the main issue is one of maintenance (as Dave will attest

). I suggest the individual documents need to updated far more frequently than the NetEA compendium, so ideally they need to be 'public' at least as far as the various champions on this forum are concerned - and by that I also include the key people from NetEA, E-UK, E-Fr etc. However, I also feel that only certain people should "Certify" a given entry (probably just the ERC?) and potentially we might need hidden audit fields for tracking purposes.
So, how can that be achieved in the most 'user-friendly' fashion?
Obviously the best approach to limited authorisation is a database, indeed that would greatly assist other aspects especially including data from different 'sources'. But how practical would this be in the Wiki location for example (if it still exists). One implication is the use of a widely available (cheap / free) tool. Can anyone make recommendations? (I have MS Access loaded, though that may well not be everyone's favourite

)
What other mechanisms can people suggest to make these documents easily maintainable by many people, and indeed is there any synergy with the existing Compendium, E-UK or other stuff (and yes I know that is highly unlikely at the moment - though not entirely out of reach . . .

)