Airframe database + 4

Ok.
Its decided. As mentioned in the last blog:

Death to the hyphen. Long live the hyphen!

That said. Here is what is currently in the mictronics database.
Note, its a CSV, comma separated variables.

It goes something like this;

ADSB hex;    REG:    ICAO type;    mil/civ;    description;    year;    owner

AE1BAB;167926;C30J;10;Lockheed Martin KC-130J Hercules;;;
AE1BEB;07-1468;C30J;10;Lockheed Martin C-130J-30 Hercules;;;

Two examples at random.
One with a hyphen in the reg and one without.
Note also that some airframes records have all the details, some have some bits missing.
That's not important.
Also unimportant is how I have been (ab)using the year and owner fields for ADSC hex and iridium registration data.
That's what's going to change.

Lets break it out for the blog;

ADSB hex: AE1BAB. We all know what this is. My site uses this first.
REG: 167926 or 07-1468. Most know these. Some folks use - some don't.
ICAO Type: C144 4 character type codes. There is a list of them somewhere. tbg does not care.
mil/civ: 10 or 00, but could be 01, or 001, or 0001 or 100 or 1000. Need me to rant about it?
Description: KC-130J Hercules. I used to put this on the website, but got yelled at. (Too much space)
Year: 1969. Most people don't care.
Owner: This used to have the air force / airline in it, but seems to have been cleaned out of the db for some reason. I used to put it on the website tables, but got yelled at. (Takes up too much space).

Ok, now lets look at what I propose to add to that ADSB community maintained database that is just for tbg.airframes.io website:

ADSC hex: AE1165 This is the satcom (ADSC) hex for AE1166 for one example.
reg_nohyp: 020201 is the ADSB reg for the airframe with no hyphen. ie, 02-0201 (internal site use only)
reg_irdm: 03026 is the Iridium reg for AE68B4;10-3026 or A6-RJC for 89641B;CGXBN
reg_irdm_nohyp:  A6RJC for 89641B;CGXBN. So same as reg_irdm, but no hyphen (internal site use only)

Note how I included two Iridium examples regs, for why see this blog rant here...
If I had just put the one in, I'm sure a few people would have said "Hey, you can just drop the - and add a 1 at the front, what's all the fuss?"
So I included the second (non military, but I'm sure its important to someone): 
The ADSB reg is: A6-RJC the Iridium reg is CGXBN.
Another example: ADSB=N78HV, irdm=700-0033. 
Another example: N256GA -> AP-NSH
And on and on it goes.... so the drop the - and add a 1 'rule' does not quite cut it for Iridium....

Do note that I intend to let people put hyphens in searches etc. and I will show the ADSB one everywhere (with or without, ie. what ever the mictronics db has). I just need to remove it everywhere for internal website search and airframe lookup use.
Hence the opening heading 'Death to the hyphen. Long live the hyphen!'
Its like Schrodinger's cat. There is no hyphen till you use it, and then it disappears, but works like its there.

Is that it?

Really? All these blogs for an extra 4 fields? Its taken me longer to talk about it than do it?
Yeah. I guess. In a way. But no, not even close. Its going to be a mega pint of work to add them, build the new database creation code, and put the new fields into use site wide.
The dumpster flames are going to white hot I'm sure.

My MAIN question is, can anyone think of anything else I / we need to add?
What have I missed? Speak up now or forever hold your peace!

I'm only doing this 'rebuild' once.