If we start with ruling out spelling mistakes, we all do them occasionally; we type a double letter, leave out one letter or two, hit the key next to the proper key, mix up g with q, i with l, and whatever. I do it, you do it, we all do it. The good thing is that we also find it, or somebody else do, and then we correct the error --- but we do not mark it unavailable and add the correct instance.
Well, assuming my guild mate is correct, a few resources are spelled one way in inventory and slightly different in the 30k crate. What could cause this? And if it really happens, how should we deal with it?
Personally I do not think that the SWG Devs are that stupid that they have resource names listed in several database tables for different use cases, one table for the 30k kit and another for inventory view, etc. That is just a so horrid idea that even a kicked-out of comp science classes at high school would not dream it up, the common rule is to have names and possibly data in one table each entry with some unique ID. Other tables relates to resources by ID but need not to double the rest of the data.
Causes? What first comes to mind is minor bugs in the GUI or in the communication system so that the data is correct but presentation sometimes go wrong. In that case we can neither trust spelling in the 30k crate nor inventory over the other, who can tell which is bugged? On the other hand, I have never found a resource that is spelled one way in an ISDroid report to be spelled slightly differently in the 30k crate when I lookup the stats. Have you? Possibly the 30k crate is more robust than the GUI

Communication errors. Sure, as far as I know the traffic is first of all compressed (compare WinZip compressed files) and it is encrypted. I have not stumbled over information on how to decompress and decrypt the traffic, perhaps the SOE Devs implemented some home-brewed code for it, then anything can happen which is since long ironed out in open source. So, it is a possibility, yes, but then that would struck also other traffic types and not just resource names and data, so ... not likely.
Locality problems. That is if a particular language has some oddities with letters, digits, time/date, etc., which must be dealt with in the operating system. Yes, this is a more common field for errors than you might think, sometimes slippery mud. Then this error could possibly happen on the less usual localities, hardly US-English or even UK. Perhaps a suspect.
Other than the above I have no idea. Have you seen this? Any ideas? But most of all, how to deal with this so that we keep the SWGCraft database pristine?
/Zimoon